Home Dashboard Directory Help
Search

Evaluation Expired unable to use Management Studio by Jamie Downs


Status: 

Closed
 as Fixed Help for as Fixed


13
1
Sign in
to vote
Type: Bug
ID: 415898
Opened: 2/18/2009 1:25:03 AM
Access Restriction: Public
3
Workaround(s)
view
8
User(s) can reproduce this bug

Description

Having run the Edition Upgrade process on RTM Evaluation Instances. I am unable to upgrade the SSMS, the SQL Server Engine upgrades but I am unable to get the management studio to work.
Details
Sign in to post a comment.
Posted by Microsoft on 1/31/2012 at 2:44 PM
Thanks James for verifying the workaround. We will consider making a fix for this in a future release.

Thanks,
[SQL Server Team]
Posted by James Snape _BNPP_ on 11/11/2010 at 5:50 AM
This repros on SQL 2008 R2 (and the workaround is fine too).
Posted by wueltschey on 4/2/2009 at 2:46 PM
I had this issue on my laptop where I had SQL 2008 Express installed. I also had the full version of SSMS installed, since I attach to our server running MSSQL 2008 Standard. We upgraded the server to the from the trial to full standard version, but I couldn't update the tools installed on my laptop. The above solution didn't work for me. There was a problem with the checksum one of the registry keys. Running the following registry patch fixed the problem.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup]
"SQLBinRoot"="C:\\Program Files\\Microsoft SQL Server\\100\\Shared\\"
"checksumref"=""
"SQLPath"="C:\\Program Files\\Microsoft SQL Server\\100\\Tools"
"SqlToolsPath"="C:\\Program Files\\Microsoft SQL Server\\100\\Tools\\Binn\\VSShell\\Common7\\IDE\\"
"Path"="C:\\Program Files\\Microsoft SQL Server\\100\\Tools\\Binn\\"
"checksum"=hex:38,38,33,66,66,66,30,65,62,38,32,62,30,34,37,62,31,30,35,31,36,\
38,32,31,30,30,63,64,36,37,34,31,65,31,38,31,37,35,62,36,38,31,33,38,62,33,\
32,62,61,37,39,36,65,61,37,65,66,36,38,39,63,35,38,39,32,31,39,32,38,35,62,\
36,61,31,61,38,35,36,31,63,65,34,63,37,39,65,35,65,30,38,32,66,62,32,30,31,\
39,66,63,36,62,31,34,64,35,34,36,39,34,30,39,39,33,34,63,30,38,35,34,39,30,\
36,37,36,35,64,33,38,61,62,38,64,39,39,33,33,65,39,65,32,31,39,30,37,38,63,\
38,36,64,36,66,64,65,65,33,39,39,61,63,33,32,32,38,37,36,63,30,61,33,64,65,\
66,64,31,35,37,34,38,00
"VSToolsPath"="C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\IDE\\PrivateAssemblies\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup\CurrentVersion]
"CurrentVersion"="10.0.1600.22"
"Language"=dword:00000409

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup\SQLCEBinRoot]
"3.5"="C:\\Program Files\\Microsoft SQL Server Compact Edition\\v3.5\\Tools\\"
Posted by Jonathan Kehayias on 2/20/2009 at 12:31 PM
See the following blog post that shows exactly how this can be fixed. I tested this on a VPC to validate and test the solution to the problem:

http://sqlblog.com/blogs/jonathan_kehayias/archive/2009/02/20/sql-server-2008-evaluation-edition-expiration-woes.aspx
Posted by Microsoft on 2/20/2009 at 9:08 AM
I've closed this bug duplicate of a known issue. This issue will be fixed in our Katmai SP1. Until then to work around the issue you can update the CommonFiles Registry Value to 3 in the HKLM\SOFTWARE\\Microsoft\Microsoft SQL Server\100\ConfigurationState Registry Hive.

Thanks,

Amy Lewis
Posted by Jonathan Kehayias on 2/20/2009 at 6:07 AM
See the work arounds for how to get around this issue. You can make a single registry change to get the upgrade installed.
Posted by jjs781_yahoo.com on 2/19/2009 at 11:53 AM
Yep, same issue. BIDS opens fine, but Management Studio displaying "Evaluation period has expired" although this was upgraded to the Enterprise Edition prior to expiration. OS: Windows 2003 EE SP2. Running on VM.
Posted by Renatuzz on 2/19/2009 at 5:32 AM
Same Message after Edition Upgrade to Standard from expired Trial (Windows XP). Reinstallation from DVD does not helped.
Posted by B11FE44C-3137-4997-8794-0D065C280689 on 2/19/2009 at 2:52 AM
Have the same issue in a customers environment after Edition Upgrade to Standard from Trial. Only difference is they run Server 2008 Standard x64. TRied reinstalling Mgmt Studio from scratch without result.
Sign in to post a workaround.
Posted by Alejandro Leguizamo on 10/10/2012 at 4:18 AM
This issue is still affecting SQL Server 2012. The procedure works for RTM. However, in a multiple instance environment, selecting the option to update "only shared components" also works. (And might save some time)

Tested in an environment with multiple instances of SQL Server 2008 , R2 and 2012 side by side.
Posted by Jonathan Kehayias on 2/20/2009 at 6:06 AM
There is an issue where Edition Upgrade does not work for SSMS.

To workaround for this issue set CommonFiles registry value to 3 in HKLM\SOFTWARE\\Microsoft\Microsoft SQL Server\100\ConfigurationState and run Edition upgrade again.
Posted by Renatuzz on 2/19/2009 at 6:50 AM
Reinstallation after _complete_ removing with manual deleting subfolder "Microsoft Sql Server\100" and registry entries "Microsoft Sql Server\100.." worked for me.
File Name Submitted By Submitted On File Size  
Detail.txt (restricted) 2/18/2009 -