Troubleshoot monitoring and reporting
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager
The following table provides troubleshooting guidance on monitoring and reporting issues.
DPM Administrator Console displays an error for jobs that are in progress and have not completed.
The DPM jobs are still in progress and have not finished running.
While DPM jobs are in progress, DPM continually retries the job until it is finished running. After the job is complete, DPM will display the correct job status.
File synchronization or recovery point creation jobs continue to run, even when DPM is not transferring data.
DPM may be perpetually attempting to cancel the job.
Verify that DPM is not transferring data, and then cancel the job. If the job continues to run, restart the DPM server.
The number of warning on DPM server does not match the number on Operations Manager.
Your DPM server has heavy workflows and is reaching the Private Byte count threshold reached and Handle count threshold reached too quickly, which is resetting the Operations Manager agent.
Increase the threshold for Private Byte count threshold reached and Handle count threshold reached on the Operations Manager Server.
View Jobs not refreshing.
You are monitoring DPM 2010 servers.
Reopen the screen if it has been open for more than 24 hours.
Unable to run consistency check from Protection Groups view.
Replica is consistent.
In the Protection Group view, consistency check will be run on the replica only if it is in an inconsistent state.
E-mail functionality for reports is not working.
You subscribe to five reports for e-mail delivery, but not all reports are delivered.
If you schedule all five reports to be sent at the same time, the memory limitations of SQL Server Reporting Services may prevent some reports from being sent.
When a DPM server is protecting a large number of file servers, we recommend that you stagger the delivery schedule for reports sent by e-mail.
Reports are not received by designated e-mail recipients and DPM does not generate any errors.
This issue is most commonly caused when the security settings of the recipient e-mail address restrict e-mail delivery. This could happen, for example, if the recipient e-mail address is a distribution group whose properties are set to only receive e-mail from authorized senders.
This issue may also occur when:
Depending on the cause of the issue, there are several solutions you can try:
For more information, in Deploying DPM 2010, see Configuring the SMTP Server.
When exporting HTML reports to MHTML, charts do not display correctly.
If you try to export an HTML report to Web Archive (MHTML format) on a DPM server running Windows Server 2003 Service Pack 2 (SP2), the charts on the report will not display.
This is an issue with Internet Explorer, and occurs only the first time you export a report. Subsequent exported reports will display correctly.
When you try to view a DPM report, you see a “Cannot find server” or “DNS error” error message, or the report is not displayed in Internet Explorer.
The proxy server settings in Internet Explorer may not be set correctly.
To display reports in Internet Explorer, the proxy server for local connections needs to be bypassed.
To bypass the proxy server for local connections:
One or more of the DPM report types are missing from the Reporting task area of DPM Administrator Console.
An administrator has manually deleted one or more of the DPM report templates from the DPM computer.
To restore the missing DPM report types, do the following:
DPM does not export reports to MHTML, Excel, or PDF formats.
If both Internet Explorer Enhanced Security and Secure Socket Layer (SSL) options are enabled, DPM cannot export reports to MHTML, Microsoft Excel, or PDF formats.
To export reports to MHTML, Excel, or PDF formats, you must disable Internet Explorer Enhanced Security.
To disable Internet Explorer Enhanced Security:
A report has no data in it when you view it from DPM Administrator Console or in an e-mail attachment.
One of the following problems might have prevented the report from running at the scheduled time:
When a report fails, the report is run again as soon as the DPM computer is back online or at the next regularly scheduled time. This resolves the problem of not being able to view the report from DPM Administrator Console.
To ensure that e-mail subscribers receive the corrected report:
The administrator is always prompted for user credentials to access DPM reports.
DPM Setup automatically adds the name of the DPM computer to the Local Intranet security zone in Internet Explorer to permit access to DPM reports without having to provide additional credentials. If you manually add the name of the DPM computer to the Trusted Sites zone, you will overwrite this default setting, and Internet Explorer will prompt for credentials before granting access to DPM reports.
To restore the default setting, manually remove the DPM computer name from the Trusted Sites zone and add it to the Local Intranet zone.
For more information on Internet Explorer security zones, in the Internet Explorer 6.0 Resource Kit see Security Zones .
When you try to view reports, you receive the following error message:
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Logon failed. (rsLogonFailed) Get Online Help
Logon failure: the user has not been granted the requested logon type at this computer.
The DPMR$<MachineName> account may not have the required user rights.
To resolve this error, you must ensure that the DPMR$<MachineName> account has the Allow log on locally user right.
To assign the Allow log on locally user right to the DPMR$<MachineName> account:
Disk utilization for inactive replicas is not reported correctly in the Disk Utilization Report.
For existing protection groups or file servers, current storage pool details do not display the current information (for example, up to the minute) for replicas that were removed, added, or removed from protection on the day that the report is generated.
Disk utilization for these replicas will be correct in reports generated at least a day after the change is made.
Notification deliveries for reports and alerts fail.
Your notification deliveries will fail if you enter the incorrect user name for authentication on the SMTP server.
To enter the correct user name for authentication, in the Options dialog box, on the SMTP Server tab, in the User name box, type the domain name of the user that appears in the "From" address box. For example, if the user name in the "From" address box is Terry@AdventureWorks.com, in the User name box type <domain name>\Terry.
Logon failure (0x80070569): The user has not been granted the requested logon type at this computer.
This error occurs when your security policy settings prevent the user from logging on using a local user account.
To add a domain user account, perform the following steps: