Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Agent polling fails after upgrading to NPM 12.3 and SAM 6.7

Agent polling fails after upgrading to NPM 12.3 and SAM 6.7

Updated October 4, 2018

Overview

After you upgrade the primary Orion Platform server to SAM 6.7 and NPM 12.3, agent polling fails.

Environment

  • SAM 6.7
  • NPM 12.3

Cause

The primary Orion Platform server was not rebooted after the upgrade. As a result, the TCP connections and the agent management service dependency of Windows Event Logging were not refreshed.  

Agent logging may display the following message in the AgentManagement.Service.log file(s) located at C:\ProgramData\Logs\AgentManagement:

INFO  SolarWinds.AgentManagement.Messaging.Core.Service.Server.WebSocketsServer - 
Attempt to connect to WebSockets endpoint from <IPADDRESS> does not have proper 
ClientId parameter. Connection won't be registered. Value: 

Resolution

  1. Reboot the Primary Orion Platform server.
  2. Wait for Agent Polling to initiate and complete.
 

 

Last modified

Tags

Classifications

Public