Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 472
  • Last Modified:

SQL 2005 Error - Connecting Excel workbook to SQL 2005 server

I am trying to connect an Excel workbook to a remote SQL server database and getting the following error below (see code snippet). Any insight would be appreciated. Wondering if there is an easier method to connecting then what I have. I have VBA coding in the Excel workbook (if needed, I can provide it).
Connection failed:
SQLState: '01000'
SQL Server Error: 10054
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead(recv()).
Connection failed:
SQLState: '08501'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.

Open in new window

0
Jeff S
Asked:
Jeff S
  • 3
2 Solutions
 
MetallimirkCommented:
Error # 08501 is a communication link failure. This is a mid-stream failure of the connection from your application client (Excel) to the SQL Server.  This typically points to problems with your networking layer, possibly even your network hardware.  For example a router in your network could be dropping connections, or a network card that is going bad, possibly you need to be on your VPN if outside of the office, or ensure your connectivity to the Wifi Network is valid (if your not plugged in).

Unfortunately there is no simple and easy to follow way to diagnose this, it typically requires someone who is expert in network layer to analyze network sniffs between client and server. It would help us out a great deal if you provide us with more information regarding your network environment.
0
 
Bhavesh ShahLead AnalysistCommented:
10054 Connection reset by peer. [NT only]
This can happen if a sockets client (which includes SPX) is actively sending or receiving data to or from SQL Server, and the network connection is lost. This error is usually seen in conjunction with error 17824 when on sockets-based connections. For example, an Microsoft Windows NT client using the NWLink SPX transport could be selecting data from SQL Server, and if the network cable is unplugged from the SQL Server computer, you will see error 10054.
0
 
Bhavesh ShahLead AnalysistCommented:
0
 
Bhavesh ShahLead AnalysistCommented:
Hi....

Does your issue is over??
did you get the answer?
0
 
Jeff SAuthor Commented:
Thanks
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

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