Database Adminsitrator - by Lisa Hess

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 778668 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/6/2013 8:46:57 AM
Access Restriction Public


SQL SERVER 2012 - SSMS - After modifying and saving a step in an Agent job, I got the following error:
Executed as user: <username>. The process could not be created for step 2 of job 0x32F9AADA510072498BE0DE5962827EED (reason: The system cannot find the file specified).  The step failed.

The job was edited in SSMS and saved.  The edit was a new pathname for the backup job.  The pathname was copied (ctrl-c) from the target server and pasted into the job.  When I got the error I tested the copied pathname by logging into the server with the login and tested it. The server could see the pathname.  I was able to make the changes by scripting out the job, editing the script, renaming the old job and re-running the modified script in SSMS.  The job ran successfully.  I also tested this by copying my correctly running line with my new (and correct) pathname, saving and running the job, starting with the step. The job failed.  With this test there were basically no changes to the text but the job should have run.
Sign in to post a comment.
Posted by Microsoft on 3/20/2013 at 6:56 PM

We took a look at this bug along with several others recently.
Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future. However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

Thanks for writing in to Microsoft.
Alex Grach [MSFT]
Posted by Microsoft on 2/21/2013 at 10:28 AM
Thank you for reporting this issue, we can't repro this issue on our side, to investigate this issue father we will need SQL Agent logs from your server. Can
you please attach SQL Agent logs to this defect?