Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Virtuoso
2023-01-06T22:34:39Z
I have 3 servers where Visualcron is installed. Last month I upgraded our Dev environment from 9.9.10 to 9.9.12. Everything went as planned and the server was signed off by the end user.

This week I upgraded our staging and production environments by downloading a new copy of 9.9.12 to each server.
Almost immediately, deployment failures were reported with vccommand.exe.

After more digging, we found the DEV executable was 10MB in size and ran successfully from the command line. (ver. 9.9.12.19047)
However, the executable which was newly deployed was only 200KB in size and failed to run from the command line. (ver. 9.9.12.21223)

When I checked the packages, I found minor version differences, and the executables deployed matched the package they came from.
This means the current downloadable package has an invalid executable included.

Luckily, I had a working server/package to pull from, but some users may not be that lucky.

This is an FYI to anyone that uses the vccommand.exe command to interface with the API.

Please fix this at your earliest convenience.

Thanks in advance.
Sponsor
Forum information
Scroll to Top