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
- :
- Compatibility issue with SCCM 2007
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
Sep 04, 2013
10:35 AM
Compatibility issue with SCCM 2007
Hi everyone,
I use the version Premier 2013, I have made a function in InstallScript that I have inserted it in Custom Actions in "Install Exec Sequence" after AppSearch.
When I generate a setup.exe and I execute it on my PC, it works fine.
When we launch installation with SCCM 2007 (in local system account), an error message has written in logfile and the installation has cancelled.
The message : "CustomAction FunctionName returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)."
Note 1: If I put the same function in the "Install UI Sequence" it works fine
Note 2: In Installshield 2011, the same function in "Install Exec Sequence" worked fine
Could you help me please to correct this problem ?
I use the version Premier 2013, I have made a function in InstallScript that I have inserted it in Custom Actions in "Install Exec Sequence" after AppSearch.
When I generate a setup.exe and I execute it on my PC, it works fine.
When we launch installation with SCCM 2007 (in local system account), an error message has written in logfile and the installation has cancelled.
The message : "CustomAction FunctionName returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)."
Note 1: If I put the same function in the "Install UI Sequence" it works fine
Note 2: In Installshield 2011, the same function in "Install Exec Sequence" worked fine
Could you help me please to correct this problem ?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 06, 2013
12:28 PM
Please compare your scenario to the information posted in the following thread:
Custom Actions fail with Error 3 on Wnidows Core OS
Custom Actions fail with Error 3 on Wnidows Core OS