@stevedennis I understand not wanting to go in blind on something so low-level. For what it is worth, the monkey-patch I applied has been stable, so far, in my lab environment. Let me know if you need me to test a build, prior to Otter 2025.

Hi Simon, I am unable to recreate this issue. Please check to make sure the path exists at run-time and that the buildmaster agent has permissions to it. You can try to test this with a different path like c:\Buildmaster\rpt\

Hello Ali, The agent version is not shown in BuildMaster 5.x's server overview page, but you can view it by going to /administration/service-status and forcing a run of the AgentUpdater executer and then checking the log for something like Connected to localhost:46336 (v39.0.0.2); checking status... (in this case, the agent on localhost is v39.0.0.2, the version of InedoAgent distributed with BuildMaster 5.8.3)

The SQL server and the application are both on server 'Production' and the application is successfully retrieving data from the SQL server. The connection string used in the application configuration is the same connection string being used in the SQL connection in Buildmaster. It is using a SQL account, so not integrated. Here is a redacted connection string: - Data Source=*************;Initial Catalog=*************;User Id=*************;Password=*************;MultipleActiveResultSets=true;

The latest agent can be downloaded from: https://inedo.com/support/documentation/inedoagent/versions

Blindly ignoring certificate validation in an orchestration tool such as BuildMaster is not recommended; basically it allows you to transfer secrets and other sensitive information to a machine that isn't what you think it is. as such, we don't have it as a checkbox or option. Instead, your better off resolving the certificate validation errors. Typically, you just need to make sure you have a self-signed certificate installed on the BuildMaster machine. If you can share more details about the configuration, we might be able to provide some more guidance on configuring certificates --- but I'm not sure how things are configured now, so it's hard to be more specific! Hope this at least helps a litte..

I was trying the Otter instructions link provided by you. When we execute step 4 and try to execute command: “InedoAgentService.exe install” We get the error message saying that InedoAgentSVC already exists.. attempting to uninstall it. Which means it first removed the already existing and running InedoAgentSVC and then created the same again. But it could not install it since I checked in services.msc and there was no such service(i.e, the already existing service was gone). I tried to do it as below as well: Since the InedoAgentSVC(Inedo agent service) had already uninstalled, I tried to install it again but this time with different port(used 8080 instead of 46336) so that we can use port 46336 for second agent installation as per otter instructions. I changed the port for Inedo agent and the service was installed successfully but its name was still InedoAgentSVC, so I tried to change name of service to InedoAgentSVCMain in app_appsettings.config and installed the Inedo agent again. It did not get installed and threw error. The point that comes out is that both Otter and Inedo Agent generate same service with name InedoAgentSVC. If we install either of these and then try to install the other one, the first one gets uninstalled. So as a conclusion, we can have only one of these agents in a machine. Please let me know if I am missing something or some step as I am still not able to use multiple agents on same service box.

Hi Tod, Thank you! I'm never sure if I'm being helpful or just getting in the way. Just can't sit still long enough :).

Check out KB#1039 - The Inedo Agent and Legacy BuildMaster Agents for more information on this.

Alright, v5.1.2 was released and it should be correct now :)

Hi, Version number for the Windows agent shows 34.0.0.1 in add/remove programs. '#justsaying' David

Hi, OK, thanks. Just to let you know, this was from version 5.10 to 5.11. David

Here are the actions that aren't supported via SSH agent currently: Unit Test Actions HTTP Reporting Actions Generate Release Notes Action (unless running on BuildMaster server) Execute Database Change Scripts Action Rename Files Action (shell script is recommended for this) Set File Attributes Action (shell script is recommended for this)

Is there any other error information e.g. stack trace or error details? You can look in the Windows Event Log for more info.

The self-hosted agent uses a proprietary binary protocol over TCP that is optimized for performance. IIS agents do indeed use SOAP over HTTP (or HTTPS). Both agent types can be secured using SSL encryption and client IP restriction. For an overview of how the agents differ, you might want to check out this article: http://inedo.com/support/kb/1039/comparison-of-buildmaster-agents

Embarrassing, a Spanish colleague had been on the server and changed all the setting!

<strike>Unfortunately no. I'll add this as an item to improve for the next release though.</strike> As of BuildMaster v4.7 this is now supported using the /ServiceName argument. For the complete list of arguments, see: http://inedo.com/support/documentation/buildmaster/installation/silent-agent-installation

Thanks a lot! That was exactly the port that was set (and I was probably notified by the installer, but I couldn't find it afterwards)

The agent does not initiate any traffic back to the BuildMaster server, so no rule needed. The agent installer has the option to auto-register the agent against the BuildMaster server, but that's done under the account of whatever user is installing it, and it only happens once. It's also easy to register a server in BuildMaster too.

You can also get this error if you do not supply a valid private key passphrase for the private key.