PENDING Distribution Manager does not have access source directory or the distribution

[James Young]

Where to begin, so many problems with the DP, here are the syptoms:

• Failing on it’s built in packages (client install and update)
• Fails to create virtual directory on its own packages as well as once I create (old and new)
• Removed and reinstalled DP many times, but the IIS components for it are not there, I tried to manually add, it didn’t help

Server 2016
Version 1702

Here are the messages from the status logs for the DP

1.
Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = STC00002).

Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point.

Solution: Verify that distribution manager can access the package source directory/distribution point.

Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.

Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.

Possible cause: There is not enough disk space available on the site server computer or the distribution point.

Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.

Possible cause: The package source directory contains files that might be in use by an active process.

Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.

2.
Failed to create virtual directory on the defined share or volume on distribution point "["Display=\\xxx.domain.xxx.org\"]MSWNET:["SMS_SITE=STC"]\\xxx.domain.xxx.org\".

Possible cause: Distribution Manager requires that IIS base components be installed on the local Configuration Manager Site Server in order to create the virtual directory. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS).

Solution: Verify that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server.

I'm lost, please help. Let me know what other logs I can provide to help.

Thanks

 

[James Young]

By the way, the DP worked a few weeks or so ago, then started having issues, so I began the process of removing the role and reinstalling it thinking that would fix it.

 

[Prajwal Desai]

Hi @James Young have you tried checking the above solutions from status logs ?. Did you check distmgr.log file ?. Have you verified if the SCCM machine account and admin account were both part of local administrators of the Remote DP to be installed.

Links -
https://prajwaldesai.com/install-iis-base-components-on-sccm-distribution-point/

 

[James Young]

Yes to solutions from logs, and yes they are both in the local admin group.

I've attached the current log file you mentioned, it looks like it's telling me the same thing. the DP was setup to use drive s: not sure why it keeps checking c:. Look at settings and it does show s:

 

[James Young]

Made some changes to IIS and still not working. New log attached.

Thanks again

 

[James Young]

How's this for a strange turn of events. I removed the DP and now the built in packages (client distribution, etc...) aren't showing errors when the packages are redistributed. How is that possible. So adding the DP, breaks distribution? Any ideas?

 

[James Young]

But the clients still aren't getting deployed or updated

 

[Prajwal Desai]

I just reviewed the log file again, on which drive is the DP content stored ?. Can you check and confirm ?.

 

[cccsss01]

In regards to the 1st post, how do I verify the DP's have the correct access?

 

[alxwtech]

Seeing the same issue on my end