Resolved ?Anoop C Nair

Resolved ? Anoop C Nair Yes thanks!

Glad to hear that it's resolved!!Anoop C Nair

Hello - Check sitecomp.log for more details?Anoop C Nair

Hello - Check sitecomp.log for more details? Anoop C Nair I dont see anything in there that is suspicious. That log hasn't been updated in 3 months. I did see something in the sitestat.log though $$<SMS_SITE_SYSTEM_STATUS_SUMMARIZER><Fri Jan 14 12:57:44.576 2011 Central Standard Time><thread=5832 (0x16C8)> omGetServerRoleAvailabilityState could not write to the registry on LEWSQL2; error = 5: $$<SMS_SITE_SYSTEM_STATUS_SUMMARIZER><Fri Jan 14 12:57:44.608 2011 Central Standard Time><thread=5832 (0x16C8)> ---->: Failed to get the Availability State on server LEWSQL2 for role SMS SRS Reporting Point. Any ideas?

Oh that is interesting. Try to restart the Site compoment service and monitor the Sitesomp.logAnoop C Nair

I am having an issue getting SRS install on my sql server. My setup 1. SCCM running server 2008 2. SQL server running server 2008 R2 and SQL 2005 I have tried this exact same setup on a test enviroment and it works great of course . When I deployed it on live I ran into an odd issue. When I added the role to the server here is what happens under component status. Thread state= Stopped Startup Type= AutoStarting Availability = Unknown I right click and do a show messages and click all. Nothing shows up. There is no SRS log on the sql server like my test enviroment. It seems like it is not even trying to install the roll. Any Ideas? When I browse to http://sqlserver/reports that show up fine so I know reporting services is working, just the SCCM side of it is not installing.

Oh that is interesting. Try to restart the Site compoment service and monitor the Sitesomp.log Anoop C Nair That did it, weird

Great, I had a similar issue I resolve it and now :It works thanks for help !