Wednesday, April 25, 2012 2:09 AM
i can create a recovery point manually but everytime it tries to sync i get this erro rin the logs
SQL Server Scheduled Job '0c0b071c-4f76-4661-bee7-0c5f8b3fee5f' (0xDB29DF779C317A4E91C4CD5F510C1255) - Status: Failed - Invoked on: 2012-04-24 21:00:00 - Message: The job failed. The Job was invoked by Schedule 247 (Schedule 1). The last step to run was step 1 (Default JobStep).
Wednesday, April 25, 2012 6:38 AMModerator
Restart your SQL agent and see if that will solve your problem. Please report back regarding your progress.
Check out my DPM blog @ http://robertanddpm.blogspot.com
Wednesday, April 25, 2012 1:35 PM
Thanks for the reply, i have tried that with no luck.
Since this post i have uninstalled DPM 2012 and sql, re-installed , restored the database, and come full circle to the same error.
This error comes up on any recovery point that is not manually iniated, not just SQL.
I have also tried creating new protection groups , same issue.
- Edited by Jeramy_T Wednesday, April 25, 2012 1:35 PM
Wednesday, April 25, 2012 3:28 PMwell after the re-install, i did not install SP1 for sql (for some reason this is not included in the DPM release).after installing it this appears to have cleared up the error in the event logs. Ill have to wait till this evening to see if everything is fixed when the backups run, but so far so good.
- Edited by Jeramy_T Wednesday, April 25, 2012 3:28 PM
Wednesday, April 25, 2012 3:33 PM
of course i spoke too soon
SQL Server Scheduled Job '30a117f3-4b94-4eb1-98ed-8cba0569715e' (0xDA17370BC3C51547B5E6B926BA0E7FB1) - Status: Failed - Invoked on: 2012-04-25 10:30:00 - Message: The job failed. The Job was invoked by Schedule 12 (Schedule 1). The last step to run was step 1 (Default JobStep).
Wednesday, April 25, 2012 4:35 PM
so this appears to be one of the failing commands from the sql agent jobs:
C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin\TriggerJob.exe 5e76a2ab-4957-4428-a994-d55634f6aeca 30a117f3-4b94-4eb1-98ed-8cba0569715e DPMserver.domain
im not sure where to dig after this for clues.
Wednesday, April 25, 2012 9:28 PM
Monday, June 04, 2012 7:37 PM
On my case, restart SQL server agent worked. Try see if that will solve your problem
- Edited by hagere Monday, June 04, 2012 7:37 PM