<div>
Hello,<br>The site status is sometimes not reliable, you may have a look into the logs behind the items to see, what is written there. You can set the status to clear the errors, warnings even there are errors in the logs. Even my server takes sometimes a day, if I clear errors and the status stills shows errors, even wehn I deleted the logs. <br><br>The error message would point me to a security issue, you may check the file permissions of the file you want to distribute. Sometimes I see on my servers, that - even I have my packages on drive D: that SCCM puts them onto drive C:, mainly if the free space on D: gets smaller than on drive C:&nbsp;
</div>


Oscar Powers

<div>
Thanks Bembi,<br>The package still in the same point, the folder I used to copy the package is open for everyone.<br>Something change because I did the same process last week and works fine. &nbsp;All solutions that I found in the internet is to enable for prestaged content, but my server has this enable.
</div>


<div>
You may check the logs and select as filter all sources. At least the error code I can find in different connections and point more to a task. <br>Have you made any updates in the past? At least the SCCM updates, which are triggered by SCCM intself may take some days as the effort depends from the maintenance windows for SCCM. If an update is still in process, possibly not all services are available. So possibly the task is just delayed due to other task. <br><br>Have you rebootet the machine shortly?&nbsp;<br><br>
</div>


<div>
I rebooted the server yesterday, no change. Still waiting for the package. &nbsp;But the server copy the drivers form my temp location to my OSD\DriverPackages\ and the package is in SCCM but not in the Distribution Point.<br>MigMCtrl the workitem queue is full!
</div>


<div>
MYD001F0 is the package that alert me about the problem, I add part of the DitMgr log and also the full log like attachment.<br><br>The size of package MYD001F0 is 1818982 KBytes &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:06:45.928+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>GetContentLibLocation - SCCM2012.mydomain.com &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:06:45.934+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>Finished GetContentLibLocation - SCCM2012.mydomain.com &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:06:45.936+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>GetDPUsableDrives - ["Display=\\SCCM2012.mydomain.com\"]MSWNET:["SMS_SITE=MYD"]\\SCCM2012.mydomain.com\ &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:06:45.938+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>Finished GetDPUsableDrives - ["Display=\\SCCM2012.mydomain.com\"]MSWNET:["SMS_SITE=MYD"]\\SCCM2012.mydomain.com\ &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:06:45.941+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>~Currently using 1 out of 3 allowed package processing threads. &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:06:50.082+240&gt;&lt;thread=3716 (0xE84)&gt;<br>~Sleep 3600 seconds... &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:06:50.084+240&gt;&lt;thread=3716 (0xE84)&gt;<br>The hash for algorithm 32780 is ABD12854A7CE7360B48559E53E4926B627BE3E16752103C822B858A7ECF2FD3F &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:48.951+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>STATMSG: ID=2376 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCM2012.mydomain.com SITE=MYD PID=3312 TID=12108 GMTDATE=Fri Jun 04 16:07:48.973 2021 ISTR0="MYD001F0" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 LE=0X0 AID0=400 AVAL0="MYD001F0" &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:48.974+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>~CDistributionSrcSQL::UpdateAvailableVersion PackageID=MYD001F0, Version=3, Status=2376 &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:48.976+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>~The source for package MYD001F0 has changed or the package source needs to be refreshed &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:48.979+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>~Adding these contents to the package MYD001F0 version 3. &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:49.002+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>~The Package Action is 1, the Update Mask is 32 and UpdateMaskEx is 0. &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:49.440+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>~Use drive D for storing the compressed package. &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:51.111+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>~Successfully created/updated the package MYD001F0 &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:51.133+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCM2012.mydomain.com SITE=MYD PID=3312 TID=12108 GMTDATE=Fri Jun 04 16:07:51.133 2021 ISTR0="MYD001F0" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 LE=0X0 AID0=400 AVAL0="MYD001F0" &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:51.133+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br>Package has the update source package flag set. ContentLibrary package flag update for remote DPs will be skipped as this will happen during content transfer to the server(s). &nbsp;$$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 12:07:51.134+240&gt;&lt;thread=12108 (0x2F4C)&gt;<br><a href="https://filedb.experts-exchange.com/incoming/2021/06_w23/1562744/distmgr.log" rel="ugc"></a><br><a href="https://filedb.experts-exchange.com/incoming/2021/06_w23/1562744/distmgr.log" rel="ugc">distmgr.log</a>
</div>


distmgr.log

<div>
<blockquote>MigMCtrl the workitem queue is full&nbsp;</blockquote>Looks like there is still running something in the background. <br>You may check the migmctrl.log<br>Check also the component status...<br><br>Also I see in the logs:<br><pre><code class="code-1 nolinks" id="code-20-43297993-1"><span>*** [08S01][233][Microsoft][SQL Server Native Client 11.0]Communication link failure  $$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;<strong>06-04-2021 11:29:50</strong>.321+240&gt;&lt;thread=5960 (0x1748)&gt; *** Failed to connect to the SQL Server.  $$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 11:29:50.321+240&gt;&lt;thread=5960 (0x1748)&gt; CSiteControlEx::GetDateLastModified: Failed to get SQL connection  $$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 11:29:50.321+240&gt;&lt;thread=5960 (0x1748)&gt; CSiteControlEx::GetMasterSCF:Failed to get DateLastModified time (MYD)  $$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 11:29:50.321+240&gt;&lt;thread=5960 (0x1748)&gt; ~Failed to get SCF while configuring ports.  $$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 11:29:50.321+240&gt;&lt;thread=5960 (0x1748)&gt; Shared DP upgrade processing thread: stopped.~  $$&lt;SMS_DISTRIBUTION_MANAGER&gt;&lt;06-04-2021 11:33:50.371+240&gt;&lt;thread=5964 (0x174C)&gt;</span>
</code></pre><br>
</div>


<div>
I find this tip: <a href="https://visualplanet.org/blog/?p=141" rel="ugc">https://visualplanet.org/blog/?p=141</a><br><br>He recommended to deselect the “Enable this distribution point for prestaged content” and next locate the package in the software library and click on “Update Distribution Points.” &nbsp;<br>So far is working, I am able to get the package in the Distribution Point.<br>The next step will be to select the “Enable this distribution point for prestaged content” &nbsp;again. This recreate the problem.<br>I will left this option unchecked but I do not get what change?
</div>


<div>
&gt; The next step will be to select the “Enable this distribution point for prestaged content” &nbsp;again<br>Have you tried it or is this an assumption?<br>Prestaged means, that you distribute the package first to a subset of clients for validation. And after validation to all other clients. If you use your SCCM for prestaging, you have to set it up in the way, that you are able to distribute it to a defined subset of clients. Just enabling it without any further configuration may mean, that there is no validation and therefore no distribution to the regular clients.&nbsp;
</div>


<div>
The next step will be to select the “Enable this distribution point for prestaged content”, yes I tried it and the problem comes back. &nbsp;<br>I only have one site, Do I need to enable prestaged content or not?
</div>


<div>
I deselect the “Enable this distribution point for prestaged content” and this fix the problem.<br>Thanks Bembi for your help.
</div>



I added a new driver package to SCCM, and it stay in "Waiting for prestaged content" for the last 12 hours. The description is "Distribution Manager is waiting for package MYD001EF content to be prestaged on the distribution point ["Display=\\SCCM.mydomain.com\"]MSWNET:["SMS_SITE=MYD"]\\SCCM.mydomain.com\. You must manually prestage the package MYD001EF on the distribution point before the content will be available.".
This works fine until today
My distribution Point is enable for prestaged content
I find these errors in distmgr.log
SetNamedSecurityInfo() failed.   SMS_DISTRIBUTION_MANAGER   6/3/2021 6:44:32 PM   3992 (0x0F98)
SetObjectOwner() failed. 0x80070002.   SMS_DISTRIBUTION_MANAGER   6/3/2021 6:44:32 PM   3992 (0x0F98)
SetFileSecurity() failed.   SMS_DISTRIBUTION_MANAGER   6/3/2021 6:44:31 PM   3992 (0x0F98)
On Site Status all roles are OK
I tried a new driver package with only one driver and get the same issue.
SCCM Version 2103
Any Ideas

Prestaged distribution point settings

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Systems Center Configuration Manager (SCCM, formerly known as Systems Management Server) is Microsoft’s system software for managing large groups of not only Microsoft computers, but those running other operating systems, such as Linux, OS-X, and various mobile technologies.