I have a client who was trying to use Adagio but was getting errors. Here is what happened:

Yesterday, he logged in to Adagio and got:
"Critical Error 1305: unknown" and "OS error accessing EZTASKS". Then he was unable to login to that specific dataset. He tried logging into other datasets and they worked fine.

Today, is was able to login to that specific dataset that he was unable to go into yesterday. When he got in, he performed a data integrity and got 39 errors. I checked his system and noticed that he was missing the EZTASKS.LD4 file in Softrak\System. So I sent him my file and tried the data integrity again, but I still got the 39 same errors. Any ideas on what I can do?

Good morning, Mach,

Re: the 1305 error and OS error accessing EZTASKS, this normally happens for one of two reasons:

(1) Someone has opened a module in Plus, then they or someone else goes to open the same module in Adagio, and they do not have any LanPaks for Plus. If the reverse were true and they?d opened Adagio first, then Plus, and they didn?t have enough LanPaks for Adagio, Adagio would give the insufficient lanpaks/licenses message instead.

(2) Or, there are bad parameters specified in the Adagio module shortcut ? eg. a directory path is specified incorrectly or it has spaces in it.

From what you are describing, it sounds like (1) above is more likely the culprit.

Regarding the data integrity check, from what I can see in the information you emailed us, all of the errors relate to departments being invalid. Check your client?s Company Profile in GL. On the Options tab, is ?Enable departments? checked? If so, uncheck it.