Upgrade 2008R2 to 2012R on Configuration Manager Site Systems – Part V – Problems after the Site Server Upgrade

Problems after the Site Server Upgrade

It’s possible some problems already started with other Operating System Upgrades.

Communication problem between Management Points and Site Server

After some days we noticed several problems with our site.
The test environment had the same problem.

  • The status for the Management Points was Critical (Monitoring – Site Status) and Column Total showed 0 bytes.
  • When opening the Status logs i didn’t see anything relevant
  • We noticed several problems with all clients
    • Compliance reports didn’t update
    • All systems where Offline in the Configuration Manager Console
    • Hardware Inventory didn’t update
  • Eventually I noticed several Outboxes had too many files on Management Points and Fallback Status Point.

I found a workaround when i searched for ‘Management Point 0 Bytes and Critical’

https://social.technet.microsoft.com/Forums/en-US/b40a082c-2a05-44bc-920a-329b41c3a094/management-point-0bytes-and-critical?forum=configmanagergeneral

I made the Management Points and the Fallback Status Point Administrator on the Site System.

It’s not clear why Operation Manager didn’t report on outboxes with too many files. There are rules in place that sould report this.

Bits problems on one Management Point

The problems with our Compliance Reports continued.

I found the following entry in the IIS logs of one Management Point
BITS_POST /CCM_Incoming/{F13B3F42-D5E3-484C-AD27-1F83C42489BB} (bits_error:,501,0×80070005) 443 – <ip> Microsoft+BITS/7.8 501 0 0 1845 0

To fix this you need to remove and add the management point role to the site system https://gregramsey.net/2012/06/18/fix-for-error-in-iis-log-on-mp-bits_error5010x80070005/

I used a trick: Change the Management Point from https to http and back.
Monitor MPSetup.log and reboot the server after you see ‘Installation completed, but a reboot is required.’

This was the first production Site System I upgraded. It’s possible something went wrong because the Site tried to reinstall the Management Point before everything was ready. SMS_SITE_COMPONENT_MANAGER wasn’t disabled during this upgrade.

Problems related to Performance Counters

This problem also existed on the test environment.

We found “CounterThreadProc: MIFs/min counter missing” in the dataldr.log
A solution is documented in https://www.mnscug.org/blogs/sherry-kissinger/326-repeated-mifs-min-counter-missing-messages or http://www.stevensnet.com/Pages/Blogs/Blog_view.aspx?articleid=479

I saw similar entries for other counters

bgbmgr.log – SMS_NOTIFICATION_MANAGER

Begin to update perf counter
WARNING: PerfCounterMgr is not initialized, performance counter Total bad files moved is not available to update.
WARNING: PerfCounterMgr is not initialized, performance counter Total files processed is not available to update.
Begin to get file list to process
WARNING: PerfCounterMgr is not initialized, performance counter Total files remained is not available to update.
Successfully updated perf counter

statmgr.log – SMS_STATUS_MANAGER

Updating performance rate counters.
CStatusManagerPerfObject::UpdateRateCounters can not complete because CStatusManagerPerfObject is not initialized.

I decided to do the same trick for all performance counters.
<SITESERVER> is the name of the Site Server
E:\CM is our installation directory on the site server.
I got the services from the perfsetup.log where you can follow this installation.

push-location
cd E:\cm\bin\x64
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_EXECUTIVE .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_AD_SYSTEM_DISCOVERY_AGENT .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_DISCOVERY_DATA_MANAGER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_INBOX_MONITOR .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_INVENTORY_DATA_LOADER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_LAN_SENDER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_MP_FILE_DISPATCH_MANAGER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_NOTIFICATION_MANAGER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_SCHEDULER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_SOFTWARE_INVENTORY_PROCESSOR .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_SOFTWARE_METERING_PROCESSOR .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_STATE_SYSTEM .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_STATUS_MANAGER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_WAKEONLAN_COMMUNICATION_MANAGER .
E:\cm\bin\x64\perfsetup.exe /install /siteserver:<SITESERVER> SMS_WSUS_SYNC_MANAGER .
pop-location

Rest of the Series

Part I – Introduction
Part II – Problems during the Upgrade
Part III – Checklist during the Upgrade
Part IV – Upgrade Screenshots
Part V – Problems after the Site Server Upgrade

This entry was posted in Configuration Manager and tagged , . Bookmark the permalink.

4 Responses to Upgrade 2008R2 to 2012R on Configuration Manager Site Systems – Part V – Problems after the Site Server Upgrade

  1. Pingback: Upgrade 2008R2 to 2012R on Configuration Manager Site Systems – Part I – Introduction | Live Space Koenraad Rens

  2. Pingback: Upgrade 2008R2 to 2012R on Configuration Manager Site Systems – Part III – Checklist | Live Space Koenraad Rens

  3. Pingback: Upgrade 2008R2 to 2012R on Configuration Manager Site Systems – Part II – Upgrade Problems | Live Space Koenraad Rens

  4. Pingback: Upgrade 2008R2 to 2012R on Configuration Manager Site Systems – Part IV – Upgrade Screenshots | Live Space Koenraad Rens

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s