Exposing process on Azure Trial not working

LAszloJagusztin — Mon, 26 Apr 2021 13:04:00 GMT

Hi,

Tried to expose a process on my Trial on BluePrism Azure:

But unable to call it, simply there is no 8181 port open on the Windows server

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5986 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8199 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49668 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49669 0.0.0.0:0 LISTENING
TCP 10.1.0.4:139 0.0.0.0:0 LISTENING
TCP 10.1.0.4:3389 188.6.91.19:55644 ESTABLISHED
TCP 10.1.0.4:49679 40.67.254.36:443 ESTABLISHED
TCP 10.1.0.4:49699 168.63.129.16:32526 ESTABLISHED
TCP 10.1.0.4:49711 51.141.128.228:443 ESTABLISHED
TCP 10.1.0.4:49718 168.63.129.16:80 ESTABLISHED
TCP 10.1.0.4:49730 40.67.254.36:443 ESTABLISHED
TCP 10.1.0.4:49997 168.63.129.16:80 TIME_WAIT
TCP 10.1.0.4:50005 40.88.32.150:443 ESTABLISHED
TCP 127.0.0.1:10333 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:3389 [::]:0 LISTENING
TCP [::]:5986 [::]:0 LISTENING
TCP [::]:8199 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49664 [::]:0 LISTENING
TCP [::]:49665 [::]:0 LISTENING
TCP [::]:49666 [::]:0 LISTENING
TCP [::]:49667 [::]:0 LISTENING
TCP [::]:49668 [::]:0 LISTENING
TCP [::]:49669 [::]:0 LISTENING
TCP [::1]:8199 [::1]:49752 ESTABLISHED
TCP [::1]:8199 [::1]:50000 ESTABLISHED
TCP [::1]:49752 [::1]:8199 ESTABLISHED
TCP [::1]:50000 [::1]:8199 ESTABLISHED
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:3389 *:*
UDP 0.0.0.0:5050 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5355 *:*
UDP 10.1.0.4:137 *:*
UDP 10.1.0.4:138 *:*
UDP 127.0.0.1:49228 *:*
UDP [::]:123 *:*
UDP [::]:3389 *:*
UDP [::]:5353 *:*
UDP [::]:5355 *:*

Please help how to call it? It is a default installation from the Azure Marketplace.

------------------------------
LAszlo Jagusztin
------------------------------

RE: Exposing process on Azure Trial not working

james.man — Wed, 26 May 2021 01:58:00 GMT

Hello,

I just launched the Azure Trial VM, and found that the default Runtime Resource was disconnected by default due to an incorrect machine name. For some reason, the default Runtime Resource was named "pkrvmio2ocbrckl", but my actual machine name is "MarketplaceTria". I needed to retire the incorrectly named Runtime Resource. After retiring, I restarted the Blue Prism software which allowed the correct Runtime Resource to launch. After that, I could see that port 8181 was open on using "netstat -a"

So, see if the following works for you:
1) Retire the existing Runtime Resource by going into "System" -> "Resources" -> "Management", and drag the Runtime Resource from the "Active Resources" Pane to the "Retired Resources" Pane.
2) Close the Blue Prism software and re-login

------------------------------
James Man
Professional Services
Blue Prism
Asia/Hong_Kong
------------------------------

topic Exposing process on Azure Trial not working in Product Forum

Exposing process on Azure Trial not working

RE: Exposing process on Azure Trial not working