Content status lists it as successfully distributed to all DPs (including the local site server)

However, component status for SMS_DISTRIBUTION_MANAGER continually logs these events:

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

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.

NOTE: It appears to not be any of these causes.

If I look at the smsdpmon.log on the server in question, the following is logged every half hour:

Intializing DP Monitoring Manager...    
SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Getting monitoring thread priority    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Getting content library root path    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Getting site code    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Getting algorithm ID    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Failed to find algorighm ID from registry. Use default algorithm.    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Getting DP Cert Type    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Failed to find DP cert type from registry. Use default type.    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Getting this DP NALPath    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Failed to create certificate store from encoded certificate..
An error occurred during encode or decode operation. (Error: 80092002; Source: Windows)    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)
Failed to initialize DP monitoring object. Error code: 0x80092002    SMS_Distribution_Point_Monitoring    1/2/2013 1:29:45 PM    2840 (0x0B18)

distmgr.log shows the following:

STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANY.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.109 2013 ISTR0="CDW00001" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Retrying package CDW00001    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
No action specified for the package CDW00001.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Start validating package CDW00001 on server ["Display=\\BRICK-CONFIGMGR.corp.COMPANY.com\"]MSWNET:["SMS_SITE=CDW"]\\BRICK-CONFIGMGR.corp.COMPANYNAME.com\...    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Failed to start DP health monitoring task for package 'CDW00001'. Error code: -1    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Updating package info for package CDW00001    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Only retrying local DP update for package CDW00001, no need to replicate package definition to child sites or DP info to parent site.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
StoredPkgVersion (2) of package CDW00001. StoredPkgVersion in database is 2.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
SourceVersion (2) of package CDW00001. SourceVersion in database is 2.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANYNAME.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.213 2013 ISTR0="Configuration Manager Client Package" ISTR1="CDW00001" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Failed to process package CDW00001 after 41 retries, will retry 59 more times    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:45 PM    2124 (0x084C)
Used 0 out of 3 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:50 PM    3784 (0x0EC8)
Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER    1/2/2013 1:29:50 PM    3784 (0x0EC8)

• Edited by mjh110 Wednesday, January 02, 2013 7:50 PM coding

Possibly related, I'm seeing this in the component status viewer for SMS_MP_CONTROL_MANAGER:

MP has rejected registration request due to failure in client certificate (Subject Name: APSP:3AB3648D-B55C-44CA-AD4A-BE54A1E50C62) chain validation. 
If this is a valid client, Configuration Manager Administrator needs to place the Root Certification Authority and Intermediate Certificate Authorities in the MPs Certificate store or configure Trusted Root Certification Authorities in primary site settings. 
The operating system reported error 2148204810: A certificate chain could not be built to a trusted root authority. 

Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see http://support.microsoft.com/kb/811833) being enabled?

• Edited by Adam MeltzerMicrosoft employee Wednesday, January 02, 2013 10:50 PM

Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see http://support.microsoft.com/kb/811833) being enabled?

Nothing special with certificates; I've used the basic stuff for intranet management of clients.

The only related thing I can think of that may have affected this, is that I discovered earlier today that my MP installation got hosed (error 500) due to a broken client install on the site server itself. I uninstalled the client manually and the server (as indicated by the component status views) appears to have repaired the MP install. Perhaps it didn't repair it completely? Would a site reset do me any good?

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.