Hi All,
I have Windows 2003 Server with MSSQL 2005 Standard.
I am able to connect via Windows Authentication, but when I try to change it to SQL Server Authentication with user 'sa' I'm then being prompted with the error msg:
A connection was successfully established with the server, but then an
error occurred during the login process. (provider: Shared Memory
Provider, error: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)
Here is the entire list of msgs that are showing up:
===================================
Cannot connect to SOLELL-QGL5PG9D.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
------------------------------
Server Name: SOLELL-QGL5PG9D
Error Number: 233
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.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
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()
Any pointers
-Alon.
Help! getting errors when trying to connect to SQL Server Management Studio
Hot Topic
- problem with custom conflict resolution
- Debugging a script component task???
- How To Avoid Table Scan
- remote instances
- .Net framework for SSRS 2005
- locking semantics on sys.transmission_queue
- Unable to use MS SQL 2000 SA Password
- How to not send subscription report if no data
- Row numbers on export
- Database Version
SQL Server
- Exceeding 1 physical CPU with SQL Server Express
- How aggregations are merged
- Create schemas programatically.
- Problems migrating DTS package
- Large text Insert
- MDX based report parameters misbehave when inter-dependent
- Replication Deadlocks
- Hierarchical data in result set
- Select Distinct
- About Indexes & Where caluse
Help! getting errors when trying to connect to SQL Server Management Studio
Troby
Since I didn't have any database created yet, I've uninstalled MSSQL and Re-installed it.
This time, I made sure it was set to the Mixed Mode.
I don't know if there was a way to verify an early install or if there is a way to change from
Windows Auth Only to Mixed mode, but Uninstalling and Re-installing took only 30 minutes and I had no databases that I needed to check previously,. so that was my solution.
Thanks for the interest.
-Alon.
CarbonFuel
I had this same issue. My MSSQL 2005 server was setup on a port other than the default 1433. Once I added the port number to the connect string, I was able to connect. ie.: SERVERNAME, 9999
Good Luck.
ChrisMorley
Hi,
just for the completion of your answer, the authentication mode can be investigated by using the SQL Server Management Studio and right clicking on the server, choosing the properties and viewing the setting in the Security pane. If you don’t have any visual tool for editing this you can use the registry key
Default instance:
"HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"
to 2 for mixed-mode or 1 for integrated.
Have in mind that changing the setting will need a restart of the server to apply.
HTH, Jens Suessmeyer.
---
http://www.sqlserver2005.de
---
OAF-NOR
I installed the MSSQL a week and a half ago, and I believe it was set to Mixed. I simply don't remember.
Is there a way to know
Can it be changed to Mixed mode in the event that I missed that or do I need to uninstall and re-install from scratch
thanks,
-Alon.
Michael Pang
didi you enable mixed authentication or did you just enable the Windows Authentication
HTH, Jens Suessmeyer.
---
http://www.sqlserver2005.de
---