Hi @solairajan_shanmugam,
Welcome to the Community!
What version of Bamboo are you currently running? I ask because the only time I have seen an error like this is after our IT team installs Windows updates that add a user defined path environment variable which overrides the system defined path variable so Bamboo agents aren't capable of finding the cmd command anymore. The defect is listed here https://jira.atlassian.com/browse/BAM-16205, but it has been fixed in version 6.10.2.
If you are indeed running into the same issue I described the workaround is to remove the user defined path environment variable and your builds should work again.
I hope that helps!
-Jimmy
My agent version is 6.9.1. Do I need to uninstall my old version and need to install latest one? I tried your workaround by deleting the local environment variable. Same error. I tried Regedit too no results. Please provide me the steps to upgrade the agent or workaround in detail steps
@solairajan_shanmugam unfortunately, you can upgrade just one agent. You need to update the Bamboo server and the agents will be updated automatically as a part of connecting to the Server after the upgrade.
If you want to go the route of upgrading the server that process is documented here:
https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html
However, if the workaround didn't work for you, I'm not sure that upgrading will necessarily resolve your issue either.
Are you able to test if this runs on any other agents?
I tried both a way by bamboo remote agent properties log on as local user and serviceid. Both a solution I am facing “'cmd' is not recognized as an internal or external command, operable program or batch file.” Same plan working in different agent. But not in newly enabled server.
Windows server 2016. Please let me know any other information you required.
It looks like you're new here. Sign in or register to get started.
