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


Guest
  •  JohnC
  • No customer Topic Starter
2014-07-23T13:13:44Z
I am using version 6.1.5 of VisualCron (yes, I know it's an older version) and we are running into log file locking issues when running SQL-Server 2008 SSIS packages.

It seems that when SSIS packages are kicked off, VisualCron maintains a log of the execution results in c:\users\<service account name>\AppData\Local\Temp\ssis.txt. What we think is happening is that if you have more than one job running at the same time, there is contention on the log file, e.g., one job will have this "ssis.txt" file locked while another job is trying to write to it. This results in VisualCron reporting a job failure.

Here is the actual error that's generated:

Unhandled error occured: System.IO.IOException: The process cannot access the file 'C:\Users\SQL_Lawson_Interface\AppData\Local\Temp\ssis.txt' because it is being used by another process.

Is there a work-around to this issue? Can I possibly turn this logging off, or have VisualCron generate a seperate and unique log file for each job instead of it writing all job results to one file?

Sponsor
Forum information
Support
2014-07-25T08:23:51Z
Hi,

this is fixed in later versions. Unfortunately here is no workaround for older versions for this problem.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top