Blue Prism 7.2 Utility environment VBO Issue

[JeslinArmstrong]

Hi Community,

We recently upgraded Blue Prism to 7.2 from 7.1 in Windows Server 2019 (64bit OS). While we were testing the process, the “start process” & “Run Until End” actions fails in utility environment VBO.

When we run it, Blue Prism 7.2 is showing below error but same works in Blue Prism 7.1

Anyone know what could be happening?

Thank you very much.

[StephanieStrydom]

Hi, we are in the process of upgrading from 6.10.4 to 7.2 (we installed 64-bit). We found that the Start Process (Utility Environment) didn't work as before. We could not send "exe" any more, neither process names such as "msedge", nor complete files paths to executables. However, what does work is sending complete File Paths: "https://www.google.com" (launches in default browser) or "C:\Users\bot\Desktop\New Text Document.txt". The other action: "Start Process Read Stderr and Stdout" still works when you send "notepad" - it launches notepad. We though the issue is related to 64-bit change. So then we installed the 32-bit Blue Prism. The issue remained. We are also on Windows Server 2019.

[_Amlansahoo]

Hi Stepahine,

I am not sure if this issue is related to Windows server 2019 or 7.2 because the same is working for mw in my local.

[ewilson]

@StephanieStrydom 

This is a known issue and is sitting with our product team for investigation. We have not seen any issues with this capability on 32-bit Blue Prism though. It's been specifically 64-bit in all reports to date. There is a workaround though which requires a small modification to the code of the VBO. We'll be publishing an update later today for that.

Cheers,

Eric

[ewilson]

@StephanieStrydom 

Version 10.1.1 of the Environment VBO has been posted to the DX. The Start Process action now exposes a new input parameter called Use Shell. It's a Flag data item. If you're experiencing issues with launching a particular process, try changing the value of that Flag.

Cheers,

Eric

[_Amlansahoo]

Hi Eric,

If that is the solution then it's better to include that in Release Notes or somewhere in the portal, So everyone will be aware of the same. Also, if there can be a document for 64-bit installer it will be great as it might take some time to stabilize.

It's just a suggestion.

[ewilson]

Hi @_Amlansahoo 

Do you mean something like this? 😁

Cheers,

Eric

[_Amlansahoo]

Hi @ewilson That's absolutely perfect.