Getting ConnectionRead(Recv() Error on connect to an SQL Server DB

Hello,

Our MS SQLServer 2000 database exists on our web hosting companies server.  We've got a few Delphi programs that connect using the following connection string.  We have suddenly begin getting the error

 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead(recv()

 whenever we run programs. It sems to fail opening a certain table. The table contains roughtly the same number of records each week, about 1000.

Nothing has changed as far as I know, and we get it running from two different locations with different firewalls, OS configurations, etc.

Can anyone tell me why we get this and how to resolve it?  And how I look at the SQL Server log on the server?

Thanks,
WS

Connection String:

'Provider=MSDASQL.1;Password=fishing;Persist Security Info=True;'+
                              'User ID=microtech;Data Source=MTCDataWeb;Mode=ReadWrite;'+
                              'Extended Properties="DSN=MTCDataWeb;Description=test connection;'+
                              'UID=microtech;PWD=fishing;APP=Enterprise;WSID=LAPTOP;'+
                              'DATABASE=microtechstaffinggroupdb;Network=DBMSSOCN";'+
                              'Initial Catalog=microtechstaffinggroupdb'

Query:

select *
from TimeCard
where WeekEndingDate between :WE_Date_Start and :WE_Date_End
order by WeekEndingDate ,
             CompanyName,
             DepartmentCode,
             LastName,
             FirstName,
             EmployeeNumber
WaterstoneAsked:
Who is Participating?
 
Partha MandayamTechnical DirectorCommented:
investigate the corporate office network. Maybe that isp has a lower speed or some network issues
0
 
AustinSevenCommented:
You can check your SQL Server error log in Enterprise Manager by expanding 'Management' and then 'SQL Server Logs'.

It's too difficult to say exactly what the cause/fix of the problem is but you can start to test a few things.   One method I use is to create a DSN (control panel, data sources (odbc)) and enter the SQL Server's details such as server name, user id and password.  At the end of the process of setting up the DSN, there is a 'test' button that will show you if you can achieve basic ODBC connectivity to the target database.  

If you can't connect via a DSN, you have to get in touch with the hosting company's help desk and raise a call.   If you can connect with a DSN, things a get a little more complicated.   However, let's see how you get on first.


AustinSeven
0
 
WaterstoneAuthor Commented:


Thanks for the reply.  I can connect to the DB, and I can use MS Enterprise Manager verion 1.2 version 5.
And I can open some of the tables.  This seems to fail based on the number of tables I'm opening, or some other communications load type condition.

I've also forgoten the sa login password.  I set up an admin user with full rights over a year ago, but when I try to use "dbcc loginfo" I get an access violation: User 'xxx' does not have permission to run DBCC loginfo.  The Manager selection expands, but doesn't offer the SQL Server selection, probably because I'm on a shared sever on the hosting system.

WS
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
arbertCommented:
"Our MS SQLServer 2000 database exists on our web hosting companies server.  We've got a few Delphi programs that connect using the following connection string.  We have suddenly begin getting the error"

Are you connecting with the apps across the internet or are the apps local on the Hosting company's server?
0
 
WaterstoneAuthor Commented:


    Connecting accross the internet.
0
 
arbertCommented:
"Thanks for the reply.  I can connect to the DB, and I can use MS Enterprise Manager verion 1.2 version 5.
And I can open some of the tables.  This seems to fail based on the number of tables I'm opening, or some other communications load type condition."

"Connecting accross the internet."

Ouch...You're bound to run into all kinds of timeout issues.  Peronally, since you can connect with other sites/routers, I would do a network trace to see why this one network seems to connect and then fail.  There have to be some lost packets/timeouts somewhere.

I assume you're using some kind of VPN or private network across the internet right?
0
 
WaterstoneAuthor Commented:


  It fails in three circumstances.
1)  Our corporate offices connectiong to the server at our web server many states away.
2)  Using terminal Server to log onto the coprporate offices and connecting as in number 1.
3)  In my home office connectiong to our web server many states away.

The corporate offices use a different ISP to connect, a different fire wall, different OS.
0
 
arbertCommented:
Well, it's definately not a SQL Server issue then.....You really aren't routing SQL Server over the internet unprotected right?
0
 
WaterstoneAuthor Commented:


   Nope.  I removed one of the tables from the application, so it now opens one less SQL table, and it seems to be fine now.  I think it was/is a timeout type issue caused by network traffic, but troubleshooting it will have to wait.  The tabkle I removed is a user log that increases each week.  I'll purge the table and add it back into the app and see what happens.  

Thanks for all your help.


WS
0
 
arbertCommented:
nice answer...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.