Forum Discussion

owalker's avatar
owalker
New Contributor
5 days ago

Com server permission error on Process.start

Hello,

Using test execute version 1575 and up I encounter an issue in com server permission settings.

Another application will run Process.Start to start a third application.

TestExecute will then run Sys.Process() with the name of that third application followed by a .Find(strPropNames,strPropValues,1,True)

This will generate a 10016 windows event due to incorrect permissions for the COM server

 

If I manually (with  the mouse) restart that third application and rerun the test, the test works as expected with no permission error. This indicates the issues is with Process.start being used to start the third application's process which test execute is interacting with.

  • 1569 - This issue does not happen on test execute version 
  • 1570 - I encounter another issue which is unrelated before the permissions issue can occur.
  • 1575 - I encounter the permissions error on this and all later versions.

Is this permission issue something that will be fixed in future versions?

The current work around is to use task schedule to start up that third process instead of System.Diagnostics.Process.start.

I've seen it is also possible to fix the permissions in the the component services DCOM Config for TestExcecute and TestComplete, but this is not a valid solution for me.

 

Thanks.

1 Reply

  • owalker's avatar
    owalker
    New Contributor

    I figured this out. Process.start was opening up the third program in Session 0 which is non-interactive and dedicated for background processes. TestComplete was running in Session 1 which is the interactive user session. The the task scheduler is a workaround to this issue because it used the /IT flag, which forces that third application into session 1. Without that flag you hit the same set of permission issues as proccess start when using task scheduler.

     

    I'm not sure why this was not an issue on older versions of test complete.