sql server connect: A transport-level error has occurred when receiving results from the server. -- sql server connect

A transport-level error has occurred when receiving results from the server.

Audrey Ng
4/23/2007 1:27:10 PM

sql server connect:

Hi all,

I am getting the error below:
I would like to also mention that this error is occuring randomly. I am
running a web application under SQL Server 2005 and .NET framework 2.0.
Has anyone encountered this issue.

Error occurred during report data retrieving and binding.
The actual error message is:

A transport-level error has occurred when receiving results from the
server. (provider: TCP Provider, error: 0 - The specified network name
is no longer available.)

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
Boolean breakConnection) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateO
bject stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateOb
ject 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.ReadByte()
at System.Data.SqlClient.TdsParser.GetTokenLength(Byte token,
TdsParserStateObject stateObj) at
System.Data.SqlClient.TdsParser.GetDataLength(SqlMetaDataPriv colmeta,
TdsParserStateObject stateObj) at
System.Data.SqlClient.TdsParser.ProcessColumnHeader(SqlMetaDataPriv col,
TdsParserStateObject stateObj, Boolean& isNull) at
System.Data.SqlClient.SqlDataReader.ReadColumnHeader(Int32 i) at
System.Data.SqlClient.SqlDataReader.ReadColumn(Int32 i, Boolean
setTimeout) at
System.Data.SqlClient.SqlDataReader.GetValueInternal(Int32 i) at
System.Data.SqlClient.SqlDataReader.GetValues(Object[] values) at
System.Data.ProviderBase.DataReaderContainer.CommonLanguageSubsetDataRea
der.GetValues(Object[] values) at
System.Data.ProviderBase.SchemaMapping.LoadDataRow() at
System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping) at
System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable
datatable, String srcTable, DataReaderContainer dataReader, Int32
startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object
parentChapterValue) at System.Data.Common.DataAdapter.Fill(DataTable[]
dataTables, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior) at
System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32
startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior
behavior) at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at private_enterprise_report_cmn_RepricingSummary.Page_Load(Object
sender, EventArgs e) in

Re: A transport-level error has occurred when receiving results from the server.

Sue Hoegemeier
4/23/2007 8:52:49 PM

You would want to check the SQL Server error logs to make
sure it's not a refused connection from an issue like full
logs, out of disk space, etc. Those would be in the SQL log.
If you don't have anything there and it's random then you
may be experiencing network burps and dropping connections.
You can following the troubleshooting steps in the following
article:
How to troubleshoot network connectivity problems
http://support.microsoft.com/?id=325487

-Sue

On Mon, 23 Apr 2007 13:27:10 -0700, Audrey Ng
[quoted text, click to view]

Re: A transport-level error has occurred when receiving results from the server.

Audrey Ng
4/24/2007 6:32:28 AM

I'm not sure if this is related to the issue but when I do try to
connect to my database server from a Remote Management Studio. I get the
same error

"A transport-level error has occurred when receiving results from the
server...."

Any ideas?

Re: A transport-level error has occurred when receiving results from the server.

Sue Hoegemeier
4/25/2007 7:23:03 PM

You still need to go through the other steps - check the
logs, check the network connectivity, etc.

-Sue

On Tue, 24 Apr 2007 06:32:28 -0700, Audrey Ng
[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.