Hello,

I know this is not a good design but we had the following solution using Windows Server 2008 and SQL Server 2008:

A SQL Server Agent powershell jobstep starts a process with [Diagnostics.Process]::Start. As the process is a software ("Eviews") that unfortunately returns errors not via return codes but "showing" a message box that cannot be suppressed, we killed the process after a certain amount of time.

That worked until we moved to a new server (same eviews version but Windows and SQL Server 2012). Then the jobsteps started to exit without an error even if the eviews did not run correctly, i. e. if the same script showed a "blocking" message b when starting the powershell script not from the agent but a "normal" shell.

Is there a different behaviour like windows recognizing that there is an application started in an environment without user interaction possible so that the software itself crashes when trying to pop up with a message box?

Kind regards

Alexander

Maybe, why not firstly troubleshoot it in Windows Powershell?