Wednesday, April 18, 2012 1:39 PM
I upgraded to DPM 2012 from DPM 2010. Everything works great except when I try to subscribe to a report on a schedule I get the following error.
An error occurred causing the reporting job on vault.pvrhs.org to fail. The system files may be corrupt.
Retry the reporting task. If the problem persists, repair your DPM installation using the steps described in the System Center 2012 DPM Deployment Guide.
The reports actually run fine on demand. I also email notifications work well. I also reinstalled DPM 2012 and it I still get this error. This looks like a bug. Anyone else seeing this?
Monday, April 23, 2012 1:54 PMI am having the same issue did you get it resolved?
Tuesday, July 17, 2012 12:45 PMHave you found a resolution to this issue? I'm having the same problem.
Monday, July 23, 2012 3:32 PMHello,
look into your new report server config file.
c:\Program Files\Microsoft DPM\SQL\MSRS10_50.MSDPM2012\Reporting Services\ReportServer\rsreportserver.config
look for the SMTP entry. You should find your SMTPserver, Port and From. it should look like this:
In my case it helped.
- Edited by Rudi.Demarini Monday, July 23, 2012 3:34 PM
Wednesday, August 08, 2012 4:54 AM
I came across the same problem when we implement DPM 2012 and I found the resoluton. When we install DPM it creates seprate SQL reporting instance which needs to be configured under SMTP settings. You need to do the following steps
1. Open SQL Server reporting Manager
2. Under Reporting Services Configuration Connection windows, CHange Report Server Instance to MSDPM2012
3. On the left menu select E-mail Settings
Now put your SMTP setting here and DPM reporting emails will work.
- Proposed As Answer by -IK Wednesday, August 08, 2012 4:55 AM
Friday, May 17, 2013 10:19 AM
I'm also having this issue. I have tried the above and this doesn't work. I have also 'repaired' the installation by uninstalling and re-installing DPM, re-importing and syncing the database using dpmsync -sync.
Can't seem to find any other suggestions to help.
Using DPM 2012 SP1 rollup 2.
Anyone got any other ideas?