SCCM Distribution Point No existing connection Win32 error 121 – While I was working on distributing the content to a remote distribution point, I saw Win32 error=121. None of the content was getting distributed to the distribution point. The distribution point server was located in a remote site. A distribution point in SCCM stores the content files and allows users to download the software. Whenever an application or program is created, it must be distributed to distribution points. When you see such errors you should always check if the server is online. You should always check if the server name is resolvable. Next I started checking the log files and found some weird errors. Let’s look at these errors and resolution to this issue.
SCCM Distribution Point No existing connection Win32 error 121
In the distmgr.log file, I found multiple errors. Failed to make a network connection to \\Servername\ADMIN$ (0x79). Cannot establish connection to [“Display=\\servername\”]MSWNET:[“SMS_SITE=P01”]\\servername\.
There is no existing connection, Win32 error = 121
Error during connection to \\servername\SMS_DP$ (121).
Upon checking Monitoring > Overview > System Status > Site Status and site system status summarizer, I found few errors logged. Site System Status Summarizer still cannot access storage object “\\servername\C$\SMS” on site system “\\servername“.
I would like to highlight that the description is very important here. If you read the description it lists out possible causes and solutions for the message id 4701.
- The distribution point could be offline, not connected or may not be working fine. Check if the server is working fine.
- Site System Status Summarizer may not have enough access rights to connect to the site system and access the storage object. Check whether the accounts are configured to allow the site to connect to the site system and access the storage object.
- Network problems could also lead to this issue.
- This issue could also come up if someone has deleted the storage object or took the storage object out of service. Monitor the status messages reported by other site components and verify it.
Resolution – After I logged in to the distribution point server, I experienced an issue. I clicked on windows explorer, the server was hung. I rebooted the server. Post the reboot the content distribution worked. I wanted to understand what was the cause of this issue. From the event viewer I saw that the explorer process had stopped interacting with Windows and was closed.