Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Management Studio cannot connect to local SQL Server 2008 on Windows Vista Expand / Collapse
Author
Message
Posted Friday, January 9, 2009 10:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, January 9, 2009 12:24 PM
Points: 2, Visits: 5
Hi,
I have reinstalled SQL Server 2008 developer version on Windows Vista Business a couple of times now. The install seems to be successful. However, SQL Management Studio cannot connect to the named instance. There is a MSSQLServer instance and a named instance on my laptop. I tried to uninstall all SQL Server instances and re-installed. I still find a MSSQLServer instance. I installed a new instance for that reason.

I went into the SQL Configuration Manager and enabled all the network protocols except Via. I read in another article that was the answer to the SQL Server service not starting. The Service is started and yet I keep getting the same error:

===================================

Cannot connect to SYNERGY_V2.

===================================

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

------------------------------
Error Number: 2
Severity: 20
State: 0


------------------------------
Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Can someone please help? I have also got the network protocols for the SQL Native Client enabled.
Post #633628
Posted Friday, January 9, 2009 11:45 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, September 25, 2014 9:07 AM
Points: 774, Visits: 1,191
This is a LOCAL SQL Server instance? if so, Remote Connection should not be an issue

You enabled the TCP/IP in Config Manager for SQL Server Service (not Clients)?

It could be that SQL is running on a different port as well?
You could try enable SQL Server Browser, and re-connect again

what did you type in the Connection Window?
LOCAL\InstanceName?


SQLServerNewbie

MCITP: Database Administrator SQL Server 2005
Post #633737
Posted Friday, January 9, 2009 11:50 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, January 9, 2009 12:24 PM
Points: 2, Visits: 5
I just open SQL Management Studio and accept the defaults. I installed under my userid (I have admin rights on my PC) and the services says to log in under my id. I used Windows Authentication.
SQL Server browser service is also started
Post #633741
Posted Friday, January 9, 2009 12:10 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 9:52 AM
Points: 2,006, Visits: 6,078
Try setting the instance to a particular port and see if you can login using that port, rather than a dynamic one.



Shamless self promotion - read my blog http://sirsql.net
Post #633754
Posted Friday, January 9, 2009 12:14 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 13,872, Visits: 9,596
You mentioned that the server was an instance, but it looks like you aren't using an instance-style server name. Try selecting "browse for more" in the server-name drop-down when you first sign in. The first tab will be available local instances, select the one you want. If it's not listed, that's a problem, but if it is, you should be able to connect.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #633757
Posted Friday, January 9, 2009 12:15 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, September 25, 2014 9:07 AM
Points: 774, Visits: 1,191
Try restart the SQL services?
or try SQLCMD at your Command Prompt to see if it can connect


>sqlcmd -?
Microsoft (R) SQL Server Command Line Tool
Version 10.0.1600.22 NT INTEL X86
Copyright (c) Microsoft Corporation. All rights reserved.

usage: Sqlcmd [-U login id] [-P password]
[-S server] [-H hostname] [-E trusted connection]
[-d use database name] [-l login timeout] [-t query timeout]
[-h headers] [-s colseparator] [-w screen width]
[-a packetsize] [-e echo input] [-I Enable Quoted Identifiers]
[-c cmdend] [-L[c] list servers[clean output]]
[-q "cmdline query"] [-Q "cmdline query" and exit]
[-m errorlevel] [-V severitylevel] [-W remove trailing spaces]
[-u unicode output] [-r[0|1] msgs to stderr]
[-i inputfile] [-o outputfile] [-z new password]
[-f ]] [-Z new password and exit]
[-k[1|2] remove[replace] control characters]
[-y variable length type display width]
[-Y fixed length type display width]
[-p[1] print statistics[colon format]]
[-R use client regional setting]
[-b On error batch abort]
[-v var = "value"...] [-A dedicated admin connection]
[-X[1] disable commands, startup script, enviroment variables [and exit]]
[-x disable variable substitution]
[-? show syntax summary]


SQLServerNewbie

MCITP: Database Administrator SQL Server 2005
Post #633758
Posted Monday, January 26, 2009 7:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, January 17, 2010 1:27 AM
Points: 1, Visits: 8
Even if you have a windows administrator account you are not automatically granted permision to login into the SQL server.

Under confugeration tools, start the surface area configuration manager and give yourself rights
Post #643419
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse