SQL Server cannot connect to (local) problem resolution

Today, when using the database, suddenly found that SQL Server08 incredibly connected. Question:

So in the online search for this problem, found that there are many similar questions, since the problem is not a few people, it seems that the problem is worth studying.

There are many possibilities for this problem. Let's start by providing a post to see if you can solve your problem here:

http://bbs.csdn.net/topics/390004720

If not. Then there's good news and bad news. The bad news is that you have been fooled by a lot of people, even to see a lot of users to unload load 08, and even someone to re-install the system ...

I also met this problem, I calmly analyzed for a while, think that everyone to solve the problem of the idea may not be right. So I used a different approach. The good news is this, with me the following method, you can certainly solve.

* Note: Only if your question on the previous page or the method you tried cannot be solved can prove to be the same problem as me, using the following method will be effective.

1. First we notice that the connection is always selected (local) and is not likely to change. And recently the computer has not been installed other plug-ins.

2. We check the existing software to see if there are any other plugins (using the 360 software uninstall feature, you can see all the plugins on the computer)

3. Open the SQL Server configuration:

3. To see if the service is enabled, the so-called service (the arrow pointing to that) is the database entity you created. ：

4. If you see the above interface, please skip to step 6, if your interface window is displayed in the red word "unable to.", then most of the plug-in is affected, this time you just opened the 360 software uninstall in the following key words of the plugin uninstall:

(Microsoft SQL Server (DB))

5. After uninstalling run regedit , locate hkey_local_machine\software\\microsoft\microsoft SQL server\100\configurationstate , change the key value of Commonfiles to 3

6. Start the SQL Server (XXX) service, and XXX represents the database entity you created.

7. If discovery fails to start, open manage-to-service in Control Panel, locate the following arrow pointing to the service, click Start:

7. If unable to start, error 17051, then open:

8. Choose Maintenance-"version upgrade then follow the next step of the interface, note that the upgrade will let you choose to upgrade the database entity, select the previous xxx can. Here I provide two keys to everyone:

(Development version) Developer:pttfm-x467g-p7rh2-3q6cg-4dmyb

(Enterprise Edition) ENTERPRISE:JD8Y6-HQG69-P9H84-XDTPG-34MBB

In general, choose an upgrade scenario for the latter Enterprise Edition.

9. Complete the upgrade, re-start the entity service as per step 7, then start the service as per step 3, OK, now try to connect your database, it's amazing!

I ' m Leifeng who Nerver told them name with good job.