Forum Discussion
my Azure pipelines are running successfully now. i'm am no longer getting the "Cannot start process because a file name has not been provided." error message. the only change I made was to ensure TestExecute is active before the pipeline kicks off. Before, TextExecute was not actively running on the VM (which is the way I've had it set up for almost a year) and the pipeline would start TE, run the test scripts and then exit TE when the pipeline completed. something has changed in the latest release(s) that seems to have altered that feature. Can anyone else confirm this as a solution?
i just returned from vacation to discover that none of my automated testcomplete pipelines will run EVEN WHEN testexecute is actively running on the VM (see my post from 7/28). now, with TE running, i'm seeing this error
Unable to connect to TestExecute: it is running with different rights, or its state is incorrect. Please close it and try again.
i have tried closing and restarting testexecute both normally and running as admin but nothing works.
when is that new release available? if not today, then which previous version does work?
Given the recent fiasco with the Chrome and Edge browsers and now this, i'm beginning to regret the recommendation i made to the management at my company to abandon Ranorex in favor of TestComplete. What is it with SmartBear lately that is causing all these show stopping issues to occur?
Related Content
- 12 years ago
- 14 years ago
- 8 years ago
Recent Discussions
- 3 days ago