Test Playback Issue - System.TimeoutException

[Zachary]

Hi - I am currently evaluating WebUI QA edition. I am able to record tests, but I am unable to get achieve playback. I receive the following error:

'3/1/2011 10:46:47 PM' - Error launching the runner. Error: System.TimeoutException: The operation has timed out.  
    at System.IO.Pipes.NamedPipeClientStream.Connect(Int32 timeout)  
    at ArtOfTest.WebAii.Design.Execution.RunnerController.Launch(Int32 waitForReadyTimeout, String pathToRunner, Int32& runnerProcId)

I have referenced another thread regarding this same error, but the steps outlined in that thread did not help the problem.
 (Changed "Network access: Restrict anonymous access to Named Pipes and Shares" from Enabled to Disabled - did not work)
 
I have WebUI installed on a VM running Windows Server 2003 R2 with Internet Explorer 8. 

I appreciate any help you can provide - this is a frustrating roadblock since I cannot proceed with testing until it is alleviated.

Thanks again.

[Cody]

Hi Zachary,

I am sorry to report that this problem never was solved for Anas or William in the thread you referenced. Anas never responded to my request for a GoToMeeting.

I did do a GoToMeeting with William to look at the problem. I determined that in his case it is being caused by some sort of network/domain group security policy being forced on his machine by his IT administrators.

He was going to try talking to his administrators to get permission to install the software on his real machine (they don't even give him Install permissions on his own machine) or try a different machine all together. I never heard back after that.

I can at least confirm we do work on many different VM environments. I have used our software successfully on Hyper-V, VMWare and Windows XP Mode for Windows 7. Out of curiosity, why are you running it on a VM? Which VM system are you trying to use? Have you tried running the software on a real machine? Does that work?

Kind regards,
Cody

the Telerik team

[Zachary]

Hi Cody,
Thanks for the timely response.

The system contains Windows Server 2003 R2 running on a VMWare ESX host - our environment is primarily virtualized. Installing it on my laptop would be an interesting test, but the fact is that we hope to take advantage of the scheduling capabilities, and it is difficult to do so on a non-stationary machine.

I have been able to playback tests intermittently in the past, so I believe it's possible on this machine. I am happy to have a GoToMeeting with you if that would help, and I am open to any other suggestions you may have.

Thanks,
Zach 

[Zachary]

Hi Cody,

I forgot to mention that I have admin rights on my test machine. Please let me know if you have any additional suggestions to alleviate this issue.

Thanks,
Zach

[Zachary]

Hi Cody,

Looks like @Dev had a similar issue (end of the thread). Any luck with him? I would really appreciate any guidance you can provide.

Thanks,
Zach

[Cody]

Hi Zachary,

Sorry, no, he also did not respond to my GoToMeeting request. I'd be happy to look at this on your machine. How soon would you be available for a GoTo?

 

Greetings,
Cody
the Telerik team

[Zachary]

Hi Cody,

I would have said today, but there is some network maintenance that is not allowing me to access my VMs. If you're the type of guy who works on the weekend, I can make that happen, if not we can go for Monday. Feel free to grab my email from my telerik user account (if you have access) and we can take this convo offline. Otherwise just let me know what works for you.

Thanks,
Zach

[Cody]

Hi Zachary,

Monday it is. Does 1:30pm EST work for you?

 

All the best,
Cody
the Telerik team

[Cody]

Hello Zachary,

For documentation purposes, the problem was solved by upgrading from 1213 build to 1421 build.

 

All the best,
Cody
the Telerik team

[JENNIFER]

I am experiencing this problem on Windows Server 2003 test playback in Chrome.  The test runs in IE and in FF.  But does not start in Chrome.  I've downloaded the latest build from my account and set up the permissions and browser per the instructions provided in the knowledge center and verified that my extensions are correct.  Are there any suggestions as to what may be going on?

5/17/2012 1:22:07 PM' - Using .Net Runtime version: '4.0.30319.1' for tests execution.
'5/17/2012 1:22:07 PM' - Starting execution....
'5/17/2012 1:22:38 PM' - Failure detected during execution. Details:
------------------------------------------------------------
'5/17/2012 1:22:38 PM' - System.TimeoutException: Wait for condition has timed out
   at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
   at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
   at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
   at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InitializeWeb(ExecutionEngineCreateParams initParams)
   at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.CreateAndInitializeEngine(Test test, ExecutionEngineCreateParams cp)
   at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)
------------------------------------------------------------
'5/17/2012 1:22:38 PM' - Test completed!

[JENNIFER]

I am experiencing this problem on Windows Server 2003 test playback in Chrome.  The test runs in IE and in FF.  But does not start in Chrome.  I've downloaded the latest build from my account and set up the permissions and browser per the instructions provided in the knowledge center and verified that my extensions are correct.  Are there any suggestions as to what may be going on?

5/17/2012 1:22:07 PM' - Using .Net Runtime version: '4.0.30319.1' for tests execution.
'5/17/2012 1:22:07 PM' - Starting execution....
'5/17/2012 1:22:38 PM' - Failure detected during execution. Details:
------------------------------------------------------------
'5/17/2012 1:22:38 PM' - System.TimeoutException: Wait for condition has timed out
   at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
   at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
   at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
   at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InitializeWeb(ExecutionEngineCreateParams initParams)
   at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.CreateAndInitializeEngine(Test test, ExecutionEngineCreateParams cp)
   at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)
------------------------------------------------------------
'5/17/2012 1:22:38 PM' - Test completed!

[Byron]

Hi Jennifer,

There is a known issue with Google Chrome 19 that prevents Test Studio from connecting to the browser for execution. If you are using Chrome 19, we plan to release an internal build addressing this issue tomorrow (May 18), which you will be able to download from your Telerik.com account.

However, your specific error appears to be caused by an inactive browser extension. If Chrome reports your Test Studio extension as active, try deactivating and reactivating the extension, then trying your test execution again.

Greetings,
Byron
the Telerik team