Support,

Can you confirm that when the Detail Listing report is generated to either preview, print or Excel Direct that the GLNUM*.* files are not supposed to get locked?

Curious since when the Detail Listing is generated I can not rename any of these files. I would have thought they were read only.

Just want to confirm.

Hi Scott,

These files have the Account Net Changes values and are used for the Detail Listing report. I wouldn't expect data files to be locked (and I can rename the GLPOST file in the midst of printing this report), so on the surface this doesn't make sense.

I presume you are wondering about file locking for a different reason, say for posting or some other multi-user access, rather than actually wanting to rename a data file while someone is in Adagio Ledger and printing a report.

Thanks Support. I purposely haven't posted anything on this yet but it is to the point now something is going wrong at a client site.

They have continually been getting corrupted Ledger data for the past two weeks now and it appears (and I stress appears) that is a user generates the detail listing this locks the files. In the meantime another user posts a Ledger batch, or that same user that generated the listing posts a batch and they get corrupted data.

In theory if these files are locked (and I know this by going out to the DOS prompt and try to rename them I get the access denied message) then when you try to post these files can not get updated and hence corrupted data?

The other issue is these corruptions appear to have coincided with the Ledger V9.3B upgrade yet no other clients are having this issue to my knowledge with the upgrade applied.

We have rebooted the server and workstations thinking this might be part of the problem but it doesn't appear so.

I have attempted on my end rename the GLNUMB*.* files when I generate the Detail Listing and they are in fact locking. Yet when I post on my end integrity comes back clean.

Continuing to investigate but in my mind these files should not be locking.

Sorry a ramble.

Hi John

I am SOOO happy you posted this. I have a client that has been experiencing multiple instances of corrupted GL data since I installed 9.3B (210225) and I also found that I couldn't rename the GLNUMB*.* files. You got further than I did to suggest that the files got mistakenly locked when printing a Detail Listing.

Of course I couldn't replicate this on my computer and in the end I decided to restore 9.3A to see if the problem continues or disappears. So far it has disappeared.

If you could provide Softrak with backups pre-posting and post-posting (corrupted), they and I would appreciate it. They asked me to provide those but I couldn't find a corrupted backup.

Steve

I can confirm that this rename locking doesn't happen in GL9.3A, and I saw this in 93B. I have already written up something for R&D to investigate. Knowing one reason why files are locked is probably all they need - it's pretty likely that if the Net Changes files are locked and unable to be written to, then the corruption would be that the Net Changes amounts would not synch to the Posted Transactions for the period(s) posted to.

Thanks support since when we run data integrity this is an example of the error:

Error: Account [104000 - ] current balance does not match net change record.
Error: Account [104000 - ] next year opening balance does not match current year current balance.
Master / Net Changes ... 2 error(s) found

I am going to suggest (as a pain as it might be) when they are ready to post for both Ledger users exit the system, one log back in check integrity to make sure it passes, then backup then post until this is resolved or we catch something unique to their environment.

Hi Steve,

Well I must admit I have to give you and Bruce the credit here. It was Bruce who put me on the the GLNUMB*.* files since he received an email from you indicating this issue (sorry Bruce cat out of the bag).

I am going bonkers here with this client and never would have got onto the GLNUMB*.* files issue had he not mentioned your email so for that many thanks.

On our end in the office on a standalone workstation as soon as I generate the Detail Listing (Preview, Print or ExcelDirect) these files get locked and only unlock when I exit the Ledger program. But if I stay in when I want it to corrupt the data it doesn't but it seems too fishy to me since the very errors we are getting are to do with the Net Change files.

FWIW the said client, I installed the V9.3B Ledger upgrade on Feb 22nd. It wasn't until March 3rd that this issue started happening. BUT I did load the SP - 210225 on March 1st (to fix the statement group issue) and then all you know what started happening on March 3rd. So I am thinking the service pack might be the culprit not sure.

I will check with the client to make sure I can send Softrak the files before and after but at this point I think they might welcome this.

And I want to be clear Support I am still not sure if this is environmental or upgrade/service pack related but it does seem to coincidental to me FWIW.

Steve/Support,

I have a set of files prior to corruption and post corruption. I have been given the go ahead by the client to upload these two you.

Let me know where to send.

Thanks in advance.

Data can be uploaded to softrak.com/dbr and select Tech Support rather than for Repair.

I did try to do a 2-user scenario where one user was printing the detail listing report, and the other user posted a number of batches. There were no errors and integrity was clean.

So we'll see what the corrupted data will show - if you know what they were doing in between, that would be helpful. Otherwise we'll need to glean what we can from the SDAPPLOG.

Thanks Support. I have gone back and forth on this a "thousand times". Environment vs the update. Every time I think it's one something comes up and makes me think the other.

As to what happened and what they were doing has been a hair pull since they keep telling me they are not doing anything out of the ordinary and this issue seems to have arose when the upgrade (or at least the service pack) was applied.

Since they don't receive an error when posting they only find out about the corruption when the print (surprise) the Detail Listing to Excel Direct when they are reconciling accounts and they discover the error that has happened before "GL Details Missing for period x" is sitting in the Description column for one or more accounts.

They then run Integrity and obviously the error appears as the example above.

FWIW the files that I will upload to you - the good files were clean as of yesterday at noon (according to their IT person). So not exactly sure when the bad files got corrupted but obviously sometime after noon yesterday.

Thanks for looking into.