The SQL Server Reporting Services service does not start correctly and you receive an error message on a Windows 2000 Server domain controller on which you have installed SQL Server 2005 Reporting Services (911846)


The information in this article applies to:

  • Microsoft SQL Server 2005 Reporting Services
Bug #: 403296 (SQL BUDT)
Bug #: 45602 (Content Maintenance)

SYMPTOMS

When you install Microsoft SQL Server 2005 Reporting Services on a Microsoft Windows 2000 Server domain controller, the SQL Server Reporting Services service does not start correctly and you receive an error message that is similar to the following:
ReportingServicesService!servicecontroller!9!8/15/2005-14:57:46:: Total Physical memory: 535838720
ReportingServicesService!library!4!8/15/2005-14:57:46:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'ComputerName\ASPNET' is not recognized., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'ComputerName\ASPNET' is not recognized.
ReportingServicesService!servicecontroller!4!8/15/2005-14:57:46:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'ComputerName\ASPNET' is not recognized. at Microsoft.ReportingServices.Library.Native.NameToSid(String name) at Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean firstTime)
NoteComputerName is a placeholder for the name of the Windows 2000 Server domain controller.

CAUSE

This problem occurs when the WebServiceAccount setting that is in the RSreportserver.config file is not specified. When the WebServiceAccount setting is not specified, the SQL Server Reporting Services service will try to use the ComputerName\ASPNET account to start the Report Server Web service. However, the ComputerName\ASPNET account does not exist in the Windows Server 2000 domain controller. By default, Microsoft ASP.NET applications that are running on a Windows 2000 Server domain controller run in the security context of the IWAM_ComputerName account.

WORKAROUND

To work around this problem, write the IWAM_ComputerName account to the WebServiceAccount tag that is in the RSreportserver.config file. To do this, follow these steps:
  1. Locate the folder that contains the Rsreportserver.config file. By default, this file is in the following folder:

    Drive:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportManager

    Notes
    • Drive is a placeholder for the hard disk of your computer.
    • MSSQL.x is a placeholder for the corresponding instance ID for the system. To determine the instance ID for the system, follow these steps:
      1. Connect to the instance of the SQL Server Reporting Services service by using the Reporting Services Configuration tool.
      2. Click to open the Report Server Status page.
      3. On the Report Server Status page, note the instance ID information.
  2. In Notepad, open the Rsreportserver.config file.
  3. Locate the line that contains the <WebServiceAccount></WebServiceAccount> tag.
  4. Add the IWAM_ComputerName account to the WebServiceAccount setting. The following example illustrates the syntax that you must use:

    <WebServiceAccount>IWAM_ComputerName</WebServiceAccount>

  5. Save and then close the RSreportserver.config file.
  6. Restart the SQL Server Reporting Services service.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For more information about the account that is used to run ASP.NET applications, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrfProcessmodelSection.asp

Modification Type:MinorLast Reviewed:12/28/2005
Keywords:kbExpertiseAdvanced kbprb KB911846 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.