Sign in
 
HomeLibraryLearnDownloadsSupportForums
Resources for IT Professionals > System Center Essentials Forums > System Center Essentials - General > Error 20058 "The Root Connector has received bad packets which have been dropped."
Ask a questionAsk a question
Search Forums:
 

AnswerError 20058 "The Root Connector has received bad packets which have been dropped."

  • Monday, August 04, 2008 1:22 PMDavid Brazier Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    We're not getting any alerts from monitored agents, and we're seeing this in the Ops Mgr event log.  Any ideas on how to troubleshoot it?  We have checked that agenst can see https://xxx.local:8531/SimpleAuthWebService/SimpleAuth.asmx and have restarted the SCE server, put it in and out of maintenance mode and restarted Helath Service, all to no avail.  At the same time the alerts stopped, we also stopped getting the Daily Health Report.  It works using the test button, but never runs at the scheduled time.

     

    Thanks for any help

     

    David

     

    Event Type: Warning
    Event Source: OpsMgr Connector
    Event Category: None
    Event ID: 20058
    Date:  04/08/2008
    Time:  14:09:43
    User:  N/A
    Computer: XXX
    Description:
    The Root Connector has received bad packets which have been dropped. It received 483 such packet(s) in the last five minutes

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

Answers

  • Thursday, August 07, 2008 8:55 AMJie-Feng Ren Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    There are two causes to these events:

    1. The Run As Profile for Data Warehouse SQL Server Authentication Account needs to be associated with Data Warehouse SQL Server Authentication Run As Account Account. You can find these information from administration->security.

    2. The Data Warehouse SQL Server Authentication Run As Account cannot have a user name specified other than a blank space if windows authentication is going to be used. To change this Change the account to use a blank space as the logon name and make up a password for this.

    After doing this, stop health service. Delete the files under folder "\programfiles\System Center Essentials 2007\Health Service State\Health Service Store" and then try to start the health service.

     

    BTW, not all warning will trigger alerts on SCE server. It depend on MP.

     

    HTH.

     

All Replies

  • Wednesday, August 06, 2008 7:11 AMJie-Feng Ren Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    Is this alert associated with SCE server or other clients? Kept RMS Computer, health service and Health service watcher node into Maintenance mode. After 5min removed all service from Maintenance.

     

    HTH

     

     
  • Wednesday, August 06, 2008 1:37 PMDavid Brazier Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Put into maintenance mode for 5 mins & then took back out - no change - still no alerts or health report.  Also seeing these errors in event log on SCE server (as were the 20058 errors):

     

    Event Type: Error
    Event Source: HealthService
    Event Category: None
    Event ID: 4506
    Date:  06/08/2008
    Time:  14:31:42
    User:  N/A
    Computer: XXXX
    Description:
    Data was dropped due to too much outstanding data in rule "AD_General_Response.PerformanceCollection" running for instance "XXXX" with id:"{8A1DEF7C-5CE7-76F7-FD08-BB05C07EC1B0}" in management group "XXXX_MG".

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     
  • Thursday, August 07, 2008 8:55 AMJie-Feng Ren Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    There are two causes to these events:

    1. The Run As Profile for Data Warehouse SQL Server Authentication Account needs to be associated with Data Warehouse SQL Server Authentication Run As Account Account. You can find these information from administration->security.

    2. The Data Warehouse SQL Server Authentication Run As Account cannot have a user name specified other than a blank space if windows authentication is going to be used. To change this Change the account to use a blank space as the logon name and make up a password for this.

    After doing this, stop health service. Delete the files under folder "\programfiles\System Center Essentials 2007\Health Service State\Health Service Store" and then try to start the health service.

     

    BTW, not all warning will trigger alerts on SCE server. It depend on MP.

     

    HTH.

     
  • Friday, August 15, 2008 1:02 PMzarborg2 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I appear to be having a similar problem.  Getting this error in the event log since upgrading my Operations Manager 2007 to SP1:

     

    Event Type: Warning
    Event Source: OpsMgr Connector
    Event Category: None
    Event ID: 20058
    Date:  8/15/2008
    Time:  6:47:44 AM
    User:  N/A
    Computer: HOODOO
    Description:
    The Root Connector has received bad packets which have been dropped. It received 621 such packet(s) in the last five minutes

     

    Here is what I did to get me here:

    1) installed OpsMgr 2007

    2) installed clients to my servers

    3) saw that SP1 came out so applied that before adding management packs

    4) upgraded all my clients to 6.0.6278.0

    5) installed new SP1 management packs

    6) installed SCCM 2007 on same server (i should be able to do this?)

    7) upgraded SCCM 2007 to SP1

    8) started noticing that we were no longer getting alerts from SCOM

    9) tried the steps above, but thinking the data warehouse was for reporting and I haven't rolled that out yet

     

    Still getting the errors.

     

    I show my scomconfig account is logged into the SQL server and has the OperationsManager database open so it looks like it's connecting ok

     

    I tried installing a new client and it's reporting back that it's not installed from the consle but I see this in the event log:

    Event Type: Information
    Event Source: OpsMgr Connector
    Event Category: None
    Event ID: 20020
    Date:  8/15/2008
    Time:  6:53:18 AM
    User:  N/A
    Computer: HOODOO
    Description:
    The health service {B16D6BBC-1042-FB8A-3CBC-0216E3AED74F} running on host funvalley.corp.lefthandnetworks.com and serving management group LeftHand with id {4F38FF14-E547-F306-4D09-E507918FE49C} is available.


    and then one of my hosts that was working just fine is now throwing this error:

     

    Event Type: Error
    Event Source: OpsMgr Connector
    Event Category: None
    Event ID: 20022
    Date:  8/15/2008
    Time:  6:59:24 AM
    User:  N/A
    Computer: HOODOO
    Description:
    The health service {7057D881-6B1E-851D-F1FC-F7908E9223EB} running on host loveland.corp.lefthandnetworks.com and serving management group LeftHand with id {4F38FF14-E547-F306-4D09-E507918FE49C} is not heartbeating.

     

     

    Any ideas for me?

     
  • Friday, August 15, 2008 2:07 PMzarborg2 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

     

    Update:  I read te release notes that stated machines were having a difficult time coming back out of maintenance mode.

    So, to test I tried putting a computer that was reporting healthy into maintenance for 10 minutes.

     

    It never came out of maintenance mode.

     

    Found this for servers that are currently reporting "Not Monitored" in the event log:

     

    Event Type: Information
    Event Source: HealthService
    Event Category: Health Service
    Event ID: 1215
    Date:  8/15/2008
    Time:  7:24:08 AM
    User:  N/A
    Computer: HOODOO
    Description:
    Suspending monitoring for instance "hoodoo.corp.lefthandnetworks.com" with id:"{6103525F-B9E1-0D11-61EE-F1B314A461B9}" as the instance maintenance mode is ON. Management group "LeftHand".

     

    But when I look in the console it's not listed as being in maintenance mode.

     

    I'm also seeing messages like this for EVERY server being monitored just a little bit later in the event log:

     

    Event Type: Information
    Event Source: HealthService
    Event Category: Health Service
    Event ID: 1216
    Date:  8/15/2008
    Time:  7:32:03 AM
    User:  N/A
    Computer: HOODOO
    Description:
    Resuming monitoring for instance "funvalley.corp.lefthandnetworks.com" with id:"{CF5D709E-232E-C370-5B7D-077F54C9C1F8}" as the instance maintenance mode is OFF. Management group "LeftHand".


    Starting to think that SP1 broke sumptin.

     
  • Monday, August 18, 2008 11:02 AMDavid Brazier Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    >1. The Run As Profile for Data Warehouse SQL Server Authentication Account needs to be associated with

    > Data Warehouse SQL Server Authentication Run As Account Account. You can find these information from

    > administration->security.

    Checked & set as expected.

    >2. The Data Warehouse SQL Server Authentication Run As Account cannot have a user name specified other

    > than a blank space if windows authentication is going to be used. To change this Change the account to use

    > a blank space as the logon name and make up a password for this.
    Checked & set as expected.

    >After doing this, stop health service. Delete the files under folder "\programfiles\System Center Essentials

    >2007\Health Service State\Health Service Store" and then try to start the health service.

    Done.

     

    No change though - same event log entries, no alerts, no daily health report.

     

    Any further suggestions?

     

    David
     
  • Monday, August 25, 2008 10:38 AMDavid Brazier Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi Again

     

    We still have these event log entries, no alerts & no Daily Health Report.  Instead of worrying about the event log & alerts, would it be best to troubleshoot the Daily Health Report?  It is easier to test than the alerts and perhaps fixing it will fix the rest.  This was working fine before, and clicking "Send Test Report" works fine, but it never appears at the scheduled time.  So what is the mechanism for the running of the scheduled Daily Health Report? 

     

    David

     
  • Wednesday, September 03, 2008 9:07 AMDavid Brazier Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi

     

    We're no further forward.  Still no alerts & no Daily Health Report.  Can anyone shed any light on:

    • What events 20058 & 4506 mean and how to troubleshoot them.
    • Why Daily Health Report would work using the "Send Test Report" button but not run at the scheduled time.

    Thanks

     

     
  • Wednesday, September 03, 2008 12:14 PMzarborg2 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I don't really have an answer for you, but I had to reinstall SCOM to get everything back up and running.

    Luckily I was just getting started so it was only a few days worth of work lost.

     

    Wish I had an answer instead though.

     
  • Wednesday, September 03, 2008 7:01 PMjdroger2 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I am having the same problem after putting two servers into maintenance mode.
     
  • Thursday, September 24, 2009 2:00 PMDrake Teran Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    We had the same issues and the key phrase is "Maintenance mode".  Microsoft recommends not to put the servers into maintenance mode due to having "alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts generated on mgmt server being suppressed".  Once the servers were removed from Maintenance Mode, all the alerts started back up.

    -----------------------------------------------------
    When a monitored object, such as a computer or distributed application, goes offline for maintenance, Operations Manager 2007 detects that no agent heartbeat is being received and, as a result, might generate numerous alerts and notifications. To prevent alerts and notifications, place the monitored object into maintenance mode. In maintenance mode, alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts are suppressed at the agent.

    Important
    We do not recommend that you put Operations Manager 2007 servers into maintenance mode. Configuration distribution, the heartbeat feature, and other features for the system might become unreliable. If you place a management server into maintenance mode, alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts generated on the management server will be suppressed. The health service on the management server continues to run. Alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts from other agent-managed computers will be processed and displayed as appropriate.

    You can initiate maintenance mode by clicking Start Maintenance Mode in the Actions pane of the Monitoring area in the Operations console. You can define maintenance mode for a monitored object and the entities it hosts. While the monitored object is in maintenance mode, you can edit the maintenance mode settings. You can also specify duration for an object to remain in maintenance mode, or schedule a time for the managed object to be removed from maintenance mode.
    -----------------------------------------------------

    Thanks,
    Drake Teran