Hi Clark,

Has anything else changed recently on your network? New server? New workstation for you with new OS? The first file named contains your posted transactions, and the second is the company profile. If these cannot be opened, then Ledger will have a problem. If you copy your data to your local workstation, does it have the same problem? What was it that prompted you to run a data integrity check (or were you just following good usage practices)?

Hello cgawryluik,

Has anything else changed in your computing environment? Server? Workstation? Do you have a backup from before the post? Have you tried restoring that and checking its integrity?

What are the errors being reported by the DIC? Failing during a posting process is usually fatal.

If your network is Novell, and Client32 on your workstation is either version 4.83 or version 4.90, you will need to go to the Novell website and download a service pack. There are known issues with the unpatched versions of these network clients, and will cause problems in programs such as Adagio.

This isn't necessarily the cause of your posting issues, but certainly the first thing to check.

You should also determine if File Caching or Opportunistic Locking is enabled on the Novell Client; it should not be for Adagio to work successfully. Often when a new update for Novell Client is installed, the default choice for the above settings is On.

It may be useful to know an example of the reported data integrity errors, such as an account out of balance or an incorrect batch total. Usually the Rebuild function will not attempt to rebalance accounts, which would be why the Rebuild did not change the error count.

Hello cgawryluik,

Does your backup pass the integrity check clean? If it does not pass clean over the network, is it clean if you restore it to your local hard disk and run the integrity check again?

Also, please let us know about the Novell settings.