ContributionsMost RecentMost LikesSolutionsRe: Chrome 69 extension for Test Complete 12.6.5545 available? Hello all, the source of the problem is found: I have two monitors and Chrome browser was running on the different one (on primary) as Test Complete (on secondary). This scenario is apparently not possible. Only if Test Complete and Chrome are running on the same monitor the extension will be recognized and tests will run. Is this a known issue? IMO it is really a pitfall - if e.g. Firefox is used, it will be recognized no matter the monitor situation (either on a different monitor than Test Complete or on the same one). This is why it was confusing... Regards, Marin Re: Chrome 69 extension for Test Complete 12.6.5545 available? Hello Alex, unfortunately it does not help - neither re-install of extension from the link nor subsequent reboot: Test Complete extension for Chrome will not be recognized and same error will be logged. Any other suggestions? Thanks, Marin Chrome 69 extension for Test Complete 12.6.5545 available? Hello all, after updating from TC v.12.5 to 12.6 my Chrome tests are not working anymore on Chrome 69.0.3497.100 ("TestComplete Chrome Extension Is Not Installed or Is Disabled"). However, the extension is installed in Chrome and add-on is enabled: In the download section at Smart Bear there is only extension for TC 12.5. My expectation was that 12.6 would already include the extension for Chrome 69? Or am I missing something? My Test Complete Version: Many thanks for any hints, Marin Re: Object Spy will not recognize popup window in Firefox 42.0 Hello Yury, thanks for the feedback. Unfortunately refreshing (CTRL+R) in Object Browser does not help - the behavior is still the same (popup window will not be recognized). Regards, Marin Object Spy will not recognize popup window in Firefox 42.0 Hello all, I wonder if anybody has problems with Object Spy recognition of popup windows in latest 11.20.1491.7 TC release? There is a strange behavior where Object Spy will only recognize the objects in main browser window in Firefox: This is not occurring in Internet Explorer. When running the tests in Firefox however, previously mapped objects in the popup will still be available and operable during the tests, so it seems as if only Object Spy is affected. Any thoughts? Many thanks for any hints, Marin Re: Adobe Acrobat Reader DC (15.0) process will not be displayed in object browser Hello Allan and Helen, many thanks for the quick replies. It seems as if the update to 11.20 has fixed the problem - now Acrobat Reader DC process will show in the object browser. Thanks again, Marin Adobe Acrobat Reader DC (15.0) process will not be displayed in object browser Hello all, has anybody encountered the problem with new Adobe Acrobat Reader DC (version 2015.009.20069) where it will not be displayed in the object browser window? I see the Adobe process in the Windows task manager (AcroRd32.exe *32) , but for some reason it will not be showing in object browser in current Test Complete (11.11.1064.7): Any thoughts? Many thanks for any hints, Marin SolvedRe: How to log error at the beginning of the OnLogError handler Hello Alex, many thanks for the excellent suggestion, this is indeed exactly what I was looking for. Eventually I ended up with your and Marsha's ideas combined -> error log from the corresponding method before start of error handler and error handler's own logs in a separate sub folder. Many thanks again, Marin Re: How to log error at the beginning of the OnLogError handler Hello Marsha, many thanks for the hint. I was aware of the event being fired prior to error, still somehow hoped that there would be a way to determine where error is logged in the thread. I like your suggestion with appending log folder - it certainly does make logs more organized. Thanks again, Marin Re: How to log error at the beginning of the OnLogError handler Hello Marsha, maybe I did not choose the right description: what I meant was that the error message from the function foo() ("Error occurred in foo") should be logged first - before all logs from the OnLogError handler. Does it make sense? Thx, Marin