July 28, 2011 at 12:20 pm
Starting from Sql Server 2000 and 2005 already installed,
I launched the New Installation choice from the Sql Server 2008 R2 install program.
The Installation Step stopped almost immediately with this message:
"Version string portion too short or too long".
I really don't know what to do.
Has anybody experienced such an error message?
Thank you
Roberto Botto
July 28, 2011 at 2:37 pm
Look at the last post on the following link.
http://forums.iis.net/t/1166244.aspx
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 29, 2011 at 1:02 am
Thank you
I tried the suggestion posted on the site, that is copied hereafter.
I deleted a couple of entries in the Registry,
but the error persists
------
Solution: Open Registry and navigate to:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform
The “version portion string” the error message is referring to is basically a list of the .NET versions that are installed on your machine and it has a limit of 256 characters. Due to the number of .NET versions on your machine, the string was getting truncated and therefore causing the application to throw that error when browsing to the Report Manager. So, first export your entire Post Platform directory in your registry in case you’d ever need to revert to it and then delete the following registry keys under that directory:
1) .NET CLR 3.0.04506.30
2) .NET CLR 3.0.04506.648
3) .NET CLR 3.5.21022
The reason why I selected these 3 is that there are newer builds of those versions already registered on your machine. Reboot your machine and the Report Manager should work now.
You should only leave the latest version of each Framework version key in here, and delete the older ones.
---------
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply