This is a bit complicated so bear with me.

Our setup: Windows Server 2012, Adagio clients: two Windows 7 machines and two Windows 8.1 machines. Using Ledger 9.1A (140221), Payables 8.1F (130826) and ODBC 9.1A (131217). ADS version 1.12.54.2623.

We have been using Adagio on Windows 8.1 since January 2014. It works correctly in every respect except one: After about two weeks or so of use, a Windows 8.1 user will suddenly encounter the “Workstation Files Must Be Updated” message. Unfortunately, even if he allows the update to occur the message keeps coming back persistently.

If another user logs on to the very same machine Adagio will work correctly. (There is no request to update files.) The only way to fix this problem is to delete and re-create the non-working user’s local account on the local machine. He can then work for about another two weeks.

I cannot really say whether it is just an elapse of two weeks, or if something else happens coincidently, such as Windows Updates.

My assumption is that there is really nothing wrong at all with the local workstation files since other user accounts on the same machine still work (at least for their two weeks). The problem must be something that gets “switched” in the non-working user’s files or registry entries.

This problem occurs on both our Windows 8.1 machines. It does not occur at all with our Windows 7 machines. So my question is, what is Adagio checking for on startup that triggers a workstation update?