RE: Package Cannot Be Located

Hi Bernie,

I flipped the switch to have the child site be a Management Point this
morning. Now it looks like Apache (for another product) is using port 80
already in IIS on that child site server. So I'm not sure if that was the
problem all along. I will find out on Tuesday if we can remove Apache and
then I'll try it again.

I'll let you know what happens. Thanks for all your help!!

"Bernie Kilshaw" wrote:

Dawn,

yes you often see the first two lines in CAS log as errors, I think it's
just a timing issue.

It's normal to configure a Secondary Site Server as a Proxy Management Point
so that it can handle Advanced Clients which are local to it. If you've
replaced the server does the new server have write permission on the System
Management Container in AD so that it can write its record in?

It sounds as if there's still an entry in the System Management Container
for the previous server - I'd get rid of that as if the clients are being
given that as the MP they won't be getting the information they need to
identify the DPs they should be using.

HTH

Bernie

"Dawn" wrote:

Hi Bernie,

Thanks for the help, sorry I didn't respond sooner, I was out yesterday.

There were errors in the cas.log. I guess the GetLogonUserSid failed error
is fairly common (although thry didn't say what it was).

Here is the other one:

Failed to get DP locations from LS for content ABC0004A.1 and location
request {7DEE7B13-09A2-4881-8CDA-AAC4CC291A37}. I could not find any
postings about this error. The DP seems to be installed fine, because when I
send a new package, it processes it correctly.

The locationservices.log, it didn't appear to have any errors. It states
the current AD site of the machine (which is correct).

Retrieved Proxy Management Point from AD: {siteserver}
Attempting to retrieve local MP from AD
Current AD site of machine is LA
Retrieved local Management Point from AD: {previous child server name}

So it looks like it is still trying to communicate with the preivous child
site. I had uninstalled the site after installing the new child site. Was I
supposed to re-install the advanced client on all the machines again?

Also, am I supposed to have the child site setup as a management point? I
don't think the previous site was setup as one.

Thanks again for the help!!

"Bernie Kilshaw" wrote:

Dawn,

A couple to look at on the client c:\windows\system32\ccm\logs:
cas.log (Content Access Service log file) shows an advanced client accessing
package content or advertised programs from a Distribution Point. The log
shows if the advanced client can find the Distribution Point and whether or
not the client can access the content on the Distribution Point

locationservices.log will tell whether or not client is getting information
about the DPs holding the package. Will also give information on AD / SMS
site assignments and the MP being used.

HTH,

Bernie



"Dawn" wrote:

Hi Bernie,

Thanks for the response. I checked the boundries and the subnet, and both
seem to be fine. I am not getting any errors within the Site Status. I was
getting them previously because IIS and BITS was not installed on the child
site, so I though that was the problem. The child site is processing the
package, and the machines are getting the advertisement. Do happen to know a
log file I can look at to see where one of these clients are trying to
connect to?

Thanks!

"Bernie Kilshaw" wrote:

Dawn,

Not sure why the first post arrived empty - I'd go back and check your
boundaries and subnet definiitions, when I've seen that message it's always
been a boundaries issue.

Bernie

"Dawn" wrote:

Did you have any thoughts on this matter? You posted a blank page.

Thanks

"Bernie Kilshaw" wrote:



"Dawn" wrote:

Hello,

I have a seconardy site setup as a distribution point. I create the package
and it successfully makes it to the secondary site. But when the clients run
the package, I get the status of "The program for advertisement "ABC20075
has not yet started because the content for the package "ABC0004A" has not
been acquired. After a few days, it eventually fails saying the package
could not be located. I can see the ABC0004A directory and contents in the
D:\SMSPKGD$\ folder.

This secondary site is new (we had to replace our server) with a different
name than the clients had been connecting to previously. Would that matter?
The site boundaries are set correctly.

Anyone have any ideas?

Thanks!
.

Relevant Pages

  • RE: Package Cannot Be Located
    ... supposed to re-install the advanced client on all the machines again? ... am I supposed to have the child site setup as a management point? ... package content or advertised programs from a Distribution Point. ...
    (microsoft.public.sms.misc)
  • Re: Package Cannot Be Located
    ... I flipped the switch to have the child site be a Management Point this ... It's normal to configure a Secondary Site Server as a Proxy Management ... supposed to re-install the advanced client on all the machines again? ... package content or advertised programs from a Distribution Point. ...
    (microsoft.public.sms.misc)
  • RE: Package Cannot Be Located
    ... It's normal to configure a Secondary Site Server as a Proxy Management Point ... supposed to re-install the advanced client on all the machines again? ... am I supposed to have the child site setup as a management point? ... package content or advertised programs from a Distribution Point. ...
    (microsoft.public.sms.misc)
  • Re: Package Cannot Be Located
    ... Proxy Management Point and that the System Management container in AD has the ... new entry and that the entry for the old server is no longer there. ... I'd then install a new client and check that it picked up the new MP data. ... package content or advertised programs from a Distribution Point. ...
    (microsoft.public.sms.misc)
  • Re: Run advertised programs - program not available
    ... <![LOG[Refreshing the Management Point List for site ... <![LOG[Persisted Management Point Authentication Information ... > with new package version or DP doesn't have the package with correct ... >> From client machine, when attempting to manually run the program, I ...
    (microsoft.public.sms.swdist)
Loading