Updates not downloading (sits at 0%)

I had this problem in my lab environment and was only able to fix it by reinstalling SCCM altogether, but this problems seems to be different.  It seems to be finding all the updates, and even says "Total actionable updates = 12" but then it just sits at 0%.  Log file is attached.  Any ideas?
 

Attachment(s)

UpdatesDeployment.txt (84.70 KB) - downloaded 121 times

These are your red liners:
<![LOG[InstallUpdates failed, error 87d00703]LOG]!><time="08:12:40.981+300" date="06-19-2012" component="UpdatesDeploymentAgent" context="" type="3" thread="1968" file="updatesdeployment.cpp:190">
<![LOG[Failed to initiate installation of updates, error = 0x87d00703]LOG]!><time="08:12:40.981+300" date="06-19-2012" component="UpdatesDeploymentAgent" context="" type="3" thread="9520" file="sdkinterfaces.cpp:943">
 
<![LOG[Failed to create UpdatesDeployment, error 80070005]LOG]!><time="11:03:16.756+300" date="06-19-2012" component="UpdatesDeploymentAgent" context="" type="3" thread="4192" file="sdkinterfaces.cpp:814">
<![LOG[Failed to create UpdatesDeployment, error 80070005]LOG]!><time="11:03:47.482+300" date="06-19-2012" component="UpdatesDeploymentAgent" context="" type="3" thread="4192" file="sdkinterfaces.cpp:814">
 
What does windowsupdate.log say ?? Check the ports for wsus
 
try
1. Remove SUP role.
2. Uninstall WSUS including updates & metadata etc. Reboot server.
3. Install WSUS with recommended setting ( ports).
4. Configure SUP & synchronize updates using SCCM admin console
 

I have another client also trying to download and they don't have the same errors - not sure why his had that error while mine didn't.  I have now attached the log from my client where that error doesn't exist.  I did accept the defaults of 8530/85301 or whatever they are when I installed.
 

Attachment(s)

UpdatesDeployment.txt (66.24 KB) - downloaded 88 times

What's the CAS.log say?  And is the content on the DP?  

Well, I hadn't created any boundary groups, and after I did, they started receiving the patches.  Is that how it's supposed to work?  I feel dumb.

Common mistake.  But it's a nice safety feature too depending on how you look at it.

So, do you only have to assign boundary groups to sites if you have boundaries assigned?  I never setup any boundary groups in my lab environment, but I also never set up and boundaries.

A boundary group can be used for site assignment or for finding content.  If you have only one site and one DP, you could simply have one boundary like a range of 1.0.0.1-223.255.255.255 and associate it to the one DP.  When you have multiple locations and want clients to grab locally, you can break up those ranges to match the IPs in those locations and assign the DPs accordingly (but could still keep the one big range for assignment).
http://technet.microsoft.com/en-us/library/gg712679.aspx