Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

Scheduled Job fails with Process Exit Code -1073741819 Expand / Collapse
Author
Message
Posted Thursday, August 5, 2010 9:27 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 24, 2014 8:11 AM
Points: 198, Visits: 141
It has been a long time since I dealt with this issue in our environment, but it seems like changing the job to a SQL step using xp_cmdshell made it work at the time. Most frustrating thing is the inconsistency!


Post #964389
Posted Friday, August 6, 2010 2:43 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, August 22, 2012 3:32 AM
Points: 13, Visits: 106
...thanks for the suggestion, I'll give it a go...

S
Post #964904
Posted Wednesday, September 1, 2010 7:36 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, August 22, 2012 3:32 AM
Points: 13, Visits: 106
...hhhm, I was happy it was working until I realised it wasn't returning a return code!

When run as a cmdexec, the step either returns 1 or 0. As xp_cmdshell it always returns null?!?

Has anyone experienced this?

S
Post #978757
Posted Wednesday, March 30, 2011 11:54 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, January 10, 2014 4:09 AM
Points: 173, Visits: 101
I m experiencing the same issue.
Running a batch file, but it is not..
"The step did not generate any output. Process Exit Code 1. The step failed."
Command Line : cmd /c "call D:\StaticBookDataRefresh\SummitBookRefreshFSA.bat >> D:\StaticBookDataRefresh\pm_%date:/=-%.log 2>&1"
Post #1086623
Posted Wednesday, July 16, 2014 12:26 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 12:26 PM
Points: 1, Visits: 14
I work in SQL SSMS 2012. We maintain a primary SQL server 2008 R2 for all the SQL agent jobs.

Many job steps include CMDEXE calling .BAT files.

All run as the same Domain Admin account to ensure access to all network locations.

On occasion, one of these jobs up and fails after having run successfully for months and years.

I just spent hours messing with this myself because there was no explanation, no change in credentials, no change to our network, etc., and no change to the code or the job steps, etc.

One of these jobs in particular, the .BAT script is "IF the file exists, do these things, ELSE GOTO END".

So I decided to handle the ELSE another way instead of simply exiting the program. I changed ELSE to "run this .vbs that emails a failure message" and VOILA, for some reason the SQL job runs perfectly fine now. I changed NOTHING else.

Does Microsoft no longer like ELSE statements that simply exit a program? What happened to just IF something and nothing else? Not sure why that worked exactly, but really nothing else changed and the SQL Job Agent worked the very next several times I tested it.



Post #1593237
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse