Content distribution is driving me a up a wall here. We've been pounding our heads against a desk for the last two weeks.

Long story short - one primary, seven remote DPs, varying WAN speeds. Also have one CloudDP.

Software distribution works fine.

Content distribution to the remote DPs and CloudDPs is NOT working fine.

When distributing content to the CloudDP, I get this from the pkgxfrmgr.log

ERROR: Could not get the package upload location!	SMS_PACKAGE_TRANSFER_MANAGER	2/25/2013 8:07:24 AM	4324 (0x10E4)
STATMSG: ID=9303 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_CLOUD_CONTENT_MANAGER" SYS=CMblah.fqdn.com SITE=ugh PID=4716 TID=4324 GMTDATE=Mon Feb 25 15:07:24.711 2013 ISTR0="ugh00034" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="ugh00034" AID1=404 AVAL1="["Display=\\(CloudDP).fqdn.com\"]MSWNET:["SMS_SITE=ugh"]\\(CloudDP).fqdn.com\"	SMS_PACKAGE_TRANSFER_MANAGER	2/25/2013 8:07:24 AM	4324 (0x10E4)
WARNING: Warning - returning null/empty download address from content upload ugh00034	SMS_PACKAGE_TRANSFER_MANAGER	2/25/2013 8:07:24 AM	4324 (0x10E4)
STATMSG: ID=9310 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_CLOUD_CONTENT_MANAGER" SYS=CMblah.fqdn.com SITE=ugh PID=4716 TID=4324 GMTDATE=Mon Feb 25 15:07:24.724 2013 ISTR0="ugh00034" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="00100034" AID1=404 AVAL1="["Display=\\(CloudDP).fqdn.com\"]MSWNET:["SMS_SITE=ugh"]\\(CloudDP).fqdn.com\"	SMS_PACKAGE_TRANSFER_MANAGER	2/25/2013 8:07:24 AM	4324 (0x10E4)
Failed to generate contentinfo for the package. BranchCache feature might not be turned on.	SMS_PACKAGE_TRANSFER_MANAGER	2/25/2013 8:07:24 AM	4324 (0x10E4)

When I remove the package and redistribute, there's a very good change it will succeed.

When I distribute to remote DPs on our WAN, I get the same "returning null/empty download address from content upload...." error.

Any ideas? I do have a ticket open with PSS, but lately it seems they are very overwhelmed.

I have seen the same a few times in different environments. I have also contacted Microsoft, hopefully I will get an answer soon. I know it might not be the answer you are looking for but now you know you are not alone.

It helps to know that, actually.

I've got an active case going. I'll post an update if I hear anything.

5 months later, new server, seeing this error again. Already have my case reopened. Kent - if you've heard anything that you can talk about, would love to know more.

Are you on SP1 CU2?

Yes.

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.