topic RE: Chrome not able to identify elements while debugging the process or running from control room in Product Forum

Chrome not able to identify elements while debugging the process or running from control room

VivekG_R — Thu, 13 May 2021 17:42:00 GMT

Hi,

I'm using Blue Prism version 6.8.1, chrome version 90.0.4430.212 and Blue Prism Browser Extension version 2.1.0. I'm able to spy elements using Browser mode from Application Modeller and able to run the actions from Object Studio. When I try to run the chrome actions from process using debug mode or from control room, BP is unable to identify the elements from chrome and process gets terminated.

I tried restarting the machine and reinstalling BP. Nothing worked so far.

I read from BP customer support page that this issue has been resolved in BP versions 6.8 and later. Have anyone come across this situation and resolved it?

------------------------------
Vivek
RPA Developer
------------------------------

RE: Chrome not able to identify elements while debugging the process or running from control room

_Amlansahoo — Fri, 14 May 2021 04:42:00 GMT

Hi Vivek,

Try enabling fixed port, it may work. Any way blue prism behaves very strange to browser mode.

------------------------------
Amlan Sahoo
RPA Consultant
Equinix
------------------------------

RE: Chrome not able to identify elements while debugging the process or running from control room

VivekG_R — Sat, 15 May 2021 17:25:00 GMT

Thanks Amlan.

Though I have this option checked in my System--> Settings, I'm facing this issue with chrome browser. I figured out below errors in BP chrome extension at the time of process execution.
1) WebSocket connection to 'ws://127.0.0.1:31924/' failed:
2) uncaught error: attempting to use a disconnected port object

I'm trying to clear this error at chrome launch (before BP tries to find an element).

------------------------------
Vivek G R
RPA Developer
------------------------------

RE: Chrome not able to identify elements while debugging the process or running from control room

EmersonF — Sun, 16 May 2021 03:25:00 GMT

Vivek, it worked for me a while ago, see if it helps you.

Try

' Looping to find the process id by the process name
For Each pProc As System.Diagnostics.Process In _
	System.Diagnostics.Process.GetProcessesByName(strProcessName)
	pProc.CloseMainWindow
Next pProc

	Success = True
    Message = ""
 
Catch e As Exception
 
    Success = False
    Message = e.Message
 
End Try

------------------------------
Emerson Ferreira
Avanade Brasil
+55 (081) 98886-9544
------------------------------