none
Errors after Update from SCCM 2012 R2 to R2 SP1 RRS feed

  • Question

  • Since I updated our SCCM 2012 R2 to R2 SP1 I got some Errors in the "Site Status" and in the "Component Status". Before the upgrade everthing went fine and without problems. Also during the upgrade there wasn't any problem and in the "About"-Window from SCCM the correct Site-Version is 5.00.8239.1000.

    The SCCM-Server is running on a Windows Server 2008 R2 and the SCCM-Database is on a SQL-Server (2008R2) in the same subnet. There is only one site and only four site System Servers (two only as a Distribution Point, one as a site database, reporting and component Server and our primary site Server)

    I think that the Errors belong together, therefore I write only one post.

    Errors after upgrade (every 30-60 minutes):

    1) Site Status/Management Point:

    - SMS_Providers/Message ID 1090:

    Site Component Manager could not stop the winmgmt Service on site System "our primary SCCM-Server".
    Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.
    Solution: Verify that the Site System Connection accounts are properly configured to allow the site to administer the site system.

    (not enough rights? Why? Nothing has changed.)

    - SMS_Providers/Message ID 1020:
    Site Component Manager failed to reinstall this component on this site System.
    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.


    - SMS_Object_Replication Manager/Message ID 620:
    Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentRuleDetail_CIID_FK". The conflict occurred in database "ConfigurationManager", table "dbo.CI_CurrentRuleDetail", co


    - SMS_Object_Replication Manager/Message ID 6004:
    Object Replication Manager failed to process Object changes. These changes will be retried on next processing cycle.

    - SMS_MP_Control_Manager/Message ID 5436:
    MP Control Manager detected management point is not responding to HTTP requests.  The HTTP status code and text is 500, Internal Server Error.
    Possible cause: Management point encountered an error when connecting to SQL Server.
    Solution: Verify that the SQL Server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (msdbrole_MP) in the SQL Server database.

    Also I found out that "SMS_Providers"-Service isn't running. When I try to start it with the "Configuration Manager Service Manager" I get the error "Error communicationg with component". I spend a lot of time, but I didn't find a solution.

    Hopefully someone can help me to find out what's the problem.

    mardi 2 juin 2015 14:29

Réponses

  • Hello,

    i had the same Problem here... it was the anti Virus scanner (TrendMicro) blocking the winmgmt Service to stop during the smsproviders update.

    Unloaded the Anti Virus Scanner and the SMS Provider Update runs fine after restarting the sms component Manager.

    Please give me Feedback if this works....

    • Marqué comme réponse BambuPH mardi 9 juin 2015 14:35
    mardi 9 juin 2015 11:53

Toutes les réponses

  • This is going to be hard to solve here in the forums. 
    - sitecomp is not able to stop wmi: can most likely be ignored as it did most likely happen during the upgrade. Examine sitecomp.log.
    - reinstall failed -> sitecomp.log plus the install logfile of the component that failed to reinstall
    - objreplmgr.log
    - mpcontrol.log + mpmsi.log: was it successfully reinstalled at all?

    Torsten Meringer | http://www.mssccmfaq.de

    mardi 2 juin 2015 14:39
    Modérateur
  • Thank you for the fast reply. I know it's not really easy to solve this problem without direct access to the system. But perhaps I find a solution with some hints.
    I looked through a lot of eventlogs to find the Problem, but in SCCM it isn't really easy. ;-)

    The Errors in the logfiles you posted look like this:

    sitecomp.log (The error wasn't only during the upgrade, it occurs every 30 minutes.)

    INFO: Stopping service 'CcmExec'...
    Could not stop service winmgmt.  The operating system reported error 0: The operation completed successfully.
    INFO: 'our primary SCCM' is a valid FQDN.
    Reinstallation failed and will be retried in the next polling cycle.
    STATMSG: ID=1090 SEV=E LEV=D SOURCE="SMS Server" COMP="SMS_PROVIDERS".....

    The component that failed look like the SMS_PROVIDERS (also it isn't running, the error seems to be a Problem with the SQL-Server time)

    SMSPROV.log
    Execute WQL  =SELECT * FROM SMS_ComponentSummarizer WHERE TallyInterval='0001128000100008'
    Execute SQL =select  all SMS_ComponentSummarizer.AvailabilityState,SMS_ComponentSummarizer.ComponentName,SMS_ComponentSummarizer.ComponentType,SMS_ComponentSummarizer.Errors,SMS_ComponentSummarizer.HeartbeatInterval,SMS_ComponentSummarizer.Infos,SMS_ComponentSummarizer.LastContacted,SMS_ComponentSummarizer.LastHeartbeat,SMS_ComponentSummarizer.LastStarted,SMS_ComponentSummarizer.MachineName,SMS_ComponentSummarizer.NextScheduledTime,SMS_ComponentSummarizer.SiteCode,SMS_ComponentSummarizer.State,SMS_ComponentSummarizer.Status,SMS_ComponentSummarizer.TallyInterval,SMS_ComponentSummarizer.Type,SMS_ComponentSummarizer.Warnings from vSMS_ComponentSummarizer AS SMS_ComponentSummarizer  where SMS_ComponentSummarizer.TallyInterval = N'0001128000100008'
    Results returned : 71 of 72
    Removing Handle 21356488 from async call map

    CExtProviderClassObject::DoCreateInstanceEnumAsync (SMS_Query)
    CSspQueryForObject :: Execute...
    ERROR>: CSspQueryForObject::ConvertWBEMTimeToDBTime invalid wbemtime [2015/06/01 14:22:44.000]
    Execute WQL  =Select * from SMS_StatusMessage as stat left outer join SMS_StatMsgAttributes as att on stat.recordid = att.recordid left outer join SMS_StatMsgInsStrings as ins on stat.recordid = ins.recordid WHERE (COMPONENT="SMS_OBJECT_REPLICATION_MANAGER") AND (stat.Time>='2015/06/01 14:22:44.000') AND (SEVERITY=-1073741824) AND (SiteCode="our Sitecode") AND (MachineName="'our primary SCCM' ") order by stat.Time Desc
    Execute SQL =select  all stat.Component,stat.MachineName,stat.MessageID,stat.MessageType,stat.ModuleName,stat.PerClient,stat.ProcessID,stat.RecordID,stat.ReportFunction,stat.Severity,stat.SiteCode,stat.SuccessfulTransaction,stat.ThreadID,stat.Time,stat.TopLevelSiteCode,stat.PartOfTransaction,stat.Win32Error,att.AttributeID,att.AttributeTime,att.AttributeValue,att.RecordID,ins.InsStrIndex,ins.InsStrValue,ins.RecordID from vStatusMessages AS stat LEFT OUTER JOIN vStatusMessageAttributes AS att ON stat.RecordID = att.RecordID  LEFT OUTER JOIN vStatusMessageInsStrs AS ins ON stat.RecordID = ins.RecordID   where ((((stat.Component = N'SMS_OBJECT_REPLICATION_MANAGER' AND stat.Time >= '2015/06/01 14:22:44.000') AND stat.Severity = -1073741824) AND stat.SiteCode = N''our Sitecode ') AND stat.MachineName = 'our primary SCCM' ) order by stat.Time desc
    Results returned : 196 of 197
    -------------

    objreplmgr.log

    *** delete vCI_ConfigurationItems where CI_ID=16790756
    *** [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentRuleDetail_CIID_FK". The conflict occurred in database "ConfigurationManager", table "dbo.CI_CurrentRuleDetail", column 'Setting_CI_ID'.
    Failed to delete Deployment Type ScopeId_B2A1FB8B-6465-4548-A1F2-B9F1CB5E6E01/DeploymentType_d1fc517d-d0ba-4239-9bac-7d683d59d827/4

    mpcontrol.log

    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server ErrorSent summary record of SMS Management Point on ["Display=\\'our primary SCCM' \"]MSWNET:["SMS_SITE='our sitecode"]\\'our primary SCCM' \ to \\'our primary SCCM' \SMS_our sitecode \inboxes\SiteStat.Box\v6wuq654.SUM, Availability 1, 94266364 KB total disk space , 16913168 KB free disk space, installation state 0.
    Http test request failed, status code is 500, 'Internal Server Error'.
    Successfully performed Management Point availability check against local computer.

    mpmsi.log (it doesn't seems that it was reinstalled. During the Installation everything went fine. The log-file Shows that an Installation was canceled (from User?).

    Property(S): CompleteDialog_Info = Setup was successful.
    Property(S): UserExitDialog_Info = The ConfigMgr Management Point setup was cancelled.
    Property(S): InstallErrorDialog_Title = Setup Aborted
    Property(S): InstallErrorDialog_SubTitle = Setup failed
    Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue.

    MSI (s) (5C:5C) [13:26:02:989]: Product: ConfigMgr Management Point -- Installation operation completed successfully.
    MSI (s) (5C:5C) [13:26:02:990]: Windows Installer installed the product. Product Name: ConfigMgr Management Point. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

    Most of the errors seems to be a SQL-problem, but it's not easy to find out why this is happened. The regional and format (date,time) settings of the SQL-server and the primary server are the same.
    Is a possible solution to start the Setup from SCCM SP1 again or are there still more problems?


    mercredi 3 juin 2015 09:23
  • Or should I try to reinstall the management point?

    mercredi 3 juin 2015 12:37
  • I got the same errors when performing a upgrade last night.  I have a primary server with SQL and all system roles on that server. No errors during the SP1 upgrade (had sccm 2012 r2, no CU's) but a while after the upgrade the component status showed a lot of errors. It first started with the SMS_PROVIERS which state is Unknown, and then the Management Point was down not anstering to http request.

    I have tried removing the MP and reinstall it several times, but getting back to the same error.

    PXE did not work at this time either.I have moved the Management point to another server and now MP is up and running and PXE is working.

    SMS_PROVIDERS still are struggeling, not really sure what this component is.

    I havent tried a Site Recovery yet.

    Hoping for a solution to resolve this issue. I dont wanna perform any other SP1 upgrades untill I know the reason for this issue.

    jeudi 4 juin 2015 19:25
  • performed a Site Reset now. Now trying to install MP on the primary server again to see if it fixed the problems. SMS_PROVIDERS still nagging, but not sure if its "empty errors"
    jeudi 4 juin 2015 19:48
  • Site Reset didnt fix any issue. Same errors after aprox an hour.

    SMS_PROVIDERS component --> Site Component Manager could not stop the winmgmt service on site system.

    Site Component Manager failed to reinstall this component on this site system.

    Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

    MP Control Manager detected management point is not responding to HTTP requests.  The HTTP status code and text is 500, Internal Server Error.


    jeudi 4 juin 2015 20:53
  • Seems that no one has a solution or idea for this problem.  But at least I am not alone in this case. So the problem was the update to SP1 and not anything else.

    Additionally to the logfile-errors...at some of our clients in the tile view of Windows 8.1 the "Software-Center"-Tile is gone. At the moment software distribution isn't possible. No software is visible. Therefore it's not a little problem and I need a solution.

    The last days I tried to find out why this is happen. I checked any logfile and try to understand the errormessages. But I can't find anything. It's not comprehensible.

    @Herman Ohlsson:
    Good to know that Site reset didn't fix the issue. After you install the management point to another server, is software distribution possible and just errors in the logfile?
    SMS_PROVIDERS seems to be the connection from the SCCM-Server to the SQL-Server. But if there is no connection I think there has to be more problems.
    Did you find a solution meanwhile?

    mardi 9 juin 2015 09:28
  • Hello,

    i had the same Problem here... it was the anti Virus scanner (TrendMicro) blocking the winmgmt Service to stop during the smsproviders update.

    Unloaded the Anti Virus Scanner and the SMS Provider Update runs fine after restarting the sms component Manager.

    Please give me Feedback if this works....

    • Marqué comme réponse BambuPH mardi 9 juin 2015 14:35
    mardi 9 juin 2015 11:53
  • Hello Daniel,

    i think that is the solution. We also have TrendMicro-Virusscanner. ;-)
    I tried it and at the moment it seems that the installation works. Also Software Center (Software Distribution) is back to business. The most of the errors disappeared actually.
    Only the SMS_Providers Service in the Config Manager Service Manager displays the error "Error communicating with the component" if you query the status. But perhaps it's the same before the upgrade, I don't know.
    I will monitor all logiles today and tomorrow and take a look if any error will return.
    Never ever I would have thought that the virus scanner is the problem.

    THANK YOU for the great help!

    mardi 9 juin 2015 14:35
  • Same problem. Same root cause Trend !!!! Thank you you save my day ;)
    mardi 30 juin 2015 18:21
  • Same here! god damn!!!

    I think there are gonna me many others on the way.

    does anybody know if there is any new exclusion we need to add to AV on R2 SP1?

    or maybe Trendmicro should have an update to support this SCCM version?

    I almost reinstalled the whole server because of this freaking problem!


    Tamir Levy

    mercredi 22 juillet 2015 10:43
  • Removing Trend also resolved my issue with not being able to right click on Site System Roles and adding a deployment to distribution point group.
    • Proposé comme réponse sfewef vendredi 12 janvier 2018 22:02
    jeudi 6 août 2015 18:01
  • Exactly the same issue here Thank you very much !
    mardi 18 août 2015 17:56
  • We had Officescan installed, and surprise! After removing it, SCCM started functioning again!
    mercredi 9 septembre 2015 01:26
  • Hi All,

    Thanks for that post. I had issues by upgrading to CU1 from R2 SP1. We had to stop Office Scan Trendmicro for starting the CU upgrade. After that, after a reboot and after a few hours later MP stopped working with the HTTP error above. Currently we have disbaled the Office Scan services, rebooted the Primary Site and everything went back up and running. I'm now going to find out the exclutions for Office Scan.

    Cheers,

    Al

    jeudi 10 septembre 2015 08:39
  • That's exactly what i wrote above....
    jeudi 10 septembre 2015 08:43
  • Saved My day love doing an upgrade if it all works fine.......

    Its now working fine after disabling Trend Office scan

    this is not the first time that its been a problem!!

    vendredi 18 septembre 2015 14:04
  • Thank you so much Daniel!

    I had this same problem with my customer. Disabling the AV solution (TrendMicro) allowed it to upgrade the components.

    Regards,



    Jose Angel Rivera


    • Modifié balboa41 mercredi 2 décembre 2015 20:00
    mercredi 2 décembre 2015 20:00
  • Hello Al,

    Same problem here.

    With the TrendMicro AV disabled MP is working fine, with TrendMicro enabled it stops work.

    Have you found out an exclusion list for TrendMicro av?

    Cheers,

    David

    mardi 22 mars 2016 14:59
  • Hi Daniel,

    Have you an exclusion list for TrendMicro antivirus? same problem here - but I cannot leave the AV permanently disabled on the SCCM Server (company policies)

    mardi 22 mars 2016 15:00
  • Hello,

    Same for me (Trend Micro) during SCCM 2012 SP1 upgrade to 1511

    Thanks

    lundi 24 octobre 2016 09:43
  • Hi, 

    sorry for the late reply:

    You do not have to disable it permanently, only for the update process. The AV prevents the WMI Service to be stopped, but this is necessary for the update process.

    Best Regards

    lundi 24 octobre 2016 09:58
  • Hi Daniel

    Thanks man that worked for me ... Uninstalling trend micro fixed the issue.

    jeudi 17 novembre 2016 07:13
  • Thanks Daniel, tmlisten was requesting a password to unload for us too which was haulting the component update. Unless tmlisten unloads the WMIMGMT service cannot stop because of the dependency relationship. Manually unloaded Trend CLient and update went through perfect.
    mercredi 7 décembre 2016 14:01
  • It wouldnt be an excluision per se. Trend causes the issue because the WMI service is a dependency. The SMS Component update process needs to stop the WMI Service and cant because Trend is running/wont unload (normally because attempting to stop the tmlisten service pops up a GUI password box). Disabling Trend when performing SMS updates is the easiest solution.
    mercredi 7 décembre 2016 14:12
  • Seriously, the single greatest post I have read the entire week.  Unfortunately, I will now be looking for an SCCM\SQL server exclusions list unless I can get sign-off to remove Trend. 
    mercredi 26 avril 2017 16:45
  • Hello,

    i had the same Problem here... it was the anti Virus scanner (TrendMicro) blocking the winmgmt Service to stop during the smsproviders update.

    Unloaded the Anti Virus Scanner and the SMS Provider Update runs fine after restarting the sms component Manager.

    Please give me Feedback if this works....

    This sorted it for me - kicked the Winmgmt service - needed to pause it before i could stop it oddly! 

    vendredi 7 juin 2019 07:29