Troubleshooting: Year End Closing Error – DB concurrency violation
Question : When I perform year end closing, system prompts an error message "DB concurrency violation”. What should I do?
Version : 1.8 / 1.9 / 2.0
Possible Reason :
CBKey and JEKey did not set to null from the past Year End Closing processing.
1) Do a backup before executing the following query.
2) Decide the fiscal year that you want to run year end. Let’s say now I wish to run Year End Closing for Fiscal Year 2016. Take note of the start date for this year, this info will be needed in SQL query later.
3) Go to AutoCount Accounting Management Studio > Tools > SQL Query, type the query as below and click on Execute.
|update APPayment set CBKey = null where docdate < '2016-01-01' and CBKey is not null|
update APRefund set CBKey = null where docdate < '2016-01-01' and CBKey is not null
4) Go run again year end closing.
Note : Please seek assistance from your software dealer if the problem persists after performing the steps as above.
By : Cheryl 180905, Lay Swan 180925, P180928
|AutoCount Accounting 2.0
|AutoCount Accounting 1.8 / 1.9
|AutoCount On The Go
|AutoCount Accounting Plug-In Documentations