It is up to the custom action to initialize COM to its liking."īecause the custom action thread which executes "Adobe_ ProcessProperty File" CA doesn't initialize COM explicitly (not creating apartment), the MTA from the main thread has to be used. However, the thread on which a DLL custom action is run is different from the main thread (on which COM is initialized) and COM will not be initialized on it.
"One of the first things that a custom action server does when it is created is to call CoInitializeEx(0, COINIT_ MULTITHREADED).
ADOBE PREMIERE PRO CS4 ERROR 130 3 WINDOWS
This question rang a bell so I dug into some of the emails that have gone across our internal Windows Installer question-n-answer alias and here is the official answer from the Windows Installer team: One part (reuse of existing MTA) is covered by my bug 17902 though CoGetClassObject() is the culprit there.Īs for the other part, I found the following blog containing useful information regarding custom actions and COM: blogs.msdn. Well the custom action thread tries to use MSXML6 COM inproc server and fails because there is no apartment (COM not initialized). Wine: Unhandled page fault on read access to 0x00000000 at address (nil) (thread 0009), starting debugger. Tried to execute Setup.exe for Adobe Photoshop CS4, and I got this output:įixme:console: AttachConsole stub ffffffffįixme:advapi: SetNamedSecurit yInfoW L"MACHINE\ \Software\ \Classes\ \.svg" 4 4 (nil) (nil) 0x1305a8 (nil)įixme:advapi: SetNamedSecurit yInfoW L"MACHINE\ \Software\ \Classes\ \.svgz" 4 4 (nil) (nil) 0x1305a8 (nil)
0 kommentar(er)
