Version upgrade / mismatch client and servers - VisualCron - Forum

Community forum

cjamieson
2015-08-14T00:35:29Z
Hi. We have been using VisualCron for some time and up to now I have been running version 4.9.40 as the client on my PC and the same version for client and server on 3 servers. 2 of those servers are running Windows Server 2003 service pack 2. The other running Windows Server 2008 R2 64-bit.
My PC has been upgraded to Windows 8.1, 64-bit. I have reinstalled version 4.9.40 but whilst it 'seems' to have installed OK, the application won't open.
I later installed version 7.7.3 as a client on my PC. Installed OK and runs, but wouldn't connect to the servers.

In my case, what would be the best way for me to configure this? Should version 4.9.40 run on a Windows 8.1 6- bit machine? If not, should a client version 7.7.3 on my PC 'talk' to version 4.9.40 on the servers?

I just wanted to check what is or is not possible with VisualCron before going further.

thanks

cj
Sponsor
Forum information
ErikC
2015-08-14T06:30:26Z
Hi cjamieson, welcome to the forum.

What I know is that the client/server level should be the same. It has to do with the way they communicate. Having a new client v7.7.3 with v4.9.40 server will not work.
Why the 4.9.40 client isn't working on your windows 8.1 64bit machine, I don't know. That might be something for support to check out.

But keep in mind that both the client and the server should be on the same level.

(It's an old version though, you have much more functionality in the latest version. Time to upgrade perhaps?)

Regards,
Erik
Uses Visualcron since 2006.
cjamieson
2015-08-14T12:51:12Z
Hi Erik.

Thanks for the reply. To start at the end - yes definitely due for an upgrade!
Just knowing that client and server should be of the same version helps me to narrow down my choices. I'll follow up when I get back to work next week.

Also, good to know that 4.9.40 should run on the PC, so I'll look further into that as well. The tray client will run, and the service can also run. It's just the client that isn't running.


Thanks again

cj
Scroll to Top