Hi guys....

Im in a desperate position at the moment. I joined a small company  a short while ago as an infrastructure engineer but have never had hands on experience with sccm 2012. The guy I was working with left at short notice and never had time to show me the system.

I am now trying to image some new systems but for some reason I keep getting the above error message. I have checked share and NTFS permissions and ensured that all the SMS accounts have a minimum of modify if not full rights including the local administrator account. The drives also have sufficient disk space. I am finding it impossible to update the distribution point (even though the wizards says successful).

Each time i try to run the task from the client I get Failed to run Task sequence, "This task sequence cannot be run because the program files for DI100005 cannot be located on a distribution point."

I have also ensured that Site system installation account is set to Use the site server's computer account to install the site system

Please can someone point me in the right direction and help me to resolve this issue.

Many Thanks

"SCCM Distribution Manager Failed to access source directory ..." is most likely seen in distmgr.log and it's the computer account of the site server that tries to access it.
"This task sequence cannot be run because the program files for DI100005 cannot be located ..." tells that the client is not able to find sources for DI100005  on a DP (might be caused by a missing or misconfigured network access account, source were not distributed to a DP, or boundary/group confi

Hi Torsten, 

Thanks for your reply. Im not sure what might have changed. It was all working a few weeks ago. Please can you give me an idea of where to look and what to look for? (as I mentioned im not familiar with the system yet).

Cheers

check the source location of the package and verify that you can access it. If you can, verify that your security settings (NTFS) hasn't changed on the folder.

Hi Kent, 

Im really sorry but in this instance I need you to treat me like the cleaning lady is doing the job as im not familiar with sccm. Do you mean \Software Library\Overview\Application Management\Packages ?

Sorry I cant post a screenshot yet until my account is verified. 

Cheers

Hi,

Please check if you have associated the DP with a specific Boundary Group.

Administration -> Distribution Points -> A DP properties -> Boundary Group

Best Regards,

Joyce

Check that the sccm site system account (the server) has acccess to the file share.

What is the distribution status for the package?
\Software Library\Overview\Application Management\Packages - Green?

If not - try to redistribute the package. See under Monitoring for the distribution status.
\Software Library\Overview\Application Management\Packages - Your package.

Michael

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Tuesday, August 26, 2014 7:34 AM

Hi, I have a "Configuration Manager Client Package" which is green and 100% compliant but neither of the boot images are green and neither is the OS image I want to use. 

Cheers

Aaron

Examine the log that I already mentioned above.

Hi Torsten, 

I have checked the log but not really sure what i am looking for. It tells me that a task has filed but not sure why?  Is SMS_Distribution _Manager a generic name used for whatever account its supposed to be using? 

Here is a snippet of the log from this morning. If you could please decypher it for me I would be very grateful. 

---------Log Start ----------

Found package properties updated notification for package 'DI100005'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:01.967-60><thread=7128 (0x1BD8)>
Found notification for package 'DI100005'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:06.969-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.032-60><thread=7128 (0x1BD8)>
~Starting package processing thread, thread ID = 0xCC0 (3264)  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.550-60><thread=7128 (0x1BD8)>
~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.552-60><thread=7128 (0x1BD8)>
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:07.720 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.720-60><thread=3264 (0xCC0)>
Start updating the package DI100005...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.721-60><thread=3264 (0xCC0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=14, Status=2300  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.728-60><thread=3264 (0xCC0)>
Taking package snapshot for package DI100005 from source \\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.115-60><thread=3264 (0xCC0)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.120-60><thread=3264 (0xCC0)>
~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.].  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.189-60><thread=3264 (0xCC0)>
~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.190-60><thread=3264 (0xCC0)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.191-60><thread=3264 (0xCC0)>
Failed to get the content library path.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
SnapshotPackage() failed. Error = 0x80004005  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.201 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim" ISTR1="Boot image (x64)" ISTR2="DI100005" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=13, Status=2302  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.363 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.363-60><thread=3264 (0xCC0)>
~Failed to process package DI100005 after 0 retries, will retry 100 more times  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.364-60><thread=3264 (0xCC0)>
~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.381-60><thread=3264 (0xCC0)>
Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.018-60><thread=8392 (0x20C8)>
~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.566-60><thread=7128 (0x1BD8)>
~Sleep 1826 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.591-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.611-60><thread=7128 (0x1BD8)>
~Sleep 1821 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.621-60><thread=7128 (0x1BD8)>
Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:42.490-60><thread=8392 (0x20C8)>
Found package properties updated notification for package 'DI100004'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:47.491-60><thread=7128 (0x1BD8)>
Found notification for package 'DI100004'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.425-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.450-60><thread=7128 (0x1BD8)>
~Starting package processing thread, thread ID = 0xE0C (3596)  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.950-60><thread=7128 (0x1BD8)>
~Sleep 585 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.952-60><thread=7128 (0x1BD8)>
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.072 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.072-60><thread=3596 (0xE0C)>
Start updating the package DI100004...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.073-60><thread=3596 (0xE0C)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=5, Status=2300  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.074-60><thread=3596 (0xE0C)>
Taking package snapshot for package DI100004 from source \\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.104-60><thread=3596 (0xE0C)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.108-60><thread=3596 (0xE0C)>
~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.].  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.122-60><thread=3596 (0xE0C)>
Failed to get the content library path.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
SnapshotPackage() failed. Error = 0x80004005  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.131 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim" ISTR1="Boot image (x86)" ISTR2="DI100004" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=4, Status=2302  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.132-60><thread=3596 (0xE0C)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.221 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.221-60><thread=3596 (0xE0C)>
~Failed to process package DI100004 after 0 retries, will retry 100 more times  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.439-60><thread=8392 (0x20C8)>
~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.965-60><thread=7128 (0x1BD8)>
~Sleep 580 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.966-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.979-60><thread=7128 (0x1BD8)>
~Sleep 575 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.980-60><thread=7128 (0x1BD8)>
Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:42:35.263-60><thread=3480 (0xD98)>

---------Log Finish ----------

Cheers, 

Aaron

~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.122-60><thread=3596 (0xE0C)>

This tells that the server where component Distribution Manager (SMS_DISTRIBUTION_MANAGER -> distmgr.log) is running on cannot access di-wsus-srv, because of error 67 (The network name cannot be found). That's an issue outside the scope of ConfigMgr though.

Any idea where i can change that file path, the D drive is not shared. SCCMContentLib is shared though. 

Also...any idea where i can double / triple check what account the Distribution manager is trying to use? I have assigned every related user i know of that works with sccm to each directory i know of and All the errors keep pointing to a permissions issue. I have even shared the D drive and still no change. 

"SCCM Distribution Manager Failed to access source directory ..." is most likely seen in distmgr.log and it's the computer account of the site server that tries to access it.

I've already mentioned to account that's being used ...

Sorry Torsten I dont see it? Is SMS_Distribution _Manager / SCCM Distribution Manager a generic name used for whatever account its supposed to be using or is that the actual account name? If the latter, I do not see that in my directory? else where is that account configured?

I have this same problem in 2012 R2 SP1 with Network Access Account being configured & VERIFIED (for Software Distribution)

This account CAN definitely access this share in question, yet it does NOT work!

Seb

That account is not being used by distmgr and it's using the computer account of the site server. 

Then it also makes no sense, as SCCM server object is also allowed to access same share.

So what the Network Access Account is actually used for?

Seb

The NAA is used by clients when accessing e.g. DPs in the WindowsPE phase of a task sequence. 

So it really is not useful at all in software installation (source access), or even remote data copy to DP during Application creation.

So to copy content from remote share Z to DP A (using SCCM client running on client X machine) what needs to have access to share Z (to be able to copy the install files to DP A)

Seb

The computer account of the site server.

Well, that is definitely not the case in my setup.

SCCM$ server object has read rights to remote share (share AND NTFS) and I can NOT copy any content to DP, not to say that I can not install anything directly from such share

Seb