Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 connection error

Author  Topic 

Mickoni
Starting Member

8 Posts

Posted - 2007-07-11 : 07:03:09
Scenario:
A website (on the same server) connects to our SQL 2005 server:
The connection string: <add key="ConnectionString" value="server=sqlserver.address.co.uk;database=DBNAME;uid=SQLUSER;pwd=SQLPASSWORD;Pooling=false;"/>

However, every so often (maybe 4 times in the first 2 months) the website cannot connect to the DB. Trying to connect to the DB through Server Management Studio, the following error appears. *ALL* other DBs continue to work.

"A connection was successfully established with the server, but then an error occurred during the login process"
"No process is on the other end of the pipe"

Under the "SQL Native Client Configuration" I have the client protocols listed as follows:
Shared Memory 1
TCP/IP 2
Named Pipes 3

(Although Named Pipes is disabled in "SQL Server 2005 Network Configuration")

The only thing to get it up an working again is to reboot the whole server. Restarting the MSSQLserver service doesnt fix it.

Any ideas?

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-11 : 12:47:02
Did you connect with tcp/ip?
Go to Top of Page

Mickoni
Starting Member

8 Posts

Posted - 2007-07-12 : 05:05:27
Well, the webuser got the following message:

"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)"

I'm not sure why only this DB would stop working. It is about 500MB in size and much larger than any other DB on the server.
Go to Top of Page

ratheeshknair
Posting Yak Master

129 Posts

Posted - 2007-07-13 : 07:56:35
Try giving the exact name oF the instance ..that is MACHINE NAME\INSTANCE NAME.If u r using SQLEXPRESS then give MACHINE NAME\SQLEXPRESS..

RKNAIR
Go to Top of Page
   

- Advertisement -