Note: These errors typically indicate network/installation-related issues. To help prevent these types of problems in the future, review the Database Administration Guide and our system requirements before installing or updating. 

Try each of the following steps in order until the error is resolved:

  1. Verify that the user name and password you are using is correct and is eight or fewer characters 
  2. Verify the SQL Server service is running on the server and attempt to login at the server  
  3. Verify the version of the executable being used on the workstations matches the one on the server  
  4. Verify the database is online. Then, detach and reattach the database to the Blackbaud Management Console  
  5. Rename the BBUPDATE.INI file on the workstation  
  6. Determine the server's IP address and then attempt to PING the SQL server by IP address and by server name (DNS name) from a command prompt
    • If the PING by IP address fails, contact a qualified IT professional for assistance with TCPIP 
    • If the IP Ping connects but the PING by server name fails or reports a different IP address than the one found on the server, contact a certified IT professional to address the name resolution problem on the DNS server, or, as a temporary fix, add information to the HOSTS file of problem machines 
  7. Determine which version and edition of SQL Server is being used (SQL Server Standard or Enterprise Edition or Express). If using a full version of SQL Server 2008 or higher, refer to Knowledgebase article 49022 for changes which need to be made to SQL Server in order to use it with Blackbaud databases.  
  8. If using the full version of SQL Server verify the authentication method being used by SQL Server
    1. [SQL Server Full version only] If using Windows Only authentication, first add the proper permissions needed for users in a Windows Only authentication environment
    2. [SQL Server Full and Express versions] If Using Mixed mode authentication or once permissions have been added for users in Windows Only authentication try to PING the server by IP address and by server name from DOS 
    3. If the PING by IP address fails, contact a qualified IT professional for assistance with TCPIP. If the IP Ping connects but the PING by server name fails, have a certified network professional address the name resolution problem on the network or add information to the HOSTS file of problem machines 
  9. Determine the port number and protocols being used by SQL Server  
  10. If a Windows firewall is running on the workstation or server, verify the correct port number is opened in the firewall. 
  11. If Enterprise Manager is installed, make sure the port is not being used by another instance of SQL Server. If it is, change port for the Blackbaud product to 5050. 
  12. If using SQL Server Standard or Enterprise Edition, verify the authentication method being used by SQL Server.
    • If using Windows Only authentication, first add the proper permissions needed for users in a Windows Only authentication environment 
  13. Verify you are running MDAC version 2.8 or higher. If not, download and install the latest version of the MDAC.  
  14. Telnet the port being used by SQL Server to verify the connection is possible
    • If Telnet connects, set the DSN for the product to use the port specifically and manually set the port on the server for all workstations 
    • If Telnet fails, contact a qualified IT professional for assistance troubleshooting the telnet utility
Please contact the appropriate software vendor or IT professional for assistance with this process or issue, which is beyond Blackbaud's scope of support.

Note: We provide links to third-party websites in an effort to help you resolve your issue. We are not responsible for the information on third-party websites, and we cannot assist in implementing the solutions on these websites.