Author |
Topic |
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2011-07-19 : 10:12:51
|
Hey everyone, I'd love some information on why my backup on a specific job with multiple DB backups is failing. There are 3 steps to this backup job of which the 2 first steps work fine then it gets to the 3rd step (backing up our Report Server DB). Then is fails with the following logged message."Job Nightly Backups reported: The process could not be created for step 3 of job 0x27A7D328A2A39C4C92F5FB29C3434EA3 (reason: 2)"I can't for the life of me, figure out what reason: 2 is. Can anyone shed any light or clarify why I might be getting this message?Steve |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-07-19 : 10:18:37
|
What do you see in eventvwr?How is your job performing the backup? |
 |
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2011-07-19 : 10:30:59
|
SQL Server Scheduled Job 'ReportServerDB_Test' (0xEB7AFDFA4B29AA4AB83557EB7376A114) - Status: Failed - Invoked on: 2011-07-19 08:31:46 - Message: The job failed. The Job was invoked by User domain/user. The last step to run was step 1 (ReportServer DB_Backup). It is run via CmdExec (batch file).Realized it wasn't spitting out the failure to the EViewer, it was initially only showing successes. Perhaps it's a permissions issue?Steve |
 |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-07-19 : 10:46:26
|
Could be. Or a disk space issue?If the backup is over the network, could be a network issue.Are you executing a T-SQL Backup command in the batch file?What happens if you manually run the backup (using T-SQL Backup command)?Just re-read your initial post. "Process could not be created" is usually permission issue opening Cmd process. |
 |
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2011-07-19 : 10:49:26
|
Backup is local, space isn't a problem. Sorry as mentioned before it's running as CmdExec, not T-SQL script.The backup runs fine directly executing the batch file. Perhaps the Local System Account (<----SQL Server Agent Service is running as) doesn't have a the proper permissions to backup this DB? It has no problem with the other 2 steps in the job.Steve |
 |
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2011-07-19 : 10:53:56
|
I can't seem to change the 'Run as:' field as it is preset to SQL Server Agent Service Account, and even if I change the owner of the job, it still errors as the same invoked user as before.Steve |
 |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-07-19 : 10:58:26
|
What are the contents of the file? |
 |
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2011-07-19 : 11:30:10
|
osql -E -S EquityReport.domain.ca -od:\MSSQL.1\mssql\LOGS\ReportServer.log -Q"backup database ReportServer to ReportServer with INIT"Steve |
 |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-07-19 : 11:43:04
|
The backup device ReportServer exists?Try changing it to go directly to disk without the device:for example...backup database ReportServer to DISK = 'D:\mssql\backup\ReportServer.bak' with INIT |
 |
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2011-07-19 : 11:57:54
|
Still failing for the same exact reason.Steve |
 |
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-07-19 : 12:28:48
|
Sure SQL Agent is running as local system?Is this win2k8 server?I'd change the file to a T-SQL Script in any event.Read this? |
 |
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2011-07-19 : 14:47:39
|
It is running as Local System and like I said the other 2 backups using the SAME EXACT batch have no issues.I also mean to point out that the -Q in the script specifies it to run it as a T-SQL statement.Steve |
 |
|
|