SQL Server Evalution Copy period has been Expired


Todas las respuestas

  • Hi

    Looks like to have some Evaluation Edition components installed. 

    Try with the SQL 2008 R2 installation DVD and run an UPGRADE. I was able to fix this problem when I faced it

    Javier Villegas | @javier_vill

    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

    miércoles, 28 de marzo de 2012 13:02
  • Hi limon,

    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.

    For more information, please refer to

    In addition, please check and


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

    jueves, 29 de marzo de 2012 11:09
  • Hi Limon,

    This issue occurs after doing an in-place edition upgrade ( of a SQL Server 2008 evaluation edition to any licensed edition, the SQL Server Management Studio and SQL Server Profiler tools that might have been optionally installed locally on the system, will still report the following error message after the evaluation period of the original edition had expired.

    Evaluation period has expired. For information on how to upgrade your evaluation software please go to (

    Note You will also notice this issue on systems where you had originally installed the evaluation edition of the shared tools and later upgrade to a licensed version.

    Microsoft has confirmed that this is a bug in the Microsoft products .

    You have the following two options to fix the problem. 

    Option 1

    Apply Service Pack 1 for Microsoft SQL Server 2008 before upgrading the evaluation edition to a licensed edition.

    Note If you had already done the edition upgrade before applying Service Pack 1 for SQL server 2008 you will be required to go through all the steps mentioned in Option 2 below to resolve the problem. The service pack will only prevent issues with future edition upgrades.

    Option 2

    Use the following procedure to fix the issue:

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

    322756 (  How to back up and restore the registry in Windows
    1. Click Start, click Run, type Regedt32, and then click OK.
    2. Locate and then click the following key in the Registry Editor:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState
    3. In the right pane of the Registry Editor, select CommonFiles DWord value.
    4. On the Edit menu, click Modify.
    5. Type 3, and then click OK.
    6. Quit Registry Editor.
    7. Rerun the edition upgrade ( procedure to complete the upgrade of all the components to a licensed edition.
    8. After the edition upgrade is complete, refer to the following Knowledge Base article to prevent issues with future updates to the instance.

      970608 (  Updates to Microsoft SQL server 2008 will fail after an edition upgrade.

    KB article published for same issue.

    Hope this helps!!!

    Regards, Vishal Srivastava

    jueves, 29 de marzo de 2012 12:42
  • Hi,

    Javier, Maggie and Vishal

    I have already try upgrade by original DVD. But it not fix. Also i tried by registry Edit by Value 3 but not solve and face some problem when registry edit value 1 to 3. I want to fix it without reinstall because its contain important data and this is running machine.

    Have any solution without reinstall.

    Thanks, Limon Dhaka,Bangladesh

    sábado, 31 de marzo de 2012 3:48
  • I have fixed this by uninstall newly install and configuration.

    Thanks, Limon Dhaka,Bangladesh

    • Marcado como respuesta limon Dhaka martes, 17 de abril de 2012 8:04
    martes, 17 de abril de 2012 8:04