Inflectra Customer Forums: Remote procedure call fails and sets tests to "Blocked" (Thread) Hi All, We have Remote Launch (v5.1) setup to run TestExecute (12.5) tests on a Windows 10 machine. Some of our tests are being Blocked and we cannot figure out why. Below is the error from the SpiraRemoteLaunch.log, and this is all it reports back to SpiraTeam. 12:01:23.6073294: Business.RunTestThread::ExecuteSet() Error running test. The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at Inflectra.RemoteLaunch.Engines.TestCompleteEngine.TestExecute12.TestExecuteEngine.StartExecution(AutomatedTestRun4 automatedTestRun, Int32 projectId) at Inflectra.RemoteLaunch.Business.RunTestThread.ExecuteSet(RemoteTestConfigurationEntry tstConfig) We have been seeing this issue a lot lately after the latest Windows 10 update, so I think that may have something to do with it. Has anyone seen this before or have any suggestions? Thanks! Seth en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/remotelaunch/automation-engines/1869.aspxthreadId=1869Seth Dippold (seth.dippold@etegent.com)windows 10 remotelaunch testexecute testcomplete rpc remote procedure call blockedRemote procedure call fails and sets tests to "Blocked" Hi All, We have Remote Launch (v5.1) setup to run TestExecute (12.5) tests on a Windows 10 machine. Some of our tests are being Blocked and we cannot figure out why. Below is the error from the SpiraRemoteLaunch.log, and this is all it reports back to SpiraTeam. 12:01:23.6073294: Business.RunTestThread::ExecuteSet() Error running test. The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at Inflectra.RemoteLaunch.Engines.TestCompleteEngine.TestExecute12.TestExecuteEngine.StartExecution(AutomatedTestRun4 automatedTestRun, Int32 projectId) at Inflectra.RemoteLaunch.Business.RunTestThread.ExecuteSet(RemoteTestConfigurationEntry tstConfig) We have been seeing this issue a lot lately after the latest Windows 10 update, so I think that may have something to do with it. Has anyone seen this before or have any suggestions? Thanks! Seth Thu, 21 Jun 2018 18:02:26 -04002018-07-02T20:06:33-04:00/Support/Forum/remotelaunch/automation-engines/1869.aspxmessageId=3322Jim R (donotreply5@kronodesk.net) It sounds like some kind of security update in Windows 10 is breaking the connection between Remote It sounds like some kind of security update in Windows 10 is breaking the connection between RemoteLaunch and TestComplete. Maybe you need to change some of the DCOM security settings. Please log a help desk ticket for more specific support. Regards Jim Mon, 02 Jul 2018 19:39:05 -04002018-07-02T19:39:05-04:00/Support/Forum/remotelaunch/automation-engines/1869.aspx#reply3322messageId=3326Seth Dippold (seth.dippold@etegent.com) Hi Jim, We have created a support ticket, but I will bring this up to them. Do you have any sugges Hi Jim, We have created a support ticket, but I will bring this up to them. Do you have any suggestions on which settings to change? Also, the tests that are blocked are not always consistent. Some runs, a test may be blocked but the next time we schedule it, it will run through completely. Thanks! Seth Mon, 02 Jul 2018 20:06:33 -04002018-07-02T20:06:33-04:00/Support/Forum/remotelaunch/automation-engines/1869.aspx#reply3326