SCOM 2012 R2: Failed to access Windows Event Log DHCPAdminEvents on decommissioned server

Scott Whittier 1 Reputation point
2021-02-05T16:23:44.727+00:00

I've read through a lot of the existing articles and forums related to this event but they all assume that the failure is happening with an existing, functional server. In my case the server has been decommissioned and removed from the environment and now the MS is generating 26004 error every 15 minutes or so. It's been happening for 3+months and I can't seem to find a way to eliminate the problem. I've cleared the cache files on the MS, restarted all servers and services including the database server. Ay idea where else to look?

TIA

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,505 questions
0 comments No comments
{count} votes

11 answers

Sort by: Most helpful
  1. CyrAz 5,181 Reputation points
    2021-02-05T18:12:13.217+00:00

    Could you provide a bit more details?
    What was decomissioned from the server? The DHCP role?
    Removed from what environment? Do you mean you uninstalled the scom agent or removed it from the management group?
    Was it a high availability DHCP deployment (with two servers)?
    Is there a workflow name in the 26004 event?

    0 comments No comments

  2. Scott Whittier 1 Reputation point
    2021-02-05T18:50:34.287+00:00

    The entire server was decommissioned. The server was shut down and removed from AD. Also, the server was removed from the SCOM environment.

    The 26004 event says:

    One or more workflows were affected by this.
    Workflow name: many
    Instance name: many
    Instance ID: many

    0 comments No comments

  3. CyrAz 5,181 Reputation points
    2021-02-05T19:25:23.093+00:00

    Do you have instances of "Microsoft Windows DHCP Server 2012 R2 Failover Relationship" or "Microsoft Windows DHCP Server 2016 and 1709+ Failover Relationship" (or whatever version of Windows the DHCP Server was running on) on your SCOM environment?
    You can check in the Discovered Inventory view > change target type task

    0 comments No comments

  4. Scott Whittier 1 Reputation point
    2021-02-05T19:43:58.16+00:00

    I see 2 entries like that:

    1. Microsoft Windows DHCP Server 2012 Failover Relationship Group
    2. Microsoft Windows DHCP Server 2012 R2 Failover Relationship Group

    I checked both views and I can see all of the expected servers listed but I don't see the previously decommissioned server.

    0 comments No comments

  5. Scott Whittier 1 Reputation point
    2021-02-05T22:26:22.87+00:00

    I verified that the DHCP configuration is NOT high availability.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.