The BI Connector is a program that is installed on your local server or PC and allows you to connect and sync MYOB company files with BI for Cloud. If, however it experiences an issue establishing a connection to your company file, you may receive an email with one of the following error messages returned by the connector which will need your attention to fix:
Company file 'X' not found / Invalid company file path 'X':
This error will occur when your MYOB company file has been renamed, moved, or is located on a network share which the software cannot access. Please see this article on how to update your connection to your company file.
If on some days you get this message and other days the overnight sync runs properly, then this indicates you have Multiple BI Connectors Installed on different computers. It is intended that you only have one BI Connector installed and that it be on the server where your Data file is located.
By having multiple installations this can cause a conflict and results in the above error message when we attempt to auto refresh data each night. Please uninstall the connector from all other computers.
Invalid MYOB administrator password:
This error will occur as you have an invalid MYOB Administrator password defined against your company file connection, or another user has set a password where one previously didn't exist. Please see this article on how to update your connection to change the password.
Invalid ODBC Driver:
This error will occur if your MYOB company file requires a version of MYOB's ODBC driver software (installed with MYOB) which is not installed on your computer / server where the BI Connector is installed. Please check that you have the correct version of MYOB installed on the computer / server where the BI Connector is installed.
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified:
This error will occur if your MYOB company file requires a version of MYOB's ODBC driver software (installed with MYOB) which is not installed on your computer / server where the BI Connector is installed. Please check that you have the correct version of MYOB installed on the computer / server where the BI Connector is installed.
Invalid MYOB version installed ARL company file:
This error will occur if your MYOB AccountRight Live Server edition installation is not compatible with your company file you currently have connected via the BI Connector. Please check that you have the correct version of MYOB AccountRight Live Server edition installed on the computer / server where the BI Connector is installed.
Company file not found (UID X not found):
This error will occur if you have removed your MYOB AccountRight Live company file from the server. Please check that you have the BI Connector installed on the correct computer / server.
AccountRight Live API Service (X) not available / not accepting connections:
This error will occur if the MYOB AccountRight Live Server edition windows service(s) are not currently running / installed on your computer / server. We rely on the following services installed as part of MYOB AccountRight Live Server edition to extract reporting data:
MYOB AccountRight API Service
We suggest if possible, restarting the computer / server, or if this is not possible restart the MYOB AccountRight API service within the Windows Services application (located within the Administrative Tools folder of Control Panel).
If, after restarting the computer / server you are still not able to perform a sync you may need to reinstall MYOB AccountRight Live Server edition, or install the install the MYOB API manually, which is done at the end of the MYOB installation.
Login failed for user 'X':
This error will occur if your SQL Server / ODBC connection to your company file has an invalid password for the user specified in the error message.
Please see this article on how to update your connection string within the Desktop Connector with the new password for the user account being used.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified):
This error will occur if your SQL Server connection to your company file is unable to locate the configured SQL Server instance.
Please check that your referenced instance of SQL Server is running / accepting connections. If the SQL Server instance has changed, please see this article on how to update your connection string within the Desktop Connector with the new SQL server instance to be used.
Cannot open database "X" requested by the login. The login failed.
This error will occur if the database listed in the error message does not exist, or the user account specified in the connection string does not have permissions to connect to it.
Please see this article on how to update your connection string within the Desktop Connector with the correct database name / user ID / password to be used to connect to the database.
No VFP ODBC Driver installed:
This error will occur if Microsoft's Visual Fox Pro ODBC driver is not installed. Please check that you have the desktop connector installed on the same computer / server as MYOB Payroll. Unfortunately, this driver is no longer available for download from Microsoft.
Error Initialising Disk Cache
The MYOB ODBC tries to use the Disk Cache and it fails because of setup, file permission of because Terminal Server issues with ODBC. See the article here
Error Disk Cache file size limit reached
The MYOB file size is greater than 1Gb and the standard cahce size is exceeded. The wrokaround is to increase cache size. See the second item in this article