Export (0) Print
Expand All

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:

  • 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, see “How to configure the SMTP server” (http://go.microsoft.com/fwlink/?linkid=51908) in DPM Help.

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:

  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:

  1. Ensure that there are no DPM jobs currently 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 IE 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 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 rebooted.

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 dropdown list, click Once.

  4. In the Date and Time dropdown 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 schedule.

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 (http://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:

  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 DPMReport account is listed, select DPMReport and then click Remove.

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:

  1. In the Services console, ensure that the status of World Wide Web Publishing Service is Started. If the service is not started, right-click the service and then click Start.

  2. If the World Wide Web Publishing Service status is Started, or if starting the service does not resolve the error, check the status of the Default Web site.

    To check the status of the Default Web site

    1. In Administrative Tools, open Internet Information Services (IIS) Manager.

    2. In the navigation pane, click Web Sites.

    3. In the details pane, ensure that the State for the Default Web Site is Running. If not, right-click Default Web Site, and then click Start.

    4. Close and then re-open DPM Administrator Console.

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:

  1. Open a command prompt.

  2. From the prompt, type

    cd /d %windir%\Microsoft.NET\Framework\v1.1.4322

  3. From the prompt, type

    aspnet_regiis /s W3SVC/1/ROOT/ReportServer

  4. Close and then re-open DPM Administrator Console.

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:

  • Uninstall SharePoint Services by using Add or Remove Programs, uninstall DPM, and then install DPM again.

-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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft