SQL server 2005 reporting services installation pitfall

Error:
  • Pit 1: Windows SQL reporting Service does not start. When started it automatically stops and says: Some service automatically stops when it has nothing to do such as alert or performance service.
  • Pit 2: After setting the new application pool with local system account and then setting up the database, initialization fails and says An Error occurred when attempting to connect to reporting server remote procedure call, RPC server is not listening
  • Pit 3: Starting service from configuration manager says: System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
    at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
    at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
  • Pit 4: Error log says: ReportingServicesService!library!4!8/11/2009-16:36:59:: 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!8/11/2009-16:36:59:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'LocalSystem' is not recognized.

Solution:
When a new application pool created with local system account and in webservice account setup the asnet account is set to Local system WMI writes wrongly in rsreportserver.config file in reportserver of server installation folder. You should manually change the entry of
LocalSystem
into
NT Authority\System
so that Local System account can be validated.

Comments