Firewall had a Data filter that was blocking the dll. Once the filter is set to allow DLL, contents are distributed successfully.
Win32 error = 64 gave me the hint to check the network side.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all,
Having issue with Distributing Packages to a DP. Initially, the ContentAuthModule.dll is not present under C:\Windows\System32\inetsrv and IIS Application Pool kept crashing because such dll is not present. So i copied ContentAuthModule.dll from another DP and placed it under the appropriate folder. IIS then working fine and am able to browse to SCCM underlying sites.
Once IIS is back running, i am then facing the issue below; Failed to Copy the ContentAuthModule.dll from the Primary Site Server to the DP. Eventually, the ContentAuthModule.dll got removed and I have to copy the above again to get IIS to work. I have tried re-installing IIS and the required features and the rebooted the server.
Appreciate any feedback.
Firewall between the Primary Site Server and the DP is allowed any and Local Domain Firewall is off.
Thanks
Firewall had a Data filter that was blocking the dll. Once the filter is set to allow DLL, contents are distributed successfully.
Win32 error = 64 gave me the hint to check the network side.
If a DLL is being removed, you need to determine what is doing this. It's not ConfigMgr or normal IIS or Windows behavior so you need to look for other things in your environment that may do this like any security products or possibly even malware. Using procmon may help or setting a SACL on the file.
I actually saw the ContentAuthModule.dll being placed under the inetsrv folder. Once the error happened, it got removed.
the Win32 error = 64 and Win32 error = 59 am getting suggest networking issue with WAN Accelerator. However, we dont use it.
Sorry, not following. What do a couple of random error codes have to do with a DLL being deleted? Also, without context, like where exactly you are seeing these error codes and when exactly they occur, they are just as noted, completely random and meaningless for troubleshooting.