[ProvideX][ODBC Driver][FILEIO]Unable to allocate memory to perform requested operation (#14) error after upgrading from Sage 100 Standard ver 2015 to 2017

Posted By CaseySkousen over 5 years ago

We use ODBC to connect to MS Access for several custom reports we use. After upgrading from Sage 100 Standard ver 2015 to 2017, ODBC connects to most files. However, when we try to connect to the AR Invoice History Header file it will display data correctly once, then errors out with this message:

ODBC--call failed.

[ProvideX][ODBC Driver][FILEIO]Unable to allocate memory to perform requested operation (#14)

We have tried with a Silent ODBC connection and with the regular MAS90 SOTA ODBC connection with the same results. The same connection works fine in the 2015 version. We need to be able to access this data in version 2017 via ODBC for our custom reports in MS Access.

Sage support says they refuse to help with ODBC issues???

How can we get ODBC to work correctly for all files in Sage 100 Standard version 2017?

Parents

0 davidonelson over 4 years ago

I got this error when using ADO.NET to connecting to the ProvideX ODBC driver. The code was depending on connection pooling. The code was connecting and disconnecting on every query. It was slow, and also I think the ProvideX ODBC driver may not support connection pooling. So after about 30 queries, I got this error on every subsequent query until the program quit. I think the ProvideX ODBC driver hit a connection limit. I change the code to open the ProvideX ODBC once at the beginning of the program and close it at the end, and the error went away.

David Nelson
Dynamic Enterprise Technologies Inc
Seattle Washington USA
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 davidonelson over 4 years ago

I got this error when using ADO.NET to connecting to the ProvideX ODBC driver. The code was depending on connection pooling. The code was connecting and disconnecting on every query. It was slow, and also I think the ProvideX ODBC driver may not support connection pooling. So after about 30 queries, I got this error on every subsequent query until the program quit. I think the ProvideX ODBC driver hit a connection limit. I change the code to open the ProvideX ODBC once at the beginning of the program and close it at the end, and the error went away.

David Nelson
Dynamic Enterprise Technologies Inc
Seattle Washington USA
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 CaseySkousen over 4 years ago in reply to davidonelson

I am again getting this error and cannot resolve it. I do not understand how you changed the code in Access to open the ProvideX ODBC once at the beginning of the program and close it at the end as you describe your solution.

How did you do that to get the queries to work?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Sage 100

[ProvideX][ODBC Driver][FILEIO]Unable to allocate memory to perform requested operation (#14) error after upgrading from Sage 100 Standard ver 2015 to 2017

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING