Hi.I am running VS2008 enterprise evalution version on XP SP3 with reporting and analysis services running fine.The problem I am facing is when I click the Report Builder Option from Report Manage . I get the error message stating "To use the report builder you must install .NET framework 3.5"I have .NET framework 3.5 installed on my system and running as implied from the below test This machine has the correct version of the .NET Framework 3.5.This machine's userAgent string is: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; SIMBAR={9A33F5AB-FB0B-4036-9CED-E5E16D795253}; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.2; OfficeLiveConnector.1.4; OfficeLivePatch.1.3; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022).Please let me know what I am missing.Also, I am running IE 8.0.6001thanksvineet

SQL 2008 is released with .NET framework 3.5 SP1.Could you have a try after 3.5 SP1 is patched? Or perhaps you have .NET 3.5 SP1 installed, but register value is broken.

Hi qxg--Windows last night automatically detected the avaiable update as .NET 3.5 SP1 and patched it. It is not working even after the SP1. How could I check whether register value is broken? I suspect this to be the case.Thanks.

Check this The .NET Framework 3.5 installer writes registry keys when installation has finished successfully. You can test whether.NET Framework 3.5 is installed by checking the registry keys listed in the following table. Registry key name Value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5 Name:Install Type:DWORD Data:1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform Name: Version Type:REG_SZ Data: .NET CLR 3.5.build number http://msdn.microsoft.com/en-us/library/cc160716.aspx~~ Mark it as Answer if you find it correct~~

I have the very same problem. I just did a repair installation of SQL Server 2008, and a repair installation of the .Net Framework 3.5. This error did not go away (using IE 7).Interestingly enough, I can start the report Builder from Firefox (!). I looked at the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platformregistry key as suggested earlier, but could not figure out how this post would apply. There are currently 3 values at this key, one for each version of .Net. There is no value called "Version".Any suggestions?

I was having same problemI just uninstalled .Net Compact Framework 3.5 with SP1 installed on my system and re-installed from MS site.http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=enIt works!!!Try it, hope it works in your case also.MSDeveloper

If you install SSRS 2008 R2 with #IE9, make sure to set Compatibility View of #IE9. Coz, #IE9 does NOT detect the installed .NET Framework 3.5.Chandana N. Athauda - MVP http://www.yeschandana.com

That worked for me, thanks a lot, I tried to mark your reply as answers, but the "Propose As Answer" doesn't show up.Tareq Ali ITWorx Arabia Technical Consultant

Thanks for posting this. Much obliged. FYI, you can bring up the developer tools using F12 to bring up the compatibility mode change menu.

Thanks for posting this. Much obliged. FYI, you can bring up the developer tools using F12 to bring up the compatibility mode change menu.

THANK YOU, THANK YOU, THANK YOU! I had no idea IE9 was the culprit. I was about to blast the whole computer and start over.

THANK YOU, THANK YOU, THANK YOU! I had no idea IE9 was the culprit. I was about to blast the whole computer and start over.

I am not sure whether this is related or not, but your question has indirectly solved a similar problem so I post what I found in case it helps someone else. I had the same problem when clicking on the Report Builder button in Report Manager on a Windows 7 PC with SQL 2008 R2 Enterprise installed. This had previously worked but when I went to demonstrate it I found it was broken with the same error message. THE CAUSE: Internet Explorer 9!!!!! I had recently installed it. The FIX: run the page in compatibility mode--fixed!

Thank you. You saved me a few hours. I was about to do all sorts of re-installs. Thanks, Vamsi.