Troubleshooting Reporting Issues
Published : September 27, 2005
Table 6.7 provides guidance for troubleshooting issues that may occur when configuring, viewing, exporting, or subscribing to DPM reports.
Table 6.7 General Reporting Issues
Issue |
Details |
---|---|
You subscribe to all five reports for e-mail delivery, but not all reports are delivered. |
When a DPM server is protecting a large number of file servers, you should stagger the delivery schedule for reports sent by e-mail. 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. |
Reports are not received by designated e-mail recipients and no errors are generated by DPM. |
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:
|
When exporting HTML reports to MHTML, charts do not display correctly. |
If a user on a DPM server running Windows Server 2003 SP1, tries to export an HTML report to Web Archive (MHTML format), charts on the report will not be displayed. 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:
|
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 IE 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 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, see the “Security Zones” chapter (https://go.microsoft.com/fwlink/?LinkId=52308) in the Internet Explorer 6.0 Resource Kit. |
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. |
To resolve this error, you must ensure that the DPMReport account has the Allow log on locally user right. To assign the Allow log on locally user right to the DPMReport account:
|
When you select the Reporting task area in DPM Administrator Console, you receive error message 3013: Could not connect to SQL Server Reporting Server because of IIS Connectivity issues |
This can occur when the World Wide Web Publishing Service is stopped or the Default Web Site under this service is disabled. To resolve this error:
|
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 for does not display the current information (i.e. 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. |
You cannot access reports. |
If you install ASP.NET 2.0 on the DPM server after DPM Setup, DPM reporting may not function correctly. To reconfigure Reporting Services to use .NET Framework 1.1:
|
You receive error 812 during DPM setup. Error: Configuration of reports failed. Make sure that Microsoft SQL Server Reporting Services is installed properly and that it is running. ID: 812. In the DpmSetup.log file, the exception text reads: The request failed with HTTP status 404. |
This problem occurs when both SQL Server Reporting Services and Windows SharePoint Services are installed in the same IIS application pool. To resolve this issue, perform one of the following tasks:
-or-
Note The Rsactivate utility referred to in “Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services” is located in the DPM installation path at \Microsoft Data Protection Manager\Prerequisites\MSSQL\Reporting Services\ReportServer\RSReportServer.config. |