April 8, 2004 at 8:49 am
Hello,
I had a strange problem yesterday. All of a sudden most of my sql jobs started failing. Few of the jobs generated this message when I looked at the job history.
The step did not generate any output. Process Exit Code 128.
There were no message in SQL server Logs. It didn't generate any output file for these jobs.
I noticed that all the jobs that had direct query in their step ran successfully. But one calling other application like command line, or SQLmaint or DTS or ISQL just failed in few seconds.
When I looked windows event log, I saw message such as..
Application popup: cmd.exe - Application Error : The application failed to initialize properly
It couldn't start any of the application. I restarted SQL agent- didn't help.
I had to restart the server. And everything ran just fine.
Does anyone know what could cause this? I am really annoyed by this unexpected behavior.
Thanks.
April 8, 2004 at 11:41 am
Never seen this. Is is SQL 2000, SP3a?
April 8, 2004 at 12:02 pm
It's SQL 2000+SP3+MSO3-031 Hotfix. I couldn't find anything anywhere on this.
Thanks.
April 8, 2004 at 1:03 pm
Kind of dumb But did any Permissions change on the server or domain.
April 9, 2004 at 12:36 am
- did you see a popup window at serverside "user32.dll failed to initialise..." ? Check KB184802
In that case, sqlagent will wait for a "ok" reply to that popup, so it freezes unless you have a person watching the server constantly at the console.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
April 9, 2004 at 11:08 am
Thanks for KB, alzdba. I don't think Applications were waiting for response at that point, they were just failing in fraction of seconds.
April 9, 2004 at 12:30 pm
Hai all i have different question....
We have a sqlserver box and now we are moving all the databases to different server/box which will have different IP address etc.
What all the changes do we need to make and where do we do...at system level and database level, users are connecting through web.
We are having sqlserver 2000.
Please provide me with info .....
Thanks
krishna
April 9, 2004 at 12:30 pm
Hai,
We have a sqlserver box and now we are moving all the databases to different server/box which will have different IP address etc.
What all the changes do we need to make and where do we do...at system level and database level, users are connecting through web.
We are having sqlserver 2000.
Please provide me with info .....
Thanks
krishna
April 9, 2004 at 1:44 pm
All the databases meaning master, model, msdb + user dbs?
April 16, 2004 at 10:16 am
One possibility for the jobs failing, if you have directed results to an output file and that output location is no longer valid or the permission on that location have changed you will get the results you mention.
I found this out when I moved my jobs to a new server and the old output file location no longer was accessible from the new machine.
November 18, 2004 at 8:26 am
Hiya, There doesnt seem to have been an answer to this problem. I am getting the same problem with a scheduled job that is calling a .bat file - I get process exit code 128 with no other explanation. It fails after only 1 second.
Does anybody know what would cause this?
Thanks
Wendy
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply