Error while running the Task Sequence from RAP "requsted software cannot be located"

I spent around 45 min to 1 Hour to find the root cause why it is happening though i have updated all the packages and use the correct TS.

When you advertise a TS to refresh the Existing Operating system ,some times u might see error like "the requested software cannot be located ,the system might be in the process of transferring thse files try again later '

Resolution:  Try looking into the CAS.log file and see what it says .

In my scenario ,it gives me an error "Location update from LS for content C0100001.01 and location request …No matching location found ,no content request with the given handle found". This is a issue with the dafualt Image Pacakge and just updated to DP with new version.

There could be scenraios like  mis match of the policy package version the client has, vs. the version of the package offered at the DP .

Look at CAS.log(c:\windows\system32\ccm\logs), check the version of package requested. Also there might be the cases where,package version mismatch occurs.Compare the packge version from your console and version from CAS.log package version.

At your client, to resolve the mismatch, if interactively logged into your client, in the Configuration Manager applet, the Actions tab, run the "Machine Policy Retrieval & Evaluation Cycle". Wait 2 minutes. Then re-run "Machine Policy Retrieval & Evaluation Cycle".Then try your install again.

3 Responses to "Error while running the Task Sequence from RAP "requsted software cannot be located""

  1. Thanks for any other great article. Where else may anyone get that kind of info in such an ideal means of writing? I've a presentation next week, and I'm on the look for such info.

  2. Hello,
    I'm french so I apologize for my english.
    I had the same problem and I resolved it:
    My configuration:
    - a Task Sequence to advertise
    - on a Branch DP
    - on a "slow" boundary

    The problem was when I advertise a TS, I cannot choose what to do if the client is in a "slow" network. I don't know yet how it's managed but when I changed the configuraiton of the boundary, the client executed the TS without problem.
    => Never advertise a TASK SEQUENCE on a SLOW boundary.


Leave a Reply