Remote procedure call fails and sets tests to "Blocked"

Thursday, June 21, 2018

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?



2 Replies
Monday, July 2, 2018
re: sdippold Thursday, June 21, 2018

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.



Monday, July 2, 2018
re: inflectra.jimx Monday, July 2, 2018

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. 



Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Thursday, June 21, 2018
  • Last Reply: Monday, July 2, 2018
  • Replies: 2
  • Views: 12255