I am currently working on a windows 2003 server with SQL2000 (developers edition). My Sqlserver and Report Server are on two different machines. This was working yesterday but frustratingly not this morning. Everytime I try to start the Reporting Server service, it gives me the following message: "The Report Server service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service. Is there a way around this??? - any help would be greatly appreciated .

Anyone?

If you are still seeing this issue...I found a solution for a similiar error (a different service, but the same error). Had to clear out the Application log in Event Viewer. See if that helps.

Possibly best not to delete the contents of the event logs, as this may provide a pointer towards solving your problem. Open the eventlogs, then start the service, find the error that is logged for it. If you post that here it may give more of an idea.

I'm facing a very similar problem. I've installed, uninstalled and reinstalled SQL server 2005 Developer Edition twice now. In each case Report Server can't be started. I've looked in the logs and the pertinent errors seem to be the following: ReportingServicesService!library!4!6/16/2006-15:28:33:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized., ;Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized.ReportingServicesService!servicecontroller!4!6/16/2006-15:28:33:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'E1705\ASPNET' is not recognized. In the other log file is the following error: ReportingServicesService!library!8!6/16/2006-15:28:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the version of the report server database and verify access rights., ;Info: Looking at the time stamp, I believe the later is just a result of the UnknownUserNameException: SQL Server works fine, I can work with the database in the Management Studio and access them through ASP.NET without a problem (or at least I could before I uninstalled a couple of times!!) .Net framework 2.0 is installed. I have a Gig of RAM, plenty of hard disk and XP Prof Ed SP 2. I'm at a total loss on how to get it to work on this machine. Any help would be greatly appreciated!! Bob O'Dell

The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help. aspnet_regiis.exe -i -enable

ASPNET user did appear as a user and I tried different permissions to no avail. What finally worked was to uninstall Report Services (actually I uninstalled ALL of SQL server) and then reinstalled the .NET framework. After that I reinstalled SQL Server and Report Services. Everything seemed to work after that. I'm not sure what was wrong, but I'm off and running now! Thanks for the help

James Wu - MSFT wrote: The problem seems to be that the default ASP.NET user is not present. Are you able to find ASPNET user on your local machine E1705? Re-registering asp.net might help. aspnet_regiis.exe -i -enable This was the 'trick' I was looking for. Now I'm able to start the Reporting Service. Many thanks!!

Have you made any changes to the rsreportserver.config file? If so, go back and check that there are no syntax errors or unclosed tags. Then try starting the service again.

Have you made any changes to the rsreportserver.config file? If so, go back and check that there are no syntax errors or unclosed tags. Then try starting the service again. FYI they had this issue back in 2007.