Re: Question!

From: David Randall [MS] (davidra_at_microsoft.com)
Date: 09/14/04


Date: Tue, 14 Sep 2004 08:54:04 -0700

ipsec23 let me know offline that the pkg update fixed the problem.

-- 
-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Randall [MS]" <davidra@microsoft.com> wrote in message 
news:OoWJUjcmEHA.3336@TK2MSFTNGP10.phx.gbl...
> Just to make sure the client policy and the server policy and the package 
> information are in sync,
>
> Right click your package and update it.  This will bump the version number 
> on the package.  Then, wait for the other servers to get the new policy 
> (every 60 minutes by default, unless you want to manually trigger a 
> machine policy cycle) and see if they can get the package.  The only thing 
> that comes to mind is an out-of-sync policy with the package version.
>
> -- 
> -- 
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
> "ipsec23" <ipsec23@discussions.microsoft.com> wrote in message 
> news:F305363C-DE0C-4DF1-AA5A-1CEDDF991E59@microsoft.com...
>> Hi David,
>> Thanks for the response. The site server and the servers are on different
>> subnets and have included both the subnets in the Site boundaries tab.In 
>> the
>> "Roaming boundaries" tab have set the "include site boundaries within the
>> local roaming boundaries of this site" . I have not enabled my DP to be a
>> protected DP.
>>
>> Some servers of the same server subnet are able to receive content and 
>> apply
>> patches which makes me wonder as to why only certain servers are acting
>> strange!!!?? Changed the adv properties to run the prg from a remote
>> ditribution point .Found that the cleint received the updated policy but 
>> then
>> again it has started showing the same old error message "ContentAvailable
>> ignoring update with no DPs for content request ID
>> {42025D82-43BC-41EF-A8F2-FF55836C3609}".
>>
>> Many Thanks!!
>>
>>
>> "David Randall [MS]" wrote:
>>
>>> ContentAvailable ignoring update with no DPs for content request ID
>>>
>>> means that you don't have the package at the distribution point for the
>>> client.
>>>
>>> Check to make sure the DP has the package (in Package Status node)
>>> Make sure your client computer is in the roaming (or site) boundaries of 
>>> the
>>> site you're intending to have it get DP's from.
>>> By default, the advertisement properties say "don't run" when the 
>>> computer
>>> is a remote roaming boundary, try changing the advertisement properties 
>>> to
>>> "run" and see if that helps.
>>> If you've got protected DP's, then the client is outside the boundaries 
>>> of
>>> all your DP's.
>>>
>>> Let us know how it goes.
>>>
>>> Dave
>>> -- 
>>> -- 
>>> This posting is provided "AS IS" with no warranties, and confers no 
>>> rights.
>>> "ipsec23" <ipsec23@discussions.microsoft.com> wrote in message
>>> news:369EF276-0100-43B6-A3B8-4875ACC04DAB@microsoft.com...
>>> > Hi carl,
>>> > Thanks for the response.I havent had much luck with recompiling the
>>> > cimwin32.mof.Heres what i did.
>>> > Found that almost all of my 2000 servers was showing this error in 
>>> > their
>>> > respectinve execmgr.log files. Fortunately found one machine that 
>>> > could
>>> > downlaod content from the DP and deploy the patch. Copied the 
>>> > cimwin32.mof
>>> > from this machine and copied it to the machine under examination. 
>>> > Created
>>> > a
>>> > batch file "troubleshoot.bat" with the location of the .mof file which
>>> > looked
>>> > like this :
>>> > Mofcomp C:\Winnt\system32\wbem\cimwin32.mof
>>> > Executed the batch file and got the message Done!, which i believe
>>> > indiacted
>>> > that the compilation was successfull. Executed the "Run Advetised
>>> > Programs"
>>> > utility to find execmgr.log is generating the follwing messgae hour 
>>> > after
>>> > hour!
>>> > ContentAvailable ignoring update with no DPs for content request ID
>>> > {42025D82-43BC-41EF-A8F2-FF55836C3609}
>>> > To stop this error messsage from getting generated  tried recompiling 
>>> > with
>>> > the old file again but it doesnt seem to fix the problem.  I guess the
>>> > problem has worsened now.Please help!! How do i resolve this issue??
>>> > Many Thanks!!
>>> >
>>> > "ipsec23" wrote:
>>> >
>>> >> Hi,
>>> >> I am running SMS 2003 on a Windows 2003. I am having a problem with 
>>> >> my
>>> >> test
>>> >> cleint receiving a patch update from the site server. execmgr.log 
>>> >> shows
>>> >> the
>>> >> following.
>>> >> Execmgr.log
>>> >> ========
>>> >> Policy is updated for Program: MBSA - 2000_Update, Package: CIT00012,
>>> >> Advert: CIT20021
>>> >> Content version for program MBSA - 2000_Update package CIT00012 has 
>>> >> been
>>> >> changed to 3
>>> >> Cancel content request for program MBSA - 2000_Update package 
>>> >> CIT00012 as
>>> >> content version has changed.
>>> >> Requesting content from CAS for package CIT00012 version 3
>>> >>
>>> >> Raising event:
>>> >> [SMS_CodePage(437), SMS_LocaleID(1033)]
>>> >> instance of SoftDistWaitingContentEvent
>>> >> {
>>> >> AdvertisementId = "CIT20021";
>>> >> ClientID = "GUID:6438FECA-0BB5-4D5C-B5BD-2A1F2B2AB111";
>>> >> DateTime = "20040910065455.421000+000";
>>> >> MachineName = "ACE";
>>> >> PackageName = "CIT00012";
>>> >> PackageVersion = "3";
>>> >> ProcessID = 1240;
>>> >> ProgramName = "MBSA - 2000_Update";
>>> >> SiteCode = "CIT";
>>> >> ThreadID = 1472;
>>> >> };
>>> >> Successfully raised SoftDistWaitingContentEvent event for program 
>>> >> MBSA -
>>> >> 2000_Update
>>> >> Execution Request for program MBSA - 2000_Update state change from
>>> >> WaitingContent to WaitingContent
>>> >> ContentAvailable ignoring update with no DPs for content request ID
>>> >> {42025D82-43BC-41EF-A8F2-FF55836C3609}
>>> >>
>>> >> From the last line of the log snippet, looks like the client is 
>>> >> unable to
>>> >> find DP's.But i find the "package distribution point" setting to show 
>>> >> the
>>> >> right DP.The DP has recd the content. The client is able to access 
>>> >> the
>>> >> mgmt
>>> >> point. I am wondering as to why it is not able to get the content 
>>> >> from
>>> >> the DP?
>>> >> Can someone kindly help me out.
>>> >>
>>> >> Many Thanks!!
>>> >>
>>>
>>>
>>>
>
> 


Relevant Pages

  • Re: Question!
    ... Just to make sure the client policy and the server policy and the package ... Right click your package and update it. ... wait for the other servers to get the new policy ...
    (microsoft.public.sms.admin)
  • Re: Question!
    ... The policy gets to the client before the package gets to the DP. ... wait for the other servers to get the new policy ...
    (microsoft.public.sms.admin)
  • Re: Roaming Boundaries Question!
    ... points on that package, or write a script that will do it for you at 8pm. ... The remote offices I ... >> There are two types of roaming boundaries - local and remote. ... If the Advanced Client is in the boundary of a protected ...
    (microsoft.public.sms.setup)
  • Re: Roaming Boundaries Question!
    ... points on that package, or write a script that will do it for you at 8pm. ... The remote offices I ... >> There are two types of roaming boundaries - local and remote. ... If the Advanced Client is in the boundary of a protected ...
    (microsoft.public.sms.admin)
  • Re: Account Lockout threshold
    ... All are window 2000 advanced servers with Service pack 3, ... Domain Contoller Security Policy - Account lockout threshold ...
    (microsoft.public.security)