Community forum

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


ct-vc
  •  ct-vc
  • No customer Topic Starter
2016-03-09T10:26:11Z
Hi Team,
Basic Info:
I have a python script that crawls the web every week, checks whether there are new files on the website, downloads these files, saves the downloaded link in a locally created DB (sqlite used), unzips these files and copies them over to a network drive. To run this script on a different server (server does not have Python installed) I packaged this .py script into exe (py2exe used).

Issue Observed:
When I run this exe manually it does its function i.e. works as desired, but when I schedule it using VC then it succeeds with the required messages that the script is expected to log, but the work is not done. It means that the script doesn't fail or give any errors at the same time it does not work. When I say it does not work, I mean it just gives a message that I have coded "the file is downloaded and the entry is made into local DB" but it does not create any local DB which the script is expected to and hence doesn't download or copy the files too.

Trouble shooting I tried:
I tried to create a new job and added the script, but the result is same. I also deleted the existing exe file and replaced it with a new exe of the same script, but in vain. Please note scripts runs perfectly when exe is run manually, i.e. creates the DB, logs the new entries in it and then copies the files as required and displays the correct message too.

Please help.
Sponsor
Forum information
bbusse
2016-03-31T20:20:44Z
Usually when things don't work as expected, it's due to testing only being done using your own user account vs the user account VisualCron is using to actually execute the process.

When you run it yourself, that's your ID with whatever environment variables you have, your permissions ,etc..

When VisualCron runs the process, it's under the context of whatever ID your VisualCron service is configured to run as, or the credential you've specified in the Task itself. We run our VisualCron service as a domain id (i.e. Domain\VCService ) and so to troubleshoot something like this, i log into the server/workstation as Domain\VCService and try running it manually as you did with your ID. See what happens then.

if it's running as LocalSystem i'm not sure what to tell you as far as troubleshooting. We have always used a Domain Account that is a local admin on the VC server for that reason, easy troubleshooting.

Brian
Scroll to Top