January 17, 2014 at 2:31 am
So since a week or 2 several of the non-essential jobs in our system have been giving the following error:
...The step did not generate any output. The return value was unknown. The process exit code was -1073741502. THe step failed.
I've checked the ssis package(s) run by the job(s),the table(s) and the job(s) themselves.
But I'm not seeing any mistake.
The source is an IBM AS400 server so if anyone ver encountered aznything simelar,any insight might be handy
January 17, 2014 at 2:52 am
Is there anything in the SQL Agent log that might give you a clue?
Regards
Lempster
January 17, 2014 at 3:09 am
'Executed as user ... The step did not generate any output. The return value was unknown. The process exit code was -1073741502. The step failed.'
is the literal error message out of Job history log
The SQL Server Agent log is not showing anything out of the ordinairy.
At first I thought it might have been a connection timeout,but out of all the jobs that get this error none actually run at a time where much happens at either source of destination.
Also some of the jobs succeed at other times of the day,while some just never seem to run properly.
January 17, 2014 at 3:15 am
Similar problem described here:
If convert the error code -1073741502 to its exadecimal equivalent, it will be 0xc0000142.
Error code 0xC0000142(STATUS_DLL_INIT_FAILED) says " {DLL Initialization Failed} Initialization of the dynamic link library has failed.
Check the permissions on the "C:\Program Files\Microsoft SQL Server\110\DTS\Binn" folder where the DTExec.exe is located
January 17, 2014 at 3:24 am
Ok I'll have this checked,so why are they showing an errorcode in decimal but not the hexadecimal number,that would would make it easier to track these things.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply