- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
06-06-2023 03:16 PM
We are seeing intermittent issues when connecting to Azure Portal. This started to occur after we upgraded to version 114 of the msedgedriver.
The error we get, is:
PSMDU018E Dispatcher error: [ConnectionComponentController :: Main -> OpenQA.Selenium.WebDriverException: unknown error: unhandled inspector error: {"code":-32000,"message":"No node with given id found"}
06-08-2023 04:37 PM
We are facing same issue with Chrome version 113.x connecting to Azure or Office365 portal.
not getting any where since support is useless.
Seems to be a bug with connectors in newer version while processing webform request using Chromium based browsers
06-21-2023 02:01 PM
Wondering if CyberArk has any suggestion and how people are working around this other than rolling back to Chrome 112. The issue is new to Chromedriver 113 (and 114) and documented on the chromium bug site (implications outside of just CyberArk), but i do not yet see a move towards a fix: https://bugs.chromium.org/p/chromedriver/issues/detail?id=4440
06-21-2023 02:03 PM
I haven't tried migrating the connectors to Edge and trying the edgedriver. It sounds though like it is both an issue on Chrome and Edge based on the original post? We've been running into the same issue on Chrome - Randomly and frequently the session doesn't open with that error across Azure Portal, AWS, and some others....eventually repeated attempts work.
06-21-2023 02:07 PM
07-20-2023 08:09 PM
Chrome and chromedriver 115 has just been released and I haven't been able to reproduce the error with my testing yet. Anyone else also had better results?
07-21-2023 05:10 AM
We haven't tried it, but mostly because the forum i posted above from chromium have users claimining the problem wasn't fixed. Hoping you or someone else can report back after a little while and confirm whether it is resolved (at least from a CyberArk perspective), in 115.
07-25-2023 11:49 PM
I have tested Azure connection components with 115 and it still has an error but it doesn't crash out. It just hangs for the amount of time the action timeout is set to and then it puts in the password and continues. I found with the action timeout set to 10 seconds for the occasions the error occurs that seems to be acceptable.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

