SQL Server cannot connect to the (local) Problem resolution method

Today, when using the database, I suddenly found that SQL Server08 is not connected. The problem is seen:

So I searched the internet for a bit of the problem. Found that there are very many similar questions, since this problem is not a few people, it seems that the problem is worth studying.

There are very many possibilities for this problem.

Provide a post first. See if you can solve your problem here:

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

Suppose 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 people to solve the problem of the idea may not be correct. So I took a different approach. The good news is this, with me the following methods, you will be able to solve.

* Note: Talent proves to be the same problem as me only if your question is not resolved on the previous page or the method you tried. Use the following methods to 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 function, you can see all the plugins on the computer)

3. Open the SQL Server configuration. What you see:

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

What you see:

4. Suppose you see the above interface. Please skip directly to step 6. Suppose your interface window shows the red word "can't.", then most of it is affected by the plugin, this time you just opened the 360 software uninstall in the following keyword plug-in uninstall:

(Microsoft SQL Server (DB))

5. After uninstalling execute 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. Suppose the discovery fails to start. Open manage-to-service in Control Panel. Locate the service that the following arrow points to. Click Start:

7. If you cannot start, error 17051. Then open:

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

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

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

Generally speaking. Select an upgrade scenario for the latter Enterprise Edition.

9. Upgrade complete. Start the entity service again as per step 7, and then start the service as per step 3. Ok. Now try to connect to your database. It ' s amazing!

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

SQL Server cannot connect to the (local) Problem resolution method