Running an Inedo Product's Services Interactively
KB#1015: Last Updated Sep 18, 2015
The example screenshots are from BuildMaster, but the process will be exactly the same no matter which one of our products you're using.
Refer to this table - depending on which product you are using, enter the coinciding name, or abbreviation, into each
space that has a red [product's name] or [xx].
|The Inedo Product You're Using||[product's name]||[xx] abbreviation|
BuildMaster & Otter
Depending on how they're configured, there will be two services configured:
- BuildMaster Service – coordinates build executions, scheduled builds, agent updates, etc.
- BuildMaster Web Server (optional) – hosts the BuildMaster web application instead of IIS
- Otter Service
- Otter Web Server (optional) – hosts the Otter web application instead of IIS
Both of these services point to the same executable (
and it’s possible to run that very same service from the command-line to see everything that’s going on as it’s happening.
ProGet will not have a separate web service by default:
This service points at the executable (
pgservice.exe), and it’s possible to run that very
same service from the command-line to see everything that’s going on as it’s happening.
Step 1: Stop the Services
By default the BuildMaster & Otter services will be named INEDO[xx]SVC and
INEDO[xx]WEBSRV. ProGet will be named only INEDOPGSVC. You can control these services a number of different ways,
but the most common is to use the Services snap in.
Just navigate to Control Panel > Administrative Tools > Services, and stop the Service(s).
Step 2: Command Line
Once the service(s) have been stopped, open up a command prompt or PowerShell (you probably want to Run As Administrator),
then navigate to the [product's name] root folder
C:\[product's name]\). Next, navigate to the Service subdirectory (
and then type in
The run command instructs the
[xx]service.exe to run in interactive mode.
You can quit by hitting CTRL-C at anytime.
Step 3: Use and Ignore Service Warnings
From here, you can log-in to the web application as you normally would. Expect to see “service not running” warnings in a number of places
including the header, but builds and deployments should still will work in exactly the same way:
Do not start the service while running interactively as it will likely result in several UnauthorizedAccessExceptions.