Completed
Last Updated: 20 Jun 2016 14:34 by Dhruv
ADMIN
Boyan Boev
Created on: 19 Nov 2014 09:31
Type: Bug Report
0
System.IO.IOException: Pipe is broken when "RunToHere" to a click step in customer specific applicatoin
The click is performed, however this exception is thrown:

ExecuteCommand failed!
BrowserCommand (Type:'Information',Info:'IsReady',Action:'NotSet',Target:'null',Data:'',ClientId:'Client_302fd325-de22-45fe-9648-47d348c56df9',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.WaitForPipeDrain()
   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)


Environment: Windows 8.1 with IE 11.

Steps to reproduce and access to the application are in the internal description.
5 comments
Dhruv
Posted on: 20 Jun 2016 14:34
Hi Konstantin,

Thanks for the information. We did go through the release notes of internal build and found this issue as fixed. We have upgraded and the issue is not reproducible on latest internal build (2016.1.609).
ADMIN
Konstantin Petkov
Posted on: 20 Jun 2016 14:14
Hello,

You need to upgrade to the latest Test Studio 2016.1 official release and will get access to it's internal builds. The latest internal build (2016.1.609) includes the change in IE Calibration.

Regards!
Dhruv
Posted on: 13 Jun 2016 07:17
Hi Daniel,

We are facing same issue on a different environment. See below environment details.

OS: Windows Server 2008 R2 Standard
RAM: 8 GB
Processor: Intel Xeon E5-2650L (Dual Core)
System:64 bit
Browser: IE 11.0.9431.0 Update Versions: Preview (KB2841134)
Test Studio Version : 2014.4.1411.0

We are unable to find the specific registry key that you mentioned in above post.
Could you let us know the specific key to be set on our environment?

Also, Could you please suggest us ,if any, internal build version in which this issue is fixed?

Thanks
-Dhruv Parekh
ADMIN
Daniel Djambov
Posted on: 27 Apr 2016 09:28
Telerik: we have found a fix for the IE issue -  it turns out that this bug is introduced with a Windows or browser update. The workaround is to set a specific registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BFCACHE]
"iexplore.exe"=dword:00000000 - for 32 bit OS

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BFCACHE]
"iexplore.exe"=dword:00000000 - for 64 bit OS

We have added this to the browser calibration in our latest source code (product with fix will be available in our next product release planned for May 2016), but in the mean time you can manually change the registry setting to get it working.
ADMIN
Daniel Djambov
Posted on: 22 Dec 2014 11:16
Telerik: this issue seems to be a problem in some IE 11 instances, related to a specific in security browser setting. This happens only on some IE11 browsers, only when a mouse Click step is performed over a hyperlink that performs navigation in browser. The workaround for this problem is to start IE browser on such environments with parameter: 'iexplore -extoff' and then attach to browser - then the problem will not be observed. No fix can be done from our code base for this for now.