The solution to the problem with SQL Server evaluation period _MSSQL

However, when you open the system before knocking, always error, unable to proceed. After checking, it turns out that there is a problem with your own database and cannot connect to the database. Turn on SQL Server2008 and always report this error:

The problem arises, you have to solve it, so start to find information on the Internet. Also really found the relevant solution, followed by step-by-step steps, but still can not repair. This can make me anxious, because the installation of SQL Server is a very troublesome thing, but also to uninstall before the clean, and some people because the uninstall is not clean and reload the system. Fortunately, the solution was found after multiple searches.

Workaround: Open the Configuration Tool--sql Server Installation Center

Select Maintenance--Version upgrade

According to the prompts to operate, when you need to enter a key, you can search the Internet a lot of keys, the other just click the next step on the line, and finally prompted the upgrade success. This solves the problem.
If the above steps are still unresolved, you will need to modify the information in the registry:
The Commonfiles value in hkey_local_machine/software/microsoft/microsoft SQL server/100/configurationstate is changed to 3.

After the modification, and then according to the above steps to operate (at this point you can try to open the first, if you are not able to follow the steps).
After this step, my problem was solved and I was able to open SQL Server, but the problem followed:

This problem has been encountered before, but also to help people solve, relatively easy to point.
Still open Configuration Tool--sql Server Configuration Manager

View whether the status of Named Pipes and TCP/IP in the MSSQLSERVER protocol is enabled and if not, manually enable

Then open the SQL Server service, but I have another problem:

There should have been a lot of content here, but we don't know why the remote procedure call failed. No way, only to find information on the Internet again. A lot of people have asked similar questions, some say can only reinstall, but also some said that the direct loading system. Look at others are asking questions, and no one can give a solution, to tell the truth, at that time the heart is cold half ah. However, it is good to have patience to find a way, one solution is to uninstall a software in SQL Server

I took the hint and unloaded it with the idea of reloading without success. The exciting is that after unloading, and really successful. Then check to see if SQL Server (MSSQLSERVER) is started, if it does not still need to be started manually.

Finally, the problem was solved satisfactorily. Although spent a lot of time and energy, but also learned a lot of things. SQL Server can be said that we often use the software at this stage, each time will not be able to avoid all kinds of problems, encounter problems to solve problems, this is our growth and harvest a process.