Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you run a report in Microsoft Dynamics CRM: "Reporting Services Error" or "An Error has occurred during report processing" or "Login failed for user '(null)'"


View products that this article applies to.

Symptoms

When you run a report in Microsoft Dynamics CRM 3.0, you receive one of the following error messages.

Error message 1
Reporting Services Error.
Error message 2
An Error has occurred during report processing. Cannot create a connection to data source 'CRM'.
Error message 3
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

↑ Back to the top


Cause

Cause 1

This problem occurs after you upgrade the operating system of the server that is running Microsoft Dynamics CRM or Microsoft SQL Server. Specifically, you upgrade the operating system from Microsoft Windows Server 2000 to Microsoft Windows Server 2003. The problem occurs because the Trust computer for delegation property is not enabled for SQL Server. This problem may occur after you upgrade the operating system of the server that is running Microsoft Dynamics CRM or that is running Microsoft SQL Server. Specifically, this problem may occur after you upgrade the operating system from Microsoft Windows Server 2000 to Microsoft Windows Server 2003.

Cause 2

This problem may occur because one of the following is not added to the PrivUserGroup group:
  • The account that is running the CRMAppPool application pool
  • The application pool under which Reporting Services is running
  • The account that is running the SQL Server Reporting Services service

↑ Back to the top


Resolution

Resolution 1

To resolve this problem, follow these steps:
  1. Log on to a domain controller in the Microsoft Dynamics CRM domain as a user who has a domain administrator role.
  2. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  3. Expand the domain node, and then expand the group unit or the organization unit that has the computer that contains the SQL Server databases for Microsoft Dynamics CRM.
  4. Right-click the computer that contains the SQL Server databases for Microsoft Dynamics CRM, and then click Properties.
  5. On the General tab, select the Trust computer for delegation check box.
  6. Restart the SQL Server service.
    1. Log on to SQL Server.
    2. Click Start, point to Administrative Tools, and then click Services.
    3. Right-click MSSQLSERVER, and then click Restart.
    4. In the Restart Other Services dialog box, click Yes.
  7. Restart the Internet Information Service (IIS) on the server that is running Microsoft Dynamics CRM.
    1. Log on to the server that is running Microsoft Dynamics CRM.
    2. Click Start, click Run, type iisreset, and then click OK.
  8. Run the report again.

Resolution 2

Verify which user is running the CRMAppPool application pool, or verify the application pool that Reporting Services is using

To verify which user is running the CRMAppPool application pool, or to verify the application pool that Reporting Services is using, follow these steps:
  1. On the Microsoft Dynamics CRM Server, or on the Reporting Services server, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Expand the server name, and then expand Application Pools.
  3. Right-click CRMAppPool, or right-click the application pool that Reporting Services is using. Then, click Properties.
  4. Click the Identity tab to see what user the account is set to. If the account is set to Network Service or to Local System, use the server name in the "Add a user or a server to the PrivUserGroup group" section later in this article.

Check the Reporting Services account

To check the Reporting Services account, follow these steps:
  1. Click Start, click Run, type services.msc, and then click Run.
  2. Find the SQL Server Reporting Services service in the list of services. Right-click the SQL Server Reporting Services service, and then click Properties.
  3. Click the Log On tab to see what account is running the service. If the account is set to Network Service or to Local System, use the server name in the "Add a user or a server to the PrivUserGroup group" section later in this article.

Add a user or a server to the PrivUserGroup group

To add a user or a server to the PrivUserGroup group in the Active Directory directory service, follow these steps:
  1. Start Active Directory Users and Computers. To do this, click Start, point to Programs, click Administrative Tools, and then click Active Directory Users and Computers.
  2. Expand the tree, and then click the Microsoft Dynamics CRM organizational unit.
  3. In the right panel, right-click PrivUserGroup, and then click Properties to open the PrivUserGroup Properties window.
  4. Click the Members tab.
  5. To open the "Select Users, Contacts, Computers or Groups" window, click Add.
  6. Locate the user or the computer that you identified in the previous procedures in this article, and then click Add.
  7. Click OK to close the "Select Users, Contacts, Computers or Groups" window.
  8. Click OK to close the PrivUserGroup Properties window.
  9. Close Active Directory Users and Computers.
Note If you are using a Microsoft Dynamics CRM user as the account that runs the application pools or that runs Reporting Services, make sure that the Restricted Access Mode check box on the User form is cleared. If the Restricted Access Mode check box is selected, the users' actions are restricted, regardless of the roles that are assigned to the users. To find this setting in Microsoft Dynamics CRM, click Settings, point to Business Unit Settings, click Users, and then open the User form for the target user.

↑ Back to the top


Keywords: KB909509, kbprb, kbmbsmigrate, kbmbsreports, kbtshoot, kberrmsg, kbmbscrm40no

↑ Back to the top

Article Info
Article ID : 909509
Revision : 4
Created on : 7/9/2007
Published on : 7/9/2007
Exists online : False
Views : 361