- 4 minutes to read

Updating the Azure Logic Apps Logging and Monitoring agent

In this section, you will learn how to update the Azure Logic Apps Logging and Monitoring agent.

Release notes

For information about the releases, please visit the release notes for the Azure Logic Apps Logging and Monitoring agent.

Running Version

The installed version is displayed in the 'Version' text box.
sourceinformation

You can also get this information from the file details property on the local installation:
fileversion

PreReq: You must have successfully installed the Azure Logic Apps Logging and Monitoring agent prior to an update. The Service account credentials to use must have Logon as Service Right. See prerequisites for Azure Logic Apps Logging and Monitoring agent for more information.
f>You must be a local administrator to have the right to install (and thereby update) Windows Services

Compatibility and versioning issues

  • 5.x -> 5.1 New installation folder (C:\Program Files\Nodinite\Agent - Logic Apps\) is being used, move 'Settings.json' from old folder to new folder and restart
  • 4.X -> 5.X review Updating from V4 to V5

Update guide

Follow the steps next to update the Azure Logic Apps Logging and Monitoring agent.

Step 1: Start the installer

Double click on the MSI file to start the update process of the Nodinite Azure Logic Apps Logging and Monitoring agent.
msi

Step 2: Welcome Screen

On successful execution of the MSI file, a Welcome screen will be presented.
Welcome

Click on the 'Next' button to continue with the update process or click on the 'Cancel' button to quit the installer.

Step 3: Custom Setup

Select features and location to update.
CustomSetup

Default settings are recommended

Note: If you change the location, your old configuration will be lost

Click on the 'Next' button to continue with the update process or click on the 'Cancel' button to quit the installer.

Step 4: Service Account Information

Enter the credentials for the Account to run Nodinite Azure Logic Apps Logging and Monitoring agent.

Domain: The name of the Domain the Server belongs to. If a local account is being used, use the name of the server or . (dot) as Domain
User: The name of the account
Password: The password for the account

Note: The account must have 'Log on as Service Right'

DomainUser

Click on the 'Next' button to continue with the update process or click on the 'Cancel' button to quit the installer.

Insufficient Privileges

Error message when account information does not meet Prerequisites.
InsufficientPrivileges

If you get this message, the most common reason is that the account is not allowed to run as a service or is not local Administrator on the server. Follow the guide How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Make sure that the credentials are typed correctly!

Tip: Check the local event log if there are errors (both System and Application)

Step 5: Completed setup

The last step of the update process gives either a success or a premature exit.
Completed
Successful update example

Click on the 'Finish' button to Exit and quit the installer (update process).

When the setup has finished your default text editor will open a text file named the 'README.txt'. The README.txt file holds the information that you need to setup and manage the agent as a Monitoring Agent Configuration for Nodinite.
README.txt

Instructions on how to add the Azure Logic Apps Logging and Monitoring agent as a Monitoring Agent Configuration is detailed in a shared article, click on the link below to learn more:


Troubleshooting

A failed update will render a premature exit.
PrematureExit
Failed update example

Support

Contact our Support for additional guidance if you fail to resolve the update problem.

Note: There may be additional information written to the Windows Event logs


Next Step

Configure Add or manage a Monitoring Agent Configuration

Prerequisites
Monitoring Agents
Install
Uninstall