Easily Fix SCCM SMS HIERARCHY MANAGER Error 3353
In this post, we will learn how to fix SCCM SMS HIERARCHY MANAGER Error 3353. The Site Hierarchy Manager component in SCCM processes and replicates changes to the site hierarchy.
In some cases, the admins may encounter an issue related to the SMS_HIERARCHY_MANAGER component. To view the error, go to the Monitoring > System Status > Component Status.
The current status of the component is critical. Right click SMS_HIERARCHY_MANAGER component and click Show Messages > Error. This displays all the error messages related to the component.
Checking one of the status message showed the following details.
- Message ID – 3353
- Description – Hierarchy Monitoring detected that the ConfigMgr SQL Server ports 1433, 4022 are not active on Firewall exception.
In the hman.log log file, we see the same error message. The following port [1433,4022] tcp firewall exception not active on SQL Server.
![The following port [1433,4022] tcp firewall exception not active on SQL Server](https://www.prajwaldesai.com/wp-content/uploads/2020/02/SMS_HIERARCHY_MANAGER-Error-3353-Snap4.webp "Easily Fix SCCM SMS HIERARCHY MANAGER Error 3353 4")
Fix SMS HIERARCHY MANAGER Error 3353 in SCCM
So, why do you encounter SMS HIERARCHY MANAGER Error 3353 in SCCM? The answer is: This issue occurs when the Windows Firewall is enabled, and you have not added the exception related to the SQL Server ports. In this scenario, the Configuration Manager and SQL Server are installed on the same machine.
For a list of all the ports used by Configuration Manager, read the following article.
The issue can fixed by allowing the above SQL server ports through firewall.
- On the Site Server, run PowerShell as administrator.
- Type the following command to add the exception in your Windows Firewall :-
New-NetFirewallRule -DisplayName "Allow ConfigMgr SQL Server ports" -Direction Inbound -LocalPort 1433,4022 -Protocol TCP -Action Allow
After few minutes, notice that the error message disappears from the hman.log.
In addition to that, the SMS_HIERARCHY_MANAGER component now shows the status as OK.
Check the status message details of message ID 3351. Hierarchy Monitoring detected that the ConfigMgr SQL Server ports are still active on firewall exception.
