I've been trying to implement Time Matrix for over a year and continue to have issues. I believe Time Matrix is working correctly, but my issue relates to our nightly Windows Server Backup.
We are running SQL on a virtual server. Time Matrix must be able to communicate with SQL continually or it times out, so when the next employee tries to clock, it throws an error message.
When our nightly backup runs, the first job is to take the virtual server off line and take a snapshot of the server. This takes about 6 or so minutes. We have tried to write a Scheduled Job to stop Time Matrix a few minutes before the backup runs, and then re-start it a few minutes later. This is where we're having the issue. I believe we can get it to stop, but are not able to get it to re-start. We don't want our employees to have access to the mouse or keyboard, so they're locked away.
Does anyone have an idea how we can get Time Matrix to re-start without having to launch it from the icon via mouse click?
If you've found this thread useful, dive deeper into User Group community content by role