Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > No polling data received on nodes

No polling data received on nodes

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,091 Votes: 1 Revisions: 10

Issue:

When the message queue reaches its limit, the MQ software sends any new messages to a file (.mq) in C:\Windows\System32\MSMQ\Storage Directory. Files accumulate until the directory exceeds its limit (1GB by default), at which point MSMQ cannot process messages, and SolarWinds products begin to fail in their attempts to poll managed nodes. Polling errors would be recorded in the polling controller log file.

Solution:

To prevent your system from reaching the MSMQ storage limit:

  1. Confirm that the polling controller log file (by default, C:\Documents and Settings\All Users\Application Data\Solarwinds\Logs\Orion\) contains this error:
    2012-01-22 14:28:13,143 [3] ERROR SolarWinds.Collector.PollingController.JobSchedulerEventsService - Error processing job System.Messaging.MessageQueueException: Insufficient resources to perform operation. at System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType) at System.Messaging.MessageQueue.Send(Object obj) at SolarWinds.Collector.Queue.MsmqQueueController.Send(PropertyBag bag) at SolarWinds.Collector.PollingController.JobSchedulerEventsService.ProcessJobResult(FinishedJobInfo jobResult) at SolarWinds.Collector.PollingController.JobSchedulerEventsService.OnJobFinished(FinishedJobInfo[] jobFinishedInfo) Application Event log started throwing the following error at 7:29am on the 21st, Machine MSMQ storage quota was exceeded or there is insufficient disk space. No more messages can be stored in user queues. You can increase Message Queuing storage quota or purge unneeded messages by using Computer Management console. This event is logged at most once per 3600 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2183 registry value to desired time in seconds.
  2. Create a script that does the following:
    1. Stops all SolarWinds services with Orion Service Manager (SolarWinds Orion > Advanced Features > Orion Service Manager).
    2. Deletes all .mq files from the MSMQ storage directory (by default, C:\Windows\System32\MSMQ\Storage Directory.
  3. Use Task Scheduler to setup the script to run every week at an hour when you know the system tends to idle.

Note: This solution is only a stop-gap measure for handling a system resource issue. You will need to perform a capacity audit of your system to decide what components need to be augmented.

Last modified

Tags

Classifications

Public