Microsoft Knowledge Base Email Alertz

KBAlertz.com: (909509) - Describes a problem that occurs after you upgrade the operating system of the server that is running Microsoft Dynamics CRM or SQL Server from Windows Server 2000 to Windows Server 2003. Provides steps to resolve the problem.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 909509 - Last Review: July 9, 2007 - Revision: 3.1

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)'"

On This Page

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.

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

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.

APPLIES TO
  • Microsoft Dynamics CRM 3.0
Keywords: 
kbmbscrm40no kberrmsg kbtshoot kbmbsreports kbmbsmigrate kbprb KB909509
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please