Forum Discussion

Smehan's avatar
Smehan
New Member
14 years ago

ToolbarWindow32 would not work

I am using Windows 7 64-Bit:



TestComplete 8.70.727.7



According to this link http://support.smartbear.com/viewarticle/15096/, I have tried several samples into my test scripts and run it.  I kept getting the error message "The Window does not respond"



Additional Information:



The window with the 0x00010098 handle exists but did not respond during the
auto-wait timeout (11000 ms).



Try increasing the 'Auto-wait timeout'
project property.



Tested
object:

Aliases["Explorer"]["wndShell_TrayWnd"]["TrayNotifyWnd"]["SysPager"]["ToolbarWindow32"]

(Sys["Process"]("Explorer")["Window"]("Shell_TrayWnd",
"", 1)["Window"]("TrayNotifyWnd", "", 1)["Window"]("SysPager", "",
1)["Window"]("ToolbarWindow32", "User Promoted Notification Area", 1))



I have increased the auto-wait timeout and yet it will not work.



I am using C#Script.



Please help me.

4 Replies

  • Hi Sandip,


    We have not faced the situation before. Please send us some information about your system through the Contact Support Team dialog in TestComplete.

  • The same error occure at my test system (Win7 64-Bit)



    Test Complete 8.70.727.7



    I'm using Keyword tests for testing our new application.(not optimal, but we decided this way)



    I tried also script tests with Jscript, but the same error occurs(only to test if its only a keyword problem)



    Additional Information:



    -

    The window with the 0x00010098 handle exists but did not respond during the auto-wait timeout (10000 ms).



    Try increasing the 'Auto-wait timeout' project property.



    Tested object:

    Aliases.Explorer.wndShell_TrayWnd.TrayNotifyWnd.SysPager.ToolbarWindow32

    (Sys.Process("Explorer").Window("Shell_TrayWnd", "", 1).Window("TrayNotifyWnd", "", 1).Window("SysPager", "", 1).Window("ToolbarWindow32", "Infobereich des Benutzers", 1))

    -



    Increasing auto-wait timeout didn't show any effect.



    If I trigger the test manually with Testexecute/TestComplete there are no problems.

    If the test is triggered via Hudson Server integration, I get the error message above.

    (Hudson is just starting Testexecute and choosing the test project for timing the starting point)



    The tests fails always at the point where the tests do a double click on the toolbar icon.





    Lars
  • mkrapivner's avatar
    mkrapivner
    New Contributor
    Was there any resolution or workaround to this issue? We are experiencing exactly the same thing.



    Thanks!

  • Hi Matt,



    Basically, you need to increase the Auto-wait timeout project option or insert a delay in your test before the erroneous action. If it does not help anyway, we need to investigate the cause of the error in your case individually, so please submit a new support ticket.