http://bugs.winehq.org/show_bug.cgi?id=5809
------- Additional Comments From focht@gmx.net 2007-16-04 16:24 ------- Hello,
you have to start the msi installer service manually before trying to run msi client on NT based wine configs. For that, use a tool which can call appropriate SCM api. A very handy one is the NT based "sc.exe" (copy it over from windows system32 installation).
The errornous CLSID you see in trace {000C101C-0000-0000-C000-000000000046} is IMsiServer, provided by CoRegisterClassObject which runs in ServiceMainThread .
You have following options:
1. run native msi under winecfg=Win9X -> runs msi as inproc server -> no service used 2. use sc.exe to spawn separate service (out-of-proc ole server) process
To ensure all necessary registry entries are created you can use following options on msiexec.exe binary itself:
/regserver (out-of-proc ole service)(out-of-proc ole service) /regserverca (out-of-proc ole service) /regnoservice (out-of-proc ole server only)
(same applies to /unregxxxxx stuff)
You can run native msiexec installer from commandline using following options:
as client: "msiexec /i <product>.msi /l*v install.log" as service (name = "msiserver"): "msiexec /v" as custom action server: "msiexec.exe -Embedding <some GUID>"
Basically:
1. "wine msiexec /regserver" 2. "wine sc.exe start MsiService" (after that you have msiexec service process running) 3. "wine msiexec /i <blah>.msi /l*v install.log"
If you have problems/encounter bugs, feel free to report back. This stuff probably applies to many native msi installer service related bug reports :)
Regards