- 4 minutes to read

Step 11: Install Pickup Log Events Service

Install the Nodinite 7 Pickup Log Events Service. There is no in-place update: v7 replaces the v6 Windows service and its local Settings.json with an IIS-hosted agent that you configure remotely in the Web Client. The full agent guide is Install the Pickup Log Events Service 7.x.

Prerequisites

Steps

Tip

If you already added the Pickup Log Events Service in the Portal during Step 10, skip to step 5.

  1. In the Portal, open your environment and go to the Agents step (field reference).

  2. Add or locate the Pickup Log Events Service for the Core Services server.

  3. Configure the service account, password, and port. The port is the agent's own IIS web site port; open it as described in the Network and Firewall Overview.

  4. Save.

  5. Go to Review and Download and download the package.

    Preparing download
    Example of the progress screen while the Portal generates the ZIP package.

  6. Extract the bundle on the application server and run the CLI from an elevated PowerShell 7 prompt, as in Step 7: Run the CLI Workflow. Use the server folder of your package:

    .\Nodinite.Installer.Cli.exe validate --config .\nodinite01\config.cli.json
.\Nodinite.Installer.Cli.exe deploy-environment --config .\nodinite01\config.cli.json --dry-run
.\Nodinite.Installer.Cli.exe deploy-environment --config .\nodinite01\config.cli.json

    The CLI prompts for service account passwords that aren't in the configuration.

  7. Verify that the Pickup Service application pool runs in IIS Manager.

  8. Open the Web Client → Administration → Monitoring Agents and confirm that the Pickup Service agent has a green status.

Note

If the Pickup Service, the Log API, or SQL Server use Windows authentication with custom domain accounts, validate Service Principal Names (SPN) before you test event pickup; this avoids hard-to-diagnose Kerberos and SSPI failures.

Migrate Configuration from v6 Settings.json

In v6, the Pickup Log Events Service read a local Settings.json on the application server. In v7, you manage the same settings through Remote Configuration in the Web Client, and the v7 agent no longer reads Settings.json.

  1. Open the Web Client → Administration → Monitoring Agents.
  2. Open the Pickup Log Events Service agent and its configuration (Manage Pickup LogEvents Service).
  3. Add each pickup source and copy the values from the v6 Settings.json:
Settings.json field (v6) Web Client field (v7) Notes
LogApiUrl Log API Endpoint The v7 Log API has its own web site and port, for example https://nodinite.contoso.com:<Log API port>/LogAPI/. Use http:// only if you chose Option B in Step 10. Never use localhost.
DatabaseName / connection string Database Name Point at your existing Configuration Database; an upgraded v6 database keeps its v6 name, for example NodiniteConfig_DEV
PollingIntervalSeconds Polling Interval Carry over a customized v6 value
BatchSize Batch Size Carry over a customized v6 value
  1. Re-enter all secrets, such as passwords, keys, and connection strings; v7 can't decrypt values encrypted by v6.
  2. Save the configuration, wait one polling interval, and confirm in a Log View that new Log Events arrive.

Completion Checklist

  • Pickup Service added in the Portal and deployed with the CLI
  • Pickup Service agent green in the Web Client
  • v6 Settings.json values moved into Remote Configuration and secrets re-entered
  • Log API Endpoint uses the v7 host name and Log API port
  • New Log Events visible in the Web Client
  • No errors in IIS or Event Viewer

Troubleshooting

IIS Application Pool Not Running

The Pickup Service agent shows a red or offline status. Check the following:

  • In IIS Manager → Application Pools, start the Pickup Service pool if it's stopped
  • The service account has the Logon as a Service right and the required permissions
  • Event Viewer for detailed errors

No Log Events Appearing

The agent runs but picks up nothing. Check the following:

  • The Log API Endpoint uses the v7 host name, Log API port, and /LogAPI/ path
  • The Database Name matches your existing Configuration Database
  • The Log API port is reachable from the application server (Network and Firewall Overview)
  • IIS logs and Event Viewer

Next Steps