locked
CRM2011 reports not working - preconfigured AD groups - SQL and SSRS on separate machines RRS feed

  • Question

  • Hi

    Our CRM2011 do not seem to work, giving a report processing error:

    [ReportServerException: Cannot create a connection to data source 'CRM'. (rsErrorOpeningConnection)]

    We have preconfigured AD groups and have added the reporting server machine name to the AD groups: PrivUserGroup and PrivReportingGroup

    Reporting extensions have been installed successfully on the Reporting services server and out of box erports are showing up in MS CRM

    User running the reports is having sysadmin role.

    Anything we are overlooking security wise?

    Thanks and Regards

    AniMandal

    Thursday, June 16, 2011 2:57 PM

Answers

  • Hi

    Had some interesting experiences with our SSRS server and reports in MSCRM.

    One of our intitial thought was find out if it is keerberos releated as our SQL and SSRS were on separate servers. This pointed out to getting creating SPNs for the Application service account and the machine name of the App server. This fixed the reports issues, but brought down the app server (not accessible from outside the server) since we have a load balanced App servers, we have a SPN setup for the Application service account on the DNS host name for running IIS in a clustered account. Multiple SPNs on the same service account doen't seem to play well, through it's not documented that an account can't have multiple SPNs setup.

    The final piece of the puzzle was to add the SSRS service account to the privusergroup and the privreportinggroup. We already had the SSRS machine names added to these groups.

    Reports are finally up!

    Thanks and Regards

    AniMandal


    • Marked as answer by AniMandal Saturday, June 25, 2011 2:13 PM
    Saturday, June 25, 2011 2:13 PM

All replies

  • It's probably not security.  It looks like an issue concerning your custom reports and their datasource.  If you can lay out some specifics on how the reports were created it might help.

    Thanks,


    Jamie Miley
    http://mileyja.blogspot.com
    Linked-In Profile
    Follow Me on Twitter!
    Thursday, June 16, 2011 3:33 PM
    Moderator
  • Hi

    It is not just custom reports, but all reports are giving this error including out of box reports.

    What do we need to look out for when the SSRS and SQL are running on separate boxes? the implementation guide seems to be pretty silent on this issues. Also it works, if i have SSRS installed ont he SQL box, but same configuration for the AD groups and user access, the reports fail when the SSRS and SQL boxes are separated. AS per IG, the reporting services extenstion is suppoed to remove the need for trust for delegation for precisely these situtations, but reports still do not work.

    Thanks and Regards

    AniMandal

    Thursday, June 16, 2011 4:16 PM
  • Hi,

    I think this is because of the duplicate records which created in CRM with same name.

    Can you download the CrmDiagTool and check for the errors, you can download from the below link.

    http://mscrmtools.blogspot.com/2011/04/new-tool-crmdiagtool-2011.html

     

    And this issue is updated in Rollup 2, install and test it again.

     

    regards,


    Khaja Mohiddin
    Thursday, June 16, 2011 9:07 PM
  • Hi

    Had some interesting experiences with our SSRS server and reports in MSCRM.

    One of our intitial thought was find out if it is keerberos releated as our SQL and SSRS were on separate servers. This pointed out to getting creating SPNs for the Application service account and the machine name of the App server. This fixed the reports issues, but brought down the app server (not accessible from outside the server) since we have a load balanced App servers, we have a SPN setup for the Application service account on the DNS host name for running IIS in a clustered account. Multiple SPNs on the same service account doen't seem to play well, through it's not documented that an account can't have multiple SPNs setup.

    The final piece of the puzzle was to add the SSRS service account to the privusergroup and the privreportinggroup. We already had the SSRS machine names added to these groups.

    Reports are finally up!

    Thanks and Regards

    AniMandal


    • Marked as answer by AniMandal Saturday, June 25, 2011 2:13 PM
    Saturday, June 25, 2011 2:13 PM