ExecuteCommand failed, Pipe broken error with WebAii 2011.2.1305

[Nick]

We use WebAii on a small team for our (HTML) website automation. After recently upgrading from version 2010.3.1421.0 to 2011.2.1305.0 and having a mostly issue-free experience, we have run into a blocking issue for one person on our team. The new version is having trouble communicating with the browser after it launches and the page loads -- this is only on a single tester's machine. Other testers run his same code with the same build and it works without issue. If he changes his references to point back at the old version, the issue does not happen.

When I trace it as far as I can, we make a call into the Click() method on a link element and 5 minutes later the below exception comes back. Are there any known issues that could cause the following exception?

ExecuteCommand failed!
BrowserCommand (Type:'Action',Info:'NotSet',Action:'Click',Target:'ElementId (tagName: 'a',occurrenceIndex: '10')',Data:'',ClientId:'Client_6ca9905c-e6c3-418c-a61f-f0cc631792fd',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'False',Response:'')

InnerException: System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at ArtOfTest.WebAii.Messaging.Process.PipeCommunication.WriteCommandToPipe(PipeCommand command, PipeStream pipe, Boolean waitForDrain)

at ArtOfTest.WebAii.Messaging.Process.BrowserRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
at ArtOfTest.WebAii.Core.Browser.ExecuteCommandInternal(BrowserCommand request)

The machine is Windows Server 2008 R2 with IE9 installed; we all run the same versions of Windows, IE, and Visual Studio. There were no code changes associated with the switch to the new version that we had to revert, so nothing in our stack has changed.

Let me know if there is a way to collect more detailed logs for investigating this issue.

Regards,
Nick

[Cody]

Hi Nick,

This is strange behavior. The stack trace basically tells us that the communication path that was created to communicate with/control the browser broke. It tried to send the .click command to the browser but timed out during that process. You can enable some additional logging by setting the registry key shown in the attached screen shots.

Greetings,
Cody
the Telerik team