Failed //**End Closing Marker

Content Authoring
21

I have mix feeling with the Software distribution wizard

22

Hello, I am observing the same behavior on my software deployments (spbs)…I did remove the marker but still I get the status completed but exitcode 1.

The log in the file reads:
At 10:11:30 +0000 - actionsite xxx
Command succeeded parameter “returnCode” = “1” (action:6144)
Command succeeded (1) exit {parameter “returnCode”} (action:6144)
At 10:11:30 +0000 -
ActionLogMessage: (action:6144) ending action

Any ideas?

23

Returncode comes from the package you are installing, not from Bigfix itself. You’ll have to look at why your setup command returned a failure code.

24

Hello, I am not sure as the package installs OK (it deploys the two files) in the correct place and has nothing else to do. also we use the same spb with other tool (TPM) and it works fine and not exit error is reported

25

Hello, Just to keep you posted. The IBM support team requested to change all the spbs

Before
echo Return code: %SWDExitCode% >> "{parameter “logFolder”}{parameter “logFile”}"
echo. >> "{parameter “logFolder”}{parameter “logFile”}"
exit %SWDExitCode%
end
waithidden cmd /C “{parameter “baseFolder”}wdlssp.exe” > “{pathname of parent folder of client & “\SIE”}\software.cfg”

After
echo Return code: %SWDExitCode% >> "{parameter “logFolder”}{parameter “logFile”}"
echo. >> "{parameter “logFolder”}{parameter “logFile”}"
wdlssp.exe > "{pathname of parent folder of client & “\SIE”}\software.cfg"
exit %SWDExitCode%
end

Once that change was done, the SPB status is completed and the exit value is 0

IMB also advised that developers would be contacted in order to modify the code.

I hope it helps someone.

26

Hello,

We are facing Same issue after upgrading 9.2.7 to .9.5.8. Action Status says Completed with Exit Code 0 but Action info showing Failed //**End Closing Marker at the End of Action info. Same screen as AlexaVon Tess shared.

We are seeing same issue for about all actions…

27

I did try above changes but getting same error.