Running Visualcron 6.2.2 on Windows Server 2003 in a virtual machine and Windows Server 2008 on non-virtual hardware. Clients are on Windows 7.

The Visualcron installation on Server 2008 is behaving normally.

The service on Server 2003 was restarted this morning. When it came back up, it continued processing jobs normally, and the client on the VM behaves normally, but two workstations (which is all of them we've been able to try at this point) display no groups or jobs, whether the list is told to group jobs or not.

User permissions are accessible, as are client connections, certificates, conditions...well, everything in the Server ribbon, really, except Running Jobs. The Log window shows all the usual messages for what is going on, except Task is always blank and Job Name is "Not Found".

Restarting the server, restarting the clients, and doing a soft reinstall of the service (reinstalled 6.2.2 without uninstalling it first) have produced no change.

Adding (via remote client) or modifying (via the client on the server machine) a job causes it to show up in the remote client's list until the connection is closed and reopened.

Anyone have an idea what could have caused this?

It appears that the problem was caused by a task having the result/stderr output:

Error in SQL query: ERROR [22018] [Microsoft][SQL Native Client][SQL Server]Conversion failed when converting the varchar value '¹§Ìƒ˜Âe.' to data type int.

Exception in Task: ERROR [22018] [Microsoft][SQL Native Client][SQL Server]Conversion failed when converting the varchar value '¹§Ìƒ˜Âe.' to data type int.

I'm guessing some part of that invocation of a dark entity, or whatever it is, couldn't be transferred via the connection on port 16444 but could be retrieved via IPC.

...Trying to add a new job with no tasks and with that message as the job description caused the client to hang and did not add the job at the server.

Try to uncheck "Use compression" on the Client connection to see if it works better.

---