January 11, 2012 at 6:59 am
Hi,
I have today installed a copy of SQL Server 2008 R2 developer edition on my 64 bit windows 7 PC and i'm having a problem with getting the report services service started.
The error in the application log is:
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)
Does anyone have any idea what might be causing this?
I've done as suggested on this link but the repair install option failed stating that the service was not in a state to be repaired because it had never been configured. Changing the user the service run as to the Network Service user and setting the permissions as outlined in the link didn't help any either.
Any help appreciated!
Thanks,
Simon
January 11, 2012 at 7:37 am
Did you miss any warnings in SQL Server installation? I hope the account you used for installation has admin rights in your PC.
If you didn’t load any data on it yet, would you try to install it freshly? Uninstall it, clean the root (SQL Server) folder, reboot & install it back. Just make sure you select all features on feature / component list.
January 11, 2012 at 7:43 am
Hi Dev,
Thanks for that, I did try uninstalling all components, reboot the machine and try again and still got this error, but i didn't clear out the SQL Server directory when i did that, so i could try that but wonder if anyone else has any suggestions before going down this root.
The user i installed as is a local administrator on the PC.
I used to have SQL Server 2005 developer on the machine but uninstalled that completely before installing 2008 R2.
Thanks,
Simon
January 11, 2012 at 7:53 am
If you have a good registry cleaning utility, use it to clean orphan entries after reboot. I usually don’t do it manually & recommend you to do it with tool only.
Also, please don't ignore any warnings in installation. It doesn't stop you but create weird scenes like this. If any confusion, please post the warnings messages here.
January 11, 2012 at 8:26 am
Have you got a reg cleaning utility you would recommend?
January 11, 2012 at 8:39 am
Sorry to say, it’s my policy I don’t recommend / endorse any tool / utility in my posts. Any tool is fine, just don’t do it manually. Also to be on safer side backup the entries before you clean them up (with tool).
January 11, 2012 at 9:38 am
Thanks ok, i'll give that a go when i get chance and report back on the results.
January 11, 2012 at 1:28 pm
How did you install the instance, did you select configure later or to let installer configure
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 12, 2012 at 2:04 am
I let the installer configure with the defaults. Maybe that was my error! 😉
Hope to be able to give this another go at some point later today.
January 12, 2012 at 4:04 am
s_osborne2 (1/12/2012)
I let the installer configure with the defaults. Maybe that was my error! 😉Hope to be able to give this another go at some point later today.
I always prefer a manual configuration myself
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 12, 2012 at 4:41 am
Hi,
Right, i've fixed it without the need to do the reg clean as Dev suggested (although this does need to be done at some point).
The fix was rather simple as it turned out... I uninstalled reporting services and attempted to reinstall it. I got an error that said:
"The SQL Server instance MSSQLSERVER already has an instance id 4 that is different than the specified instance of MSSQLSERVER. Specifying more than one instance ID for the same SQL Server instance is not supported."
This appeared before the feature selection screen so i was stuck. Jumped on google and found this link i deleted the reg key for Instance ID 4 because that was the incorrect one ie. HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Name\RS.
When i then tried to the add features to an existing install option again i was able to install reporting services on it's own selecting manual configuration. Once that compelted 5 minutes later i'd configured reporting services and it's all working sweet as a nut. 🙂
Thanks for your help Perry/Dev. Hopefully someone else will find this thread useful in the future....
Thanks,
Simon
January 15, 2012 at 6:31 am
I am happy you were able to resolve the issue but you achieved with manually editing / deleting registry entries only. Manual Registry Cleanup can crash your system (worst scenarios) and if you are in SLA, IIRC none of the SLA covers this loss (it’s not your case, I know).
It’s a bad practice IMO which is a lot tempting. Please try to control this temptation.
October 23, 2012 at 2:07 am
Hi All,
Even I am facing the same error.
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)
My mistake , there was a collation issue and I unistall sql server Database engine not Reporting service thinking after new installation I will be able to link the reporting service to this instance.
BUt from two days I am not able to configuire RS. I did try to remove from Add / Remove program files but it failed. Even add a new RS also fails.
Please suggest , it is very important .
Cheers,
Got an idea..share it !!
DBA_Vishal
October 23, 2012 at 2:29 am
Hi,
From what you've described, if I were you I'd uninstall SQL Server completely and then reinstall it from fresh with all the features you want.
If you run into problems after that and you can't solve them start a new thread. You'll get better answers that way.
Thanks,
Simon
January 21, 2014 at 9:15 pm
Hi
I had a similar problem, with the same error message, and found it was caused by a corrupted reportserver.config file.
I have described what I found and how it looked here: http://www.sqlservercentral.com/Forums/Topic1533454-1550-1.aspx
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply