April 10, 2013 at 9:21 am
Hello,
I'm in process of installing several servers with SQL Server 2008 R2 SP2. So far I've completed 5 of them and I'm finding a common issue. That Reporting Services fails to start after applying SQL Server 2008 R2 SP2. I've dug a little bit and have found one Connect post where Microsoft says they cannot reproduce it and several blogs indicating removing this KB resolves the issue.
My question is this, has anyone else ran into this issue and have differing opinions? The information I've dug up seems a bit inconclusive and nothing concrete. I have however uninstalled it from one server and confirmed it now starts successfully.
April 10, 2013 at 10:47 am
This caught my attention as we are planning on installing SQL 2008 R2 SP2 next week.
Did you try changing the timeout setting as GrumpyDBA suggests here?
http://grumpydba.blogspot.com/2012/09/sql-2008-r2-reporting-services-wont.html
April 10, 2013 at 12:01 pm
Thanks for this tip, I have 4 more servers to fix so I'll try this on one of them to see if it works. The odd thing is that Reporting Services did work after the initial installation of the RTM version. It was only after the service pack update they failed. I'll let you know how it goes.
April 10, 2013 at 12:42 pm
I am struggling to remember if it was after SP2 (I think it was) but i certainly hit the same problem where SSRS did not start and there were no error messages (not even a new log), and the registry change above fixed it for me.
I would try that before an uninstall of SP2.
---------------------------------------------------------------------
April 10, 2013 at 2:41 pm
Yeah, an uninstall of SP2 definitely is the last resort (not even considered an option IMO) for me. My prior statement to uninstalling it was in reference to KB266124, not SP2.
April 10, 2013 at 3:05 pm
I'm confused, which KB did you uninstall, (neither number seems correct) and was it a post SP2 patch?
---------------------------------------------------------------------
April 11, 2013 at 12:06 am
george sibbald (4/10/2013)
I'm confused, which KB did you uninstall, (neither number seems correct) and was it a post SP2 patch?
Oops, typo - http://support.microsoft.com/?kbid=2661254
That is the KB number I meant to reference.
April 11, 2013 at 3:40 am
so, to confirm, you were also able to resolve this issue by removing a WINDOWS security patch? (2661254)
---------------------------------------------------------------------
April 11, 2013 at 12:47 pm
george sibbald (4/11/2013)
so, to confirm, you were also able to resolve this issue by removing a WINDOWS security patch? (2661254)
Yes, I removed that security patch and Reporting Services started up with no delay. Here is the original Connect post that lead me to that - http://connect.microsoft.com/SQLServer/feedback/details/774645/windows-hotifx-kb-2661254-breaks-reporting-services-in-sql-2008-r2-sp2.
April 11, 2013 at 12:50 pm
FYI - I will be trying out the recommendation that GrumpyDBA posted that Dan linked to (above). I'll post the findings here.
April 22, 2013 at 11:20 am
Ok, I tried the recommendation by Grumpy DBA and it worked fine just by extending the SCM timeout from the default of 30 seconds to 60 seconds. This was done on a brand new virtual server with the previously mentioned KB article still installed.
November 19, 2015 at 6:35 am
Worked for me thanks...
December 1, 2015 at 6:32 am
Try the link. it took few seconds to resolve.
http://sqldbworld.blogspot.com/2015/11/sql-server-reporting-services-fails-to.html
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply