Windows Remote Agent Build Failing When Run As a Service

[Brandon Hall]

I have a Windows Server 2008 instance which is successfully able to execute a build when the bamboo-remote-agent is run from the command line under an administrator account but fails when run as a service under the same administrator account with the error:

'findstr' is not recognized as an internal or external command, operable program or batch file.

The most relevant resources I've found pertaining to this thus far are:

• Visual Studio task fails when running Bamboo as a Windows service
• 'findstr' is not recognized as an internal or external command

I'm already running the service under an administrator account and C:\Windows\System32 is already apart of the PATH environment variable. Yet, it does seem that there is likely a pathing issue of some sort since its unable to find 'findstr' which I've confirmed is in the C:\Windows\System32 folder.

I'm pleased that the remote agent successfully completes the build when run from the command line but for obvious reasons I need (or at least very greatly prefer) it to be able to run as a service.

What am I missing?

[rsperafico · Accepted solution]

Hello Brandon,

Thank you for your inquire.

Since you are running as a Windows Service, there are great chance you have a PATH (user environment variables) that is overwriting PATH (system environment variables).

windows-7-user-environment-variables.gif

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

—

Kind regards,
Rafael P. Sperafico
Atlassian Support

[Brandon Hall]

You're correct, in an effort to solve another issue I had defined a user PATH variable. Deleting it solved my problem. Thanks.