For our automatic deployment we use the Commandline tool AutomateC.exe with the parameter /exportpackage.
We want to log the output-result (AutomateC is executed by our Releasing-Tool), but every time we redirect the standard-output, the AutomateC.exe returns an Exception.
The issue is also reproducible, if the call is redirected to a file:
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\AutomateC.exe" /exportpackage "PackageNameXXX" /user username password > ResultToFile.txt
Â
Error processing action: exportpackage.
BluePrism.BPCoreLib.BluePrismException: Failed writing XML for type: releaseout; ID: 43; Name: PackageNameXXX - Release 33; Error message: Das Handle ist ungÂltig.
 ---> System.IO.IOException: Das Handle ist ungÂltig.
  bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
  bei System.Console.SetCursorPosition(Int32 left, Int32 top)
  bei AutomateC.AutomateC.ReportProgress(Int32 perc, Object msg)
  bei BluePrism.BPCoreLib.clsProgressMonitor.OnProgressChanged(Int32 value, Object data)
  bei BluePrism.AutomateAppCore.clsRelease.WriteXmlHead(XmlWriter writer)
  bei BluePrism.AutomateAppCore.PackageComponent.ToXml(XmlWriter writer)
  --- Ende der internen AusnahmestapelÂberwachung ---
  bei BluePrism.AutomateAppCore.PackageComponent.ToXml(XmlWriter writer)
  bei BluePrism.AutomateAppCore.clsRelease.Export(Stream stream, clsProgressMonitor mon)
  bei BluePrism.AutomateAppCore.clsRelease.Export(FileInfo file, Boolean compress, clsProgressMonitor mon)
  bei AutomateC.AutomateC.Run(String[] args)
Â
Is it possible to fix the problem? Otherwise we can not monitor the deployment process.
Â