Installing the Nodinite Pickup Log Events Service Logging Agent
This comprehensive guide to installing the Nodinite Pickup Log Events Service Logging Agent covers both the modern Portal-based installation (recommended) and the legacy MSI-based approach for remote servers.
Nodinite v7.0.4 and Later (Recommended)
New 7.0.4
Pickup Log Events Service Logging Agent v7.0.4 and later should be installed using the Nodinite Portal-based scripted installation. This modern approach provides automated installation and configuration with minimal manual intervention.
Why Use Portal-Based Installation?
✅ Automated agent installation and configuration via PowerShell scripts
✅ Configures multiple agents simultaneously with consistent settings
✅ Eliminates manual MSI installations and reduces human error
✅ Centrally manages all environments from the Portal
✅ Includes AI Diagnostics New 7.0.4 for intelligent error analysis
✅ Supports .NET 10 Hosting Bundle for modern runtime performance
Get Started with Portal-Based Installation
Follow the comprehensive Install Nodinite v7 guide to install the Pickup Log Events Service Logging Agent using the Portal-based approach. The Portal generates PowerShell scripts that install and configure the agent automatically.
Key Steps:
- Register your environment in the Nodinite Portal
- Select Pickup LogEvents Service Agent in the Agents configuration tab
- Configure agent settings (port, service account, pickup directories)
- Download the installation package with embedded PowerShell scripts
- Run the PowerShell script to install and configure automatically
Complete Portal Installation Guide - Step-by-step instructions with screenshots
Legacy Installation (Remote Servers Only - Not Recommended)
Warning
Deprecated: The MSI-based installation method is legacy and intended only for remote server installations where the Portal-based approach cannot be used. This method is not recommended for new deployments and will be retired in future versions.
Important
Version 7.0.4+ Users: If you are installing Pickup Log Events Service Logging Agent v7.0.4 or later, use the Portal-based installation method instead. The MSI approach below is for legacy v6 installations or remote servers only.
When to Use MSI Installation
Use this method only if:
- You are installing on a remote server that cannot be managed via Portal scripts
- You are maintaining a legacy v6 environment (upgrade to v7 recommended)
- You have specific infrastructure constraints preventing automated installation
MSI Installation Prerequisites
Before You Begin
- Ensure you meet all prerequisites for the Nodinite Pickup Log Events Service Logging Agent.
Step 1: Start the Installer
- Double-click the MSI file to launch the Nodinite Pickup Log Events Service Logging Agent installer.
The image below shows the MSI installer file.
Step 2: Welcome Screen
- When the installer starts, you will see the Welcome screen.
The image below displays the Welcome screen of the installer.
Click Next to proceed or Cancel to exit the installer.
Step 3: Accept the EULA
- You must accept the End User License Agreement (EULA) to continue. If you do not accept the terms, you cannot install the logging agent.
The image below shows the EULA acceptance screen.
Click Next to proceed or Cancel to exit the installer.
Step 4: Custom Setup
- Select the components and installation location. Default settings are recommended for most users.
The image below shows the Custom Setup screen.
Click Next to proceed or Cancel to exit the installer.
Step 5: Service Account Information
- Enter the credentials for the account that will run the Nodinite Pickup Log Events Service Logging Agent. This account may be used to access and query monitored databases, depending on your configuration.
- Domain: Enter the domain name. For local accounts, use the server name or a dot (.) as the domain.
- User: Enter the account username.
- Password: Enter the account password.
The account must have 'Log on as a Service' rights.
The image below shows the service account credentials screen.
Click Next to proceed or Cancel to exit the installer.
Insufficient Privileges
If the account information does not meet the prerequisites, you will see an error message.
The image below shows the Insufficient Privileges error.
Common causes include the account not being allowed to run as a service or not being a local administrator. Follow the How to set Logon as a Service right guide and click Retry. If the issue persists, click Cancel and restart the installer with valid credentials.
Tip: Check the Windows Event Logs (System and Application) for additional error details.
Step 6: Complete the Setup
The final step displays either a successful installation or a premature exit.
- Successful installation example:
The image below shows a successful installation completion.
- Failed installation example:
A failed installation results in a premature exit, as shown below.
Click Finish to exit the installer.
Support
If you encounter issues you cannot resolve, contact Support.
Additional troubleshooting information may be available in the Windows Event Logs.