Hi Hugh,

Thank you for the indication of the actual error messages. I believe this is something we know about, that will be addressed in the next Ledger service pack.

We believe the issue to be strictly multi-user based, where the first user opens Ledger, then a different user opens Ledger concurrently and posts one or more batches, then exits. The first user then runs an integrity check, and for that user, an internal transaction count for integrity check reasons was not visible for the program in that timing. Currently, as you have found, closing and re-opening the program will refresh the count and thus the errors go away.