Report render failure when running new reports (Not out of the box reports)!

Hi,

It's kind of strange problem, I can run all the out of the box CRM reports smoothly without any problem. But when I try to run any new reports that I create using report wizard they error out (Report render failure. Error: An error has occurred during report processing. (rsProcessingAborted)). 

Any help is highly appreciated!

Thanks!

  • Hi, i actually had that issue last week on my VM.

    Have a look at the SQL Server and check for the following:

    Reporting Extensions is installed.

     

    then take a look at this link for more ways to resolve if you don't come right.

    http://blog.simpletrees.com/2013/04/mscrm-and-dreaded-rsprocessingaborted.html

  • In reply to Rod:

    The Reporting Extensions is already installed. Anyway, thanks for the link, I will try out on the advises  there and let you know!

    Thanks again!

  • There are several reasons why this error can happen most of which are quite easy to solve. The key to solving it is knowing how to analyze it properly.

    The most common reasons I've come across for getting this problem are as follows:

    ·                     A problem within the report or a sub report. 

    ·                     Problems with Data Sources set on the reports

    ·                     Reporting Extensions not installed on the report server

    ·                     SSRS Logon context not having adequate rights

    ·                     CRM App Pool running under a user context and not configured correctly

     

    Generally, the issue you'll face is initially not having an awful lot of information to go on. When you run the report all you get back is:

     

    rsProcessingAborted - An error has occurred during report processing

     

    So, how exactly would you investigate this to get to the root cause? First, a quick checklist:

    ·                     Open up Reporting Services: http://[SSRS Server Name]/Reports

    ·                     Are the Data Sources set correctly? The report should be point to:

    o                  FetchXml reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_FetchDataSource

    o                  SQL reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_DataSource

    ·                     If you open up Deployment Manager does it give you a warning about reporting extensions not being installed? If so you will need to install/re-install reporting extensions



    After verifying the above and if the report still isn't working you need to do a bit more in depth analysis to get to the root of a problem like this.

    Run the report in Report Services

    If nothing worked so far, check if it will run in reporting services. As I mentioned above, the URL to get to your reporting services is:

     

    http://[SSRS Server Name]/Reports

     

    Within here your custom reports will live in a folder like the following:

     

    [Organization Name]_MSCRM/CustomReports

     

    Open up the report you're having a problem with. 

     

    Tip: If you get a window asking for your user name and password, and if the report is set up correctly, you will need to enter in the following:

    Username: Your systemuserid from the systemuser table for your user record.
    Password: Your organizationid from the organization table within MSCRM_Config

     

    If the report doesn't work then it might give you more information about the problem that will lead to the solution. Quite commonly you might see an error such as "Cannot create a connection to Data Source XYZ" or something like this. Or maybe it will be something syntactically wrong with the report and not related to the Data Source. If so it's problem with the report itself that you will have to fix.

     

    If it does run, and you've confirmed the above check list, then the only questions I can think of is:

    1. Have you been using shared datasets? If so then the bad news is I don't think these will work with Dynamics CRM. Although, I haven't confirmed if shared datasets can be used with Dynamics CRM so if anyone can confirm this please let me know. But generally, if I see a shared dataset I immediately convert it to an embedded dataset and link it to a shared data source instead. If you've edited it using Report Builder you should be able to choose the MSCRM_DataSource for SQL or MSCRM_FetchDataSource for FetchXml. If you're using visual studio you can create an embedded datasource and then convert it to shared afterwards.

    2. Have you been using a child/parent folder structure for parent/sub reports? If so, I don't think you can easily do this in CRM either. I'm sure it's possible, but it's probably tedious to get working. So you'll need to make sure they're all in the same folder and correctly linking to each other.

     

     

    SSRS Account Rights

     

    If you see an error like this:

    e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Immediate caller DOMAIN\SSRS_Account has insufficient privilege to run report as user S-[XYZ]

     

    This generally means you are running the SSRS service under a domain account (as opposed to NetworkService or similar) and it doesn't have adequate rights. In the above example the user "SSRS_Account" was our domain account and it needs to be added to the following groups:

     

    [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    These must match the same groups that exist in the security section of the [ORGNAME]_MSCRM database. For example:

    SQL Server à [ORG NAME] à Security Tree view à Users à Check whether the same group exists.

     [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    Note: You should not add the SSRS_Account to the group SQLAccessGroup. If you do you may encounter errors installing / reinstalling Reporting Extensions.

    The steps to enable/disable this is as follows:

    ·                     On the Microsoft Dynamics CRM server(s), open up IIS Manager:

    o                  Start > Run: inetmgr

    ·                     Expand SERVER > Sites

    ·                     Click on Microsoft Dynamics CRM 

    ·                     Within the Features view, double click on Authentication

    ·                     Right-click on Windows Authentication and go to Advanced Settings

    ·                     Check "Enable Kernel-mode authentication"

    ·                     Click Ok

     

    Thanks!

     

  • There are several reasons why this error can happen most of which are quite easy to solve. The key to solving it is knowing how to analyze it properly.

    The most common reasons I've come across for getting this problem are as follows:

    ·                     A problem within the report or a sub report. 

    ·                     Problems with Data Sources set on the reports

    ·                     Reporting Extensions not installed on the report server

    ·                     SSRS Logon context not having adequate rights

    ·                     CRM App Pool running under a user context and not configured correctly

     

    Generally, the issue you'll face is initially not having an awful lot of information to go on. When you run the report all you get back is:

     

    rsProcessingAborted - An error has occurred during report processing

     

    So, how exactly would you investigate this to get to the root cause? First, a quick checklist:

    ·                     Open up Reporting Services: http://[SSRS Server Name]/Reports

    ·                     Are the Data Sources set correctly? The report should be point to:

    o                  FetchXml reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_FetchDataSource

    o                  SQL reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_DataSource

    ·                     If you open up Deployment Manager does it give you a warning about reporting extensions not being installed? If so you will need to install/re-install reporting extensions



    After verifying the above and if the report still isn't working you need to do a bit more in depth analysis to get to the root of a problem like this.

    Run the report in Report Services

    If nothing worked so far, check if it will run in reporting services. As I mentioned above, the URL to get to your reporting services is:

     

    http://[SSRS Server Name]/Reports

     

    Within here your custom reports will live in a folder like the following:

     

    [Organization Name]_MSCRM/CustomReports

     

    Open up the report you're having a problem with. 

     

    Tip: If you get a window asking for your user name and password, and if the report is set up correctly, you will need to enter in the following:

    Username: Your systemuserid from the systemuser table for your user record.
    Password: Your organizationid from the organization table within MSCRM_Config

     

    If the report doesn't work then it might give you more information about the problem that will lead to the solution. Quite commonly you might see an error such as "Cannot create a connection to Data Source XYZ" or something like this. Or maybe it will be something syntactically wrong with the report and not related to the Data Source. If so it's problem with the report itself that you will have to fix.

     

    If it does run, and you've confirmed the above check list, then the only questions I can think of is:

    1. Have you been using shared datasets? If so then the bad news is I don't think these will work with Dynamics CRM. Although, I haven't confirmed if shared datasets can be used with Dynamics CRM so if anyone can confirm this please let me know. But generally, if I see a shared dataset I immediately convert it to an embedded dataset and link it to a shared data source instead. If you've edited it using Report Builder you should be able to choose the MSCRM_DataSource for SQL or MSCRM_FetchDataSource for FetchXml. If you're using visual studio you can create an embedded datasource and then convert it to shared afterwards.

    2. Have you been using a child/parent folder structure for parent/sub reports? If so, I don't think you can easily do this in CRM either. I'm sure it's possible, but it's probably tedious to get working. So you'll need to make sure they're all in the same folder and correctly linking to each other.

     

     

    SSRS Account Rights

     

    If you see an error like this:

    e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Immediate caller DOMAIN\SSRS_Account has insufficient privilege to run report as user S-[XYZ]

     

    This generally means you are running the SSRS service under a domain account (as opposed to NetworkService or similar) and it doesn't have adequate rights. In the above example the user "SSRS_Account" was our domain account and it needs to be added to the following groups:

     

    [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    These must match the same groups that exist in the security section of the [ORGNAME]_MSCRM database. For example:

    SQL Server à [ORG NAME] à Security Tree view à Users à Check whether the same group exists.

     [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    Note: You should not add the SSRS_Account to the group SQLAccessGroup. If you do you may encounter errors installing / reinstalling Reporting Extensions.

    The steps to enable/disable this is as follows:

    ·                     On the Microsoft Dynamics CRM server(s), open up IIS Manager:

    o                  Start > Run: inetmgr

    ·                     Expand SERVER > Sites

    ·                     Click on Microsoft Dynamics CRM 

    ·                     Within the Features view, double click on Authentication

    ·                     Right-click on Windows Authentication and go to Advanced Settings

    ·                     Check "Enable Kernel-mode authentication"

    ·                     Click Ok

     

    Thanks!

     

  • There are several reasons why this error can happen most of which are quite easy to solve. The key to solving it is knowing how to analyze it properly.

    The most common reasons I've come across for getting this problem are as follows:

    ·                     A problem within the report or a sub report. 

    ·                     Problems with Data Sources set on the reports

    ·                     Reporting Extensions not installed on the report server

    ·                     SSRS Logon context not having adequate rights

    ·                     CRM App Pool running under a user context and not configured correctly

     

    Generally, the issue you'll face is initially not having an awful lot of information to go on. When you run the report all you get back is:

     

    rsProcessingAborted - An error has occurred during report processing

     

    So, how exactly would you investigate this to get to the root cause? First, a quick checklist:

    ·                     Open up Reporting Services: http://[SSRS Server Name]/Reports

    ·                     Are the Data Sources set correctly? The report should be point to:

    o                  FetchXml reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_FetchDataSource

    o                  SQL reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_DataSource

    ·                     If you open up Deployment Manager does it give you a warning about reporting extensions not being installed? If so you will need to install/re-install reporting extensions



    After verifying the above and if the report still isn't working you need to do a bit more in depth analysis to get to the root of a problem like this.

    Run the report in Report Services

    If nothing worked so far, check if it will run in reporting services. As I mentioned above, the URL to get to your reporting services is:

     

    http://[SSRS Server Name]/Reports

     

    Within here your custom reports will live in a folder like the following:

     

    [Organization Name]_MSCRM/CustomReports

     

    Open up the report you're having a problem with. 

     

    Tip: If you get a window asking for your user name and password, and if the report is set up correctly, you will need to enter in the following:

    Username: Your systemuserid from the systemuser table for your user record.
    Password: Your organizationid from the organization table within MSCRM_Config

     

    If the report doesn't work then it might give you more information about the problem that will lead to the solution. Quite commonly you might see an error such as "Cannot create a connection to Data Source XYZ" or something like this. Or maybe it will be something syntactically wrong with the report and not related to the Data Source. If so it's problem with the report itself that you will have to fix.

     

    If it does run, and you've confirmed the above check list, then the only questions I can think of is:

    1. Have you been using shared datasets? If so then the bad news is I don't think these will work with Dynamics CRM. Although, I haven't confirmed if shared datasets can be used with Dynamics CRM so if anyone can confirm this please let me know. But generally, if I see a shared dataset I immediately convert it to an embedded dataset and link it to a shared data source instead. If you've edited it using Report Builder you should be able to choose the MSCRM_DataSource for SQL or MSCRM_FetchDataSource for FetchXml. If you're using visual studio you can create an embedded datasource and then convert it to shared afterwards.

    2. Have you been using a child/parent folder structure for parent/sub reports? If so, I don't think you can easily do this in CRM either. I'm sure it's possible, but it's probably tedious to get working. So you'll need to make sure they're all in the same folder and correctly linking to each other.

     

     

    SSRS Account Rights

     

    If you see an error like this:

    e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Immediate caller DOMAIN\SSRS_Account has insufficient privilege to run report as user S-[XYZ]

     

    This generally means you are running the SSRS service under a domain account (as opposed to NetworkService or similar) and it doesn't have adequate rights. In the above example the user "SSRS_Account" was our domain account and it needs to be added to the following groups:

     

    [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    These must match the same groups that exist in the security section of the [ORGNAME]_MSCRM database. For example:

    SQL Server à [ORG NAME] à Security Tree view à Users à Check whether the same group exists.

     [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    Note: You should not add the SSRS_Account to the group SQLAccessGroup. If you do you may encounter errors installing / reinstalling Reporting Extensions.

    The steps to enable/disable this is as follows:

    ·                     On the Microsoft Dynamics CRM server(s), open up IIS Manager:

    o                  Start > Run: inetmgr

    ·                     Expand SERVER > Sites

    ·                     Click on Microsoft Dynamics CRM 

    ·                     Within the Features view, double click on Authentication

    ·                     Right-click on Windows Authentication and go to Advanced Settings

    ·                     Check "Enable Kernel-mode authentication"

    ·                     Click Ok

     

    Thanks!

     

  • There are several reasons why this error can happen most of which are quite easy to solve. The key to solving it is knowing how to analyze it properly.

    The most common reasons I've come across for getting this problem are as follows:

    ·                     A problem within the report or a sub report. 

    ·                     Problems with Data Sources set on the reports

    ·                     Reporting Extensions not installed on the report server

    ·                     SSRS Logon context not having adequate rights

    ·                     CRM App Pool running under a user context and not configured correctly

     

    Generally, the issue you'll face is initially not having an awful lot of information to go on. When you run the report all you get back is:

     

    rsProcessingAborted - An error has occurred during report processing

     

    So, how exactly would you investigate this to get to the root cause? First, a quick checklist:

    ·                     Open up Reporting Services: http://[SSRS Server Name]/Reports

    ·                     Are the Data Sources set correctly? The report should be point to:

    o                  FetchXml reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_FetchDataSource

    o                  SQL reports: /[ORGNAME]_MSCRM/CustomReports/MSCRM_DataSource

    ·                     If you open up Deployment Manager does it give you a warning about reporting extensions not being installed? If so you will need to install/re-install reporting extensions



    After verifying the above and if the report still isn't working you need to do a bit more in depth analysis to get to the root of a problem like this.

    Run the report in Report Services

    If nothing worked so far, check if it will run in reporting services. As I mentioned above, the URL to get to your reporting services is:

     

    http://[SSRS Server Name]/Reports

     

    Within here your custom reports will live in a folder like the following:

     

    [Organization Name]_MSCRM/CustomReports

     

    Open up the report you're having a problem with. 

     

    Tip: If you get a window asking for your user name and password, and if the report is set up correctly, you will need to enter in the following:

    Username: Your systemuserid from the systemuser table for your user record.
    Password: Your organizationid from the organization table within MSCRM_Config

     

    If the report doesn't work then it might give you more information about the problem that will lead to the solution. Quite commonly you might see an error such as "Cannot create a connection to Data Source XYZ" or something like this. Or maybe it will be something syntactically wrong with the report and not related to the Data Source. If so it's problem with the report itself that you will have to fix.

     

    If it does run, and you've confirmed the above check list, then the only questions I can think of is:

    1. Have you been using shared datasets? If so then the bad news is I don't think these will work with Dynamics CRM. Although, I haven't confirmed if shared datasets can be used with Dynamics CRM so if anyone can confirm this please let me know. But generally, if I see a shared dataset I immediately convert it to an embedded dataset and link it to a shared data source instead. If you've edited it using Report Builder you should be able to choose the MSCRM_DataSource for SQL or MSCRM_FetchDataSource for FetchXml. If you're using visual studio you can create an embedded datasource and then convert it to shared afterwards.

    2. Have you been using a child/parent folder structure for parent/sub reports? If so, I don't think you can easily do this in CRM either. I'm sure it's possible, but it's probably tedious to get working. So you'll need to make sure they're all in the same folder and correctly linking to each other.

     

     

    SSRS Account Rights

     

    If you see an error like this:

    e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Immediate caller DOMAIN\SSRS_Account has insufficient privilege to run report as user S-[XYZ]

     

    This generally means you are running the SSRS service under a domain account (as opposed to NetworkService or similar) and it doesn't have adequate rights. In the above example the user "SSRS_Account" was our domain account and it needs to be added to the following groups:

     

    [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    These must match the same groups that exist in the security section of the [ORGNAME]_MSCRM database. For example:

    SQL Server à [ORG NAME] à Security Tree view à Users à Check whether the same group exists.

     [DOMAIN]\PrivReportingGroup {GUID}
    [DOMAIN]\ReportingGroup {GUID}
    [DOMAIN]\PrivUserGroup {GUID}

     

    Note: You should not add the SSRS_Account to the group SQLAccessGroup. If you do you may encounter errors installing / reinstalling Reporting Extensions.

    The steps to enable/disable this is as follows:

    ·                     On the Microsoft Dynamics CRM server(s), open up IIS Manager:

    o                  Start > Run: inetmgr

    ·                     Expand SERVER > Sites

    ·                     Click on Microsoft Dynamics CRM 

    ·                     Within the Features view, double click on Authentication

    ·                     Right-click on Windows Authentication and go to Advanced Settings

    ·                     Check "Enable Kernel-mode authentication"

    ·                     Click Ok

     

    Thanks!

     

Related
Recommended