SCCM 2007 Clients Waiting for Content

I am trying to update an application using sccm.  I have configured the package the same way I always do.  I've ripped it out and recreated it.  No luck.
PolicyAgent log shows PolicyDownload started for the package number then CCM_PolicyAgent_PolicyDownloadSucceeded

 CAS log states "location update from CTM for content package#.1 and request (UUID) - repeating exactly 1 hour apart

The DataTransferService log shows that a DTS job was created to download from http://SCCMserver/site/pakcage to c:\windows\...\UUID.tmp - that's the last entry in the DTS log.  If I browse from the client to http://SCCMserver/site/pakcage I get a page full of XML

The Content Transfer Manager log shows  "Created and Sent Location Request '{8C02C6CC-2B03-4638-BCB9-3D2CB4DCC1C6}' for package SITE00160

Execmgr log shows
"state change from WaitingContent to WaitingContent" several times.

However, days later, the program in SCCM console states "Waiting for Content" and the package has not installed.  Any ideas before I call Microsoft?
whoamAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Please upload full locationservice.log as an attachment.

Is this the only package with the issue? Your boundaries may need to be checked if this is failing for entire offices.
whoamAuthor Commented:
Mr Singh,

Here is the log.
LocationServices-20150518-052201.log
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
stop sms agent host and move all the existing log files elsewhere.

Then start the smsagent service again. New sets of logs would be created.

locationservices.log should have the DP info.

Is this the only client that is failing the downloads or is it universal or just a single office?
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

whoamAuthor Commented:
Here you go, thank you.
LocationServices.log
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Is this the only client that is failing the downloads or is it universal or just a single office?
whoamAuthor Commented:
Universal, multiple pkgs, tried hosting the source files on different share/server too. No luck.
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
OK.

Find a client which is in an office which also has a DP.
Make sure that the content is on the DP
Push the program/package to the a collection containing this client.
Refresh the policy on this client. You should get the package/program name in execmgr.log
Deployment should fail. If it does not then case closed.

If it has failed then create a boundary range (IP range type)
Make this range 3 address long and it should have the ip address of this client 192.168.1.5-192.168.1.6
Assign this to the DP
Wait 5 mins and then refresh the policy on the client

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
whoamAuthor Commented:
The question alwasy seems so simple when you have the answer.  It was boundaries.  Some time ago, like 12 months ago, we reconfigured AD sites. Three were connected by gig or better fiber, so made one site of many subnets.
Odd thing is things continued to work for many months after this change, why I never connected the two events.
Anyway: Site Management>Site>SiteSettings>Boundaries.  Right clidk Boundaries, choose New Boundary.  Set Type to AD Site and browse the AD sites to add in the missing site(s).  Be sure to prune the defunct site(s).  Wait or just restart the SMS Agent Host services on the clients.  Clients will now find their SCCM/sms site or boundary and all will work.
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
The answer in this case maybe: In most places AD boundaries are misconfigured.

Also SCCM does not support Supernetted subnets. It expects a standard subnet.

http://blogs.technet.com/b/configmgrteam/archive/2009/12/21/known-issue-supernets-in-active-directory-sites-used-as-site-boundaries.aspx
whoamAuthor Commented:
full points to the expert, just wanted a fully detailed answer for any other users to see
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.