kinook
01-19-2007, 09:13 AM
InstallShield sometimes returns this spurious exit code on (apparent) success (at least since v. 9: http://www.kinook.com/Forum/showthread.php?threadid=438). To cause VBP to ignore that exit code, add a vbld_StepDone script event like this to the InstallShield step (VBScript, requires Visual Build Professional 6 or later):
Sub vbld_StepDone()
If CLng(Application.ExpandMacros("%RUNPROGRAM_EXITCODE%")) = -1073741819 Then
Step.BuildStatus = vbldStepStatSucceeded
End If
End Sub
You may wish to open a support incident with InstallShield support to fix IS so that it doesn't return a non-zero exit code when compilation succeeds. An exit code of -1073741819 decimal corresponds to C00000005 hex (access violation).
To reproduce the problem outside of VBP:
1) Check the 'Log command-line...' checkbox on the Options tab of the InstallShield action
2) Rebuild the step
3) Using Notepad or a text editor, create a batch file with the ISCmdBld.exe command-line from the build log on the first line, followed by
echo %errorlevel%
on the second line, and run the batch file at a Command Prompt.
Sub vbld_StepDone()
If CLng(Application.ExpandMacros("%RUNPROGRAM_EXITCODE%")) = -1073741819 Then
Step.BuildStatus = vbldStepStatSucceeded
End If
End Sub
You may wish to open a support incident with InstallShield support to fix IS so that it doesn't return a non-zero exit code when compilation succeeds. An exit code of -1073741819 decimal corresponds to C00000005 hex (access violation).
To reproduce the problem outside of VBP:
1) Check the 'Log command-line...' checkbox on the Options tab of the InstallShield action
2) Rebuild the step
3) Using Notepad or a text editor, create a batch file with the ISCmdBld.exe command-line from the build log on the first line, followed by
echo %errorlevel%
on the second line, and run the batch file at a Command Prompt.