June 22, 2003 at 5:21 pm
Hi all,
I run a box with IIS and SQL on it...unforuntately I have to due to restrictions in an ancient ODBC driver that is used to talk to the accounting system via web pages etc.
I frequently get 'GENERAL NETWORK ERRORS' reported in the replication monitor when it tries to connect to a remote box that is highly unlikely to be offline. Other users also have problems occasionally connecting to this box whe using the intranet.
I have never been able to trace this general network error when this box seems to drop off the network. Anyone have any ideas how I can get more information or try and track down this error/glitch in the network...?
Thanks for any input...Rolf
June 23, 2003 at 1:55 pm
Version of SQL Server? What version is the ODBC driver? So really old (3+ years) versions of the driver used to toss these errors all the time.
June 23, 2003 at 4:55 pm
Its SQL2000 with service pack 3. The ODBC driver is old (3+ years) but its not that that is causing the problem. The old driver is the reason the IIs has to be on the same box as the ODBC driver wont look over the network for the accounting software.
I was wondering if there was any other monitoring I could do in SQL server to help capture this GENERAL NETWORK error as their doesnt seem to be problems with other applications on the network. Its only the SQL server agent that seems to be unable to connect to the remote servers (outside the intranet used for replication) and it is only ever the SQL server box that other people on the network cannot connect to. I have tried monitoring the network and nothing untoward seems to be occuring.
Rolf
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply