Page tree


 

 

Errors

This section lists the errors that may occur when checking your database.

 

Error Message

Explanation and Resolution

Invalid connection string

The connection string provided by the lookup.xml file is incorrect. This might be due to a reference to an older database that is no longer in use, or it may be a problem with your file. If the database is supposed to be working, then there is an issue with your MYOB AE/AO installation.

Please contact MYOB Support to resolve this issue.

Could not connect to the database

The MYOB AE/AO database is inaccessible. If the database is running fine for the MYOB AE/AO installations, the issue could be with permissions.

Please ensure that the person running the MYOB OnTheGo service has permission to access the database destination.

If the database is hosted in a different location to that of where MYOB AE/AO is installed, the issue could be that the person is running the service has no network access. Make sure that the person running the MYOB OnTheGo service has the appropriate privileges.

If you cannot connect to the database if may be that the connection string is invalid. See Invalid connection string above.

SQL table [AF_OnlineProvisioning] does not exist

This error could occur because the database version is invalid. MYOB OnTheGo service requires version AE 5.4.4 or later, Australia AO 2013.2 or later, or New Zealand AO 2014.0 or later.

To resolve this error, upgrade the MYOB AE/AO database, then activate MYOB OnTheGo for this database.

SQL table [AF_OnlineProvisioning] is invalid

This error could occur because the database version is invalid. MYOB OnTheGo service requires version AE 5.4.4 or later, Australia AO 2013.2 or later, or New Zealand AO 2014.0 or later.

To resolve this error, upgrade the MYOB AE/AO database, then activate MYOB OnTheGo for this database.

Database has not been provisioned to use the MYOB OnTheGo service

This error could occur because a provisioning record had not been found in the [AF_OnlineProvisioning] table. MYOB OnTheGo has not been activated for the database.

To resolve this error, follow steps 1 - 4 in Setting up MYOB OnTheGo.

SQL table [UserProperties] does not exist

This error could occur because the database version is invalid. MYOB OnTheGo service requires version AE 5.4.4 or later, Australia AO 2013.2 or later, or New Zealand AO 2014.0 or later.

To resolve this error, upgrade the MYOB AE/AO database, then activate MYOB OnTheGo for this database.

SQL table [UserProperties] is invalid

This error could occur because the database version is invalid. MYOB OnTheGo service requires version AE 5.4.4 or later, Australia AO 2013.2 or later, or New Zealand AO 2014.0 or later.

To resolve this error, upgrade the MYOB AE/AO database, then activate MYOB OnTheGo for this database.

The [PracticeToken] cannot be found in the table [UserProperties] or the [PracticeToken] is empty

This error could occur because MYOB OnTheGo has not been activated for the database.

To resolve this error, follow steps 1 - 4 in Setting up MYOB OnTheGo.

The [PracticeToken] xml format is invalid or the [CheckSum] element is missing from the [PracticeToken]

This error could occur because MYOB OnTheGo has not been activated for the database.

To resolve this error, follow steps 1 - 4 in Setting up MYOB OnTheGo.

The [CheckSum] element in the [PracticeToken] is empty

This error could occur because MYOB OnTheGo has not been activated for the database.

To resolve this error, follow steps 1 - 4 in Setting up MYOB OnTheGo.

The [CheckSum] element in the [PracticeToken] does not match the calculated check sum of the connection string in the lookup.xml file

This error could occur due to one of the following reasons:

  • The database credential changed. The lookup.xml file has been manually updated to reflect the changes.

  • The database has been moved. The lookup.xml file has been manually updated to reflect the changes.

To resolve this error, follow steps 1 - 4 in Setting up MYOB OnTheGo.