topic RE: Windows Command Processor has stopped working in Digital Exchange

Windows Command Processor has stopped working

AnthonyMullen — Thu, 23 Mar 2023 17:09:00 GMT

Hi all

I am randomly getting error saying "Windows Command Processor has stopped working" as a pop up and it is throwing my BOT off.

This is on Runtime resource.

Has anyone seen this before?

when I click close program, it closes the cmd window that is running Automate.exe

Can you help with this please?

Thanks in advance

------------------------------
Anthony Mullen
------------------------------

RE: Windows Command Processor has stopped working

expertcr — Wed, 26 Apr 2023 16:48:00 GMT

Not sure if this error is related to a process that is running using cmd.
You said that you closed the window where Automate was running. Well, you can modify the batch file to close this window automatically after launching the listener.

This is my batch example, after running the 3 lines the cmd windows close.
cd\
cd C:\Program Files\Blue Prism Limited\Blue Prism Automate
start Automate.exe /resourcepc /public

------------------------------
Luis Lopez
Customer Support Engineer English and Spanish
Blue Prism Ltd
------------------------------

RE: Windows Command Processor has stopped working

AnthonyMullen — Thu, 27 Apr 2023 08:07:00 GMT

Hi Luis

thanks for your reply, this is a good option to have to close the window.

I did find the issue.

I was logging into the BOT machine, while the process was already running so it was trying to run the exact same batch file again as it is set to launch when BOT logs in.

Kind regards

------------------------------
Anthony Mullen
------------------------------