Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo Job Exit with Error cmd' is not recognized as an internal or external command

Hi ,

I have setup a remote bamboo agent to run in a windows environment where The server runs in a Linux environment.

Here i have setup a plan to build a multi module maven project. and that plan runs using that remote agent.

I have split the build process by having few tasks which will execute one after another to build speprate modules.

But after successfully executing the 1st Task the build get failed with a Error message

'cmd' is not recognized as an internal or external command,
operable program or batch file.
Failing task since return code was 1 while expected 0

any tips to find a solution for this issue is highly appriciated.



3 answers

I solved this issue on my Windows build agent. This has to do with the environment variables set for the user that runs bamboo. Log in as that user and verify that %SystemRoot%\system32 is included in your Path variable for that user.

System Path has %SystemRoot%\system32 bit still facing that error

1 vote

On your remote agent, make sure that directory with cmd.exe is in the PATH variable by setting it for the user used to run the agent.


Thanks for the answer. I accually tried adding this to PATH using ENV variable settings but no luck. Then i re do it in the place where we can define ENV variables in Bamboo dashbord. Then it worked when the agent is running as a normal process. But when i install it as a service i faced the issue again.



Like Rahul Goutham Banka likes this

I faced the same issue but resolved by following this Doc.

PS: I know this is a very old post, this might help someone.

Hi Przemek, I am aslo facing the similar issue. its running fine in Bamboo console and but failind with the below error when bamboo is run as service. I have to run it bamboo as service.

Could you please help in sorting this out?

27-Jan-2012 05:00:12 [INFO] ------------------------------------------------------------------------
27-Jan-2012 05:00:12 [INFO] Total time: 2:26.750s
27-Jan-2012 05:00:12 [INFO] Finished at: Fri Jan 27 05:00:12 GMT-12:00 2012
27-Jan-2012 05:00:12 [INFO] Final Memory: 51M/369M
27-Jan-2012 05:00:12 [INFO] ------------------------------------------------------------------------
27-Jan-2012 05:00:13 'cmd' is not recognized as an internal or external command,
27-Jan-2012 05:00:13 operable program or batch file.
27-Jan-2012 05:00:13 Failing task since return code was 1 while expected 0
27-Jan-2012 05:00:13 Parsing test results...

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events