Additionally you may see the following error message when you try to connect to an expired installation of SQL Server instance:
Note The connectivity error message is a generic message, and it is not always tied to an expired installation of a SQL Server instance.
Note In the case of SQL Server 2008, you may see this error message even after upgrading to a licensed version because of a known bug.
Case 1 - You have an expired version of SQL server evaluation edition
Note This also applies to scenarios wherein only tools are installed from an evaluation version.
To upgrade the Evaluation Edition to a retail edition, you can consult the following topics in Books Online:
Note In either of these topics, you can select the version picker tool at the top to pick a topic that is relevant to your environment.
Note For SQL Server 2008 you can also refer to the following KB article:
Case 2 - Moving from an enterprise evaluation edition to an express editionIn some cases, you may decide to move from an Enterprise evaluation edition to an Express edition. Since there is no upgrade path available, you can consult the following article on moving your user databases from the evaluation edition to express edition.
Scenario 1 - You are still able to start your SQL Server evaluation versionConsult the following topic in SQL Server Books Online on how to move user databases:Note The maximum relational database size for SQL Express editions is 10 gigabytes (GB).
Scenario 2 - You cannot start an expired edition of your Enterprise evaluation edition because the evaluation period has expiredIf the database size is less than 10 gigabytes (GB), you can follow these steps:
- Install an express edition of the product.
- Locate the data files (mdf and ldf) files for your database.
- Attach these files to the SQL express edition.
Note Before you attach the data files to SQL Express edition, if these files are currently located in the default data directory for the old instance, you may want to move the database files from their current location to either the new data directory for the new installation or to another location on the server.
Case 3 - You are running into this issue in SQL Server 2008 environments even after upgrading to a licensed version of SQL ServerIn this case, you have the following options.
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.
Option 1Apply Service Pack 1 for Microsoft SQL Server 2008 before upgrading the evaluation edition to a licensed edition.
Note If you had already performed the edition upgrade before applying Service Pack 1 for SQL server 2008, you will be required to go through all the steps mentioned in the Option 2 section to resolve the problem. The service pack will only prevent issues that involve future edition upgrades.
Option 2Use 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
- Click Start, click Run, type Regedt32, and then click OK.
- Locate and then click the following key in the Registry Editor:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState
- In the right pane of the Registry Editor, select CommonFiles DWord value.
- On the Edit menu, click Modify.
- Type 3, and then click OK.
- Quit Registry Editor.
- Rerun the edition upgrade procedure to complete the upgrade of all the components to a licensed edition.
- 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
How to check whether SSMS will expire?
- Start SQL Server Management Studio.
- Select the Help menu and then the About… submenu from the list.
Additional pointers on the connectivity errorIf you are encountering the connectivity error in the "Symptoms" section, you can check various posts on the following blog:
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Article ID: 971268 - Last Review: Jul 12, 2014 - Revision: 1