Article ID: 971268 - View products that this article applies to.
You may encounter the following error message when using Microsoft SQL Server tools such as SQL Server Management Studio (SSMS) or SQL Profiler:
Evaluation period has expired. For information on how to upgrade your evaluation software please go to http://www.microsoft.com/sql/howtobuy
Additionally you may see the following error message when you try to connect to an expired installation of SQL Server instance:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Note The connectivity error message is a generic message, and it is not always tied to an expired installation of a SQL Server instance.
The problem usually occurs when you are running an evaluation instance of SQL Server and the evaluation time period has expired.
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:
How to upgrade an expired installation of SQL Server 2008 Evaluation Edition to a retail version of SQL Server 2008Note For SQL Server 2005, check the following KB article
You receive an error message when you try to upgrade an expired installation of SQL Server 2005 Evaluation Edition to a retail version of SQL Server 2005
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:
Database Detach and Attach (SQL Server)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:
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:
(http://support.microsoft.com/kb/322756)How to back up and restore the registry in Windows
How to check whether SSMS will expire?
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:
SQL Protocols Team blog
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
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: July 12, 2014 - Revision: 4.0