Re: Question!

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


Date: Mon, 13 Sep 2004 08:51:18 -0700

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: Advertisement Status Issue
    ... see execmgrsend a request to CAS, ... or something to do with Package versions. ... > package source version to be available. ... > Unless package doesn't have source, client will always generate this status ...
    (microsoft.public.sms.swdist)
  • Re: Advertisement Status Issue
    ... error on the client. ... On the SQL server, you can run SQL profiler to see what query MP is running. ... If it is a problem with package version, then check CAS.log to see what ... > request to LS, which ultimately seems to request DP Info from the ...
    (microsoft.public.sms.swdist)
  • Re: Advertisement Status Issue
    ... If there is a mis-match in version like this then it means that client ... Once cleint will receive updated policy, ... will request for package version 13. ... If it is a problem with package version, ...
    (microsoft.public.sms.swdist)
  • Re: breaking the model
    ... > The forms data then is in the Request object. ... HTTP Request; in this case, the form POST Request from the Page. ... client and server. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Resolving record with enumerated type
    ... In a CPU BFM package, ... because data goes in two directions (request from the ... from the server to the client), you'll need some way to orchestrate ...
    (comp.lang.vhdl)