SD Job fails with error - Exit code 255 [SDM228001]
search cancel

SD Job fails with error - Exit code 255 [SDM228001]

book

Article ID: 8498

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

A SD Job which executes a command batch fails with error :

Exit code 255 indicates possible error [SDM228001]

 

 

 

Environment

Client Automation - All versions

Cause

A .bat or .cmd file could generate an exit code 255 if it contains a line like this :

program1.exe | program2.exe

and program1.exe could not be executed successfully (it could not be found or it fails).

Example :

reg.exe query "HKLM\Software\ComputerAssociates\Unicenter ITRM\InstalledFeatures" /v "Agent" 2>NUL | find /I "14.0.1000" > NULL

If reg.exe is not found, script exits with exit code 255

Resolution

Check that executable is working fine on target machine and make sure that executable could be found in a path set in PATH variable.

SD Job is executed under Local System Account and in some configuration, variable PATH may not contain some directories like %systemRoot% and %SystemRoot%\system32

If the path of executable is not in PATH variable in Local System environment, put the full path in command line :

fullpath/program1.exe | program2.exe

 

Example :

%Systemroot%\system32\reg.exe query "HKLM\Software\ComputerAssociates\Unicenter ITRM\InstalledFeatures" /v "Agent" 2>NUL | find /I "14.0.1000" > NUL

 

Another method :

Check if reg.exe could be found and if it could not be found add %SystemRoot%;%SystemRoot%\system32 and PATH variable :

reg.exe /? > nul 2>&1

IF ERRORLEVEL 9009 set PATH=%SystemRoot%;%SystemRoot%\system32;%PATH%