CFF KB - Carrz-Fox-Fire Promotions Knowledge Base
CFF KB is all about 1 thing: The Sharing of Knowledge and the Power we gain from it.Knowledge Base
- Breadrumbs:
Microsoft SQL Server Management Studio Failed to connect to server
- Article ID:
53 - Date Created
Wednesday, November 24, 2010 - This Article Has been Viewed
2755 times - Short Desc
When you loose connection with SQL Server from Microsoft SQL Server Management Studio you will get the Failed to connect to server error. - Details
When using Microsoft SQL Server Management Studio 2005 and other possible versions, you may loose connection with the server, if this happens, you will receive this error.
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
Failed to connect to server CARRZ-DEVELOPER. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2) - Recreate Issue
If you leave the Microsoft SQL Server Management Studio running for a long period of time, it may loose connection to the Server, if and when this happens, you will get this error.
This can also accure if the system you have installed SQL Server on is faulty or becomes unstable due to driver issues or other program type issues. - Resolve Issue
To correct this issue, perform one of the following Scenarios.
Scenario #1:
Close out of Microsoft SQL Server Management Studio and the re-open it.
Scenario #2:
Restart your computer, this resets everything for a fresher and cleaner running system.
Scenario #3:
If the above 2 Scenarios do not work, and you continue to experiance this issue, then you will need to reinstall SQL Server all together on the machine.
This can be done without reinstalling the OS it is on.
Simply uninstall SQL Server (Backup your Database's first)
Then Reinstall the SQL Server version on your system.
Share With Friends (Updated 6-8-2010)
Recent Articles
All Topics
- Coming Soon - Knowledge Exchange
Trending Articles
- Microsoft VBScript runtime error '800a0046' Permission denied FileSystemObject 24694
- Microsoft OLE DB Provider for SQL Server error '80040e57' String or binary data would be truncated. or The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data. 21297
- ADODB.Parameters error '800a0e7c' Parameter object is improperly defined 19544
- After Effects warning: Audio conforming failed for the following file .cfa. Perhaps due to disk space 17785
- The backup set holds a backup of a database other than the existing 16825