Hondo wrote:I really prefer the Forum so that it might help someone else down the road. It's infuriating to me when I find a post that applies to my exact situation only to discover you guys took it off line and didn't follow up posting the solution.
As you prefer, I also like the forum more, but that means it might take a day in between answers due to our (apparent) time difference. I would definitely update this thread even we found a solution "offline"...
Hondo wrote:What's up with the Plugin.FireFoxWebFlavor? Is it trying to phone home? What is it doing?
I'm in WPF land. We don't need no FireFox stuff.
No, the FireFoxWebFlavor does not try to phone home, IPC channels are limited to local communication only
That error means that you probably have Firefox open, but do not have the Ranorex Firefox extension installed that is required to automate (and communicate with) Firefox. Either close Firefox, install the Ranorex Firefox extension, or add "firefox" to the "Black-listed process names" setting of the Win32 plugin to get rid of that error message.
- Capture.PNG (8.86 KiB) Viewed 1089 times
Hondo wrote:We do use SVN, but the Automation scripts are being managed outside of Ranorex Studio (not using the built in Source Control feature).
"The node" it can't find does in fact exist.
This could actually cause a performance degradation when working withing Ranorex Studio, but usually not for automation. You could try to completely disable the RanorexStudio source control support by deleting following folder:
"<Ranorex Install Folder>\Addins\SourcControl"
And now let's dig into the issue a little bit more by trying to get as much information as possible (we would usually do this one by one in a remote session):
- Do you have any Anti-Virus program running? Please, try to (completely) disable that
- Could you produce and send us two snapshots of your AUT, one when automation is performing slowly (with VS 2017 installed) and one when it's working alright?
- Can you try to disable some Ranorex plugins and see which plugin actually causes the issue? If you can reproduce the issue with Ranorex Spy, disabling a plugin is easy: open Spy -> click the Ranorex Studio icon in the upper right corner -> right click a plugin in the list of plugins and choose "Disable temporarily". After that click on the "Browse endpoint" button in Spy's element tree to make sure that plugins are refreshed and try if that makes a performance impact
- The problem could also be caused by interaction with some process that is not the AUT. Either try closing all open applications (except for the AUT and Ranorex) when automating or download the Ranorex 8.2 beta1 which adds a process whitelisting feature allowing you to select the processes Ranorex should interact with
Hondo wrote:Major Hang this morning from Ranorex. It got stuck in a bad loop trying to display the error.. I clicked the 'Send Report' button.
I had a look at that bug report, an "Invalid Window Handle" exception stemming directly from the WPF code. I can only imagine this to be connected to the other weird issue, both having to do with C++ interaction...
One thing to add: We will try to get rid of the Visual C++ setups with Ranorex 8.3 and include the required C++ DLLs directly into the Ranorex setup. Not sure if that will make a difference for your problem, but if you want to try out that change as soon as we implemented it, make sure to join our Beta program:
https://www.ranorex.com/beta-program/
I hope we get a little bit further with your answers to my question. Thank you for your cooperation!
Regards,
Alex
Ranorex Team
