ReportingServices will not start after 2008 to 2008R2 upgrade

Question

Hello, A server was recently upgraded to 2008R2 from 2008. Before upgrade reportingservices was running. After upgrade, I cannot start ReportingServices from rsconfig, I receive this error.

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)

 If I look into the Windows Application log I see this error.

Message
Service cannot be started. System.Exception: Default appdomain failed to initialize.
   at Microsoft.ReportingServices.Library.ServiceAppDomainController.Start()
   at Microsoft.ReportingServices.Library.ReportService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

Any idea where to look at? Thanks

---

Thanks/Regards, Philippe Cand

Answer 1

Hi Philippe,

Based on my experience and research, change the Service Account to NetWork Service and grant write permission to Network Service account to ASP.net Temp folder. Refer to http://msdn.microsoft.com/en-us/library/aa545633(CS.70).aspx for how to assign write permissioin to the temp asp.net folder. Then, retry to start the services. If the issue persists, if there is no report in report server, remove and reinstall reporting services.

thanks,
Jerry

Answer 2

Thanks Jerry, for the record, here is the story.

the first error I was getting was Access denied.

I found out that when upgrading, the service account got somehow changed to "Networkservice" instead of "Network Service". I could no longer put it back to network service so I changed the service account to a windows account with all access required to asp net temp and rs application folder as well as database. Then I was getting the time out error and asked for help.

I did not follow your advice exactly, I tried to run the "Repair" option so that I would not have to uninstall/reinstall and I did not have the product key.

It turned out that the repair option was kind enough to actually fix the issue. After that The service started automatically and I simply had to restore the rs encrypted key. I did not know the password for the key that was on that server and could not reach the guy who knew it. Never mind, I took the rs key from my development server for which I know the password and I could restore it and regain full control of this report server which uses same connections. Hopefully, this is a pre-production server and I have admin rights for now.

Voila. Have a great week-end

---

Thanks/Regards, Philippe Cand

Answer 3

Hello, i have same problem, but on Wiindows Server 2008 R2, i not found user ASP.Net.