[Bug 30439] Lexware 2012 products update manager "LxUpdateManager" fails due to "LxWebAccess" COM server requiring WMI
wine-bugs at winehq.org
wine-bugs at winehq.org
Mon Apr 16 15:16:44 CDT 2012
http://bugs.winehq.org/show_bug.cgi?id=30439
Anastasius Focht <focht at gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |focht at gmx.net
Depends on| |20651
Summary|Lexware Update Manager |Lexware 2012 products
|unable to connect |update manager
| |"LxUpdateManager" fails due
| |to "LxWebAccess" COM server
| |requiring WMI
Ever Confirmed|0 |1
--- Comment #2 from Anastasius Focht <focht at gmx.net> 2012-04-16 15:16:44 CDT ---
Hello,
--- quote ---
Which is a CEventSystem and completely not implemented in Wine.
--- quote ---
MSDN documentation:
http://msdn.microsoft.com/en-us/library/cc226283%28v=prot.10%29.aspx (Component
Object Model Plus (COM+) Event System Protocol Specification)
http://msdn.microsoft.com/en-us/library/cc226297%28v=prot.10%29.aspx (Standards
Assignments)
I've got hands on a similar product from same company, "Lexware Financial
Office Pro 2012" which seems to use same update mechanism.
The updater service is implemented as local COM server, instantiated by
LxUpdateManager.exe:
--- snip ---
0009:trace:ole:create_server activating local server L"\"C:\\Program
Files\\Common Files\\Lexware\\LxWebAccess\\LxWebAccess.exe\" -Embedding" for
{4c785741-7f95-4309-b372-41bf7cd4804c}
...
--- snip ---
The COM server creates a log file "LxWebAccess.log" which gives some hints:
--- snip ---
$ pwd
/home/focht/.wine/drive_c/users/focht/Local Settings/Application
Data/Lexware/LxWebAccess/Konfiguration
$ ls
LxWebAccess.log
--- snip ---
--- snip LxWebAccess.log ---
...
[2012-04-16 21:17:50.0846] pID 62 tID 71 LxWebAccess version I80.00.0027
starting up
[2012-04-16 21:17:50.0859] pID 62 tID 71 Warning in method
[CLxWebAccessXMLConfigManager::LoadConfiguration]. Message: Cannot open file.
[2012-04-16 21:17:50.0864] pID 62 tID 71 Plugins found:
[2012-04-16 21:17:51.0062] pID 62 tID 71 Etwork Diagnostic Tool
?0.?"
[2012-04-16 21:17:51.0380] pID 62 tID 71 Error in method
[CLxSensNetworkManager::RegisterSubscriptions]. Message: Failed to create
EventSystem object Error code: 80040154.
[2012-04-16 21:17:51.0384] pID 62 tID 71 Error in method
[CLxSensNetworkManager::Init]. Message: RegisterSubscriptions failed.
[2012-04-16 21:17:51.0387] pID 62 tID 71 Error in method
[CLxWebAccessObject::FinalConstruct]. Message:
CLxSensNetworkManager::getInstance()->Init() failed.
[2012-04-16 21:17:51.0392] pID 62 tID 71 Error in method
[CLxWMINetworkManager::PrepareWMI]. Message: pLoc->ConnectServer failed. Error
code: 80041001.
[2012-04-16 21:17:51.0396] pID 62 tID 71 Error in method
[CLxWMINetworkManager::Init]. Message: PrepareWMI or RegisterEvents failed.
[2012-04-16 21:17:51.0399] pID 62 tID 71 Error in method
[CLxWebAccessObject::FinalConstruct]. Message:
CLxWMINetworkManager::getInstance()->Init() failed.
...
--- snip ---
Failure to instanciate COM server for CLSID_EventSystem seems not critical, WMI
is used as "backup" strategy.
This obviously fails due to bug 20651 , setting dependency.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the wine-bugs
mailing list