SQL 2005 report server and web service running account

 
 
When SQL 2005 report server web service account is changed to "LocalSystem" in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rsreportserver.config, report server will not be started and you will get the following error in report server log file (C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ServerService__main_DateTime.log):
 
ReportingServicesService!library!4!2/22/2006-10:13:02:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name ‘LocalSystem’ is not recognized., ;
 Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name ‘LocalSystem’ is not recognized.
ReportingServicesService!servicecontroller!4!2/22/2006-10:13:02:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name ‘LocalSystem’ is not recognized.
 
You need to use NT Authority\NetworkService or APSNET account to run the service in the configuration file under <WebServiceAccount> element.
 
The web service account can only be changed in the configuration file. The Reporting service configuration manager does not support editing the account. 😦

 

The windows service of report server can run under LocalSystem account. This account information can be changed in two places:
  1. Service control panel
  2. Reporting service configuration manager (windows service identity task)
The changes in either places are synchronized. However, if you change the account from Reporting service configuration manager, it asks you to backup the encryption key. If you change it from service control panel, it deos not. So the safer way is to use the Reporting service configuration manager.
 
 
Advertisements
This entry was posted in SQL server 2005. Bookmark the permalink.

One Response to SQL 2005 report server and web service running account

  1. phe1129 says:

    sp_helprotect does not return information about securables that were introduced in SQL Server 2005. Use sys.database_permissions and fn_builtin_permissions instead.
    — From BOL

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s