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

Quick question:

When I use the Archive-Compress task and select to use 7-Zip as the format, I'm running into a problem. I'm using a wildcard to select *.log files that are older than 5 days. This is fine, however when the process is done, all the filenames are in the 7-Zip, but only the first file is actually there. All the other files are blank and have a zero length. I don't think it is just a display issue because if I extract one of them it is really blank.

This does not seem to be a problem if I select .ZIP, but I really need to use 7-Zip since my department standardized on that format for archiving log files.

Has anyone seen this issue or know how to get around it?

Forum information
Have not heard of this before, could you:

1. zip the files here (normal zip 😁 )
2. attach some screenshots of your settings
Please like  VisualCron on facebook!
I'll try to get some screenshots together. It only seems to occur when the files are on a remote server and the files are on the larger side (say 25MB per log file). If use small files, it works.

The task is set so that the content to archive is specified on a share, such as "\\server\sharedfolder". It is using a domain admin account as the credentials in the content tab. It compresses the first file, then all the rest are blank.

I think this could be a permissions issue where it is losing it's ability to access the files after the first one. If I use small files it works, large files it does not.

I was able to work around this (I think) in one of two ways. First, I tried using a mapped network drive, and that seemed to work. I then changed the "Visual Cron" service to use a domain account that has access to the share, and now that seems to be working well too.

I'm going to do some more testing...

It seems like a bunch of people on the forums change the service to use a domain account. I think I like that approach since a large number of my tasks are accessing domain resources anyway. Except for having to alter the service anytime an upgrade is done (since it switches back to SYSTEM), is there any downside to running it as a domain account?

Scroll to Top