Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Polling engine takes a very long time to start after reboot and the MSMQ advises it took 20 mins to load

Polling engine takes a very long time to start after reboot and the MSMQ advises it took 20 mins to load

Updated October 16, 2017

Overview

You notice the polling engine server takes a very very long time to start after a reboot.

 

Windows event logs show an error such as:

 

Log Name:      System
Source:        Service Control Manager
Date:          27/09/2017 15:29:59
Event ID:      7044
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      hostname
Description:
The following service is taking more than 16 minutes to start and may have stopped responding: Message Queuing
 
Contact your system administrator or service vendor for approximate startup times for this service.
 
If you think this service might be slowing system response or logon time, talk to your system administrator about whether the service should be disabled until the problem is identified.
 
You may have to restart the computer in safe mode before you can disable the service.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="32768">7044</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2017-09-11T10:29:59.265625000Z" />
    <EventRecordID>16603328</EventRecordID>
    <Correlation />
    <Execution ProcessID="576" ThreadID="580" />
    <Channel>System</Channel>
    <Computer>hostname</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Message Queuing</Data>
    <Data Name="param2">16</Data>
  </EventData>
</Event>

 

Environment

 

Cause 

The MSMQ has orphaned data.

 

 

 

 

Last modified

Tags

Classifications

Public