MYOB Cache Issues

MYOB Classic files are synchronised to Bi4Cloud using a MYOB supplied ODBC connection.

There have been a few issues associated with ODBC and the cache settings

1. Terminal Server Installations and ODBC Cche

The BI Connector gets a disk cache error from MYOB when a user using the connector is a Terminal Server session. The c:\b4cloud\ir_intranet_docs\irDBimportLog.txt has an error 

ERROR: Could not add Table Customers from a1 as Customers  ERROR
[01000] [MYOB ODBC] Error initialising the disk cache

Disk cache is used by the MYOB ODBC when the datafile is being read and the system memory needs to write data to the C:\MYOBODBC\Cache directory. So the connector may function fine on smaller files but larger file ie greater than 100mb can fail because they need to write to disk cache. The failure is because MYOB cannot determine the cache directory in terminal server environments. The fix is to copy the OpenRDA.ini file to the users directory as belowScreen_Shot_2018-02-26_at_1.16.09_pm.png

The full article on the MYOB site is here

2. Larger MYOB files ie 1.0Gb and larger 

For company files that exceed the 1GB size, the data extract will eventually fail as the MYOB ODBC driver runs out of allocated memory.

The error message is this

ERROR : Could not add Table JournalRecords from a1 as table JournalRecords ERROR [01000] [MYOB ODBC]Disk Cache file size limit has reached

 The workaround is -

1. Edit the C:\Windows\openrda.ini file and increase MAX_SIZE to 512 for CacheOptions:

CacheOptions=PATH=C:\MYOBODBC\cache;INITIAL_SIZE=10;INCREMENT_SIZE=5;MAX_SIZE=512;DATABLOCK_SIZE=64

Save and close the file.

2. Ensure all users are out of MYOB

3. Close any other add-on applications that use MYOB ODBC

Re-run the data extraction.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Please sign in to leave a comment.

Powered by Zendesk