http://bugs.winehq.org/show_bug.cgi?id=7624
dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|wine-ole |wine-msi
------- Additional Comments From dank@kegel.com 2007-04-03 01:03 ------- Hmm, using native dcom didn't fix it. Maybe it's an MSI problem. The +relay log of the app failing with native DCOM shows the custom action doing the following repeatedly:
0012:Call kernel32.TlsGetValue(0000000b) ret=00c06219 0012:Ret kernel32.TlsGetValue() retval=7ee52878 ret=00c06219 0012:Call kernel32.TlsGetValue(0000000b) ret=00c06362 0012:Ret kernel32.TlsGetValue() retval=7ee52878 ret=00c06362 0012:Call kernel32.TlsGetValue(0000000c) ret=00c06364 0012:Ret kernel32.TlsGetValue() retval=00c300f8 ret=00c06364 0012:Call kernel32.SetLastError(00000000) ret=00c063bf 0012:Ret kernel32.SetLastError() retval=00000000 ret=00c063bf 0012:Call kernel32.GetLastError() ret=00c06349 0012:Ret kernel32.GetLastError() retval=00000000 ret=00c06349
Then after a while it seems to give up and raise an exception: 0012:Call kernel32.RaiseException(e06d7363,00000001,00000003,7d46c8dc) ret=00c01a11