


I'd appreciate any help in trying to determine what could cause this strange behavior. The operating system is Windows Server 2003 Enterprise Edition SP2. All three instances have the same linked server configured in the same way and pointing to the same ODBC driver on the physical machine, yet only one instance (the most important one, of course) produces the error messages referenced above.Īll instances are running SQL Server 2005 Standard Edition SP3 (.00). Here's the strange part - I have only seen the ODBC error message while running the import scripts on the DR instance.

This DR server is a physical machine with three SQL Server 2005 instances running – DEV, UAT, and DR. To make this issue even more interesting, I've noticed that this error message only appears on our DR instance (which is currently our Production instance due to a hardware issue that killed our Production server). The vendor who provided the driver has indicated that this is an issue with our client-side application (i.e., SQL Server), not their driver. OLE DB provider "MSDASQL" for linked server "prodIntrader" returned message "Unexpected Network Error. OLE DB provider "MSDASQL" for linked server "prodIntrader" returned message "Socket closed.". OLE DB provider "MSDASQL" for linked server "prodIntrader" returned message "Server crash likely.".
