Posted: 4 Mar 2019 11:28 EST Last activity: 7 Mar 2019 8:21 EST
Why aren't the Factory objects being matched during an automation?
While an automation running, the active IE window that is being worked on will freeze up and become unresponsive until it is manually closed. Upon investigation, the RuntimeLog points to 3 different Factory objects being unable to find a valid factory module: ActiveXFactory, WinInetFactory, and MicrosoftHTMLFactory.
During interrogation, these 3 factories are matching without a problem. But every time theyre failing to match in the RuntimeLog it shows them trying to match with netprofm.dll, npmproxy.dll, and MSVCR100.dll.
I am not entirely sure what these factories are used for, or if theyre even the reason why the IE window would be freezing, but would appreciate some guidance if possible. Thanks!
The messages you are showing are informational. Matching is a "trial and error" process, meaning a majority of the time that matching is occurring, it will fail to match a given control as Pega Robotics is testing each of the match rules against all possible targets, the majority of which, are not the target that we are attempting to match too. Think of a valet going through a parking garage attempting to find your car. They are going to test each car to see if it is yours. Unless yours is the first one they encounter, they'll fail to match on many before they get to the right one.
In your case, the IE freezing seems to be the issue not the messages indicating that PR failed to match specific dlls to a factory. I would open an support request to get someone to look into why IE is freezing. Generally, this is because of security software or some other environmental issue.
Is there a way to close the window without stopping the adapter? When I use the Stop() method to attempt to close the window (using the various different properties to terminate), the only result I'm getting is the automation stopping and not progressing forward until the window/process has been closed