RE: Package Cannot Be Located
- From: Dawn <Dawn@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 5 Oct 2006 12:25:01 -0700
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!
- Follow-Ups:
- RE: Package Cannot Be Located
- From: Bernie Kilshaw
- RE: Package Cannot Be Located
- References:
- RE: Package Cannot Be Located
- From: Bernie Kilshaw
- RE: Package Cannot Be Located
- Prev by Date: Re: Useing SMS to push out excel files
- Next by Date: RE: Package Cannot Be Located
- Previous by thread: RE: Package Cannot Be Located
- Next by thread: RE: Package Cannot Be Located
- Index(es):
Relevant Pages
|
Loading
