SCOM 2007 R2 CU 5 (OpsMgr / CU 5 cumulative Update) – Fehler 1603

Startseite – Aktivität Foren System Center Operations Manager Konfiguration & Architektur SCOM 2007 R2 CU 5 (OpsMgr / CU 5 cumulative Update) – Fehler 1603

Tagged: ,

This topic contains 0 replies, has 1 voice, and was last updated by  Jan Obes 6 years, 10 months ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #341

    Jan Obes
    Keymaster

    Hallo zusammen,

    bei der heutigen Migration von SP1 auf R2 CU5 trat ein Fehler auf (EventID 1023):

    ********************************************************************************

    Produkt: System Center Operations Manager 2007 R2 – Update “System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674)” konnte nicht installiert werden. Fehlercode 1603. Weitere Informationen sind in der Protokolldatei C:UsersUserNameAppDataLocalTemp3KB2495674-x64_0.log enthalten.

    ********************************************************************************

    Ferner konnte im Eventlog dieser Fehler gefunden werden:

    ********************************************************************************

    14 user registry handles leaked from RegistryUser:
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSERS
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftWindowsCurrentVersionExplorer
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwarePoliciesMicrosoftSystemCertificates
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftSystemCertificatesRoot
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftSystemCertificatesSmartCardRoot
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftSystemCertificatesTrustedPeople
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftSystemCertificatestrust
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftSystemCertificatesDisallowed
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftSystemCertificatesMy
    Process 6388 (DeviceHarddiskVolume2Program FilesSystem Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe) has opened key REGISTRYUSER

    SoftwareMicrosoftSystemCertificatesCA

    ********************************************************************************
    Doch was war passiert? Während des Upgrades traten Fehler auf, dass der Prozess noch im Zugriff von einem anderen Prozess ist und der SDK Dienst konnte nicht mehr gestartet werden.

    Wie löse ich das Problem? Relativ einfach :))

    Lösung:

    Im Manifest (Root Verzeichnis vom Operations Manager 2007 R2) des SKD Dienstes:
    ProgrammeSystem Center Operations manager 2007
    die beiden Dateien:
    •Microsoft.Mom.Sdk.ServiceHost.exe.config
    •Microsoft.Mom.ConfigServiceHost.exe.config
    Zwischen dem Bestehenden <runtime> Tags einfach eine neue einfügen:
    <generatePublisherEvidence enabled=”false”/>
    Diese Lösung deaktiviert die CLR Überprüfung dauerhaft.

    Hoffe, dass hilft euch :)

    lg + schönen Abend

    jan

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.