none
DPM 2019 – Reporting Services Server cannot connect to DPM Database RRS feed

  • Question

  • Hi,

    I am getting below error while scheduling report on DPM server. I have faced this same issue and resolved it by following https://support.microsoft.com/en-za/help/4457489/reporting-services-server-cannot-connect-to-the-dpm-database-when-you.

    However, in my production environment I have DPM database running on remote computer and Reporting database locally on DPM server. I am now confused that on which server(DPM Server or SQL Server) should I create local account as suggested in above article. I have checked on my test environment and this account needs access on DPM database not on Reporting database. Please correct if I am wrong.

    Reporting Services Server cannot connect to DPM Database

    Tuesday, November 26, 2019 10:27 AM

Answers

  • Hi,

    The KB article assumes that you have the DPM database on the same server as you've installed DPM, in your case since you have the DPM database located on a remote server it's slightly different.

    What you could try is to create a local group on the DPM database server, then create a AD domain account and add it to the local group (instead of creating a local user).

    Then perform the same steps for the domain account, and then on the DPM Reporting add the same permissions as the KB article specifies for the domain user that you've created.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by SC2317 Wednesday, November 27, 2019 2:20 PM
    Tuesday, November 26, 2019 12:09 PM

All replies

  • Hi,

    The KB article assumes that you have the DPM database on the same server as you've installed DPM, in your case since you have the DPM database located on a remote server it's slightly different.

    What you could try is to create a local group on the DPM database server, then create a AD domain account and add it to the local group (instead of creating a local user).

    Then perform the same steps for the domain account, and then on the DPM Reporting add the same permissions as the KB article specifies for the domain user that you've created.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by SC2317 Wednesday, November 27, 2019 2:20 PM
    Tuesday, November 26, 2019 12:09 PM
  • Hi Leon,

    Thanks. I can try that, however when I try to add local group as mentioned in the step 4, I get below error. I believe its SQL cluster so that's why its throwing this error because sql instance will have different name than the actual machine name. Please suggest.

    TITLE: Microsoft SQL Server Management Studio

    ------------------------------

    Create failed for Login 'XXXXXXX\DPMDBReaders$XXXXXXX'.  (Microsoft.SqlServer.Smo)

    For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=15.0.18142.0+((SSMS_Rel).190722-0816)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476

    ------------------------------
    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    Windows NT user or group 'XXXXXXX\DPMDBReaders$XXXXXXX' not found. Check the name again. (Microsoft SQL Server, Error: 15401)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.1000&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476

    ------------------------------
    BUTTONS:

    OK
    ------------------------------

    Tuesday, November 26, 2019 12:17 PM
  • If it's a cluster, you will need to create the local group on all cluster nodes.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, November 26, 2019 12:25 PM
  • Hi Leon,

    I did created local group on all cluster nodes but it did not help. However, your previous suggestion did helped me resolving the issue. I have domain service account running SQL services for DPM database and that account has permissions on DPM database.

    I just had to follow that same article and just perform step 15 to add that domain account in Reporting services URL and it resolved the issue.

    Many thanks for your help once again.

    Tuesday, November 26, 2019 12:37 PM
  • Great to hear that, you're welcome!

    (Please don't forget to mark helpful replies as answer)


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, November 26, 2019 12:51 PM