I'd tempted to un-install INC and clear out the 3rdparty folder (where the .DI1 and .DI2 fields reside). Then re-install.

That message would indicate that it thinks it is processing a PO 5.3 table which you clearly are not running.

Hi jmainland sorry to ask the obvious questions, can you confirm your DEV and Prod environment are running identical Product Update versions?  Please confirm you're running identical ODBC driver setups between both versions.  Also, please open the Event Viewer to locate the error written at the same time the Sage 300 error occured. Being an access violation I'm thinking something like AppLocker, Windows Defender or some other security application is terminating the process.

Let us know what you find.  Good luck!

Yes my dev and prod systems are the same except for the operating system. There's no clear event viewer or SQL log error when it fails, but I did notice the following event viewer error when closing out of any of the number change programs. This happens on both my production and dev systems so I don't think this is causing my problem.

At this point I think I may try starting Accpac up as admin and try posting. 

Hi JMAINLAND,

Can you also try another database (maybe Sample Data) as a test in the problem environment?

Also, try zipping up the 3rdParty folder in your Dev environment and rename and replace it in your Prod environment.

Regards,

DCrampton

DCrampton I pulled the 3rd Party folder down from Prod onto my Dev and it still is able to post the changes no problem. 

I'll have to keep digging. It's clearly an environment issue.

Maybe its some sort of permissions issue?  I know this is another obvious one but have you tried launching Sage 300 as Administrator on Prod, entering an account with Local Admin rights, and tried posting a change?  Have you confirmed your ODBC driver is the same version on Dev as Prod?  I've had certain activities (like db dump and load) throw an error before, even when Sage 300 generally runs fine, from ODBC DSN driver versions that were a bit too old for the system in use.

It appears the issue is UAC related. I tried opening Accpac as Administrator but it still errored out with the same Access Violation Error. I restored from back up and tried posting again but turned the UAC level all the way down. It posted successfully.