none
Upgrate to SCOM 2016

    Question

  • Hi guys! I have SCOM infrustructure that consist of two management servers (first server - management,webconsole and acs; second - management server) and one separate SQL-server. I updated management server to SCOM 2016. When i open console i see that one server have build of scom 2016, but second server still have build scom 2012 7.1.
    PS C:\> Get-SCOMManagementServer
    
    HealthState DisplayName                                             Version
    
    ----------- -----------                                             -------
    Success     scom2                                                 7.2.11719.0
    Error       scom1                                                 7.1.10226.0

    How i can resolve this mistake?
    Thursday, February 7, 2019 11:13 AM

All replies

  • Hi

    Did you upgrade both servers? What path did you take to upgrade?

    Cheers


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Thursday, February 7, 2019 11:16 AM
  • Yes, i upgrade both servers. I cleared ETL tables, then upgraded server scom1 with 3 roles and then upgraded scom2.
    Thursday, February 7, 2019 11:18 AM
  • Hi,

    You could first of all try rebooting the management server having issues, also check the .dll files in the SCOM installation folder (C:\Program Files\Microsoft System Center 2016\Operations Manager\Server) to see whether they have the same version as the updated management server.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 7, 2019 11:20 AM
  • Reboot server and check file version. They have the same version as the updated management server
    Thursday, February 7, 2019 11:29 AM
  • Was the upgrade successful or did you have any errors/warnings?

    How does it look in the Operations Manager console? -> Administration\Device Management\Management Servers

    Your scom1 server reports "Error" under HealthState when running the Get-SCOMManagementServer, what is it complaining about?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 7, 2019 11:48 AM
  • Upgrade was successful

    in console:

    Health state for corrupted management server:

    Thursday, February 7, 2019 11:54 AM
  • You should use the following order when upgrading: Management servers first, followed by the gateways, operations consoles, and then agents. Next, you can upgrade any remaining features, such as the web console, reporting and Audit Collection Services (ACS).

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 7, 2019 12:22 PM
  • That's great, but what can i do to resolve this error? Delete management server?

    • Edited by viennaа Thursday, February 7, 2019 12:32 PM
    Thursday, February 7, 2019 12:30 PM
  • You could try performing a repair on your management server, see what outcome it gives.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 7, 2019 12:38 PM
  • Repiar from control panel - uninstall programm? if yes - still see old version
    Thursday, February 7, 2019 12:52 PM
  • Repair from the SCOM 2016 installation media, in worst case scenario you might have to remove all roles from the ”bad management server”, if you do that you could just fresh install the SCOM 2016 management server role.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, February 7, 2019 1:03 PM
  • I deleted "bad management server", reboot and install another, all work fine. But now i have error with report server, i am getting mistake "The Management server to which this component reports has not been upgraded" message and the upgrade is not proceeding.

    I installed console 2012 R2 SCOM (and 2016 console) and try install,but it's doesn't help me.


    • Edited by viennaа Monday, February 11, 2019 5:13 AM
    Monday, February 11, 2019 5:12 AM
  • Monday, February 11, 2019 7:18 AM
  • Yes, i installed scom 2016 console and now i get error:

    Unable to connect to the Data Access service for this management server. Ensure the Data Access service is running and that the service, the management group, and setup are all the same version.

    All both management server is ping and have open tcp-port 5723. System Center Data Access Service is also running
    Monday, February 11, 2019 7:52 AM
  • Try installing the SCOM 2012 R2 console and then upgrade it to 2016, as mentioned in the last comments in the post.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, February 11, 2019 7:53 AM
  • Now i doesn't have error about "The Management server to which this component reports has not been upgraded". I have this error:

    "Unable to connect to the Data Access service for this management server. Ensure the Data Access service is running and that the service, the management group, and setup are all the same version."



    • Edited by viennaа Monday, February 11, 2019 8:08 AM
    Monday, February 11, 2019 8:07 AM
  • Monday, February 11, 2019 8:12 AM
  • C:\Windows\system32>setspn -L mrsk-c\OM_OpSDK
    Registered ServicePrincipalNames for CN=OM_OpSDK,OU=SCOM,OU=ServiceInfAccount,DC=domain,DC=local:
            MSOMSdkSvc/scom2.domain.local
            MSOMSdkSvc/scom2
            MSOMSdkSvc/scom1.domain.local
            MSOMSdkSvc/scom1
    Monday, February 11, 2019 8:26 AM
  • Check whether the Data warehouse Writer account and Data Reader accounts and SDK account have local admin permissions on your server. If they are not, try adding them to the local administrators group.

    You can also check the logs to see if you find any more clues:
    %LocalAppData%\SCOM\Logs


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, February 11, 2019 11:19 AM
  • I added all scom accounts to local admins. In log i see:

    [15:02:31]:	Info:	:Could not connect to Management Server: scom1.domain.local with exception: Threw Exception.Type: System.TypeInitializationException, Exception Error Code: 0x80131534, Exception.Message: .......................... ........ "Microsoft.EnterpriseManagement.Common.Internal.SettingsCacheManager" .......... .....................
    
    [15:02:31]:	Info:	:Inner Exception.Type: System.TypeLoadException, Exception Error Code: 0x80131534, Exception.Message: .... .............. .................. ...... "Microsoft.EnterpriseManagement.Mom.InternalSdkOnly.IdUtil" .... ............ "Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35".
    
    

    Monday, February 11, 2019 12:04 PM
  • It was easy than i though. I uninstalled console, reboot server, install console and install UR for my scom servers, than my installation was started.
    • Proposed as answer by GouravIN Tuesday, February 12, 2019 4:54 PM
    Tuesday, February 12, 2019 1:30 PM