Error: "The application was unable to connect to the database due to disabled TCP/IP protocol"

This support note applies to:

Insolvency (AU)

These instructions require technical expertise

Make sure you know what you're doing and are using one of the products listed. If you're not sure, ask your IT professional or MYOB.

Article ID: 31933

After upgrading the workstation longer connects to the database. An issue in relation to application performance was resolved in release 3.1.

The issue was caused by the server defaulting to the Named Pipes protocol (where TCP/IP was disabled) to connect to the SQL Server. In version 3.1 release the application forces the connection to use TCP/IP, however, if this protocol is disabled you may get one of the following messages when trying to open the application:

'The application was unable to connect to the database', or

'SQL Server does not exist or access denied'.

To configure the protocols on SQL Server 2005:

Open the SQL Server Configuration Manager
Click on SQL Server 2005 Network Configuration > Protocols for [Server name]
double click on TCP\IP
Set the 'Enabled' property to 'YES'
Restart the SQL Server Services

The TCP/IP Protocol is now enabled on the SQL Server.

To configure the protocols on SQL Server 2000:

Open the SQL Server Client Network Utility
Click on General tab
Ensure TCP\IP appears in the list 'Enabled protocols by order'
Restart the SQL Server Services

The TCP/IP Protocol is now enabled on the SQL Server