• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 510
  • Last Modified:

A transport-level error has occurred when sending the request to the server.

The following is the 2nd posting for this issue and it was fortunately resolved.

http://www.experts-exchange.com/Programming/Languages/.NET/Visual_Basic.NET/Q_26219810.html

However, I have run into it again.  I have an existing client who had (5) Windows XP workstations with a Windows XP 'server' in a workgroup environment.  They were running gigabit speed.  At that time I NEVER received transport-level errors from any of the workstations.

Six months ago, I replaced all machines with Dell Vostro's with Windows 7 Professional 64-bit machines including the glorified server where the SQL Express 2008 R2 database is installed.

My VB.NET application was re-installed with the same version executable.

I IMMEDIATELY began to receive these errors.  Generally 1-2 per day.  Sometimes skipping a day. My original posting/solution involved a true Win 2003 Server with a Broadcom NetXtreme adapter where I disabled TCP Chimney Offload.  I just identified that these Dell machines have a 'Broadcom NetLink (TM) Gigabit Ethernet' adapter.  We're now talking about another Broadcom adapter but not within a Windows Server OS.

Has anyone seen this adapter cause issues and does the TCP Chimney Offload exist within the Win 7 OS?

Sincerely, Phil
Transport-Protocol.txt
0
TSFLLC
Asked:
TSFLLC
1 Solution
 
Racim BOUDJAKDJIDatabase Architect - Dba - Data ScientistCommented:
What is the common network element between the two architectures ? switches ports...
0
 
TSFLLCAuthor Commented:
Are you asking what are the common components between the workstations and the PC with the SQL database they are connecting to?  10/100/1000 DLink switch.

And to reiterate.  The only changes are new PCs and different operating systems....Period.

Also, the protocols used with SQL Express as such:

Shared Memory - Disabled
TCP/IP - Enabled
Named Pipes - Disabled
Via - Disabled


I just remoted back into the SQL box.  Noticed something disturbing.  May be nothing.
Notice the attached file & the power management settings.
BroadCom-Details.PNG
0
 
CodeCruiserCommented:
SQL Express does not allow network connections by default. Did you change that by going into Surface Area Configuration? Are the ports open? Enable all the protocols. Also start the SQL Browser service.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
TSFLLCAuthor Commented:
CodeCruiser, this customer's been using my software for years.  The only thing that changed was the computers themselves.
0
 
senadCommented:
How are you connecting to the server (server name) ? It might be that the application is getting the server name wrong.
Checked this ?
http://social.msdn.microsoft.com/forums/en-US/sqldataaccess/thread/9609559d-f7ce-4bd8-97d0-0003ff7c9c98/
I installed 2012 version (default instance) and the instance became my computer name. So I had to change the connection string.
0
 
Ramesh Babu VavillaCommented:
check you database engine is running or not

user services.msc

if your sql service is already started. use ip address the access
0
 
TSFLLCAuthor Commented:
senad, sqlservr,

I appreciate your postings.  However, this company has been up and running day-in/day-out since I put these new computers in.  There are no problems with the database name, service not running.

I happen to be in their office the other day taking care of a problem not related to any of this when the manager had my application up and running, he left the office for about 20 minutes, came back and it generated another transport protocol error.

The issue is with the application having a connection open with no activity for a period of time.  THIS IS THE ROOT OF THE PROBLEM.

Unless I create an auto-logoff function or create a timer that hits the database every 30/60 seconds this problem will continue.  I welcome any other ideas or past experiences in how to resolve this.

Thanks.
0
 
TSFLLCAuthor Commented:
This is my workaround for dealing with this issue.  Testing connection and attemting to recreate.  Thanks to everyone who helped.

Sub()

       da.SelectCommand = New SqlCommand
       da.SelectCommand.Connection = TMSConnection

End Sub


    Public ReadOnly Property TMSConnection() As SqlConnection
        Get
            Dim da As New SqlDataAdapter
            Try
                da.SelectCommand = New SqlCommand
                da.SelectCommand.Connection = TSFConnection
                da.SelectCommand.CommandType = CommandType.Text
                da.SelectCommand.CommandText = "SELECT config_id FROM tbl_config"
                da.SelectCommand.ExecuteNonQuery()

                If IsNothing(TSFConnection) Then
                    OpenConnection()
                End If
                If TSFConnection.State = ConnectionState.Closed Or TSFConnection.State = ConnectionState.Broken Then
                    OpenConnection()
                End If
                da.Dispose()
                Return TSFConnection
            Catch sql_ex As System.Data.SqlClient.SqlException
                'Select Case sql_ex.ErrorCode
                'Case Is = -2146232060
                OpenConnection()
                'End Select
                da.Dispose()
                Return TSFConnection
            End Try
        End Get
    End Property
0
 
TSFLLCAuthor Commented:
Got help with this but ended up having to develop a function that checked for open connection.  Thanks to all.
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now