I have a job that has begun failing with the error:

Exception in Task: The process cannot access the file 'C:\Windows\TEMP\VisualCron\35a8cc8a-205f-49ca-972a-6b03a4418232' because it is being used by another process.

When the job runs in the schedule, it fails, If I go to the folder and delete the offending file, the job run fine.

Any thoughts?

Thanks,

Don

Which version are you using now?

---

Version 8.2.7

Can you let me know if you still get the issue in this build:

http://www.visualcron.co....aspx?g=posts&t=7329 

---

I run this in a live production transaction processing system. I cannot upgrade to a point release without some process unless I have good reason to believe the upgrade will address my issue.
Looking at the change log for that release, I do not see any indication that this issue might have been addressed.
Is there any other insight anyone can give me about this? The problem is intermittent, but causes us some heartburn when it happens, as the notification of failure goes out to external clients.
Anyone?

Thanks,

I recall that I have seen this before and that it has been fixed. But are you saying that once it fails it will fail again and again until the file is deleted?

---

Thank you for your response.
I don't have the luxury of waiting to see if it continues to fail - this is the only job showing this behavior and it only runs once a day. When it fails, I simply delete the files and the issue is resolved. I suspect that I don't even have to delete the file to see it resolve, but because it generates external notifications, I cannot easily verify that.

However, since I posted this question the job has run without issue every night. At this point, I'm willing to wait until we can upgrade the point release and see if it really is gone.

I'll hop back if it shows up again, and I will try and see if I can re-run it without manually deleting the files (we'll play some sort of game with our SMTP server or something).

Thanks,
Don

I'm having this same problem with build 8.2.8
I had to revert back to build 7.6.3 so that the errors would stop.
It was only occurring with ssis 2012 tasks.
I had powershell tasks and process tasks that would report success with no issues.
I was noticing that when the ssis 2012 task was running it would create the temp file with 0KB and then when it reported the failure about few seconds later it would finish writing what it was trying to write to the file. So it looks like the thread that tries to read the file is racing against the thread that is writing to the file. When running ssis tasks it writes lots of text, so I am thinking the thread that reads the file is initialized to early before the running process is finished writing to the temp file.

Exception in Task: The process cannot access the file 'C:\Windows\TEMP\VisualCron\05d5ddfa-9a66-4a45-925b-18d6c7a4c3fb' because it is being used by another process.