Link to home
Start Free TrialLog in
Avatar of techques
techques

asked on

A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

Hi

I have a .Net 2.0 web application running several months fine. I use MSSQL 2005 server and asp.net.

Suddenly, I got an error message:
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

Was it hacked?

I checked the shared memory and name pipe started.

Error log:
2009-02-18 12:58:08.15 Logon       Error: 18452, Severity: 14, State: 1.
2009-02-18 12:58:08.15 Logon       Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: <local machine>]
Avatar of Anthony Perkins
Anthony Perkins
Flag of United States of America image

That usually occurs when the connection is dropped.
Kindly Change the Authentication Mode of the SQL server from "Windows Authentication Mode (Windows Authentication)" to "Mixed Mode (Windows Authentication and SQL Server Authentication)".

This should resolve you out.
To do this, Right click Server in SSMS, choose Properties --> Security --> Choose Mixed mode Authentication
ASKER CERTIFIED SOLUTION
Avatar of Anurag Thakur
Anurag Thakur
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of techques
techques

ASKER

it was already Mixed mode Authentication

connection is dropped - It came from the following code:
string strSql = "select * FROM product";
DataSet ds = new DataSet();
try
{
ds = SqlHelper.ExecuteDataset(DBConnection.ConnString, CommandType.Text, strSql);
CollectionPager.DataSource = ds.Tables[0].DefaultView;
CollectionPager.BindToControl = ItemUserControl.PublicRepeaterInUC;
ItemUserControl.PublicRepeaterInUC.DataSource = CollectionPager.DataSourcePaged;
ds.Dispose();
ds = null;
}

Open in new window

hi,
 you could not do any thing for this error due to network connectivity issues only. this is common issue not only for sql server . smtp also you can get this error.
these type situation you could not log this error to database. use some text file based log and find the statistics
 
 
after one hour of the transport level error, it throws another error.

timeout period elapsed prior to completion of the operation or server is not responsing.

as in those time period, the web site needs to process 40 insert records in every 20 seconds

how should i fix it?