SCCM 2012 R2 Pull DP fails, works on Update Distribution Points

Question

I'm seeing some odd behavior out of a DP, in particular around driver packages. The system is running SCCM 2012 R2.  When I create the driver package I deploy it to the DP on the Primary Site Server. That usually happens in a couple of minutes or less.
I then deploy to a remote DP configured for Pull.  This generates the log entries below in the PullDP.log. Even waiting hours doesn't seem to help. If I do a Update Distribution Points for the package, it runs successfully.  I know
there was something similar fixed in SP1 CU3.
Intializing DP Monitoring Manager... PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting site code PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting DP Cert Type PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting this DP NALPath PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report state message 0x00000004 to MP PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report Body: <ReportBody><StateMessage MessageTime="20140322004854.000000+000" SerialNumber="1"><Topic ID="ACC0006D" Type="902" IDType="0"/><State ID="4" Criticality="0"/><UserParameters
Flags="0" Count="3"><Param>ACC0006D</Param><Param>["Display=\\DP.xxxxx.xxx\"]MSWNET:["SMS_SITE=ACC"]\\DP.xxxxx.xxx\</Param><Param>{B187E44B-4BF3-4748-B437-AFF29D679AA3}</Param></UserParameters></StateMessage></ReportBody>
 PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
CPullDPResponse::ReportPackageState return value 0x00000000. PullDP 3/21/2014 8:48:55 PM 3564 (0x0DEC)
Start Download  package ACC0006D version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
Start Download  package ACC00070 version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
ExecuteJob (1-NotStarted) 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
 Cannot find FileInfo (\\?\E:\SMS_DP$\ACC00070\9A25E477-3C0C-499E-A0C1-65243BDBCBF0.tar), content download failed PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
CPullDPPkgContJob::ExecuteJob() failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
State at failure: NotStarted PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Content job 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Package job has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Bob

Answer 1

We ended up changing the DP back to a standard distribution point.  That allowed the driver package to distribute successfully.  so as a result I can't access the logs any longer.
I should note for anyone who goes searching for this that we had problems with every one of our driver packages.  As I dug into it I found the contents, it looked like for some reason that it wasn't being transferred from the download location into
the final DP distribution location.  It almost looked like SCCM was ignoring driver package types.  I don't know if its a bug or just something quirky about this environment.
We were hoping to use Pull DP to handle our distributions more effectively, but we've backed off on that because of all the issues we've had with it.  I hate say it, but it appears to be another SCCM 2012 feature that sounds like a good idea, but the
implementation leaves a lot to be desired.
Bob