• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 493
  • Last Modified:

CRM reports don't work for non domain admin users after upgrading from CRM 3.0 to CRM 4.0





We were running CRM 3.0 with all reports working perfectly for all users.  After an inplace upgrade to CRM 4.0 with the latest Rollup Updates, most reports no longer work.  They work for me as a domain admin, but not for the other users.  As I test I changed one users roll to a Sys Admin in CRM, but I did not see a change.  I've looked at the SSRS side and all the permissions look okay.  The exact error users get when they run the report is:
 
An error has occurred during the report processing:  Query execution failed for data set 'DSNeglectedAccouts'.  For more information about this error navigate to the report server on the local server machine, or enable remote errors.
 
Notice that "Accouts" is missing the "n".  Not sure why, thought that is odd.
 
Any ideas on this?  Since the report works fine for me, I don't feel like its an issue with the report itself.
0
chome81
Asked:
chome81
  • 3
  • 2
1 Solution
 
Feridun KadirPrincipal ConsultantCommented:
PLease review this article and let me know if it assists.

Another area to check is whether users have been added to the appropriate groups in AD (especially reportinggroup) as shown below:

PrivUserGroup
¿The account that the CRMAppPool application pool uses
¿The account that the ASP.NET process model uses
¿The user account that runs the Microsoft Dynamics CRM installation
¿The computer account on which the Microsoft Dynamics CRM-Exchange E-mail Router will be installed
ReportingGroup
¿All Microsoft Dynamics CRM user accounts (this includes the user who is installing Microsoft Dynamics CRM)
SQLAccessGroup
¿The account that the CRMAppPool application pool uses
¿The account that the ASP.NET process model uses
UserGroup
¿All Microsoft Dynamics CRM user accounts (this includes the user who is installing Microsoft Dynamics CRM)
PrivReportingGroup
¿The computer account on which the Microsoft Dynamics CRM Data Connector for Microsoft SQL Server Reporting Services will be installed


See http://support.microsoft.com/kb/946677 for more details (the above information came from this article).
0
 
Feridun KadirPrincipal ConsultantCommented:
Oops, forget the link to "this article" in the first sentence of the last post, http://www.experts-exchange.com/Database/Software/CRM/A_3552-Troubleshooting-Microsoft-Dynamics-CRM-Reports.html

0
 
chome81Author Commented:
Thank you for the response.  I checked the link and psawed all the tests.  I have know issues running the reports when I login with my domain admin account.  All the users are part of the reporting group.  I'm really stumped on this one.
0
 
chome81Author Commented:
Anybody have any other ideas?
0
 
Feridun KadirPrincipal ConsultantCommented:
How about deleting all the reports on the SQL Server and then using the Manually Publish Reports step in the article I referred to above? This may fix up any permission issues on the reports.

But before you do that, what happens if a user (for whom a report doesn't run) runs a report directly from SSRS (i.e. without going through CRM)?
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now