We have been using Adagio for 8 years with several users in a Server / Windows 7 workstation environment. We are running 60 Lanpaks, 10 modules (DC\AP\AR\GL\GV\IC\OE\CQ\PO\MC) and 3rd party software (Tookit/PrintBoss/Paymate).

Around November 2015 we began experiencing a problem that we have never experienced with Adagio before. Users working in Adagio began freezing (cursor circle spins). When one user freezes, we all freeze. The only way we can proceed when this happens is for all users except those who were in the middle of posting, to crash close their Adagio programs. This usually frees up those who were posting and allows them to complete their post and prevent data corruption.

This problem was occurring 5 or 6 times a day in our Nov/Dec busy season. We have slowed down now but still having this problem 2 or 3 times a week. In general, the most heavy usage is in OE although PO, IC and other modules are also in use.

We are working with our Adagio Consultant and looking at options with our IT people to move from a Server / Workstation environment to an RDP Server (Terminal Server) environment to eliminate the Adagio data transferring over the network.

I am wondering if anyone else has reported Adagio freezing with multi-users? If so, how long has it been happening? Was a direct cause ever determined?

It doesn't make sense to me that after many years of using Adagio that this problem just began occurring a few months ago and continues to occur even at times when Adagio usage is very light. I am comfortable moving ahead to an RDP Server environment to improve stability and avoid data corruption, but I would still like to understand the cause for the freezing.

Have you never seen a piece of hardware get flaky after years of use?

Are you supporting the same number of users since Adagio was originally provisioned 8 years ago? If you are supporting more users, have you increased the installed RAM in the server to support the additional load?

Thanks for your suggestions Andrew. We are hopeful that replacing the hardware and upgrading will resolve the issue. Are we the only site reporting this type of "freezing" behaviour?

You're not the only one. But most of the time "freezing" is related to hardware or the OS failure to execute a task.

There are many variables that could contribute to the "freezing" behaviour. If the server is 8 years old it's presumably near the end of it's life. Lack of RAM, hard drive failure, issues with a switch...Like Andrew said, the performance on any old equipment can become flaky.

But if the freezing occurs for everyone at the same time, it seems to me that it has to be the server and you would need to start your troubleshooting there. But if you're already replacing the equipment, it's no longer worth your time to figure it out.

If the freezing is only occurring during periods of very active usage in OrderEntry, you can ask your Adagio consultant to install V 9.2A (160125) with the (160201) Hot Fix.

This incorporates a multi-user change to the user logging to resolve a problem we were having in our in-house CRM product during periods of high usage. User activity is logged into common file similarly in both applications, and occasionally workstations in our office would hang in a "deadly embrace" resulting when a dropped resource unlock call resulted in a workstation waiting for its own task to complete, and then other workstations waiting on the first one.

The Hot Fix incorporates the change in resource logging implemented in our in house system. Although there was nothing incorrect in the original code, we have not experienced the deadly embrace since it was changed.

You can see whether this reduces the number of workstation "freezes" at your site.

Thank-you Dan and Andrew for the information.

I've experienced more freezing also since the upgrading all my modules last week. Better since the sp and hotfixes from last week but still hanging from time to time and still getting access violation errors. My main modules affected are PO's when many open, A/R when changing companies to another A/R and G/L when going from Financial reporter back to gl. This is not really related but i'll add this here too, the print jobs are extremely slow now to process. My m/e printing large reports took forever in Inventory module, it took 20min to print a sales history for the month which normaly would take 30 secs. I'm not sure why it appears to be an issue now with the upgrades and never was before when it comes to the printing process. All workstations are windows 7, and windows server 2008 and have necessary hardware so i don't think that is the problem.
if you have any ideas let me know thanks.Treasure

Hi Treasure,

Well, it all starts with a Snapshot. Could you send one to support at softrak.com please? You generate the snapshot file to email us by running \softrak\system\chksys.exe and selecting the Snapshot button on the top left hand corner of the main dialog.

The Adagio 9.2A modules completely revised the printing technology used in Adagio so that we could ship the current version of SAP Crystal Reports 2013. This required architectual change (our previous technology was over 10 years old) has resulted in some additional overhead in generating reports.

If you want us to investigate the performance of a specific report, we will need a copy of your data uploaded to www.softrak.com/dbr to the attention of technical support with a concurrent email that has a screen shot of the report options you are using and the duration the report takes to print on your system.

Several large Adagio sites have engaged Main Computers:
to troubleshoot Adagio set up issues at their sites. Much of this can now be done remotely. Main Computers supports Softrak's IT infrastructure.

Today I would be expecting 4 to 8 GBytes of RAM on each workstation and 64 GBytes in the server running over a switched 1 GBit network.

If you are running DataCare every night, include the address DataCareFail at softrak dot com to your email on failure distribution list so that someone can monitor the health of your data.

thanks Andrew i'll get what i can to you next week when i have a min.
I haven't had any Datacare failures, but yes i can include you in that