I have a job/task that creates a report, it's called by Execute, Run hidden, Use shell execute.
It's calling a bat file.
There's no change to the task since like forever.
Monday night was the last successful execution.
On Tuesday night the job did not execute, giving error "No such interface supported".
I've tried several things and eventually rebooted the server.
To no avail:
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 )

No Log entry is generated, but a popup appears for this unhandled error.
No changes were made to the server nor to the Job or VC on Monday ...
Version 8.27

What could be causing this to cease working?

Let me add, after rebooting the task tested to be ok, but actually returned the error when it was scheduled.
I just now rebooted the server again, and the task now executes ok again, tested twice.
But that's how it was yesterday too, so I'm pretty sure the task will fail tonight...

No idea what causes the change, but you could try not using shell execute:

https://stackoverflow.co...such-interface-supported 

No idea what causes the change, but you could try not using shell execute:

https://stackoverflow.co...such-interface-supported 

Thanks, but it is not working without shell execute.
The bat is simply calling a sequence of cmdline utilities.
When started without shell execute it immediately returns with exit code 1.

Try to find out which line in the script that causes the error and post it here. You might have to remove line by line to find out.

---

The problem is "Shell execute".
As soon as that's activated I'm getting the interface not supported.
Even when the bat file is empty.
After a reboot it is ok for a while and then at one point this error occurs and persists until the next reboot.

My guess is, there's a service or other program that's causing this, but what to look for?

Shell execute prevents you from using a Credential. I think you need to use a Credential with Load profile option. If it still fails you need to find the row that causes the error.

---