none
DPM 2012 R2 Upgrade - Scheduled jobs not running RRS feed

  • Question

  • Hi,

    We're having an issue after upgrading to DPM 2012 R2 where the scheduled jobs are not running.

    We're running Server 2012 R2 with SQL Server 2008 R2 SP2.

    Looking at SQL jobs, if we run the job step we get an error.

    Message

    [136] Job 18822c3e-8fe 7-47a2-bb6e-0feccecc2952 reported: The process could not be created for step 1 of job 0xA746B176EAD99943A14A57DAF684829F (reason: %1 is not a valid Win32 application)

    However, if we place quotes around the triggerjob.exe path in the SQL default job step:

    "C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\TriggerJob.exe" 9b30d213-b836-4b9e-97c2-db03c3eb39d7 18822c3e-8fe7-47a2-bb6e-0feccecc2952 server.domainname.com

    It is successful. 

    We've already uninstalled DPM 2012 R2 and re-installed, restored the database and run dpmsync -sync with the same result. We've checked the DCOM Config Launch and Activation Permissions for Microsoft System Center 2012 R2 Data Protection Manager Service and has full access.

    Has anyone else had this issue and been able to resolve it?

    Any help would be greatly appreciated.

    Thursday, December 18, 2014 8:57 PM

Answers

  • Unfortunately that didn't resolve the issue.

    We ended up doing a workaround by using the short name for the location of TriggerJob.exe as it couldn't find the location.. (Kept getting stuck at C:\Program)

    We changed the location in the registry setting HKLM\Software\Microsoft\Microsoft Data Protection Manager\DB\TriggerJobPath to C:\PROGRA~1\MI81C5~1\DPM\DPM\Bin

    This now works.

    • Marked as answer by dallas_77 Wednesday, January 14, 2015 7:39 AM
    Wednesday, January 14, 2015 7:39 AM

All replies

  • Hi,

    The below blog may assist with troubleshooting your issue.

    http://blogs.technet.com/b/dpm/archive/2014/10/08/how-to-troubleshoot-scheduled-backup-job-failures-in-dpm-2012.aspx

    **********************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

     

    Friday, December 19, 2014 12:23 PM
  • Unfortunately that didn't resolve the issue.

    We ended up doing a workaround by using the short name for the location of TriggerJob.exe as it couldn't find the location.. (Kept getting stuck at C:\Program)

    We changed the location in the registry setting HKLM\Software\Microsoft\Microsoft Data Protection Manager\DB\TriggerJobPath to C:\PROGRA~1\MI81C5~1\DPM\DPM\Bin

    This now works.

    • Marked as answer by dallas_77 Wednesday, January 14, 2015 7:39 AM
    Wednesday, January 14, 2015 7:39 AM
  • In my cenario that blog (http://blogs.technet.com/b/dpm/archive/2014/10/08/how-to-troubleshoot-scheduled-backup-job-failures-in-dpm-2012.aspx) didn't solve my problem. My doubt was logon credencials, but both SQL and Agent Services use the same credencials.

    I look for "TriggerJobPath" in the registry, but didn't found. It was curious.

    So, the only solution that i can see is recreate the protection groups. Any more ideas?

    Wednesday, March 21, 2018 5:21 PM
  • I recreated a Protection Group, but Scheduled Jobs didn't run yet. Looks like i really need reinstall DPM.
    Wednesday, March 28, 2018 8:41 PM
  • So, no success yet!

    I reinstalled SCDPM 2012 R2, without keep data, but after reconfigured Protection Groups and our schedules, jobs not running.

    Wednesday, April 4, 2018 7:42 PM