Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
JAdauto
Posting Yak Master
160 Posts |
 Posted - 2004-05-19 : 16:39:50
|
| We are having a rather serious issue and I (and two others) have searched the Internet for 2 days for a resolution with no good results. Once again, I am hoping you come through for me as you have saved me in the passed.We are getting the following errors:[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.The problem with these errors are that they are not consistent. They only happen in TWO places in our code that does some pretty hefty processing. These errors do not occur on every machine. They NEVER occur on the server machine. They NEVER occur on my machine. They SOMETIMES occur on our MIS guy's machine. One client machine gets these errors EVERY single time. Another client's machine at the same location NEVER gets them. When processing one day's business it may fail and return these errors and then they turn around and process it again and it works fine.We are finding this now at two separate clients sites... again never consistently.I dont know what kind of information you could possibly use to help us out here, but here is my attempt. If anyone has any ideas or information I can give, please let me know.We are running VB6 SP(5), SQL 2000 (SP3a), MDAC 2.71 SP(1) and ADO 2.7. We upgraded to MDAC 2.8 to try to fix it, but that did not, so we went back to 2.71. We did find a forum last night that said something about someone seeing problems when tables were created with different collation types. We have found that we do have a few user tables with fields that have these types COLLATE SQL_Latin1_General_CP1_CI_AS according to information in sys columns. Anyone have any input if this could be a problem?Any input at all that anyone can provide is greatly greatly appreciated. We are at a complete loss.Thank you again,JAdauto |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-19 : 16:45:13
|
| The error message indicates that the client machine is not able to find the SQL Server. Can these machines even ping the database server at the time of the error? Is there a firewall in between the client and the database server? Is SQL Server listening on a port other than 1433? If so, are there aliases on the client machines?Is your server's collation different than those columns? I believe what you posted is the default. I've never heard of a problem like this that was caused by different collation settings.Tara |
 |
|
|
JAdauto
Posting Yak Master
160 Posts |
Posted - 2004-05-19 : 17:09:19
|
Thanks for the speedy reply. I really appreciate it. These are answers by our MIS guru who is just as plagued by this issue:quote:
The error message indicates that the client machine is not able to find the SQL Server. Can these machines even ping the database server at the time of the error?
Yes all machines can ping the server both by name and by ip address without a problem. Ping replies are <10msquote:
Is there a firewall in between the client and the database server?
At no location. They are all on the same 100 Base-t switched networkquote:
Is SQL Server listening on a port other than 1433? If so, are there aliases on the client machines?
No only port for sql is the default 1433 |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-19 : 18:03:56
|
| Given those answers, I would setup a trace on the database server to capture what is occurring when those clients get that error. Let the trace run for a few hours to capture enough data. See if exceptions are occurring. If none, then you probably would need to escalate it to MS. A network sniffer might also be helpful if you have one available.Tara |
|
|
|
|
|
|
|
|
Inconsistent Errors