Edit

Reporting Services Server cannot connect to the DPM database error when you schedule an email report

  • Article

This article helps you work around an issue where you receive the Reporting Services Server cannot connect to the DPM database error when you try to schedule a report to be emailed in Data Protection Manager (DPM).

Original product version:   System Center Data Protection Manager
Original KB number:   4457489

Symptoms

Assume that you do a new installation, or you upgrade to Microsoft System Center 2012 R2 Data Protection Manager or a later version. When you try to schedule a report to be emailed, you receive the following error message:

Reporting Services Server cannot connect to the DPM database.
To repair the configuration, follow steps for repairing DPM from DPM Setup Help.
ID: 3001

Details of the Error ID 3001 Reporting Services Server cannot connect to the DPM database.

When you try the steps that are mentioned in Repair DPM, this problem isn't resolved.

Workaround

To work around this problem, follow these steps to make correct configuration changes that will enable Data Protection Manager reports to be emailed.

Note

Some steps may not be necessary if you experience this problem after you upgrade from System Center 2012 Data Protection Manager Server Pack 1. Review and do these steps as applicable.

  1. On the DPM server, create a local group that's named DPMDBReaders$<DPMServerName>. In the following example, the <DPMServerName> value is WINB-DPM.

    Create a new local group in the New Group window.

  2. Create a local user that's named DPMR$<DPMServerName>, and provide a strong password that never expires.

    Create a new local user in the New User window.

  3. Add the new local user to the DPMDBReaders$<DPMServerName> group that was created in step 1.

    Add the new local user to the local group that you created in step 1.

  4. Start SQL Server Management Studio by using administrative permissions, and then connect to the SQL Server instance that's used by DPM. Under Security, right-click Logins, and then select New login > Search.... Under Object Types, select the Groups object type, and then select OK. Add the local group DPMDBReaders$<DPMServerName>, and then select OK. After the group is added, it will be listed under Logins.

    Select New login to add the local group.

  5. Right-click the new login group, and then select Properties. In the General section, change the Default database field to the DPMDB name.

    Set the Default database field to the DPMDB name in the Login Properties window.

  6. Under User Mapping, select both the check box for the DPMDB name and the check box for the db_datareader role.

    Select the DPMDB name and the related database role membership.

  7. In SQL Server Management Studio, navigate to Databases > DPMDB > Programmability > Stored Procedures.

  8. Right-click the following stored procedures, and then select Properties > Permissions > Search > Browse. Add the DPMDBReaders$<DPMServerName> group, grant the Execute permission, and then select OK.

    • Prc_MOM_Heartbeat_Get
    • prc_MOM_ProductionServer_Get

  9. Exit SQL Server Management Studio.

  10. Start the SQL Server Reporting Services Configuration Manager and connect to the SQL Server instance hosting the DPM reports.

  11. Select Web Portal URL, and then select the URL.

    Select Web Portal URL in the Reporting Services Configuration Manager.

  12. Select the URLs link, as shown in step 11. This opens the https://localhost/Reports/Pages/Folder.aspx portal, as shown in the following screenshot.

    Select the URL link that is shown in the step 11.

  13. Select the DPMReports_<GUID> link to open the DPM reports page, as shown in the following screenshot.

    Open the DPM reports page by selecting the DPMReports.

  14. Select DPMReporterDataSource to open its properties window, as shown in the following screenshot.

    Select DPMReporterDataSource to open its properties window.

  15. On the DPMReporterDataSource configuration page, follow these steps:

    1. Select the Using the following credentials option.
    2. Change the Type of credentials list selection to Windows user name and password.
    3. Add the DPMR$<DPMServerName> user account and password that you created in step 2.
    4. Select Test connection to determine whether the server can connect successfully.
    5. Select Apply.

    Set up credentials and test connection on the DPMReporterDataSource configuration page.

  16. Close the DPMReporterDataSource configuration page to return to the Reporting Services Configuration Manager screen. Select Service Account. On Service Account page, change the Report Server Service Account service to use Network Service. If you're prompted for the backup encryption key, type the value, and then select Apply.

    Change the Report Server Service Account service to use Network Service in the Reporting Services Configuration Manager.

  17. Restart the DPM server to make sure that all configuration changes take effect.

  18. Now, you can schedule email reports without experiencing the original error that's mentioned in the Symptoms section.

    Restart the DPM server and you now can schedule email reports.