Package missing from DP causing Task Sequence Failure

As you can see below a machine fails to run the Task Sequence.  Normally you should see the error like "ABC00001" was not found.  Here we have only the ID's of the Application.
 

Using the query below we are able to find the offending application./*** Script for SelectTopNRows command from SSMS  ******/
SELECT TOP 1000 [CI_ID]
      ,[PkgID]
      ,[CI_UniqueID]
      ,[SecuredTypeID]
      ,[ModelName]
  FROM [CM_CM0].[dbo].[vSMS_CIContentPackage]
  where CI_UniqueID like '%2caa%' 

CI_UniqueID		PkgID	CI_ID
138181		ABC0018D	ScopeId_EA3D3752-B4D4-453F-B3F3-03C70EAD781A/Application_2caa0766-569b-48c0-91b8-79bb3a22c0d7/1

Find the Application and ensure it is distributed to the DP/Secondary.

CDTSJob::HandleErrors: DTS Job '{GUID}' BITS Job '{GUID}' under user 'S-1-5-18' OldErrorCount 01 NewErrorCount 02 ErrorCode 0x801901F4

When testing out your distribution of files make sure you have a stable client and depending on your settings make sure your PKI certs are correct.  Are you using the Cert option when installing the client for HTTPS mode?  If so then the client will require a proper certificate.  Many times I see clients that have multiple certificates with Client Authentication enabled on the cert.  For this reason you might want to install the client with a specifiic Subject ID.  Also make sure the client certificate you are using is well formed.

When reviewing your logs you will see the the job is not able to pull down and the Server is showing errors.  Yet when you look at the IIS logs it shows that everything is working correctly.  This points to a local client issue. 

DataTransferService.log
CDTSJob::HandleErrors: DTS Job ID='{1CA46B86-16B6-4246-83CC-FEF3C8B2AAFD}' URL='http://DP.foo.com:81/SMS_MP' ProtType=1

CDTSJob::HandleErrors: DTS Job '{1CA46B86-16B6-4246-83CC-FEF3C8B2AAFD}' BITS Job '{19DA1164-3EDC-4B02-B8FA-5F82DE4BC240}' under user 'S-1-5-18' OldErrorCount 73 NewErrorCount 74 ErrorCode 0x801901F4

DTS job {0286E76F-90EA-4882-A0A2-0EAB93C82E14} BITS job {35BA3E86-6BFA-488A-83A6-AB756BE53500} failed to download source file http://DP.foo.com:81/SMS_MP/.sms_dcm?Id&DocumentId=e5ebd347-1856-40ad-91c0-099cdf211de9/MANIFEST&Hash=F14C08616AB4A7D5EFBB12C5B633CD5EEBD7C9ADDD79E9EF3487826962A8B3A5&Compression=zlib to destination D:\Program Files\SMS_CCM\CIDownloader\Staging\{944B51A2-C4ED-4194-8EE8-F66A005CCCA7}_1.zip with error 0x801901F4

DTSJob {92E53D9A-7924-42B8-AED6-755CEE4673E8} in state 'Error'.

CDTSJob::JobError: DTS Job ID='{0286E76F-90EA-4882-A0A2-0EAB93C82E14}' BITS Job ID='{35BA3E86-6BFA-488A-83A6-AB756BE53500}' ErrorCode=0x801901F4

Resuming DTS job '{0286E76F-90EA-4882-A0A2-0EAB93C82E14}' as BITS job '{35BA3E86-6BFA-488A-83A6-AB756BE53500}' went to error state earlier.

ProcessDTSManifest failed. (0x80070057)

IIS logs:
2013-12-16 21:48:41 163.188.195.3 HEAD /SMS_MP/.sms_dcm Id&DocumentId=e5ebd347-1856-40ad-91c0-099cdf211de9/PROPERTIES&Hash=7B1B04C6D389406C4B15D924304CCDA581B9E0643E38224D24CE14BE327C511D&Compression=zlib 3480 - 10.10.15.3 Microsoft+BITS/7.7 - 200 0 0 15

Testing with BitsAdmin
C:\Windows\system32>bitsadmin /info {19DA1164-3EDC-4B02-B8FA-5F82DE4BC240} /verb
osE
BITSADMIN version 3.0 [ 7.7.9600 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.
BITSAdmin is deprecated and is not guaranteed to be available in future versions
 of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cm
dlets.
GUID: {19DA1164-3EDC-4B02-B8FA-5F82DE4BC240} DISPLAY: 'CCMDTS Job'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\SYSTEM
PRIORITY: NORMAL FILES: 0 / 2 BYTES: 0 / UNKNOWN
CREATION TIME: 12/16/2013 2:34:50 PM MODIFICATION TIME: 12/16/2013 3:41:45 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: REGISTERED NOTIFICATION FLAGS: 11
RETRY DELAY: 60 NO PROGRESS TIMEOUT: 28800 ERROR COUNT: 68
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://DP.foo.com:81/SMS_MP/.sms_dcm?Id&DocumentId=e5ebd347-1856-40ad-91c0-099cdf211de9/PROPERTIES&Hash=7B1B04C6D389406C4B15D924304CCDA581B9E0643E38224D24CE14BE327C511D&Compression=zlib -> D:\Program Files\SMS_CCM\CIDownloader\Staging\{DB2577BC-B521-45F3-B11B-FAF6547424B0}_2.zip
ERROR CODE:    0x801901f4 - HTTP status 500: An unexpected condition prevented the server from fulfilling the request.
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION:
JOB FILES:
        0 / UNKNOWN WORKING http://DP.foo.com:81/SMS_MP/.sms_dcm?
Id&DocumentId=e5ebd347-1856-40ad-91c0-099cdf211de9/PROPERTIES&Hash=7B1B04C6D3894
06C4B15D924304CCDA581B9E0643E38224D24CE14BE327C511D&Compression=zlib -> D:\Progr
am Files\SMS_CCM\CIDownloader\Staging\{DB2577BC-B521-45F3-B11B-FAF6547424B0}_2.z
ip
        0 / UNKNOWN WORKING http://DP.foo.com:81/SMS_MP/.sms_dcm?
Id&DocumentId=e5ebd347-1856-40ad-91c0-099cdf211de9/MANIFEST&Hash=F14C08616AB4A7D
5EFBB12C5B633CD5EEBD7C9ADDD79E9EF3487826962A8B3A5&Compression=zlib -> D:\Program
 Files\SMS_CCM\CIDownloader\Staging\{DB2577BC-B521-45F3-B11B-FAF6547424B0}_1.zip
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ?           true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
         Enable download from peers      :true
         Enable serving to peers         :true
CUSTOM HEADERS: NULL

Resolution:

I tried many different solutions.  But I ended up deleting the duplicate computer certificate that had Computer Authentication and renewing the current one with a new key...
Then the client started to work correctly.

File C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1639

Sometimes error are not exactly what they seem

Error 1639: Windows Installer Error 1639: 'Invalid command line argument' during installation

is seen in your ccmsetup.log file or the client.msi.log file similar to this:

clent.msi.log

MSI (s) (D0:A4) [09:48:51:623]: PROPERTY CHANGE: Modifying SMSCACHEDIR property. Its current value is 'Default'. Its new value: 'D:\CorpCache" CCMHTTPSSTATE='.

ccmsetup.log

Running installation package
  Package:     C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
  Log:         C:\Windows\ccmsetup\Logs\client.msi.log
  Properties:   REINSTALL=ALL REINSTALLMODE=vmous  SMSSITECODE="ABC" DNSSUFFIX="foo.com" CCMHTTPPORT="80" CCMHTTPSPORT="81" SMSCACHESIZE="20000" SMSCACHEDIR="D:\CorpCache"" CCMHTTPSSTATE="480" CCMFIRSTCERT="1"

File C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1639
Action:

Solution:

Turned out the machine was seeing an extra " or space. 
I re-arranged the setup command and placed "" around the values, it installed correctly

Always check your install package or command line when running the full commnad line with parameters.

Could not access network location %APPDATA%

Installing the SCCM 2012 client can be a daunting task when errors occur.  Here one such error can be seen:

MSI: Action 12:51:08: CostFinalize. Computing space requirements
MSI: Could not access network location %APPDATA%\.
MSI: Could not access network location %APPDATA%\.
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1603
Action: CostFinalize.
I have seen this error only once on a new machine.  I have seen it several times on a machine that was upgraded from SCCM 2007 to SCCM 2012 and then reveted back to SCCM 2007.  This error occurs shortly after the install process to once again move it to SCCM 2012.

I don't know if the state of the machine was already damaged but you will see the Security regisitry look something like this:

In order to fix this problem you need to fix the AppData folder setting seen here in a working machine:

In some cases the damaged registry is missing many of the enviromental variables and it is necessary to recreate or fix all of them.  The registry in question is the s-1-5-18 account SID:
SECURITY_LOCAL_SYSTEM_RID

A special account used by the operating system. 

Failed to Add Update Source for WUAgent of type (2) and id ({GUID}). Error = 0x80004005.

There are many reasons why WU will not work correct with the SCCM Agent.
Various fixes:

1. Run Windows Update and let the update fix the machine
2. Stop the Update Agent Service, Delete the Software Distribution folder and restart the service.

Here is yet another way:

WUAHandler.log:
Unable to find or read WUA Managed server policy.
Unable to read existing WUA Group Policy object. Error = 0x80004005.
Failed to Add Update Source for WUAgent of type (2) and id ({GUID}). Error = 0x80004005.

UpdatesHandler.oog:
Updates scan completion received, result = 0x80004005.

Try this:

C:\Windows\System32\GroupPolicy\Machine
Rename the Registry.pol file

Then re-run the Software Updates Scan Cycle in the Configmgr Actions tab.

then watch the logs:

WUAHandler.log:
Waiting for 2 mins for Group Policy to notify of WUA policy change...
Added Update Source ({GUID}) of content type: 2
Async searching of updates using WUAgent started.