• Article

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.

Jobs

Issue Possible Cause Resolution
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.

Monitoring

Issue Possible Cause Resolution
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. Important: If you have multiple Operations Manager Servers monitoring a DPM server, you must increase the threshold on all the management servers.
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.

Reporting

Issue Possible cause Resolution
E-mail functionality for reports is not working.
  1. The Reporting Services Service Account should be changed to run under a domain account.

     
    1. Open Reporting Service Configuration Manager from Start Menu->SQL Server 2008->Configuration Tools.
    2. Select the service account to be a domain account having permissions to send mail from SMTP server.
  2. Set the SMTP settings from the DPM Administrator Console or the Reporting Service Configuration Manager.

     
    1. Enter the SMTP server as SMTPHost.
    2. Ensure that the account is the same as the service account.
  3. Set the SQL Service to run under any domain account from SQL Server Configuration Manager
  4. Open reporting configuration file. By default it will be at C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPM2010\Reporting Services\ReportServer\rsreportserver.config. Change the SMTP Authenticate tab to 2.
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:

- The e-mail address of the recipient is not valid.
- The From address for e-mail messages on the SMTP Server tab is an invalid or unmonitored e-mail address.		 Depending on the cause of the issue, there are several solutions you can try:

- Verify that the e-mail addresses used for subscribing to reports are valid.
- Verify that the security settings on the e-mail alias or distribution group do not restrict e-mail notifications from being delivered to the intended addressee(s).
- Verify that the From address, which is specified on the SMTP Server tab for use in e-mail messages, contains a valid e-mail address.

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:

1. In Internet Explorer, on the Tools menu, click Internet Options.
2. In the Internet Options dialog box, on the Connections tab, click LAN Settings.
3. In the LAN Settings dialog box, ensure that the correct proxy server name is entered and the Bypass proxy server for local connections check box is selected.
4. If the proxy server setting is correct but you cannot select the Bypass proxy server for local connection check box because of company policy, then select Advanced Options and add Http://DPM <server name> to Exceptions.
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:

1. Ensure that no DPM jobs are running.
2. Close DPM Administrator Console.
3. In Add or Remove Programs, uninstall DPM with the Retain data option enabled. If you do not enable the Retain data option, your existing data protection configuration will be deleted, including the protection schedule, replicas, and shadow copies.
4. After uninstallation has completed successfully, reinstall DPM.
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:

1. In Add or Remove Programs, click Add/Remove Windows Components.
2. In the Windows Components Wizard dialog box, clear the Internet Enhanced Security Configurations check box.
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:

- Reporting could not connect to the DPM database.
- The DPM computer was down for maintenance.
- The DPM computer was being restarted.		 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:

1. Select the report type in the Reporting task area of DPM Administrator Console.
2. In the Actions pane, click Schedule.
3. In the Frequency drop-down list, click Once.
4. In the Date and Time drop-down lists, select the next available schedule.
5. After the "run once" report is generated, it will be sent to all subscribers. After the report has been successfully sent, set the reports back to their regular schedules.
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:

1. In Administrative Tools, open Local Security Policy.
2. Under Security Settings, expand Local Policies, and then click User Rights Management.
3. In the details pane, right-click Allow log on locally, and then right-click Properties.
4. In the Allow log on locally Properties dialog box, click Add User or Group.
5. In the Select Users, Computers, or Groups dialog box, click Locations, click the name of the DPM server, and then click OK.
6. In the Select Users, Computers, or Groups dialog box, enter DPMReport, and then click OK.
7. In the Allow log on locally Properties dialog box, click OK.
8. In the details pane, right-click Deny log on locally, and then right-click Properties.
9. If the DPMR$<MachineName> account is listed, select DPMReport, and then click Remove.
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:

1. Remove the DPMR$DPMMACHINENAME account from the DPMDBReaders$DPMMACHINENAME group.
2. Delete the DPMR$DPMMACHINENAME account.
3. Add a domain user account (not an administrator account) to the DPMDBReaders$DPMMACHINENAME group.
4. Perform the following steps to modify the DPMReporterDataSource account to use this domain user account.
For more information about modifying the Report Manager, see Data Sources Properties Page (Report Manager).
5. Edit the Allow log on locally Group Policy setting and add the domain user account.