Forum Discussion
Could you give more of the log? From what I'm seeing, there's a navigation line above the error... so... are you SURE it's happening there and not on the BrowserWindow.Close? Double click on the error line should take you to the line of code generating the error.
Also... I suspect that the code you posted here is NOT exactly what is executing. Is it possible for you to post the actual code generating the error?
Please make a try plain script (without aliases)
- BenoitB5 years agoCommunity Hero
I think this is time to call the Support team because you are able to reproduce systematically the problem.
Just one question, if you test any other web page like a page in google or yahoo, do you have same problem, working on W7 and not on WS16 ?
Bah c'est le lieu ou l'on cause ici ;^)
- Nikolayev5 years agoContributor
Good Idea BenoitB , I 'll made a lab tests with the Smartbear website..
Then find others similar topics in the community...
and then... A least open a support case with the lab example easy to reproduce.
It looks like not to be a time-out matter, I add a 30sec delay objets still unreachable.
Any other idea tristaanogre ?
I thought it was a bad settings with Chrome Smartbear Add-On but exaclty the same settings with the one W7
I thought it was also again an SSL settings with Chrome ,.... but not...
Yes because, I just cant access to my website from Chrome just before this new issue,.. and now it seems to bo ok with SSL in chrome, I import a Cert.PFK file and it looks good.
Any other idea ?
- Nikolayev5 years agoContributor
Hi sonya_m ,
TC Version is 14.30.743.7 x64.
Same player shoot again ! ^^
I tried to reproduce with the smartbear web site and then open a case as suggested by
BenoitB .... But can't open a Case, because everything works fine with SmartBear Website
No more ideas came to me for the moments.
If I have one, I'll let you now...
Regards,
Nico
- sonya_m5 years agoSmartBear Alumni (Retired)
Hi Nikolayev , maybe you could consider updating first? I see that you are using not the latest version.
If this doesn't help, contacting support would be the best next step.
- Nikolayev5 years agoContributor
Hi Shehnaz
Hi There,
I have exactly the same issue too.
I have a Chrome test that works perfectly on 2 W7 machines and returns error msg "window was destroyed during method execution " with a W Server 2016.
I have to fix. BenoitB Asks you to try with Aliases , I have done it and it's the same issue.
In my situation , the distroyed object is somthing like that :
Aliases.browser.pageMyWebSite.panelContent.textnode.Click()
then I change with :
Sys.Browser("chrome").Page("https://MyWebSite/").Panel("content").Header(0).Panel("zone_connexion_deconnexion").Panel(0).Link(0).TextNode(1).Click()> same behaviour, I'm wondering why ?
(Hey salut benoit, c'est cool de se retrouver ici 🙂 ! )
(Hey benoit, cool to see you back here ! )
Related Content
Recent Discussions
- 2 days ago