Hi VisualCron support,

2 of our servers are on VC 7.7.3 and have an execute task that runs a batch file.
There are no arguments/credentials/anything - it's a very simple task.

About every week or two, we get the following error.
Restarting the VC service resolves it, but it's starting to become a pain.
Any idea what could cause this?

Error at starting process: System.ComponentModel.Win32Exception (0x80004005): No such interface supported
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.CNOMLBFDJANALDAEIKLKHLCGKEJIGMLIMBLK.ICIFCCBPPIKNFACOHPNGNNHLKMDBPHAFOCNG(Boolean ) in C:\sourcefiles\code\VisualCronService\Jobs\TaskProcesses\Process\clsProcessTaskExecute.vb:line 565

Thanks!

Hi,

do you have an executable we can test?

---

Should have included this bit of detail.

There are a couple steps in the batch file:
1. Run an .exe that calls one of our client facing servers, outputs a csv containing names of datasets
2. Make a copy of jobs.xml (from the VC settings folder) and place it in the same folder as the output of #1
3. Loop through the file from #1 using a 'for' loop with findstr, to filter the csv results to only show names of datasets that also exist in jobs.xml

Idea: There are some old data sets on our client facing servers that we don't touch anymore. Those don't have any corresponding tasks in VC.
The idea is to take the csv from #1 and only show the data set names that have a task in jobs.xml with the exact same name.

This parsing jobs.xml is unique to this pair of servers having the issue. We have dozens of other places where we are running #1 alone and has never had a problem.
So I think the question is: Is there a safe (or different) way to make a copy of jobs.xml so I can parse it safely?

Thanks!

The safest way is probably to schedule Export settings Task first - and to export Jobs only. Then you can use the Extract Task to extract the file and later use it in your executable.

---

Thanks Henrik, I forgot that task even existed.
I switched to running that as a separate export beforehand and haven't seen it reoccur in about a week. Marking it solved for now.

Thanks,
Kevin