Review Change log in the change screens. - it may  point out the issue.

Regardless, after a failed code change you must restore to your backup (you did do one, right?)

Then database Copy data to a test company. 

Update to the PU 2 if not there yet. Apply this hot fix. It is for banks but it is about the code changer so relevant:
support.na.sage.com/.../viewdocument.do

Rerun code change there, review.

If it still fails,  advise Sage.

Install Product Update 3

Hi,

Someone tell me about Update 3 needs a certifcate for SQL but if we still are in Windows Server 2016 and SQL Server 2016 with Native Client 11 not a problem, right? We don't need to change anything regarding SQL and works right?

Thank you

HI,

We are in PU2. We just use ACC not Vendor/Customer Number Change, even not installed. ok

Thanks

I haven't done one yet, but you should be OK :

"Existing DSNs with the driver SQL Server Native Client ## will continue to be supported until further notice."
From here:

https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=116170&sliceId=1&cmd=&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

HI MusickInt,

We just did in a test server with a copy of real company data and same issue. And database damage !!!

Not sure what to do now !!! See my last post related please.

Thanks

Hi Oscar, 

Have not seen any problems with PU3. 

Can you duplicate the error in your office?

Is the data corrupted before running ACC? 

Does ACC report any problems/errors? 

[email protected]

Hi,

Yes that was I hear because I get error with ACC just wth Update 2 so I install Update 3.

Yes I get same error but Update 2. I dont upgrade mine to Update 3 as I get same error with customer.

No, data its OK. We dbload data and every time we run ACC we get error and database is damage (No history) !!!

Yes. Please see my other post related.

Thank you

Account Code Change v2022 Error - AR68ARRD Critical Error [1212] Invalid working directory path - Financials Suite - Sage 300 - Sage City Community

It looks like you are trying to run ACC version 2022 on AR 2021 data.  They must be the same version.

Hi Jim,

I dont understand why error shows AR68 but we have AR69. When we first get an error similar but Update 2 it mention specifically an error with PJC modules (we dont use and not install but anyway get error) and we found a fix. Install those files at a third party directory ACC use and solve but then we get this error but no found a hot fix. But in resume all data it is in Sage 300 2022, we upgrade first from old version a couple months ago. Only problem is with Account Code Change.

Thanks