March 7, 2011 at 8:49 am
The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)
Stack Trace:[SqlException (0x80131904): The client was unable to establish a connection because of an error during connection initialization process before login.
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3618
March 7, 2011 at 9:22 am
Is your client on the same machine as the server? Can you switch to TCP/IP instead? I am not sure, but it seems there was some issue with named pipes not being allowed by default from remote machines.
March 7, 2011 at 9:36 am
Steve,
Thanks for your reply. Client & the server are different machines. Its already in TCP/IP.
March 7, 2011 at 9:41 am
Not according to the error you posted. The provider is named pipes.
Can you explain better what your setup is?
March 7, 2011 at 12:26 pm
Steve,
I'm on the client pc (local) working in .net platform and this application was developed 5 years ago and it doesnt gave me an error in the past. The Production Database server is based remotely. This particular .net application is designed in such a way that when the user post their comment, it will be stored in the database table. Whenever you want to see the comments posted on that particular date the user selects the date and they can see all the comments posted for that day in their intranet portal.
I am not an admin to the production database. I am a user and have limited access (view/read) access to the dabase. When I talk to the DB guys they are saying that the Network Protocol TCP/IP is enabled for MSSQLSERVER.
We are getting this error every once/twice in a week or 15days once and then if you logoff/restart the client PC or wait for 5-10 and again if u access the page means its working.
Thanks.
March 7, 2011 at 12:34 pm
The protocol used is dependent on the client and server. It's possible that you have this client using named pipes and for some reason it flakes out at times. It's possible something was changed recently.
You haven't provided enough technical information to dig further in here. When it occurs, can you perform other connections to the server? Have you tried a simple connection from the Control Panel data sources applet to see if the server is visible?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply