DATA-CARE Error
He's the problem for about the past 3 months our consulant is not able to fix this issue and wanted me to contact you at Softtrak Tech Central for he seems to be out of answers on this consent problem.
The Data Care has an Error Occur each day when starting the backup procedure and it doesn't go away. Every day The Error Occure reads like this
c:\Prgam Files\Syscon\weAPICOM\SysTrayIcon.exe.log" for
This will not allow us to handshake the process to allow a remote backup with web safe . Can you help me fix this issue?
Thanks,
Les Frischman
Best Buy Uniforms
Pittsburgh PA USA

Have you updated the link from WebSafe to VitalESafe?

Actually, this is the error that Lester is receiving:

“Unable to start data integrity check. System Account has Adagio DataCare open.”

DataCare is installed on the server, and is scheduled to start each evening at 9:00 pm.
The GridView Server is also on this server is scheduled to stop at 8:55 pm.
Both of these events are occurring at the appropriate time.

However, it appears that the DataCare is open before we even start. We are not really sure why this is, as no one is on the workstations at this time, and no one is opening the DataCare.
As well, all users logout of Adagio at the end of each day.

Further more, if I were to look at the Active Users during the day, I will find that DataCare is open, even though to the best of our knowledge, no one opened the program.

So any ideas how we can ensure that DataCare is not open each evening?

Samuel

Hi Samuel,

If nobody for sure is using DataCare but the Active Users list is showing this, then the file that determines which users are in which application has become corrupted.

First try getting everyone out of everything Adagio and then remove the EZSEMTAB.dat file from the company data directory (substitute the real company data extension for dat). Then open any one Adagio program and check the Active Users to see if the DataCare usage has gone away. Should this work, then continue along and keep a watch if the scenario re-occurs. The likely cause is that DataCare is not getting closed correctly, for whatever reason.

If removing the EZSEMTAB data file does not resolve the DataCare user issue, then try getting everyone out of everything Adagio and then remove the EZTASKS.LD4 system file from the appropriate system directry. It probably is \softrak\system but it may be loaded elsewhere. To check for sure, edit the ADSPROF.dat file in the data directory (using notepad) and at the top will be the location of the 'EZTASKS path'.

All of this is just to remove the user who is being listed as using DataCare but actually is not.

Perhaps others have practical suggestions for ensuring that DataCare is not open at the end of the day.

If we are successful in getting rid of our "phantom user" using your instructions, is there anything that we should additionally do to ensure that DataCare is closed on the server after it has completed its job, at the end of the night?

How do they run DataCare overnight? A scheduled task or a delayed job (with the workstation locked)? If the former case then it should just happen. If the latter then by definition DataCare will not close when finished.

I imagine if run by a scheduled task and DataCare does close, have the first person in the morning check the Active Users to see if DataCare closed.

I can't suggest any ways to ensure that DataCare closes while it is run unattended. DataCare and Windows and the network all have to do their thing correctly.