Receiving Event ID:21016,21006,21024,10801 on newly installed management servers SCOM 2019

shankar431 471 Reputation points
2021-03-19T11:34:13.073+00:00

Hi All,

We recently installed New Management servers using SCOM 2019.
Below event id's were are receiving on management servers.
Event ID:21016,

Event ID:21016
OpsMgr was unable to set up a communications channel to XXXX.XXXX.com(SCOM Management server) and there are no failover hosts. Communication will resume when XXXX.XXXX.com is available and communication from this computer is allowed.

Event ID:21006
The OpsMgr Connector could not connect to XXXX.XXXX.com:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.

Event ID:21024
OpsMgr's configuration may be out-of-date for management group XXXX_MG, and has requested updated configuration from the Configuration Service. The current(out-of-date) state cookie is "5853ca63bca72be91d957711644c0b07,803765a1d17f47a58b1f7cc534c552fc:00006148"

Event ID: 10801
Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons:

  • Discovery data is stale. The discovery data is generated by an MP recently deleted.
  • Database connectivity problems or database running out of space.
  • Discovery data received is not valid.

Please assist us in resolving these issues.

Regards,
Ravi shankar

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,419 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amit Sanwal 1 Reputation point
    2021-03-22T07:37:25.787+00:00

    Hello Shankar,

    As the events indicate a communication issue. Have you ensured communication of your management servers on port 5723?? OR any firewalls blocking the communication?

    Once confirmed, please try clearing cache on your management server.

    Regards,
    Amit

  2. Amit Sanwal 1 Reputation point
    2021-03-22T09:50:52.783+00:00

    Hi Shankar,

    You can check a few more things communication-wise.

    1. Are you able to ping the Management server?
    2. Are you able to resolve the Management server name? NSLOOKUP
    3. I hope you're following the system requirements per https://learn.microsoft.com/en-us/system-center/scom/system-requirements?view=sc-om-2019
    4. Try clearing the management server cache and see if the errors have resolved or not. You can run the below PS Cmd for clearing the cache: 
         stop-service "HealthService"
      get-childitem -recurse -Path "C:\Program Files\Microsoft System Center\Operations Manager\Server\Health Service State" | remove-item -force -recurse
      start-service "HealthService"
    5. For event id 10801, please check your DB(Both opsmgr & DW) to see if you're able to connect to them.
    6. Lastly, try rebooting the Management server(hope they're not live yet)
    0 comments
  3. Marius Ene 335 Reputation points
    2024-01-16T21:43:40.86+00:00

    Event ID:21006
    The OpsMgr Connector could not connect to XXXX.XXXX.com:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.).

    This is a common error that clearly shows that ports are not yet open, I am sure of this. You might have requested them but have you checked? Please do a test to confirm by testing the communication between the management servers. You can use PS Test-NetConnection cmdlet or the telnet client.