Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM Distribution point problem

  • Thread starter Thread starter mhue
  • Start date Start date
  • Replies Replies 4
  • Views Views 2K

mhue

New Member
Messages
2
Reaction score
0
Points
1
Hello everyone,
Since few weeks, my Distribution point has not been working. the download of the packages is in error and then the Distribution point drives have disappeared in the SCCM console. when I reconfigured the Distribution point, the drives are not present in the SCCM console.

Alert in SCCM:
ID 3353 :
Hierarchy Monitoring detected that the ConfigMgr SQL Server sccmdb ports 1433,4022, are not active on Firewall exception.

ID 3340
Hierarchy Monitoring detected that the SQL Server sccmdb Port 1433 has been changed to .

Hman.log:
Failed to connect HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL registry key for reading on SQL Server [sccmdb].

Can you please help me?
 
Hello everyone,
Since few weeks, my Distribution point has not been working. the download of the packages is in error and then the Distribution point drives have disappeared in the SCCM console. when I reconfigured the Distribution point, the drives are not present in the SCCM console.

Alert in SCCM:
ID 3353 :
Hierarchy Monitoring detected that the ConfigMgr SQL Server sccmdb ports 1433,4022, are not active on Firewall exception.

ID 3340
Hierarchy Monitoring detected that the SQL Server sccmdb Port 1433 has been changed to .

Hman.log:
Failed to connect HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL registry key for reading on SQL Server [sccmdb].

Can you please help me?
none of those have anything to do with dp. They are all about Sql. What have you done to troubleshoot these?
 
Thank you for your feedback
But, the dp is not necessarily the problem, the problem could come from the SCCM configuration or an access right that is not correct?
 
Thank you for your feedback
But, the dp is not necessarily the problem, the problem could come from the SCCM configuration or an access right that is not correct?
Correct that is why I asked what troubleshooting have you done?
 
Back
Top