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


osirisja
2014-11-11T10:16:25Z
Hi Henrik

I have discovered an issue with V7.07 and setting variables. I have a critical parameter that must be set but it doesn't seem to be getting invoked correctly.
Screenshot 1 shows the Set Variable command, and the key value is the filename 'iasa_commsbox.csv'. The command definitely runs according to the LastRun column (screenshot 2) however screenshot 3 shows the value is not being updated.

There are also other instances of this happening. The screenshot MIDAS1 shows the MIDAS_DEENV variable being set in the VC Log file with a filename highlighted, however the screenshot MIDAS 2 shows the SET VARIABLE command clearly setting the same variable to a different filename.

This has actually caused a bit of a panic - is there anything that might be the cause?

Cheers

Andy
osirisja attached the following image(s):
Sponsor
Forum information
Support
2014-11-11T11:31:17Z
Have you tried the same in 7.5.0?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
osirisja
2014-11-11T13:40:37Z
Hi Henrik

No, these are live tasks on VC 7.07 installed across multiple servers, at the moment we do not have a test server set up to test versions, particularly as we have so many production servers running VC.

We are planning on upgrading soon though, but I was hoping there may have been a logical explanation to our issues

Cheers

Andy
Users browsing this topic
Scroll to Top