Hi Folks,
Hope this helps someone. After upgrading to IE9 and SQL Server 2008 R2 CU7, I found that I couldn't access Report Manager anymore. I found that even though I was in the BUILTIN\Administrators group, that I had to specifically add myself to the Content Managers role in Reporting Services for the root folder of Report Manager. (I have no idea why as it used to work ok) NOTE: I had to do this with UAC turned off, otherwise, Site Settings, etc. were not visible. Remember to turn UAC back on if you did this temporarily.
But the bigger issue was that Report Builder 3.0 would not launch, even after I got the button back on the screen. The message was that I needed to install the .NET Framework 3.5, even though I already had .NET Framework 4.0 installed. Nothing I did seemed to fix the problem.
In the end, the issue is that Report Builder 3.0 will not launch from Report Manager in IE9 unless you enable Compatibility Mode (normally used for older web sites that don't render properly in IE9) for the Report Manager web site. Once I set Compatibility Mode, Report Builder 3.0 launched as expected.
Hope this helps save someone else a bunch of time.
Regards,
Greg
It does seem to me that there's a missmash of what works with what just now. For example I was somewhat upset to discover installing VS2010 removed SQL2008R2 Bids and you can't put it back, then to discover you can't write reports in VS2010 – the fix is to install vs2008. I haven't gone IE9 yet and SSRS R2 is only in early test, but I'm grateful for your post – very useful to know, thanks
Had a similar issue. It all seemed to work if I ran IE as Administrator. Not ideal I know.
Hi Steve, the problem still occurs if you run as admin.
I think it should work….Go to user account control and keep the security level off or low.
Hi Sri, yes, but you don't want to have to run with UAC off to use RS.
Hi Greg, after 4 to 5 hours of research i came with that soution, that one worked for me. Im using the R2 version with windows 7. How abt you?
Hi Sri,
Yes, I can make it work with UAC off but that's not the point. Surely the team can make a version that works with UAC on. You shouldn't have to disable the security of the whole machine to make one app work.
UAC has been with us since Vista.
Regards,
Greg
Thank you very much Greg,it definitely helped me. in my case i was trying to launch report builder 1 and it says .net framework 2 must be installed but i already have .net 4 installed. once i turned on comptability view it worked just fine.
The compatibility view hack is probably related to the new compact user-agent string in IE9 [1].
In normal IE9 mode, the UA doesn't include the installed .NET versions, so the server can't detect whether you've got .NET installed. In compatibility mode, it sends the full UA, including the .NET versions.
[1] http://blogs.msdn.com/b/ie/archive/2010/03/23/introducing-ie9-s-user-agent-string.aspx
See http://www.wiseowl.co.uk/blog/s186/report-builder.htm for how to do this. For what it's worth, I was using SSRS 2008 R2 and Windows 7. I find that running IE as an administrator does get round some security issues.
Thanks 🙂