This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Custom action fails only on XP
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 09, 2010
03:18 PM
Custom action fails only on XP
I have a custom action that works fine on Vista and Windows 7. The install fails when it tries to invoke it on XP. The custom action code is not being entered at all, I don't think. The first line of code is a log msg, which isn't showing up.
The CA is in the Exec Install sequence, and is Immediate Execution.
Here's a snippet of the install log:
Action ended 14:38:44: MigrateFeatureStates. Return value 0.
MSI (s) (40:D0) [14:38:44:290]: Doing action: MyAction
Action 14:38:44: MyAction.
Action start 14:38:44: MyAction.
MSI (s) (40:D8) [14:38:44:306]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI17.tmp, Entrypoint: MyActionFunc
MSI (s) (40:DC) [14:38:44:306]: Generating random cookie.
MSI (s) (40:DC) [14:38:44:322]: Created Custom Action Server with PID 3552 (0xDE0).
MSI (s) (40:84) [14:38:44:368]: Running as a service.
MSI (s) (40:84) [14:38:44:368]: Hello, I'm your 32bit Impersonated custom action server.
Action ended 14:38:44: MyAction. Return value 3.
Action ended 14:38:44: INSTALL. Return value 3.
My log from Win 7 shows the same lines till:
Action start 14:59:52: MyAction.
MSI (s) (FC:3C) [14:59:52:278]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCD2.tmp, Entrypoint: MyActionFunc
MSI (s) (FC:40) [14:59:52:278]: Generating random cookie.
MSI (s) (FC:40) [14:59:52:279]: Created Custom Action Server with PID 5956 (0x1744).
MSI (s) (FC:08) [14:59:52:302]: Running as a service.
MSI (s) (FC:08) [14:59:52:303]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (FC!5C) [14:59:52:836]: Creating MSIHANDLE (2) of type 790531 for thread 5980
-- QCICA Logging -- MyActionFunc - entry
Any ideas?
Thanks,
Tim
The CA is in the Exec Install sequence, and is Immediate Execution.
Here's a snippet of the install log:
Action ended 14:38:44: MigrateFeatureStates. Return value 0.
MSI (s) (40:D0) [14:38:44:290]: Doing action: MyAction
Action 14:38:44: MyAction.
Action start 14:38:44: MyAction.
MSI (s) (40:D8) [14:38:44:306]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI17.tmp, Entrypoint: MyActionFunc
MSI (s) (40:DC) [14:38:44:306]: Generating random cookie.
MSI (s) (40:DC) [14:38:44:322]: Created Custom Action Server with PID 3552 (0xDE0).
MSI (s) (40:84) [14:38:44:368]: Running as a service.
MSI (s) (40:84) [14:38:44:368]: Hello, I'm your 32bit Impersonated custom action server.
Action ended 14:38:44: MyAction. Return value 3.
Action ended 14:38:44: INSTALL. Return value 3.
My log from Win 7 shows the same lines till:
Action start 14:59:52: MyAction.
MSI (s) (FC:3C) [14:59:52:278]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCD2.tmp, Entrypoint: MyActionFunc
MSI (s) (FC:40) [14:59:52:278]: Generating random cookie.
MSI (s) (FC:40) [14:59:52:279]: Created Custom Action Server with PID 5956 (0x1744).
MSI (s) (FC:08) [14:59:52:302]: Running as a service.
MSI (s) (FC:08) [14:59:52:303]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (FC!5C) [14:59:52:836]: Creating MSIHANDLE (2) of type 790531 for thread 5980
-- QCICA Logging -- MyActionFunc - entry
Any ideas?
Thanks,
Tim
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 09, 2010
04:54 PM
Hi There,
Platform specific issues are usually due to missing dependencies.
I'd copy your *.dll to one of the problematic XP machines and have a look with Depends.exe. Or, just switch to statically linking the custom action.
Platform specific issues are usually due to missing dependencies.
I'd copy your *.dll to one of the problematic XP machines and have a look with Depends.exe. Or, just switch to statically linking the custom action.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)