Executable output works fine in PS console, but not in Powershell ISE?

Question

I have an SAP program call sapgenpse.exe.

If i excute the below command from powershell command, the output is perfect.

But if i do the same operation in powershell ISE, the output breaks abruptly.

Answer 1

It looks like sapgenpse.exe outputs to the stderr stream rather than to stdout.

Unfortunately, the Windows PowerShell ISE - unlike the regular console - treats and renders stderr output from external programs as errors, even though that isn't appropriate, given that stderr output cannot be assumed to (always) represent errors.
(I have no explanation for the strange format you're getting, however).

There are two workarounds:

• Redirect PowerShell's error stream (through which stderr output is routed in the ISE) to its success output stream, and call the .ToString() method on each error record:

.\sapgenpse.exe ... 2>&1 | ForEach-Object ToString

• Call your executable via cmd.exe and use its redirection features to redirect stderr to stdout:

cmd /c '.\sapgenpse.exe ... 2>&1'

---

As an aside:

• The Windows PowerShell ISE is no longer actively developed and there are reasons not to use it (bottom section), notably not being able to run PowerShell (Core) 6+. The actively developed, cross-platform editor that offers the best PowerShell development experience is Visual Studio Code with its PowerShell extension