ADO Pipeline Fails with Exit Code '2147483647' and Upgrading to TC/TE 15.75

Originally posted by jkrolczy on June 26, 2025

I noticed recently for my ADO pipelines, as I have updated my Hyper-Vs to the latest TC\TE 15.75,

My ADO pipelines are failing to launch TC\TE.

##[error]Cmd.exe exited with code ‘2147483647’.

When uninstall and downgrade back down to TC\TE 15.74 my ADO pipelines work again.

Anyone seen this or have any advise on what is going on here.

I am updating my TC\TE like I done in the past as newer minor versions come out.

Originally posted by jkrolczy on June 26, 2025

SmartBear - no new changes in the Command-line syntax that would be causing this error in TC\TE 15.75 ?

I send in my cmd line from my ADO pipeline Command Line Script task.
Again, this works for 15.74 but not for 15.75

Originally posted by Hassan_Ballan on June 26, 2025

The error code 2147483647 from cmd.exe is a high-level indication that something went wrong during execution, but it’s not very specific by itself. This value could usually means:

  • An unhandled exception occurred in the application.
  • There’s a deeper issue like missing dependencies, incorrect path, or permissions.

Since your Azure DevOps (ADO) pipeline is failing specifically when launching TestComplete or TestExecute only after upgrading to 15.75 and your installation is valid, I can only suggest you attempt further isolation:

  1. On your Hyper-Vs run TeswtComplete/TestExecute manually to validate operation and license access
  2. In Console run the pipeline command line and check for any crash logs in “C:\ProgramData\SmartBear\TestExecute\Logs” and any error reported in “Event Viewer > Application Logs”

Beside that I suggest you revert back to 15.74 and report to SmartBear support by creating an incident.

:speech_balloon: If a response helped you out, don’t forget to Like it! And if it answered your question, mark it as the solution so others can benefit too.

Originally posted by rraghvani on June 27, 2025

From past experience, it’s best not to upgrade, unless it’s absolutely necessary. Every minor version seems to constantly have issues!

Is your pipeline calling a batch file, having parameters to launch TC/TE? If yes, does calling the batch file work?

Originally posted by jkrolczy on June 27, 2025

Thanks for info to try.

Originally posted by jkrolczy on June 27, 2025

I tried the command line on the Hyper-V in a cmd window
In 15.75 - it did nothing
In 15.74 - it worked as it should to start up TE

I’ll continue to play with and debug

Originally posted by rraghvani on June 27, 2025

“In 15.75 - it did nothing” - this suggests that something is wrong with your command. Are you able to provide the actual commands you are using?

Originally posted by jkrolczy on July 06, 2025

This works in In 15.74 or below, but not for 15.75

“C:\Program Files (x86)\SmartBear\TestExecute 15\Bin\TestExecute.exe” “C:\Git.ClaimValidationService\ClaimValidationService\EmbeddedSolutions\TestComplete\TC15_Version\EmbeddedSolutionsProjSuite\EmbeddedSolutionsProjSuite.pjs” /r /e /SilentMode /DoNotShowLog /p:EmbeddedSolutions /test:“Script|Smoke_Group_1|SmokeGroup1” /PrjVar:NwkENV=B2B /PrjVar:ReportqTestResults=true

Originally posted by rraghvani on July 07, 2025

Can you verify that TestExecute launches as normal (not via command line, and on the same machine it’s failing on)?

Then ensure that the application is fully closed and does not appear in the task bar.

Can you modify your command line so that it uses x64 executable file instead,

"C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\TestExecute.exe"

and also add the following parameters (modify the path as appropriate),

/ExportLog:"C:\Sandbox\Log\index.html" /ExportSummary:"C:\Sandbox\Log\SummaryReport.xml"

Can you then test the batch file, does it work? If no, then what does index.html and SummaryReport.xml show? If yes, run via your ADO pipeline - again, what does index.html and SummaryReport.xml show if it fails?

Since you have mentioned “Hyper V”, take note of the following

A Fixed User license cannot be used on physical computers that have Hyper-V enabled. To run TestComplete, you can use a Floating license, or you can disable Hyper-V

Originally posted by jkrolczy on July 09, 2025

I’ll have to take one of my Hyper-Vs and upgrade it back to TC\TE 15.75
to play around with the above suggestions.

** NOTE: My licenses are floating

I’ll get back with results.

Originally posted by jkrolczy on July 15, 2025

Now that TestComplete 15.76 is out, I’ll being p[laying with that version to see if my issue has been resolved itself.

I’ll report back.

Originally posted by jkrolczy on August 05, 2025

I am not seeing this issue with TestComplete 15.76

Originally posted by jkrolczy on August 25, 2025

Issue still seen in TC\TE 15.76

I have down graded back to 15.74

Originally posted by Michael_B on September 02, 2025

What a frustrating issue to be stuck on. I saw the same error today and it looked like a AV/security service was blocking a new file related to load testing. I fixed that and now it is working. Can you check to see if something is getting blocked? v15.77 came out today, maybe it will be better?