Distribution Point Configuration Status - Warning - Failed to retrieve the package list on the DP.

Hi,
Some of our DP's have a warning (Shown with a yellow exclamation mark) that never goes away. I have run a script on the DP's that could check for inconsistency in WMI, but it found nothing. Everything seems to work fine, but it is annoying that everything
is not green when it should be!
The warning is:
Failed to retrieve package list on the distribution point. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure.

Hi Peter,
Yes I have tried to validate all content to no avail. ;(
No help to find in smsdpmon.log, I really think it is a bug...
Here is a small part of it:
]LOG]!><time="03:50:29.934-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
<![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:29.943-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Start to evaluate package 'C010003E' version 0 ...]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:586">
<![LOG[Report status message 0x4000094C to MP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.996-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Start to evaluate package share for package 'C010003E' version 0 ...]LOG]!><time="03:50:32.510-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:629">
<![LOG[Package C010003E is verified successfully]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:649">
<![LOG[Report state message 0x40000950 to MP]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:889">
<![LOG[Report Body: <ReportBody><StateMessage MessageTime="20141129025032.000000+000" SerialNumber="0"><Topic ID="C010003E" Type="901" IDType="0"/><State ID="2384" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>C010003E</Param><Param>["Display=\\dk01dc1sscm01.local.avk.dk\"]MSWNET:["SMS_SITE=C01"]\\dk01dc1sscm01.local.avk.dk\</Param></UserParameters></StateMessage></ReportBody>
]LOG]!><time="03:50:32.520-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
<![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:32.528-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Report status message 0x40000959 to MP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[Report status message 0x40000952 to MP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
<![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
file="smsdpmon.cpp:1051">
<![LOG[DP monitoring finishes evaluation.]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:500">

Similar Messages

DP's have Warning "Failed to retrieve the package list on the distribution point" - How to Clear it?

All but one of my DP's (A new one I just created) have this Warning Message: "Failed to retrieve the package list on the distribution point". They all seem to be working, I can update and push new content to them.
When I go to the smsdpmon.log, it has an error for a package, but I've since redistributed it, and it is working fine. (Items below are snips from the smsdpmon.log)
CContentDefinition::LibraryPackagesWmi: The package data in WMI is not consistent to PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
CContentDefinition::LibraryPackagesWmi: Package PS10011B can't be found in PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
CContentDefinition::LibraryPackagesWmi failed; 0x80004005 SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
Failed to evaluate package PS10011B, Error code 0x80070002 SMS_Distribution_Point_Monitoring 11/16/2013 6:29:50 PM 3920 (0x0F50)
Since then, after redistributing the package, it clears up the logs... but not the warning in Monitoring:
Start to evaluate package share for package 'PS10011B' version 0 ... SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
Package PS10011B is verified successfully SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
So since everything appears to be working fine, how do I clear out that Warning, so I have nice Green Check Mark Icons in my Monitoring Tab, so when something actually does go wrong, I won't just ignore it since it's always been set to Warning?

I'll have to review this. The script
here, alone did not solve the my issue. Interesting that it say I do not have any inconsistencies on any my DP's now, but I run the other one on a single DP, it states I have inconsistencies still.
$WMIPkgList = Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib | Select -ExpandProperty PackageID | Sort-Object
$ContentLib = (Get-ItemProperty HKLM:SOFTWARE\Microsoft\SMS\DP).ContentLibraryPath
$PkgLibPath = ($ContentLib) + "\PkgLib"
$PkgLibList = (Get-ChildItem $PkgLibPath | Select -ExpandProperty Name | Sort-Object)
$PkgLibList = ($PKgLibList | ForEach-Object {$_.replace(".INI","")})
$PksinWMIButNotContentLib = Compare-Object -ReferenceObject $WMIPkgList -DifferenceObject $PKgLibList -PassThru
##### section 1 #######################
Write-Host Items in WMI but not the Content Library
Write-Host ========================================
$PksinWMIButNotContentLib
Foreach ($Pkg in $PksinWMIButNotContentLib){
Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib -Filter "PackageID = '$Pkg'" | Remove-WmiObject -Confirm
I wonder if the first script is not looking for INI's whereas the second one is. I verified that the INI's do exist...
I'll run the second on all of my DP's, remove the left over INI's, and report back again next week on status.
-Tony

All DPs read "Failed to retrieve the package list on the distribution point"...

About 2 weeks ago all 10 of my DPs started reporting the following warning (roughly 2 weeks after upgrading to R2):
"Failed to retrieve the package list on the distribution point ["Display=\\<server.FQDN>\"]MSWNET:["SMS_SITE=<code>"]\\<server.FQDN>\. Or the package list in content library doesn't match the one in WMI. Review
smsdpmon.log for more information about this failure.
This warning has appeared in my environment once before and I've read a number of posts regarding it. In the previous situation I found the problematic package ID recorded in smsdpmon.log and followed the standard procedure of redistributing and then proceeded
with a validation check on the affected DP. These steps resolved the issue originally.
This time around the package ID is not referenced in smsdpmon.log. It had the same error but the ID was not listed. Unfortunately the logs have already rolled over and I forgot to save a copy so I don't have anything to reference. I'm curious if anyone else
has seen this behavior and what the recommended fix is.
As always, appreciate the help!

I used the following process to clean up these warnings on my DPs:
Setup content validation checks for each of my affected DPs to run every morning (previously only set to weekends). I did this so when I made a change I could validate whether or not it worked the following day. It would be great if there was a way to force
these checks manually but I haven't found a method yet.
After the content validation check completed I filtered through the smsdpmon.log on each affected DP. This revealed the package ID that was causing the issue.
In my environment the package in question was not needed so I deleted it. If it is required I suspect re-distributing it would work as well.
At this stage the problem was still not fully resolved for me. Even though I had deleted the package WMI was still inaccurate. I used this script to scrub WMI on all affected DPs and it picked up the problematic package ID:
http://gallery.technet.microsoft.com/Powershell-script-to-fix-81dc4e69
My content validation checks are now passing and the warnings are being cleared. YEAH!
As a final note - After running the PS script Nickolaj posted I ran started seeing dozens of error checks on my packages (Distribution Manager failed to process package "Laptop Drivers" (package ID = XYZ00123).) After doing some research
I found I was prone to this issue:
Failed to start DP health monitoring task. In my case the suspect file was called "Microsoft". I moved it to another location and the errors cleared immediately.
Hope this info is helpful to others!

Distribution Point Configuration Status - SMS Client - Restart might required

SCCM 2012 was updates to SCCM 2012 R2. After that Management Console display for one of servers in Monitoring section - Distribution Point Configuration Status: SMS Client - Restart might required - In Progress. This DP was restartred but status "In
Progress" stay.
Distribution point works fine but status is confuses me.
How delete this status? Where can I delete dp status from SQL server?

Check the database to find any DP with the InsStr2 value is 3010. Here are the steps for your reference. > Make sure you have good backup of the site DB> Run the following select statement to find the Distribution Points in this state:
select * from dbo.DistributionStatus where InsStr2 = '3010'
> Once identified then Delete a record an affected DP with:
delete from dbo.DistributionStatus where ID = <DPID of affected DP identified by above command>

Last Status Update in Distribution Point Configuration Status after 2012 R2 Upgrade not updating

I am having the oddest problem, and I was wondering if anyone had some pointers or knows how I can get this working. After I upgraded from
2012 SP1 CU3 to 2012 R2, the status update date on the DP config status will not update at all, even though under each DP it is updating? I can still push content to them, but instead of getting a % of transfer that is complete I get the generic 'Detail will
be available after the server finishes processing the messages'. I have tried to remove and re add the DP role to the DP's and am met with the same problem. I am assuming it's something is SQL but where to begin to look I have no idea.

Yes, I know this is an old post, but I’m trying to clean them up.
Did you solve this problem, if so what was the solution?
BTW I find that most of these type of things take ~ 24 hours to update.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Distribution Point Group Status Pie Chart Incorrect

In my SCCM 2012 R2 environment, I have only one Distribution Point Group, which contains all 20 of my DPs.
All packages have been distributed successfully to this DP group (verified via the Content Status node and checking each package, as well as the Distribution Point Configuration Status showing all 20 DPs with the green check-mark.
However, when I look under the Distribution Point Group Status, I see my DP group ("All DPs"), showing 20 members, but an Overall Distribution Status of "Error". The pie chart for that group shows package status as Success: 106
/ In Progress: 0 / Failed: 163. The pie chart for "Distribution Point Group Status" for the "All DPs" group shows the colors appropriate to these (incorrect) numbers. If I click the "View Status" link next to the pie
chart, the different tabs (Success, In Progress, Error, Unknown) show:
Successfully distributed content: 20 (269 Content Items) (last status time: today)
Successfully processed content on distribution point: 19 (263 Content Items) (last status time: yesterday)
Nothing in the In Progress, Error, or Unknown tabs.
So my question... Why is my Distribution Point Group Status showing the group with 163 Failures, but all Distribution Points showing 100% success on all packages? Is there a bug that causes the Distribution Point Group Status to not update?
I've restarted the server a couple of times, and still no change.

Hello all together!
I've the same issue in my SCCM R2 environment.
Has everybody an idea, how to correct this issue?
Thanks for your reply.
Regards Luke

Warning: failed to retrieve...

when i type "pacman -S gnome" i get this
warning: failed to retrieve some files from extra
error: failed to comit transaction (unexpected error)
errors occurred, no packages were upgraded.
if someone can assist me with this problem it would be appreciated
thank you in advanced

Glad you were able to resolve your issue.
Please edit your initial post and add "[SOLVED]" somewhere in the topic. This way people don't have to read the thread to know that you have resolved the issue.
See http://bbs.archlinux.org/viewtopic.php?id=50161.

[SOLVED] warning: failed to retrieve some files

Hello ,
I am new to ArchLinux and i have been struggeling with pacman today. I cant get it to download pakages from the mirrors. I have downloaded pakages through the archlinux.org website and used the command "pacman -U". But "pacman -S" only generates error messages.
--2012-03-12 23:06:50-- [url]ftp://ftp.ds.hj.se/pub/os/linux/archlinux/extra/os/x86_64/eclipse-3.7-1-x86_64.pkg.tar.xz[/url]
=> `/var/cache/pacman/pkg/eclipse-3.7-1-x86_64.pkg.tar.xz.part'
Resolving [url=ftp://ftp.ds.hj.se]ftp.ds.hj.se[/url]... 193.10.239.170
Connecting to [url=ftp://ftp.ds.hj.se]ftp.ds.hj.se[/url]|193.10.239.170|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD (1) /pub/os/linux/archlinux/extra/os/x86_64 ... done.
==> SIZE eclipse-3.7-1-x86_64.pkg.tar.xz ... done.
==> PASV ... done. ==> RETR eclipse-3.7-1-x86_64.pkg.tar.xz ...
No such file `eclipse-3.7-1-x86_64.pkg.tar.xz'.
warning: failed to retrieve some files from extra
error: failed to commit transaction (error invoking external downloader)
Errors occurred, no packages were upgraded.
I have changed dns to 8.8.8.8 and i have uncommented the wget line in pacman.conf but still no positive result. I have also uncommented several mirrors in the mirror list.
Any clues?
Best Regards
Problemer
Found this thread one day later : https://bbs.archlinux.org/viewtopic.php?id=130138
Last edited by Problemer (2012-03-13 16:49:33)

Ok... So now i have generated a new mirrorlist through the wiki. I guess that the lower the score the better the mirror is.
I have tried several new pakages and one of them was chromium.
--2012-03-12 23:59:22-- http://mirror.devnu11.net/archlinux/extra/os/x86_64/chromium-14.0.835.202-1-x86_64.pkg.tar.xz
Resolving mirror.devnu11.net... 78.46.68.28
Connecting to mirror.devnu11.net|78.46.68.28|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-03-12 23:59:22 ERROR 404: Not Found.
Still nothing... Any guess? Excuse the spoon feeding approch but i'm tired of this now
Last edited by Problemer (2012-03-12 23:05:35)

Failed to retreive the pacakge list on the distribution point...

I am slowly cleaning up some content mismatches among my distribution points after an R2 upgrade. I am down to my final 2 DPs, both of which are my only standalone DPs. Both servers report the same errors in smsdpmon.log:
Failed to evaluate package XYZ0013A, Error code 0x80070002
Failed to evaluate package XYZ0013B, Error code 0x80070002
I checked the following locations and these Package IDs are nowhere to be seen:
DP\SCCMContentLib\PkgLib - no matching INI files.
WMI - no matching records (gwmi -Namespace root\sccmdp -Query "select * from SMS_PackagesInContLib where PackageID = 'XYZ0013A")
SCCM Console - nothing listed.
Where else could these packages be recorded? They're obviously not in use anywhere.

Hi,
Do you have any errors in the distmgr.log and pkgxfermgr.log file on the site server?
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Distribution Point migration status in CM12 console

Hi,
We are using sccm 2012 r2 cu2. we are in middle of migration.
We have in sccm 2007 under secondary site server name assd1 it contain MP and DP role.
Under ASSd1 server i was created one of the distribution point server and copied all the package to the new server assd2.
I created this new distribution point last week.
Today I gathered data from sccm 2007 to sccm2012.
Previously I did the same almost 5 servers and after sccm2012 administration-->under site hierarchy--> shared distribution point it shows. after that i will migrate to sccm2012 DP
but this server not showing. but when i saw migctrl.log i can see the log
The DP assd2.xxx.org is eligible for upgrade
but not showing under administration-->under site hierarchy--> shared distribution

Issue got resolved..

Is it possible to retry Distribution Point role removal if failed initially?

During my lab testing I came across a scenario where if you select to remove a distribution point role while the remote server hosting the distribution point isn't contactable, SMS_DISTRIBUTION_MANAGER won't retry the removal. Is there a (clean) way to manually
remove the distribution point role from the remote server or trigger SMS_DISTRIBUTION_MANAGER to attempt the removal again? In this case I will be rebuilding the server anyway, but I'm curious if there is a way to do this in case I encounter it in a production
scenario

may be you can try this solution http://blogs.msdn.com/b/rslaten/archive/2006/03/01/removing-a-retired-dp-from-all-your-packages.aspx
http://eskonr.com/2009/11/report-that-gives-bad-distribution-points/
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

Failed to retrieve git package from all mirrors [Solved]

Hi there. I'm having trouble installing git. Everything else I've installed has been fine (and I have installed other things while this problem persists)
$ sudo pacman -S git
resolving dependencies...
looking for inter-conflicts...
Targets (2): perl-error-0.17018-1 git-1.7.12-1
Total Download Size: 2.66 MiB
Total Installed Size: 17.00 MiB
Proceed with installation? [Y/n]
:: Retrieving packages from extra...
error: failed retrieving file 'git-1.7.12-1-x86_64.pkg.tar.xz' from mirror.aarnet.edu.au : The requested URL returned error: 404 Not Found
I leave pacman running through all the other mirrors, and it just cannot find the file on any of them.
When I look at http://mirror.aarnet.edu.au/pub/archlin … os/x86_64/ I see that there is git-1.7.12.1-1-x86_64.pkg.tar.xz which is named differently to the target pacman is looking for (git-1.7.12-1-x86_64.pkg.tar.xz)
I'm new to arch and pacman. Where could this inconsistency be coming from, and how would I go about resolving it?
EDIT: Just found the -y option in the pacman man page. Solved!
Last edited by oadams (2012-09-23 07:26:37)

I used the following process to clean up these warnings on my DPs:
Setup content validation checks for each of my affected DPs to run every morning (previously only set to weekends). I did this so when I made a change I could validate whether or not it worked the following day. It would be great if there was a way to force
these checks manually but I haven't found a method yet.
After the content validation check completed I filtered through the smsdpmon.log on each affected DP. This revealed the package ID that was causing the issue.
In my environment the package in question was not needed so I deleted it. If it is required I suspect re-distributing it would work as well.
At this stage the problem was still not fully resolved for me. Even though I had deleted the package WMI was still inaccurate. I used this script to scrub WMI on all affected DPs and it picked up the problematic package ID:
http://gallery.technet.microsoft.com/Powershell-script-to-fix-81dc4e69
My content validation checks are now passing and the warnings are being cleared. YEAH!
As a final note - After running the PS script Nickolaj posted I ran started seeing dozens of error checks on my packages (Distribution Manager failed to process package "Laptop Drivers" (package ID = XYZ00123).) After doing some research
I found I was prone to this issue:
Failed to start DP health monitoring task. In my case the suspect file was called "Microsoft". I moved it to another location and the errors cleared immediately.
Hope this info is helpful to others!

Status is failed when a batch is scheduled when the destination is PDF

Hi,
I have couple of batched which need's to be scheduled among those one of the batch which are ll running with PDF destination is getting the status as error so what would be the error for this.
It's an urgent task please let me know any suggestions
Thanks

check FrConfig.cmd file it will point to Setenv.bat file... make sure you have correct path there. when i made changes in there it is now accepting the folders
OR
There is a related Bug (known issue) for this. You'll have to use the hyperion service user(the user account which was used to install) to burst to a shared directory.
How about creating a hard link and adding that as an ExportFolder. (I've never tried it). It may work because FR might think that as a local folder.
When i said hard link was a referring to a link created using MKLINK command Mklink not a local folder.
let me know if more inputs required.
Thanks,
~KKT~

Failed to retrieve SSIS package

Hi , When I would like to browse the package in MSDB, it failed.
And also can't import Package

See if this helps
https://msdn.microsoft.com/en-us/library/ms137789.aspx
also check this
http://vasudevtroubleshooting.blogspot.ae/2009/09/sql-server-specified-in-ssis-service.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

An incorrect email address I put in the BCC field has repeated itself infinitely and blocked outgoing messages. I can select but not delete the long list from the Warning. What can I do?

I put an incorrect email address in the BCC field of an email. A 'Warning' dropped down where the address was repeated until it fell off the bottom of the screen. No closure button at the top so I can't close it. I can select all the repeat addresses but can't delete them. I can't shut down or restart the computer because Mail can't close. Any ideas, please?

Aha! Pressed escape button and managed finally to close the Warning. Phew! I could then erase several hundred repeats of the mistaken address from the BCC field. Sorry to bother you all. Hellen.

Distribution Point Configuration Status - Warning - Failed to retrieve the package list on the DP.

Similar Messages

Maybe you are looking for