Changes in 7.0.5

[FEATURE] Client/Server: Added 30 VMWare Tasks
[FEATURE] Client/Server: Added Activate/Inactivate Trigger in Job/Task control Task
[FEATURE] Client/Server: Added Content-type option based on file type
[FEATURE] Client/Server: Added option to run Execute Task on remote Server without creating Job or Task at remote Server
[FEATURE] Server: Performance fixes in the Excel - Create Task
[BUGFIX] Client: Fixed an issue causing crash in Running Jobs window
[BUGFIX] Install: Handled some possible install problems
[BUGFIX] Client: Fixed a problem with Client not storing Add new line property in File write Task - added new line break options
[BUGFIX] Server: Fixed a issue with SQL Trigger raising wrong events (inactivated) when updated
[BUGFIX] Server: Fixed a problem with updating status for Jobs that were started throught he Job/Task control Task.

---

New version uploaded. Further fixes to Running Jobs window and new VMWare Tasks.

---

Hi Henrik,

Can you have a look at Client Updates where the Job is Called.

We have a number of Sub Jobs we call from other Jobs.

We are not seeing the client update when these jobs are called.

Also we *sometimes* see the tasks not updating in the client, though they have run.

When you drill down (Job / Task History) Information is complete (and correct).

We have tried from both 7.01 <Released> and 7.05 <Beta> Clients . . . . assume this may be server side ?

Please see screen prints attached

Hi Again Henrik,

File Triggers, Polling, and NAS

I posted separately in the Enhancements that Triggers are more stable now it seems on the NAS (as of 7.0.3 changes).

Unfortunately it didn't last . . . . please see the attached notes.

This was a File Trigger, with Polling switched on, pointed at a Hitachi NAS.

The file trigger was able to be setup, and was working for a period of time, but then crashed the visualcron service.

The Error is what I got without Polling (Samba) switched off.

The server log is what I got with Polling switched on (which worked initially as a file trigger but eventually failed).

New version uploaded, changes:

[FEATURE] Client/Server: Added 30 VMWare Tasks
[FEATURE] Client/Server: Added Activate/Inactivate Trigger in Job/Task control Task
[FEATURE] Client/Server: Added Content-type option based on file type
[BUGFIX] Client: Fixed an issue causing crash in Running Jobs window
[BUGFIX] Install: Handled some possible install problems

---

Hi Again Henrik,

File Triggers, Polling, and NAS

I posted separately in the Enhancements that Triggers are more stable now it seems on the NAS (as of 7.0.3 changes).

Unfortunately it didn't last . . . . please see the attached notes.

This was a File Trigger, with Polling switched on, pointed at a Hitachi NAS.

The file trigger was able to be setup, and was working for a period of time, but then crashed the visualcron service.

The Error is what I got without Polling (Samba) switched off.

The server log is what I got with Polling switched on (which worked initially as a file trigger but eventually failed).

Please let us know if latest version works better.

---

Sorry Henrik, No Joy.

Using Latest 7.0.5 Beta

Again it worked for a While . . . . and then the VisualCron Server Seemed to go into a loop on the file trigger, and a set of files were added to the directory and they had been processed.

Was firing into the logs every second per attached.

Disabling the Trigger or Job Didn't Stop it on the Client.
Switching the Server off didn't help either.
Ended up Stopping the Service

Please see screen print attached.

Again this is a File Trigger on a NAS with Credentials & Polling On (Every 60 Seconds).

New version uploaded, changes:

[FEATURE] Client/Server: Added option to run Execute Task on remote Server without creating Job or Task at remote Server

If you get problems installing this version (overwriting files) then go to:

C:\Users\<your username>\AppData\Local\Temp and delete the folder VisualCron and try again.


KJDavie - please test this version and send the log or screen print again.

---

Hi Henrik,

I get an Archive Error on the latest beta file for 7.0.5, install works for 7.0.4.

Please see attached screen print.

Hi Henrik,

I get an Archive Error on the latest beta file for 7.0.5, install works for 7.0.4.

Please see attached screen print.

What archive error? Did you follow the steps we mentioned:

If you get problems installing this version (overwriting files) then go to:

C:\Users\<your username>\AppData\Local\Temp and delete the folder VisualCron and try again.

---

Sorry Henrik,

My Bad, I did an uninstall, but those files were left around.

Once I tidied up that path all was good.

I have the trigger running again, have put some files through and have included some log output.

Seems OK so Far . . . . . I will leave it running overnight and review logs again in the morning.

Trigger Still Looking good after overnight.

Polling and Processing Files.

Hi Henrik,

Write Files Task - Add New Line Checkbox - Does not seem to be updating when unchecked.

Please see attached we are needing to output a file in Unix Format / without the <CR>. As such we don't want this task adding <CR> so have unchecked this box.

When we hit OK and come back into the task, the checkbox is set again.

Please see attached

Enhancement

Also Attached is the options you provide in your SQL Output Task.

Having more options like this on the Write Files Task would be an even better. Particularly the option to Toggle <CR><LF> and <LF> as the line breaks to cater for Windows Style or *nix style file outputs.

Hi Henrik

Issue raised by KJDavie is confirmed just as we are about to upgrade 🙂.

Cheers

Andy

Hi Henrik,

Write Files Task - Add New Line Checkbox - Does not seem to be updating when unchecked.

Please see attached we are needing to output a file in Unix Format / without the <CR>. As such we don't want this task adding <CR> so have unchecked this box.

When we hit OK and come back into the task, the checkbox is set again.

Please see attached

Enhancement

Also Attached is the options you provide in your SQL Output Task.

Having more options like this on the Write Files Task would be an even better. Particularly the option to Toggle <CR><LF> and <LF> as the line breaks to cater for Windows Style or *nix style file outputs.

We have fixed this and added your suggestion. Thanks for the report! A new version will be available for download later today.

---

New version, changes:

[BUGFIX] Client: Fixed a problem with Client not storing Add new line property in File write Task - added new line break options
[BUGFIX] Server: Fixed a issue with SQL Trigger raising wrong events (inactivated) when updated

---

Hi Henrik,

Some overlap here perhaps with an issue Keith Davis raised on 29/08 under General Problem Solving "Backup Settings Jobs Fail".

I am seeing some issues with archiving (the Archive - Compress Task).

This is with the latest 7.0.5 Beta (but per above I don't think its necessarily about this beta).

We are Using variables to define the folder path. If the Path (or the Variables) are invalid then I think we are seeing a crash in the logs rather than a useful error back to the User ? - We just get the generic 7777.

I have included a screen print of the mouseover text also from the system log.

What is in the Mouseover is correct (Error in the Compress Zip Folder).

I have also attached todays System Log which Includes multiple examples.

VC Service Running as delivered (Local System Account).

See Final Screen print with a File in use error generated from the 7-zip Application (nothing to do with VisualCron other than that is 7-zip).

There are many and varied reasons why the Compress Task (really the Underlying 7-Zip) might fail.

Perhaps in part it's just a question of how you capture (and expose) 7-zip errors back to the Archive - Compress Task (and the User) in as user friendly way as possible to assist with diagnosis and resolution ?

Hi Henrik,

Some overlap here perhaps with an issue Keith Davis raised on 29/08 under General Problem Solving "Backup Settings Jobs Fail".

I am seeing some issues with archiving (the Archive - Compress Task).

This is with the latest 7.0.5 Beta (but per above I don't think its necessarily about this beta).

We are Using variables to define the folder path. If the Path (or the Variables) are invalid then I think we are seeing a crash in the logs rather than a useful error back to the User ? - We just get the generic 7777.

I have included a screen print of the mouseover text also from the system log.

What is in the Mouseover is correct (Error in the Compress Zip Folder).

I have also attached todays System Log which Includes multiple examples.

VC Service Running as delivered (Local System Account).

See Final Screen print with a File in use error generated from the 7-zip Application (nothing to do with VisualCron other than that is 7-zip).

There are many and varied reasons why the Compress Task (really the Underlying 7-Zip) might fail.

Perhaps in part it's just a question of how you capture (and expose) 7-zip errors back to the Archive - Compress Task (and the User) in as user friendly way as possible to assist with diagnosis and resolution ?

I tested and there is no problem resolving Variables generally. About the lock it might because of that specific error, we have to located it first.

Are you using a local or remote path? Please add screenshots of Variable and content of Variable. The problem can be in 3 place; 1. archive path 2. archive item->folder 3. archive item->file mask. I suspect it is wrong in on of these places.

---

Is 7.0.5 going to be a Offical version release soon.

Is 7.0.5 going to be a Offical version release soon.

Hopefully by the end of this week.

---

New version uploaded - added more debug logging.

---

New version - fixed an issue in Copy files Task.

---

Hi Henrik,

Compression Task & Errors on Archiving

The problem came to down to an undefined variable in the Archive Path.

So the Error in VisualCron on the Compress Task (7777) is correct.

Screen Prints attached.

And the Crash in the System Log "Error in CompressZipFolder" is what the issue was (and much more informative). . .

Perhaps this is an enhancement request, for a future version, but it would be *nice* if more of the details around what is wrong from the Compression Task / 7-Zip . . . . . could be exposed back to the Client - Output (Stderr). . . . .

Thanks

Kevin

New version released today, changes:

[FEATURE] Server: Performance fixes in the Excel - Create Task
[BUGFIX] Server: Fixed a issue with SQL Trigger raising wrong events (inactivated) when updated

---

Final version was released today. Please upgrade with that official version. Thank you for your testing!

---