This support note applies to:
- AO Tax (NZ)
- AO Practice Manager (NZ)
- AO Practice Manager (AU)
- AO Tax (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.
When opening MYOB Accountants Office (AO) you may receive the error "A network-related or instance-specific error occurred while establishing a connection to SQL Server".
This error occurs when MYOB AO cannot connect to the SQL Server. This may occur on all workstations or just one workstation and may be intermittent. You may also encounter this error after performing a migration.
If the issue is occurring on all machines, this indicates the SQL Service has stopped. You need to start it again on the server. To do this follow the menu path Start > Control Panel > Administrative Tools > Services. Right-click the SQL Server (MYOBACCT) service and select Start or Restart. If there are issues starting the service, or if you have troubles doing this, please contact your IT provider.
If the server machine works without issue, check that the SQL Server Browser is running. You need to start it again on the server. To do this follow the menu path: Start > Control Panel > Administrative Tools > Services. Right-click the SQL Server Browser (MYOBACCT) service and select Start or Restart.
Ensure that named pipes and TCP/IP protocols are enabled in SQL Server Configuration Manager as follows.
- Follow the menu path: START > All Programs > Microsoft SQL Server 2014 > Configuration tools > SQL Server Configuration Manager. The SQL Server Configuration Manager appears.
- Expand SQL Server Network Configuration. The Protocols for SERVERNAME\MYOBACCT option appears, where SERVERNAME\MYOBACCT is the name of the instance.
- Click on Protocols for SERVERNAME\MYOBACCT. The Protocol Name and Status columns appear.
- Right-click on Named Pipes and select Enable. The Warning window appears.
- Click OK. Named Pipes are enabled.
- Right-click on TCP/IP and select Enable. The Warning window appears.
- Click OK. TCP/IP is enabled.
- Click on SQL Server Services in the left-hand pane. A list of SQL Servers appears.
- Right-click on SQL Server (SERVERNAME)\MYOBACCT and select Restart where SERVERNAME\MYOBACCT is the name of the instance. The service is restarted.
If the issue persists after this, it indicates that the error is being caused by a network related issue, such as firewall. Ensure the following exceptions are created for outbound connections on the server, unless you have strict firewall settings, in which case, you may need to configure your firewall for inbound connections on all workstations:
MYOB SR DAL
SQL Server MYOBACCT
Dynamic port (see below)
SQL Server MYOBACCT Browser
sqlservr.exe (32-bit machine)
C:\Program Files\Microsoft SQL Server\MSSQL12.MYOBACCT\MSSQL\Binn\sqlservr.exe
sqlservr.exe (64-bit machine)
C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.MYOBACCT\MSSQL\Binn\sqlservr.exe
If this issue still occurs after allowing everything above except for SQL Server MYOBACCT, you need to identify the dynamic port number and allow this as well.
How to find the MYOBACCT Instance Port Number
On the server, follow the menu path: Start > All Programs > Microsoft SQL Server 2014 > SQL Server 2014 Configuration Manager. Expand SQL Server Network Configuration from the left-hand pane and select Protocols for MYOBACCT.
In the right-hand pane, right-click TCP/IP and select Properties. Select the IP Addresses tab and scroll down to IPAll and note the port number next to TCP Dynamic Ports. This is the port you need to forward on the TCP protocol.
If the issue persists after this, or if you have any issues following the above steps, you will need to speak to your IT provider for further assistance.
If you experience issues with MYOB software after performing a migration, additional assistance on your migration may fall outside of the terms of your Sales and Service Agreement. Please contact your Client Manager to organise further assistance.