Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

SQL 2008 R2 Report services won't start Expand / Collapse
Author
Message
Posted Thursday, January 12, 2012 4:41 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Monday, April 07, 2014 1:34 AM
Points: 702, Visits: 2,163
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




MCSA: SQL Server 2012
Follow me on Twitter: @WazzTheBadger
LinkedIn Profile: Simon Osborne
Post #1234657
Posted Sunday, January 15, 2012 6:31 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, January 30, 2014 12:01 AM
Points: 2,013, Visits: 1,581
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.


Dev

Devendra Shirbad | DBA / Data Architect | Ex-Microsoft CSS (SQL 3T)
LinkedIn: http://www.linkedin.com/in/devendrashirbad
Post #1236288
Posted Tuesday, October 23, 2012 2:07 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 7:52 AM
Points: 89, Visits: 451
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
Post #1375885
Posted Tuesday, October 23, 2012 2:29 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Monday, April 07, 2014 1:34 AM
Points: 702, Visits: 2,163
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




MCSA: SQL Server 2012
Follow me on Twitter: @WazzTheBadger
LinkedIn Profile: Simon Osborne
Post #1375898
Posted Tuesday, January 21, 2014 9:15 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 8:45 PM
Points: 61, Visits: 301
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
Post #1533455
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse