Navigate
Wasp Helpdesk
  • Register

  • or
  • Login
    Need a password reminder?
or
Contact Us
  • Get in touch

    Send us an email

  • Start a chat session

  • Knowledgebase Read help articles
  • News News & updates
  • Contact Us We are here to help
  • Training View our options
  • Product Sunsets Non-Supported Products
Barcode System Consult
Barcode Printer Consult
Barcode Label Consult
  • Portal
  • Knowledgebase
  • FAQs
  • All Products - Troubleshooting SQL connection errors
Subscribe Download PDF

All Products - Troubleshooting SQL connection errors

Jason Whitmer
2017-04-10
in FAQs

There are 3 main error numbers given when attempting to establish communication with a SQL database:

Error 26

Error 26 indicates that the client was able to contact SQL on the designated server name, but then the login failed. This could be because the instance name is entered incorrectly, or the username/password is incorrect, or other similar failure of the login information.

 

Verify that the connection information was correct, and try adding the port number for the specific instance.

 

Error 0/Error 40

These are similar errors, both indicating a failure to connect. It is my belief that Error 0 is more an indication of failure to connect with the server machine at all, and Error 40 indicates that the machine was contacted, but then it was unable to communicate with SQL on that server. 

 

Microsoft provides troubleshooting steps for both Error 0 and 40 in a single page, listed in order of increasing complexity, at this link: http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx 

Rate the quality of this page

This page was helpful :) :( This page was not helpful

8 of 57 people found this page helpful


Quick Jump
  • Wasp Helpdesk
  • Knowledgebase
  • News
  • Contact Us
Top
Helpdesk software provided by Deskpro