Getting a couple SCCM Component Status Warning for SMS_HIERARCHY_MANAGER and SMS_RULE_ENGINE

Cody 321 Reputation points
2021-01-26T15:34:56.743+00:00

Hello,

I'm not sure what's causing these two warnings.

Component: SMS_HIERARCHY_MANAGER
Microsoft SQL Server reported SQL message 15401, severity 16: [42000][15401][Microsoft][SQL Server Native Client 11.0]
[SQL Server]Windows NT user or group 'ADServer.Domain.com\service-act' not found. Check the name again.

Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

I've added the domain\service-act local to the local administration group and I'm able to login to the server with the service-act. I don't know why it's getting the error.

Component: SMS_RULE_ENGINE

Content download failed.
Message: Failed to download one or more content files.
Source: SMS Rule Engine.

This one, I don't know what failed to download. Which log would I check to find content files failed to download?

Thanks.

Microsoft Security Intune Configuration Manager Other
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. SunnyNiu-MSFT 1,706 Reputation points
    2021-01-27T10:02:39.953+00:00

    @Cody

    [SQL Server]Windows NT user or group 'ADServer.Domain.com\service-act' not found. Check the name again.

    According to the error you provided, we may try to go to the SQL Manager Studio to check if domain\service-act has been added to Security>Logins. Corresponding login account properties:
    We may check the corresponding option in Server Roles and User Mapping. Like below screenshot:
    60936-31.png
    60952-32.png

    Component: SMS_RULE_ENGINE

    We may check ruleengine.log to find the content files that failed to download through the CMTrace (by default, %WinDir%\CCM\CMTrace.exe).


    If the response is helpful, please click "Accept Answer"and upvote it.
    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 No comments

  2. Cody 321 Reputation points
    2021-02-12T14:28:06.593+00:00

    @SunnyNiu-MSFT

    Any further thoughts on this? Hoping you can assist.

    0 comments No comments

  3. Christoph von Wittich 1 Reputation point
    2021-04-19T06:28:44.49+00:00

    I just had a similar problem with the Reporting Services User.

    USERDOMAIN is different here from USERDNSDOMAIN (check env vars with "set" on commandline) and I used USERDNSDOMAIN\sqlReportingServicesAccount in the Reporting Services Config in SCCM. -> FAIL

    It only works with USERDOMAIN\sqlReportingServicesAccount

    0 comments No comments

  4. Cody 321 Reputation points
    2021-01-28T21:51:01.63+00:00

    @SunnyNiu-MSFT

    I checked the SQL Manager Studio and verified that the domain\service-act are on both Server Roles and User Mapping, see screenshots
    ![61585-microsoft-sql-server-server-managerment-stidio-ser.png][1]![61586-microsoft-sql-server-server-managerment-stidio-ser.png][2]

    As for the Component logs. Here's what I see
    SMS_HIERARCHY_MANAGER
    Microsoft SQL Server reported SQL message 15401, severity 16: [42000][15401][Microsoft][SQL Server Native Client 11.0][SQL Server]Windows NT user or group 'campus.berkeley.edu\svc-ist-sccm-dev-act' not found. Check the name again.

    Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

    ruleengine.log
    Rule XML is: <AutoDeploymentRule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DeploymentId></DeploymentId> <DeploymentName>Automatic Deployment Rule for System Center Endpoint Protection</DeploymentName> <UpdateGroupId>ScopeId_369B21C2-5615-46FF-9878-C9415BD40FC2/AuthList_0082d71e-ca12-4166-895d-54e34f6d2ed3</UpdateGroupId> <UpdateGroupName></UpdateGroupName> <LocaleId>1033</LocaleId> <UseSameDeployment>true</UseSameDeployment> <AlignWithSyncSchedule>true</AlignWithSyncSchedule> <NoEULAUpdates>false</NoEULAUpdates> <EnableAfterCreate>true</EnableAfterCreate> <ScopeIDs><ScopeID>SMS00UNA</ScopeID> </ScopeIDs> <EnableFailureAlert>true</EnableFailureAlert> <IsServicingPlan>false</IsServicingPlan> <IsOldUpdateGroupCurrent>false</IsOldUpdateGroupCurrent> </AutoDeploymentRule>

    Criteria Filter Result XML is: <AutoDeploymentRule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DeploymentId></DeploymentId> <DeploymentName>Automatic Deployment Rule for System Center Endpoint Protection</DeploymentName> <UpdateGroupId>ScopeId_369B21C2-5615-46FF-9878-C9415BD40FC2/AuthList_0082d71e-ca12-4166-895d-54e34f6d2ed3</UpdateGroupId> <UpdateGroupName></UpdateGroupName> <LocaleId>1033</LocaleId> <UseSameDeployment>true</UseSameDeployment> <AlignWithSyncSchedule>true</AlignWithSyncSchedule> <NoEULAUpdates>false</NoEULAUpdates> <EnableAfterCreate>true</EnableAfterCreate> <ScopeIDs><ScopeID>SMS00UNA</ScopeID> </ScopeIDs> <EnableFailureAlert>true</EnableFailureAlert> <IsServicingPlan>false</IsServicingPlan> <IsOldUpdateGroupCurrent>false</IsOldUpdateGroupCurrent> </AutoDeploymentRule>

    SQL written back is: update Rules set Data = N'<AutoDeploymentRule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DeploymentId></DeploymentId> <DeploymentName>Automatic Deployment Rule for System Center Endpoint Protection</DeploymentName> <UpdateGroupId>ScopeId_369B21C2-5615-46FF-9878-C9415BD40FC2/AuthList_0082d71e-ca12-4166-895d-54e34f6d2ed3</UpdateGroupId> <UpdateGroupName></UpdateGroupName> <LocaleId>1033</LocaleId> <UseSameDeployment>true</UseSameDeployment> <AlignWithSyncSchedule>true</AlignWithSyncSchedule> <NoEULAUpdates>false</NoEULAUpdates> <EnableAfterCreate>true</EnableAfterCreate> <ScopeIDs><ScopeID>SMS00UNA</ScopeID> </ScopeIDs> <EnableFailureAlert>true</EnableFailureAlert> <IsServicingPlan>false</IsServicingPlan> </AutoDeploymentRule>' where RuleID = 1

    CRuleHandler::CreateFailureAlert - Alert ID = 16777222

    SMS_DMP_DOWNLOADER - dmpdownloader.log
    ERROR: Failed to download Admin UI content payload with exception: The underlying connection was closed: An unexpected error occurred on a send.

    Failed to call AdminUIContentDownload. error = Error -2146233079

    ![61601-microsoft-sql-server-server-managerment-stidio-ser.png][2]![61602-microsoft-sql-server-server-managerment-stidio-ser.png][3]

    0 comments No 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.