Hi all,
I'm running into an odd issue with Adagio over a network (Server 2016). With Windows 7 Pro, I had no problems with Adagio, but with Windows 10, it randomly goes to "not responding" (often after sitting with no activity for an hour or so).

I've set the GPO for drive disconnects as recommended by Adagio.
I have the Adagio folders on the network drive and the local drive excluded from AV scans/realtime.
I've set the Ledger and Payables processes excluded from AV realtime.

It isn't packet loss because I've tested for that, and the server isn't running at high utilization.

Any suggestions would be greatly appreciated.

Thane

Make sure that the workstation is not putting the network cards to sleep under the power saving options.

I set the card in Device Manager that Windows cannot put it to sleep (should have mentioned that in the first post, sorry).

Does Adagio put any information in a log that I could check?

Generally, the Adagio applications write to a file called SDAPPLOG as work is performed. However, they can only do this when they are actively being used.

"Not responding" is a terrible Windows message, because it is displayed every time an application fails to process a mouse click or keypress in a specific amount of time. Sometimes the application is just "busy".

If a user has Adagio open, but leaves it idle for a long time, Windows may swap the application out to disk in order to free up memory for other applications. Outlook is an enormous resource chewer and will take every available byte if launched. Excel may or may not need lots of memory, depending on the size of the spreadsheets being used.

On older machines, loading a swapped application can take a measurable amount of time - often beyond the patience limits of most users. When you launch Task Manager, make sure that you have I/O read bytes and I/O write bytes displayed in the details tab so that you can see whether the application is busy doing other I/O.

If users just have the applications open and their main Grid displayed, then there is little exposure (other than convenience) in killing the task and restarting. Users should be actively discouraged from minimizing an application with a batch or transaction open and not saved to disk. They risk losing their work in that event.

PS - Could you please post the name of the company you are trying to assist.

This is a shot in the dark, but could there be a window opening up an a monitor that is not connected? Clicking on Window; original sizes, will fix this. This happens to me a lot when I move from a docked situation to a non-docked situation. The "not responding" message pops up in that instance.

This is a known issue for Domain Controllers 2012R2 or newer. They have a default policy that recreates the mapped drives which disconnects Adagio and make it crash.
It only happens with W10; not with W7

Hi Thane,
We have seen this same situation on W10 on my Notebook. You attempt to start up Adagio (as in a demo) and it just locks up the entire workstation. You cannot even do a task manager to break it out. The whole machine freezes and my only recourse is to wait or hard boot the notebook.

We have had my notebook rebuilt from scratch wiped and brand new windows install, and with the number of programs installed, it's not something that I take lightly. About after a month of re-installing upgrades from Adagio the situation recurred.

And now the situation is almost random and very frustrating.

We believe but not proven, that there is conflict with the Crystal Driver mix being linked in with the various Adagio upgrades. The fact that you have to install the Adagio modules and upgrades/service packs in an oldest to most recent date order because of the various drivers and dates of drivers that link up with the downloads makes us very cautious on installation process.

So if I install Adagio on my workstation as a standalone install, I have problems with not responding. If I run the same workstation with the same workstation install, (ie my notebook is configured to run like a server with shared drives that match to our LAN servers), then the LAN connection works fine. So the issue is not the workstation install.

If and when we have more time to test, we will update if we get a resolution.

Best,
Brian