January 24, 2008 at 3:06 pm
Hi,
Any jobs which runs in the command executable fails and when looking into the job history the message is "Process Exit Code 128. The step failed."
Please assist.
January 27, 2008 at 9:41 pm
Exit code 128 is a quite general code. We need more information to tell what caused this error, such what program you ran in this step.
Here is a link telling us one of possible reasons for this exit code.
Hopefully, it helps.
January 27, 2008 at 10:09 pm
Thanks for the reply. We were callinga exe through the comman line which was causing the error.
When we tried to execute the exe file directly and was getting error so concluding that execuatable file error is shown as exit code 128 in the job history.
January 29, 2008 at 10:14 am
I forgot to include the link in the previous post. Here is it.
February 22, 2008 at 1:00 pm
We encountered the same error code "Exit Code 128" on SQL Server 2005 and were faced with issues pertaining to the children processes invoked by the called EXE.
We had the following command defined for our DTS Step:
c:\mypath\myexe.exe parameter1
After many debugging steps on our custom EXE, we tried a very simple change:
start c:\mypath\myexe.exe parameter1
This resolved our issue immediately and all child processes launched by our main EXE worked correctly.
Hope this helps.
🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply