Skip to main content

sms: distribution manager fails to send a package to a distribution point...

just a couple of links to some ways to address this. i find this crops up either occasionally on some of our servers, especially when concerning large packages like security updates. it happens during migration to new hardware occasionally, too. this is the typical error you'll receive:

Package XYZ00234 requires a newer version (3) of source files and the new compressed files haven't arrived yet, current version is 2, skip E:\SMS\inboxes\\INCOMING\Z3AWAX9I.PKG

multiple things you want to look at if you're running into this error:

this a really quick rundown on a way to get things moving. i don't suggest doing this unless you've exhausted the methods above outlined in the first 3 bullets. the dx21 method is the one i'm outlining here for reference. read it in full before you try this to understand what kind of unsupported position you will be putting yourself in.

to begin with, run this package status query:

SELECT * FROM PkgStatus WHERE Type=1 AND Status=1 AND ID='XYZ00234'
most likely, you'll get back a list of the distribution points where you're having a problem with the package. it should look like the following:
ID Type SiteCode PkgServer Personality Status SourceVersion UpdateTime Location ShareName HTTPUrl
XYZ00234 1 XYZ SMSServer1 0 1 93 2008-01-01
to give this a kick in the rear, run this next statement to reset the delta replication value by changing the status to 2 and changing the sourceversion to 0:
UPDATE PkgStatus SET Status=2, SourceVersion=0
WHERE (ID='XYZ00234') AND (TYPE=1) AND (PkgServer='SMSServer1')

and now it should look like this:

ID Type SiteCode PkgServer Personality Status SourceVersion UpdateTime Location ShareName HTTPUrl
XYZ00234 1 XYZ SMSServer1 0 2 0 2008-01-01

if you want to track the progress of a distribution, use the query below.

declare @ver int
declare @pkgid nvarchar(8)

set @pkgid = 'XYZ00234'

select    @ver=MAX(SourceVersion)
from    v_PackageStatusRootSummarizer
where    PackageID = @pkgid

create table #PkgProgress (RecordID int not null, Time datetime not null, SiteCode char(3) not null, PctComplete int not null, MessageID int not null, PRIMARY KEY(SiteCode,Time,RecordID))
insert into #PkgProgress(RecordID,Time,SiteCode,PctComplete,MessageID)

select    msg.RecordID, msg.Time, insSC.InsStrValue as SiteCode, IsNULL(insPC.InsStrValue,100)
       as PctComplete, msg.MessageID
from    v_StatusMessage msg
       join v_StatMsgAttributes att on msg.RecordID=att.RecordID
       and msg.Time=att.AttributeTime
       join v_StatMsgInsStrings insVER on msg.RecordID=insVER.RecordID
       and insVER.InsStrIndex=1
       join v_StatMsgInsStrings insSC on msg.RecordID=insSC.RecordID
       and insSC.InsStrIndex=2
       left join v_StatMsgInsStrings insPC on msg.RecordID=insPC.RecordID
       and insPC.InsStrIndex=3
where    MessageID in (3531,3532,3533)
       and Component in
       and att.AttributeID=400
       and att.AttributeValue= @pkgid
       and insVER.InsStrValue=CONVERT(varchar(10),@ver)

select    Sites.SiteCode, prog.Time, prog.MessageID, prog.PctComplete as 'Sending % Complete',
       Sites.Targeted as 'DPs Targeted', 100*Sites.Installed/Sites.Targeted as '% DPs Complete'
from    v_PackageStatusDetailSumm Sites left join (#PkgProgress prog join
       (select SiteCode, MAX(Time) as MaxTime
        from #PkgProgress group by SiteCode)
        as LastProg on prog.Time=LastProg.MaxTime and prog.SiteCode=LastProg.SiteCode)
        on Sites.SiteCode=prog.SiteCode
where    Sites.PackageID = @pkgid and Sites.Targeted>0
order by prog.SiteCode

drop table #PkgProgress


  1. Invalid object name 'v_PackageStatusRootSummarizer'

  2. make sure you're using the right database cliffe.

  3. hi, what do you mean with "database cliffe" i never heard the word "cliffe" in this case.


  4. hey kalla. i was actually telling "cliffe" to make sure he was using the right database. :)


Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here . (get-netadapter | get-netipaddress | ? addressfamily -eq 'IPv4' ).ipaddress   update: this is by far the easiest. PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress     are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does. done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it. i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we wa

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it. let’s look at the context of the alert: The Domain Controller's Op Master is inconsitent. See additional alerts for details. first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details. this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are: interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s o

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m