Forum Discussion

EagerTester's avatar
EagerTester
Occasional Contributor
9 months ago

Azure batch node DistributedCOM error when running SessionCreator

Hi, I am having an issue with running SessionCreator on Azure. Our automation setup uses Azure Batch to run Tasks on nodes. Each task will run the test project using SessionCreator on the node.  Th...
Integrations
  • EagerTester's avatar
    EagerTester
    8 months ago

    Thanks for the reply. After further analysis and debugging, It appears as though the /UseActiveSession option was the problem. I had left this in the command after testing, and this appears to have been causing the problem. 

    My guess is the first task finished, but did not close the first session immediately once it was done. The second task then ran and used the first session, which shut down shortly after.

rraghvani's avatar
rraghvani
Champion Level 3

DistributedCOM is a Windows error, not relating to SessionCreator.

When you say second task run, has the first task actually finished? Is it launching more than one instance of SessionCreator?

EagerTester's avatar
EagerTester
Occasional Contributor
9 months ago

Thanks for the reply.

I do understand that the DCOM error is a Windows one, but I am wondering if it is being triggered by SessionCreator by any chance?

The order of events is:

  • Node starts
  • First task runs and kicks off SessionCreator
  • First task finishes
  • Second task runs and kicks off SessionCreator again
  • Error occurs shortly after.

 

There should not be more than one instance of SessionCreator being launched. I dont see any related SessionCreator logs in the event viewer. Is there anywhere I can get this information to ensure the first instance of SessionCreator has infact stopped correctly?

  • rraghvani's avatar
    rraghvani
    Champion Level 3
    9 months ago

    What are the actual commands and parameters used for SeesionCreator?

    Is the VM always on, with a user already logged on? How many interactive user sessions can there be on your VM?

    The utility opens an interactive user sessions, and this can been seen via Task Manager -> Users.

    • EagerTester's avatar
      EagerTester
      Occasional Contributor
      8 months ago

      Thanks for the reply. After further analysis and debugging, It appears as though the /UseActiveSession option was the problem. I had left this in the command after testing, and this appears to have been causing the problem. 

      My guess is the first task finished, but did not close the first session immediately once it was done. The second task then ran and used the first session, which shut down shortly after.