Ranorex Forum

I noticed this yesterday. I was trying to run a test on Chrome but it was like it wasn't instrumented, it could only see /form and not /dom. So I reinstrumented, nothing. I was using Ranorex version 9.4 so I updated today, to the latest version. I re-instrumented all the browsers but the only browser Ranorex sees the dom for is Internet Explorer. I really don't know what else to do to get this to work. I've un-instrumented/re-instrumented....what else can I do?

Hi,

Please make sure that neither Chrome and Edge is running in background (by default enabled). Then try to uninstall Ranorex plugin via instrumentation wizard and install it back.

odklizec wrote: ↑

Tue Sep 14, 2021 8:57 pm

Hi,

Please make sure that neither Chrome and Edge is running in background (by default enabled). Then try to uninstall Ranorex plugin via instrumentation wizard and install it back.

I have the running in background disabled for both Chrome & Edge. But I double checked just to be sure.

I have removed the plugin and reinstalled but it's still not seeing the /dom

Hi,

Just in case, please check if there is anything in the whitelist. If there is whitelisted anything but Chrome and Edge, Ranorex will ignore DOM in these browsers

odklizec wrote: ↑

Tue Sep 14, 2021 9:31 pm

Hi,

Just in case, please check if there is anything in the whitelist. If there is whitelisted anything but Chrome and Edge, Ranorex will ignore DOM in these browsers

The whitelist only contains Chrome

I've uninstalled Ranorex completely and then reinstalled, instrumented and instrumented and instrumented. I enabled developer mode on Chrome extensions and the ranorex extension is throwing an error:

Unchecked runtime.lastError: Specified native messaging host not found.
Context
background.html
Stack Trace
background.html:0 (anonymous function)

Hi,

Unfortunately, it's hard to tell what's wrong here? I think this kind of issue must be investigated by Ranorex developers. My best guess is, that it's some kind of permission/GOP issue? Have you tried to install Ranorex on another computer and reproduce the problem there?

I would suggest to create an official support ticket and request assistance directly from Ranorex support.

I've got a call with Ranorex Support this morning to figure it out.

So, it’s sorted out? What was the reason of the issue?

It was because I had Chromium, Firefox and Chrome instrumented. Support had me de-instrument all the browsers, and then just re-instrument Chrome. Then I had to refresh a few times and Ranorex finally saw Chrome again. Oh and she had me check "Allow access to file URLs" in the Ranorex extension in Chrome.

Unfortunately, it only worked until I ran a test. Now I can't get any browser to stay instrumented with Ranorex.

I ended up getting it to work. Something I had installed must have had a conflict because I just removed and reinstalled Windows and all my programs and I haven't had a problem. Probably a .NET version or something.

I'm experiencing the same issue.
From time to time, Ranorex doesn't recognize anymore the content of Edge pages.

This has nothing to do with updating Ranorex, updating the (Chrome) plugin, the plugin' settings, whitelisting, Chrome running in the background ... and all these things the current support is telling you.

You can just see by yourself that the problem is that the plugin isn't running properly when Edge is started.

You don't need Ranorex for that; just start Edge manually and:
- go to Extensions
- click on the link "background.html" in "Ranorex Automation"
- there you see that an error has occurred:
Unchecked runtime.lasterror: Specified native messaging host not found

Same error happens when the browser is started by Ranorex rather than manually.

When I wait for a while, the error isn't there anymore ... then it may come back later.
As you guessed, a process is interfering with the plugin ... but which one ?

PROBLEM: how can I find out what is conflicting with the plugin ? How do I investigate ?

Any help welcome,
Thanks,
Yves

I had that error once. But I can't remember the plug in that was breaking. What you should try and do is disable all your plugins except Ranorex and then enable one by one to see if you get the same error messaging.