Forum Discussion
I would check and see if the .xml actually ends up where you think it is. Also check permissions on that folder.
Hi Marsha,
Seems like I have fixed the issue with Test Results not being published. Now it shows the results in the "Test" tab.
However, now I want to run SessionCreator.exe using local user account and not the domain account.
so, when I try to run using the local user account from the pipeline, I am getting the below error -:
SessionCreator.exe : The term 'SessionCreator.exe' is not recognized as the name of a cmdlet
do you know how can I get around this problem?
I am also getting the same error when I login to the VM using local user account and run it directly through PowerShell as administrator. However, when I run the TestExecute first and then run SessionCreator.exe it runs fine which is wierd.
Not sure how can i make it run through the Azure DevOps Pipeline.
Thank you
- Marsha_R3 years ago
Champion Level 3
See if this helps
https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/index.html
- Marsha_R3 years ago
Champion Level 3
I would check the local user account privileges and make sure that it is allowed to do everything you need.
- dave_user3 years agoContributor
local user account is already an administrator.
I dont understand why it would show "SessionCreator.exe is not recognized as the cmdlet"
Can you think of any other way to troubleshoot this issue?
Thank you
- Marsha_R3 years ago
Champion Level 3
I would ask Support that question directly. Here's the link:
- dave_user3 years agoContributor
Thanks.
I have been trying to get in touch with the Tech support team since quite a few days but their support is extremely slow which is very frustrating.
have you encountered the same issue?
- Marsha_R3 years ago
Champion Level 3
I usually hear back within 24 hours unless they are working on a solution for me. Do you have an open ticket?
- dave_user3 years agoContributor
Yes, i have the ticket open since Jan 18th
- dave_user3 years agoContributor
Thank you Marsha_R and sonya_m . Appreciate your help.
I added the path to the Environment variables in the windows and it seems to be working fine now.
Does sessioncreator.exe needs me to be logged into the VM where testexecute is installed all the time? When I logged into the VM and i am actively watching, the test runs fine but when i move away from the VM to work on something else and i am not actively watching it gets stuck and does not move forward. Even worse, when i disconnect from the VM (Not signout) it fails to connect and test fails.
Do you know any workaround for that?
Thank you