SQL Server 2008 Evaluation Edition Expired? Believe me, I already upgraded it. What’s up?

Once you install evaluation edition of SQL Server 2008 and then perform in place upgrade to full version, you may get below error message when you open SQL Server Management Studio.


For better search, below is the text of the message

Microsoft SQL Server Management Studio:
Evaluation period has expired. For information on how to upgrade your evaluation software please go to http://www.microsoft.com/sql/howtobuy

Have a close look at error… This is for Management Studio. This means that this is the problem with management studio only. If its not yet expired, inside of Management Studio, going to Help > About... still shows this the expiration countdown.

This is identified as a known issue where SSMS is not upgraded when you do edition upgrade for SQL Server 2008. To workaround the problem you can hack registry keys. Set CommonFiles registry value to 3 in HKLM\SOFTWARE\\Microsoft\Microsoft SQL Server\100\ConfigurationState Registry Hive. You will then need to reinstall (if the tools are not installed currently) or run edition Upgrade. Reference: connect bug

This is already fixed in SP1.

Update: 12 May 2009.

KB article published for same issue. http://support.microsoft.com/kb/971268

Comments (25)
  1. Brian says:

    Thank You, this fixed a major upgrade issue I had.

  2. Rori Stumpf says:

    Thanks, you just saved me a bunch of time.

  3. Dopo l’applicazione dell’SP1 di SQL Server 2008, se avete un’installazione che avete inizalmente installato

  4. eva says:

    BIG FAT THANKS, this worked perfectly!

  5. Balmukund says:

    Thanks Eva, great to know that it helped.

  6. Mos says:

    Thank you for this – My head was spinning trying to figure out why it kept giving the message!!!

  7. Ravenous Bugblatter Beast says:

    Thanks – I thought I was going mad!

  8. Hiren says:

    This is an awesome hack and work perfectly Thanks a lot

  9. lil_kid says:

    You are the Dood… good stuff.

  10. Guy H says:

    Thanks a lot

    work like a charm!

  11. Vijay says:

    Thanks a lot. Great fix . Saved my hair.

  12. Gareth Parfitt says:

    How do I run an "Edition upgrade". I have distribution media but when I run setup.exe it does not offer an Edition upgrade.

  13. Balmukund says:

    1, Insert the SQL Server installation media. From the root folder, double-click setup.exe

    2, To upgrade an existing instance of SQL Server 2008 to a different edition, from the SQL Server Installation Center click Maintenance, and then select Edition Upgrade.

    ref: msdn.microsoft.com/…/cc707783(SQL.100).aspx

  14. hsingh says:

    Thanks guys.. It works like a charm.. struggle with for two days as I was doing it cluster and I was little sacred that it might break my cluster. However Everything went well.. It is working fine now… Thanks again..

  15. William says:

    It is July 2nd, 2010 and I am experiencing the same problem so SP1 did not fix it.  I will try this work around

  16. Balmukund says:

    Hey William,

    Are you saying that you applied SP1 before Edition Upgrade to "full" version and its still SSMS expired?

    How about SQL Engine, is that running?


  17. Ryo says:

    Hello, i have same issues just like this, have hacked the registry value to 3, then i tried to do the "Edition Upgrade" but i couldn't finish the installation. The error's feedback is on SQL Server 2008 edition upgrade which is failed.

    please help me..

    • Ryo
  18. Balmukund says:

    hi Ryo,

    Could you please send me setup logs to my official email id = blakhani (at) microsoft (dot) com ?

  19. k.kowalewicz says:

    Same problems (message) appears on SQLSERVER2008 R2 evaluation version.

    After 2 weeks, the sql server engine is down and management studio is also unavailable. Windows server is also eval version 2008 standard…. why it happens? I just want to eval product for 180 days not to write an essey about windows disability or installation problems.

    Could you help?

  20. Joel says:

    Can anyone help me to know the meaning behind the values 0,1,2,3 of ConfigurationState in the registory hive?

  21. James says:

    thanks for info

  22. Lizardman says:

    I am lookging at the Management console's Help/About and we are on SP2 but still received this error and our cleint did not do and upgrade eval this was a full blown install.  BUt I am verifying that the customer did not eval it then registered it.  But the Version is @ SP2.

  23. Min says:

    Big Thanks!

  24. Damodar Bhattarai says:

    You can use the below registry update to fix the issue. I faced the same problem and after applying this registry able to open SSMS.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server100ToolsClientSetup]

    "SQLBinRoot"="C:\Program Files\Microsoft SQL Server\100\Shared\"


    "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\"









    "VSToolsPath"="C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\"

    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server100ToolsClientSetupCurrentVersion]



    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server100ToolsClientSetupSQLCEBinRoot]

    "3.5"="C:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Tools\"

  25. erick says:

    didn't work for me, but i resolve this problem with uninstall sql server and install again… 😀 hope these help

Comments are closed.

Skip to main content