Share via

SCCM Compnent Status - Critical

N Kerr 6 Reputation points
2022-01-20T16:52:33.553+00:00

We are running SCCM version 5.00 9068.1000 build 9068.

I have noticed that the following components have a critical status:

SMS_REST_PROVIDER
SMS_NOTIFICATION_SERVER
SMS_TEAM
SMS_INVENTORY_DATA_LOADER

All of the devices are showing as offline so this may have something to do with it.

Microsoft Configuration Manager

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. N Kerr 6 Reputation points
    2022-01-20T17:38:15.487+00:00

    Inventory Data Loader failed to process the delta MIF file "XH808QF7B.MIF" and has moved it to "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\Outdated\zr1n00lb.MIF."

    SMS_TEM
    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_NOTIFICATION_SERVER

    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_REST_PROVIDER
    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.

    0 comments
  2. AllenLiu-MSFT 44,111 Reputation points Microsoft Vendor
    2022-01-21T02:53:11.213+00:00

    Hi, @N Kerr

    Thank you for posting in Microsoft Q&A forum.

    All of the devices are showing as offline , I think we may start from checking the client notification logs, shch as bgbmgr.log on site server and BGBServer.log on MP and CcmNotificationAgent.log on client.

    https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/log-files#BKMK_BGB

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. N Kerr 6 Reputation points
    2022-01-24T12:59:17.64+00:00

    BgbManager is waiting for file and registry change notification or timeout after 60 seconds $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:55:15.687+240><thread=13876 (0x3634)>
    Wait for events timed out after 60 seconds. $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:56:15.690+240><thread=13876 (0x3634)>
    Begin to get file list to process $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:56:15.691+240><thread=13876 (0x3634)>
    BgbManager is waiting for file and registry change notification or timeout after 60 seconds $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:56:15.692+240><thread=13876 (0x3634)>
    Wait for events timed out after 60 seconds. $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:57:15.694+240><thread=13876 (0x3634)>
    Begin to get file list to process $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:57:15.694+240><thread=13876 (0x3634)>
    BgbManager is waiting for file and registry change notification or timeout after 60 seconds $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:57:15.696+240><thread=13876 (0x3634)>
    Cleaning bad files in folder C:\Program Files\Microsoft Configuration Manager\inboxes\bgb.box\bad older than 30 days. $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:57:23.270+240><thread=12352 (0x3040)>
    Begin to update perf counter $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:57:23.280+240><thread=12352 (0x3040)>
    Begin to get file list to process $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:57:23.280+240><thread=12352 (0x3040)>
    Successfully updated perf counter $$<SMS_NOTIFICATION_MANAGER><01-24-2022 08:57:23.281+240><thread=12352 (0x3040)>

    0 comments
  4. Kalyan Sundar 566 Reputation points
    2022-01-24T20:58:36.52+00:00

    Is the bgbisapi.msi successfully installed kindly verify the BgbSetup.log for any error,

    If you see any fatal error, refer the below article

    https://www.prajwaldesai.com/fatal-msi-error-bgbisapi-msi-could-not-be-installed/

  5. Kalyan Sundar 566 Reputation points
    2022-01-26T19:01:34.96+00:00

    Did you face this issue after SCCM 2111 upgrade?

    Is all available SCCM hotfix are installed?

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.