How to solve the problem that has passed the evaluation period of SQL Server, SQL Server

How to solve the problem that has passed the evaluation period of SQL Server, SQL Server

However, when you open the system you have previously typed, an error is always reported and cannot be performed. After checking, it turns out that the database has a problem and cannot be connected to the database. When SQL Server2008 is enabled, the following error message is always reported:

When the problem occurs, you have to solve the problem, so you can search for information online. I have found a solution and followed the steps Step by step, but it still cannot be repaired. This can make me anxious, because installing SQL server is a very troublesome thing, but also to uninstall the previous clean, some people because the uninstallation is not clean and reinstall the system. But fortunately, after searching for multiple parties, we found a solution.

Solution: Open the configuration tool-SQL server Installation center.

Select maintenance-Version Upgrade

Follow the prompts to perform the operation. When you need to enter the key, you can find a lot of keys on the Internet. For other keys, you only need to click Next. The upgrade will be successful. In this way, the problem can be solved.
If the above steps still cannot be solved, you need to modify the information in the registry:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft SQL Server/100/ConfigurationStateThe value of CommonFiles in is changed to 3.

After the modification, follow the steps above (you can first try to open it, if not, follow the steps ).
After this step is performed, my problem is solved successfully, and the SQL server can be opened, but the problem arises again:

This problem has been encountered before and solved by some people, which is relatively easy.
Still open the configuration tool-SQL server Configuration Manager

Check whether the statuses of Named Pipes and TCP/IP in the MSSQLSERVER protocol are enabled. If not, manually enable them.

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

There should have been a lot of content here, but I don't know why the remote process call failed. No way. You can only search for information online again. Many people have asked similar questions. Some say they can only reinstall the system, and some say they can directly install the system. Looking at other people's questions, no one can give a solution. To tell the truth, my heart was cool. However, it's better to be able to work on it. One solution is to uninstall a software in SQL server.

I loaded my mind when I failed to do so. The exciting thing is that, after the uninstallation, it was actually successful. Then, check whether SQL server (MSSQLSERVER) is started. If not, manually start it.

Finally, the problem was solved successfully. Although I spent a lot of time and energy, I learned a lot from it. SQL Server can be said to be the software we often use at this stage. Every time we encounter various problems and solve them, this is a process of our growth and success.

Articles you may be interested in:

• How to solve the MySQL server has gone away problem
• SQL Server 2008: how to set the change problem when saving a table that requires a new table Creation
• Solutions and serial numbers that have passed the sql2008 evaluation period
• How to solve the problem of installing sqlserver 2000 in win2008 r2
• How to solve the problem that the SQL Server database becomes inaccessible to a single user
• MySQL prompt: Solution to The server quit without updating PID file problem
• How to solve the problem of MySQL remote connection loss (Lost connection to MySQL server)
• SQL statement optimization and efficiency in SQL Server
• Solve the problem that SAS accounts of different versions of SQL Server cannot log on
• SQL Server database prompts "tempdb" log is full solution