SCOM 2019 UR4 Console Problems

Lentz Andreas 6 Reputation points
2022-06-22T06:37:56.503+00:00

Hello, after installing the UR4 for the SCOM 2019 console, we have no way to open the console and connect to a Managementserver. No matter if this is running on UR3 or UR4.
Is this a known issue? The console remains in "Try to connect" on various system. Only after uninstalling the UR4 for the Console the connection works again. This happens locally and remotely.
Some ideas or similar behaviour?

Greetings, Andreas

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,413 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SChalakov 10,261 Reputation points MVP
    2022-06-22T07:17:47.14+00:00

    HI Andreas,

    can you please check a couple of things:

    - The Operations Manager Event Logs

    What do you see there, can you please check the entries and post the relevant events here? This way we could check them out and try to give some more useful advices.

    - The SCOM Setups Logs

    Can you please check the OpsMgrPatchWizard.log located under %LocalAppData%\SCOM\Logs ?
    Can you post some of the last related log entries from the UR4 Install?
    Do you see error in there?

    • Last, but not least, please post a small feedback item on the SCOM feedback site. It just might be that you have hit a know isssue and the System Center PG could help you out:

    Feedback System Center Operations Manager
    https://feedback.azure.com/d365community/forum/2a49c9ee-4436-ec11-b6e6-00224824730c

    Let's see what we can find out.

    Of course, if you want your SCOM functioning again, you coozuld uninstall the Update as described here:

    Update Rollup 4 for System Center Operations Manager 2019
    https://support.microsoft.com/en-us/topic/update-rollup-4-for-system-center-operations-manager-2019-07ad0ef3-a330-4373-92f6-2dda3821bee5

    > To uninstall an update, run the following command:

    msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid

    Note The <PatchCodeGuid> placeholder represents one of the following GUIDs.

    For uninstalling the server component, only binaries are rolled back while databases and imported management packs remain unaffected.

    Component

    RTMProductCodeGuid

    PatchCodeGuid

    Server

    {5016D727-313F-451D-9990-4DB326D00F06}

    {AC13F9AB-9D10-424C-80FB-2123FA6022CD}

    Console

    {88D7DF38-306E-4195-8C1A-C19A4E35C728}

    {FFD816D2-4B5F-40D1-9C25-917F0D2840AC}

    webconsole

    {D80F1A1B-200C-421C-B876-F440A7BDAA67}

    {C9D46C3F-13D1-4D69-9B42-4D8DE2C60B72}

    Reporting

    {10137A63-5AE9-4B40-8BF2-DBAE7B596359}

    {22168A62-6396-44A4-929C-FE946AA75E55}

    Gateway

    {4ED3E2E8-E655-4F9C-8A95-10ADD6700181}

    {5B507C4A-A53A-46BB-A22A-64F9C5625D72}

    Agent

    {CEB9E45B-2152-4C10-A022-0825B53B632F}

    {C5414DAC-DF39-4CE8-8C54-CC843AC9775A}

    ACS

    {78BDC6D0-9348-4D0D-9350-E1F0779D498E}

    {F1C93848-3D96-436A-9781-1693A6ABC4DA}

    (If the reply was helpful please don't forget to upvote or accept as answer, thank you)
    Regards,
    Stoyan

    1 person found this answer helpful.
    0 comments
  2. Jamy 6 Reputation points Microsoft Employee
    2022-08-10T11:36:13.933+00:00

    Hi Andreas,

    We have identified the issue and it is from this 'small change' in the UR4 upgrade:
    https://support.microsoft.com/en-us/topic/update-rollup-4-for-system-center-operations-manager-2019-07ad0ef3-a330-4373-92f6-2dda3821bee5 :
    "The MP Reference Alias generator is case-sensitive now and will create only unique Aliases for Management packs."

    This means that in the past Alias References were not checked if they were key sensitive so you might have MPs with Alias References such as:
    VMware and VMWARE - in the same MP.

    You can check with the script bellow, run it on a MS:

    $mps = Get-ChildItem -Path "C:\Program Files\Microsoft System Center\Operations Manager\Server\Health Service State\Management Packs"
    foreach ($mp in $mps) {
    $mpText = Get-Content $mp.PSPath
    $references = @()
    foreach ($line in $mpText) {
    if ($line -like "Reference Alias") {
    $references += $line.ToLower()
    }
    }
    $ht = @{}
    $references | foreach { $ht["$"] += 1}
    $ht.keys | where {$ht["$"] -gt 1} | foreach {write-host "Duplicate element found $_"; write-host $mp.PSPath }
    }

    If you do have such MPs from custom or 3rd party vendors you will need to remove them, perform the upgrade and reimport them after, or fix the Reference name inside the MP so that they don't repeat, even without being key-sensitive.

    0 comments