- 5 minutes to read

FAQ and Troubleshooting the Nodinite Monitoring Agents

Installation failures

  • If you cannot launch the .MSI executable, ensure it is not blocked by Windows (right-click on the file, click properties, uncheck the block if it exists).

UAC may interfere with installation. Sometimes, users need to launch the MSI using an administrative command prompt or even start the installation using the following command:

msiexec /i Nodinite.MonitoringAgent.XYZ.Installer-x.x.x.x.msi

Unattended installation

You can perform unattended installations and updates. Use the command below as a template.

msiexec /i C:\<path>\Nodinite.MonitoringAgent.WindowsServer.Installer- /qn /norestart SERVICEACCOUNTUSER=<AccountName> SERVICEACCOUNTPASSWORD=<Password>

After the first installation, you must add the Monitoring Agent to Nodinite.

How do I download the diagnostics?

Direct download

If the agent is operational and Nodinite can reach the agent, you can download the diagnostics files as a ZIP directly from the Nodinite Web Client.

Download diagnostics

The download operation gives you a ZIP file with the diagnostic.log.json files and a file info.txt that contains information about the agent type, version and generation time. Attach this file with the support ticket.

Manual download from Server

  • Log on to the server with the installation of the Monitoring Agent.
  • Open the installation folder; the default root path is:
`C:\Program Files\Nodinite\` 

Diagnostics files

  • Attach to a zip file with the support ticket. We prefer if you ZIP the files. Instead of 15MB+ it will take less than 1 MB in size.

Installation of multiple instances on the same server

Installing multiple Monitoring Agents on the same server is an advanced topic. You should follow these instructions to install multiple instances of the same type of Monitoring Agent on the same server.

Any number of the same type of Monitoring Agent can be installed on the same Windows Server if:

  • The address from the endpoint section in the %MonitorAgent%.exe.config is unique. Either change the Name part (preferred change) or Port.
  • The name of the Windows Service is unique (as seen in Services.msc).

NOTE: You cannot use the installer when updating other than the first installed service if you install multiple instances. Then, manually perform a copy/paste operation from the first installation to later.

  1. Install the first Monitoring Agent according to the default documentation.

This installation acts as the master for future manual copy/paste operations.

  1. Copy the folder to a new location. Rename the folder to make it unique and easy to distinguish.

  2. In the new folder; Edit the %.exe.config file using Notepad or Notepad++ with elevated privileges.

  3. Find the endpoint XML element <endpoint ... and change the address to be unique on that server.


  1. Change the path to the Settings.json file (target the path in step 2). It is imperative you perform this step, otherwise, the other Settings.json for the other agent instance file will be overwritten with data from this instance.

  2. Open 'Services.msc'

    1. Copy the Service Name from the first Monitoring Agent to a row in Notepad++.
    2. Rename the service (for example, PROD, TEST), making this Windows service instance unique.
    3. Copy to another row in the instance.
  3. Open an Administrative Command Prompt and use the following command as a template to install the new Monitoring Agent (replace the path and service name):

sc create "%UNIQUE OTHER NAME OF Monitoring Agent FROM CLIPBOARD%" binpath="C:\Program Files\Nodinite\Nodinite Monitoring Agent - Windows Server TEST\Nodinite.MonitorAgent.WindowsServerHost.exe"

  1. Change The startup type in the Services MMC to Automatic (Delayed)

  2. Enter the credentials

  3. Start the service

  4. The README.txt file in the run-time folder will now have the proper address for use as a Monitoring Agents

NOTE: Remember to copy (backup) the config file before updating the agent.

What Monitoring Agents exist?

You will find an overview of all services and functions that Nodinite can monitor on the Monitoring page.

Follow the links to get additional information about the Nodinite monitoring agents:

Monitoring Agent Description Prerequisites Install Configuration
Azure Agent Web jobs, Azure storage (Queues, Files, Blobs), Functions, Event Hub, Data Factory, API Management Services, Event Grid, Certificates, Application Insights Prerequisites Installing Configuration
Azure Logic Apps Logic Apps Prerequisites Installing Configuration
Boomi Integrations Monitoring agent Boomi Integrations Prerequisites Installing Configuration
Database SQL Server, SSIS, Azure SQL Database, PostgreSQL Prerequisites Installing Configuration
File File (SMB), File (NFS), SFTP, FTP/FTPS Prerequisites Installing Configuration
IBM Datapower IBM Datapower Prerequisites Installing Configuration
IBM MQ IBM MQ Broker, Queues, Channels, Listeners Prerequisites Installing Configuration
JMX CPU, Memory Prerequisites Installing Configuration
Log File Parser .log, .txt, json, out, ... Prerequisites Installing Configuration
Message Queueing MSMQ, ActiveMQ, Azure ServiceBus, AnypointMQ Prerequisites Installing Configuration
Microsoft BizTalk Server BizTalk Artifacts, Health check, Environment Prerequisites Installing Configuration
Microsoft Dynamics 365 CRM Prerequisites Installing Configuration
Mule ESB Mule ESB, MuleSoft, Cloudhub Prerequisites Installing Configuration
Non-Events Non-Events Prerequisites Installing Configuration
RabbitMQ RabbitMQ, CPU, Memory Prerequisites Installing Configuration
Web Services Web Services, SOAP, REST, Certificates Prerequisites Installing Configuration
Windows Server Services, Disk, Memory, CPU,
Scheduled tasks, IIS, Ping, Event log, Certificates
Prerequisites Installing Configuration