Forum Discussion

GradyJr's avatar
GradyJr
Contributor
5 years ago

iexplore main window not found and RPC server unavailable

This post is actually about two issues. I doubt the second one has anything to do with TestComplete but thought someone here might have seen it and be able to comment on it and both appear in the ima...
  • tristaanogre's avatar
    tristaanogre
    5 years ago

    As BenoitB , there could be an iexplore process running in your Windows environment that doesn't have a UI... this is a pain in my side with regards to iexplore.. even when you close the browser manually, sometimes that process remains memory resident.  So, your WaitBrowser process FOUND the browser... but couldn't call the "Close" command because there was no window to close.

    What I've taken to doing is, rather than attempting the "Close", I'd actually use "Terminate" to kill the process entirely.

BenoitB's avatar
BenoitB
Community Hero
5 years ago

Beware of that iexplore process could be used by another application or Windows itself and then as no dedicated window of this process is available the closing process could be erratic (invisible confirm dialog e.g.).

 

You can reduce time with setting a maximum time of closing:

Sys.Browser(browser).Close(10000);

 

And to be more robust, manage confirm or #32770 dialog that can appear.

 

Unless that i don't know, never had this problem.

 

About RPC error, i've had it (not in TestComplete) and it was a nightmare to get rid of .. Sort of Windows inside settings...

 

 

 

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    5 years ago

    As BenoitB , there could be an iexplore process running in your Windows environment that doesn't have a UI... this is a pain in my side with regards to iexplore.. even when you close the browser manually, sometimes that process remains memory resident.  So, your WaitBrowser process FOUND the browser... but couldn't call the "Close" command because there was no window to close.

    What I've taken to doing is, rather than attempting the "Close", I'd actually use "Terminate" to kill the process entirely.

    • GradyJr's avatar
      GradyJr
      Contributor
      5 years ago

      I changed my Browser check routine to the following (incorporating the suggestions from both  @BenoitB and tristaanogre). The result can be seen in the attached image. IE starts right up now AND (i'm guessing the two issues must have been related somehow because) I have not see the RPC error the last two or three time I have executed the project suite. SWEEEEET!  I gave kudos to both but accepted tristaanogre as the solution. I initially just tried BenoitB suggestion which helped but it seemed to be even better once I added the Terminate specifically for IE.

       

      Thanks for your help