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?

We have a utility that gives us basic workstation runtime-checking information. Please run ....\softrak\system\GetAdagioWorkstationInfo.exe, selecting both GL & AP on a {failing} 8.1 machine. Copy the result and email it to me (rdowning@softrak.com).

If you have a Win8.1 machine that is not failing, please do the same, so that when it starts failing we can do it again and have a baseline comparison.

NOTE: I don't understand your version of ADS - that version comes from Jan 4/2010 (!!) Your GL shipped with version 1.12.54.3087, dated Dec 17/2013. Where did you get that value from? Can you please verify it?

Finally, when an Adagio module starts cycling on Win8.1, is it just that module or do they all start cycling?

Thanks, Rod

I have a similar problem right now with a Win 8 machine. But there is only one user and it is the Administrator on the machine. Client is running a peer to peer network with 4 workstations (3 Win 7 machines and the one Win 8). "The server" is Win 7. All modules started cycling on the Win 8 machine after ePrint was installed and it's the only Win 8 machine there.

I have already ran the workstation update for ePrint and it is the only module that logs in properly on this machine with the exception of Countersales.

I took the workstation info on all modules. And I noticed this on all modules info: "PDF Must update: [True]; Reg: [] >= File: [20110510]"

Why aren't the other modules picking up the PDF update?

John:

This has been an ongoing problem since, I believe, Windows v8.1 was released:

You have to rename the folder: x:\SOFTRAK\SYSTEM\AdagioPDF to x:\SOFTRAK\SYSTEM\AdagioPDFXXX

This has to be done every time you install any Adagio update.

Thanks Doug! John's posting was an old one. But I picked up on it since the answer wasn't posted on his original post.

PLEASE run the program in Rod's post and send him the results! Renaming the Folder short circuits a process that the Adagio modules expect to have been run. We need to determine why these workstations are not properly updating their Registry settings.

Thanks.

Sent it to Rod.

Our company is experiencing this same problem with a Windows 8.1 computer for all our Adagio programs. I ran the utility that Rod suggested, and I emailed him the information for both a working and non-working Win8.1 computer. Let's see if Softrak can suggest any resolution. Thanks.

Andrew Novasitis
IT / LAN Support
Line Systems, Inc.

As far as we can determine, on some machines Windows is reporting to the Install that a value has bee written to the registry, but when the program goes back and queries the value Windows is reporting that the value doesn't exist.

We have not yet determined a "why" for this and are exploring whether we need to take another approach.

Thanks for sending the report to Rod.

Just a thought: why do users -- even some larger ones -- assume that their software will automatically, seamlessly work with a new operating system? Did no-one learn from the problems upgrading software, printer drivers, etc. from Win 98 to XP or XP to Win 7?

Software developers, including Softrak, should simply state: "We have not fully confirmed that our programs work fully and without issue on the new operating system. If you want to try it, go ahead, but you are on your own; DON'T CALL US."

As of today, that statement is still true.