Thanks in advance Support files have been uploaded.

Hi Scott,

Based on the integrity errors that exist in the 'After' data for 8 particular accounts, I believe the problem to have happened when batch 1028 was posted. It was the first batch posted after the 'Before' data backup was made. I determined this because for the one income statement account that had an error, the difference between the Net changes and the Posted Transactions for period 12 of year 2021 is exactly the amount posted to that account by batch 1028. Another batch 1031 posted about 4 hours later contained that same account and it was included in the Net Changes value.

Prior to retrieving batch 1028 from Payables and posting it, 2 other users, different than the user who retrieved and posted the suspect batch, had printed the Detail listing report earlier in the day. One user printed it twice, both about an hour before batch 1028 was posted. They had closed the GL program prior to batch 1028 posted. The other user had printed the detail listing once, about 10 minutes before batch 1028 was posted. They did not exit Ledger until they did the retrieve and post for the other batch 1031.

This doesn't prove nor disprove anything as to how the integrity errors started. It's interesting that there were a number of other accounts posted to from batch 1028 that do not show any integrity errors.

I will email you offline with more specifics, rather than the forum posting here. We can post a solution when we know more.

R&D indicated to me that they couldn't see any differences in the code between GL 9.3A and 9.3B in regards to the Detail Listing report and file handling. But investigation is still ongoing.

Many thanks for you investigation and effort. Got you email and reviewing.

I am convinced it has something to do with the Detail Listing FWIW. I can replicate the file locking of the GLNUMB*.* files on my end and only when I exit Ledger do they get "released". Unfortunately I can not replicate the data corruption. Not sure who posted from Support yesterday but you could on your end replicate that the GLNUMB*.* files do not lock in V9.3A but do in V9.3B.

Regarding your analysis if the user printed the detail listing 10 minutes prior to 1028 being posted and did not exit the Ledger system my assumption is the GLNUMB*.* files are at that point locked and the issue appears. But why did other accounts post OK? That is the maddening part of this.

I am hoping R & D can find something at least correct the issue of the file locking on those files.

So as a pain in the you know what as it might be for the time being before they post anything in Ledger will have:

1. All users will communicate with each other and exit out of Ledger.
2. One user will go back in and check data integrity.
3. User will backup the Ledger data.
3. User will post the batch.
4. User will re-run data integrity to make sure all OK.
5. User will backup Ledger data again.

Thanks in advance for any further investigation and posts on this issue.

Support their Next fiscal '2022' is open.

Assume this shouldn't make a hill of beans difference but at this point thought I should mention FWIW.

Support using the above procedures for posting batches there were no issues yesterday at said client.

Any word from Development?

Hi Scott,

No sorry, nothing more or new from R&D regarding this. I tried again this morning, and no new information.

Having the next year 2022 shouldn't have any influence over what is happening. Apart from additional DIC errors being reported for the balance sheet reports because the closing balance for 2021 doesn't match the opening balance for 2022.

Good to know that nothing bad happened on Friday. Perhaps that had to do with being extra careful at this time.

I understand the frustration of problems happening 'sometimes', when it seems the same thing is being done in exactly the same way. What has been found so far has been helpful for investigation.

Thanks Support keep me posted.

Hi Scott,

As from my offline reply, R&D found the place where the GLNUMB files were being read by the report but not closed. I've been informed that a service pack will be release as soon as we can with highest priority.

Thanks for your information and your patience thus far.

For others reading this thread, if you print the detail listing report, you should probably close and re-open the Ledger program in order to unlock those data files.

Has the service pack in question been halted for download? GL detailed listing is probably the most used report during this week (fiscal year end for all First Nations and most NFP's)