Forum Discussion

sirsergy's avatar
sirsergy
New Contributor
8 years ago

Spira RemoteLaunch - Exception from HRESULT: 0x8001010A when using TestComplete\TestExecute engine

It is possible to launch auto-tests, created in TestComplete tool, with Spira RemoteLaunch tool. But when I try to use TestComplete\TestExecute automation engine in SpiraTeam system, every time I get an error presented below:

 

Exception:
The message filter indicated that the application is busy. (Exception from HRESULT: 0x8001010A (RPC_E_SERVERCALL_RETRYLATER))

Stack Trace:
at Inflectra.RemoteLaunch.Engines.TestCompleteEngine.TestExecute12.TestExecuteEngine.StartExecution(AutomatedTestRun4 automatedTestRun, Int32 projectId)
at Inflectra.RemoteLaunch.Business.RunTestThread.Execute()

 

I have asked Spira Support team about this problem. They answered that for the TestComplete engine they call the TestComplete ActiveX/COM API directly (the same for TestExecute engine), and something is blocking our ability to connect to TestComplete.

 

Is there any possibility for me to fix the issue?

 

Thanks for the help in advance.

 

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    Permissions, most likely.  Also, the remote machine that you're attempting to execute on, is it logged in with an active user session and an available desktop?  If not, you can't run tests... and I think that TestComplete/TestExecute when attempted to run without that will return an error condition.

    • sirsergy's avatar
      sirsergy
      New Contributor
      8 years ago

      Yes, remote machine is logged in with an active user session and an available desktop.

       

      What kind of permissions should be changed? On what side - Spira RemoteLaunch or TestComlete\TestExecute?

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        8 years ago

        Is the RemoteLaunch configured to use that logged in session? See, I've never used Spira, so I don't know... I know what TestComplete and TestExecute require.  They need to have an active, interactive desktop session.  So, if you're RemoteLaunch is using some other session other than the logged in one, you might  problems.

        As for permissions, again, not sure what is needed to access the API... you might need local admin permissions.  If nothing else, the remote launch needs to launch the tests within the existing logged in session and with at least the same user permissions if not elevated to administrator.

  • AlexKaras's avatar
    AlexKaras
    Icon for Champion Level 3 rankChampion Level 3
    8 years ago

    Hi,

     

    Is it the very first test that fails with this error or some subsequent (second, third, ...) one?

    The reason for my question is that according to, say, https://social.msdn.microsoft.com/Forums/vstudio/en-US/70ef972b-51b6-4ece-a4af-d6b4e111eea5/msword-automation-error-the-message-filter-indicated-that-the-application-is-busy?forum=vsto or http://stackoverflow.com/questions/23707475/dcom-config-settings-for-microsoft-interop-word-automation, the 0x8001010A error means that the server is busy and rejects to serve the request.

    In case of TestExecute this may mean that TestExecute completed execution of first test but is busy unloading from memory or something like that while Spira does not wait enough / does not do proper checks to wait until it is safe to start the next test.

    Just my guess...