Failed to Update Distribution Point

I have an interesting issue with distribution point updating a deployment package. I have ADRs that run for AV definition updates. The rules run, add to an existing deployment package and update distribution points. This works great for
about a month at a time. After that, I have to delete the package and recreate it. I can try to update DPs, use Powershell to update, remove all DPs and add them again as if it were a new distribution, but none of those work. Does anyone
else experience this or have seen it in the past? The error I'm getting is the 80070003 in Package Transfer Manager. Note, this happens every 4-5 weeks and I've experienced it now for the 3rd time. Thanks in advance.
Best, Jacob I'm a PC.

0x80070003 = "The system cannot find the path specified."
Make sure your deployment package where you download definitions is configured properly and accessible.
Is the source folder of the package on shared storage or saved locally on SCCM server?
What release of CM12 are you on?
I would also recommend looking at A/V exclusions for SCCM server:
http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx
http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012

Similar Messages

SCCM 2012 R2 Pull DP fails, works on Update Distribution Points

I'm seeing some odd behavior out of a DP, in particular around driver packages. The system is running SCCM 2012 R2. When I create the driver package I deploy it to the DP on the Primary Site Server. That usually happens in a couple of minutes or less.
I then deploy to a remote DP configured for Pull. This generates the log entries below in the PullDP.log. Even waiting hours doesn't seem to help. If I do a Update Distribution Points for the package, it runs successfully. I know
there was something similar fixed in SP1 CU3.
Intializing DP Monitoring Manager... PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting site code PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting DP Cert Type PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting this DP NALPath PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report state message 0x00000004 to MP PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report Body: <ReportBody><StateMessage MessageTime="20140322004854.000000+000" SerialNumber="1"><Topic ID="ACC0006D" Type="902" IDType="0"/><State ID="4" Criticality="0"/><UserParameters
Flags="0" Count="3"><Param>ACC0006D</Param><Param>["Display=\\DP.xxxxx.xxx\"]MSWNET:["SMS_SITE=ACC"]\\DP.xxxxx.xxx\</Param><Param>{B187E44B-4BF3-4748-B437-AFF29D679AA3}</Param></UserParameters></StateMessage></ReportBody>
PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
CPullDPResponse::ReportPackageState return value 0x00000000. PullDP 3/21/2014 8:48:55 PM 3564 (0x0DEC)
Start Download package ACC0006D version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
Start Download package ACC00070 version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
ExecuteJob (1-NotStarted) 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Cannot find FileInfo (\\?\E:\SMS_DP$\ACC00070\9A25E477-3C0C-499E-A0C1-65243BDBCBF0.tar), content download failed PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
CPullDPPkgContJob::ExecuteJob() failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
State at failure: NotStarted PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Content job 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Package job has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Bob

We ended up changing the DP back to a standard distribution point. That allowed the driver package to distribute successfully. so as a result I can't access the logs any longer.
I should note for anyone who goes searching for this that we had problems with every one of our driver packages. As I dug into it I found the contents, it looked like for some reason that it wasn't being transferred from the download location into
the final DP distribution location. It almost looked like SCCM was ignoring driver package types. I don't know if its a bug or just something quirky about this environment.
We were hoping to use Pull DP to handle our distributions more effectively, but we've backed off on that because of all the issues we've had with it. I hate say it, but it appears to be another SCCM 2012 feature that sounds like a good idea, but the
implementation leaves a lot to be desired.
Bob

Change "Update distribution points on a schedule" in SCCM 2007 via powershell script

Hi
I would like to change the Custom Schedule start time in the "Update distribution points on a schedule" on a package in SCCM 2007 with out logging into the SCCM console.
I have following line code to query the package.
Get-WmiObject
-Namespace
"Root\SMS\Site_$sitecode"
-Query
"SELECT * FROM SMS_PackageBaseclass WHERE PackageID='$PackageID'"
-ComputerName $ServerName
The problem is I only get the "SourceDate" and "LastRefreshedTime" from the query. I am not sure if I change the "LastRefreshTime" that it would change the start time in the Custom Schedule

Hi Jason
I progressed a little bit with you help. I now have the following bit of code.
$Package = Get-WmiObject -class SMS_Package -Namespace "Root\SMS\Site_$sitecode" -Filter "PackageID='$PackageID'" -ComputerName $ServerName
$RefreshPkg = $Package.RefreshSchedule()
$RefreshPkg.RefreshSchedule
I get the following error:
Method invocation failed because [System.Management.ManagementObject] doesn't contain a method named 'RefreshSchedule'.
At line:7 char:1
+ $RefreshPkg = $Package.RefreshSchedule()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (RefreshSchedule:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFound

Difference between "Distribute Content" and "Update Distribution Points"

Hi,
Can someone clarify this for me, I need to redistribute a package to all my distributions points. Should select distribute content and then select the DP's or should I just use the option "Update Distribution Points" to redistribute? TIA

Yes. Once content has been distributed you can not "Distribute Content" again to the same DP. However, you do have another option, go to the properties of the DP, "Content" tab, find the package in question and conduct a re-distribute.
This approach does not increase the versioning of the content whereas "Update Distribution Points" does.
P.S. If you have not read it yet, here is a great
article about content monitoring and validation.
-Tony

Content fails on a distribution point

Hi all,
We have a distribution point located in China that continues to fail receiving content. Can some one guide me the best approach to identify and hopefully resolve this issue ?
Thanks in advance.
Naga Sai Jonnavithula

More info:
Troubleshooting content in Configuration Manager 2012
http://configmgrblog.com/2011/08/17/troubleshooting-content-in-configuration-manager-2012/
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

RBAC: grant rights to update distribution point

Hi,
I have created a specific group which has all rights to manage specific items within SCCM 2012 console.
Everything works fine BUT the distribution of packages to the distribution point, this is empty when distributing the packge.
Rights on Distribution point are: Read, Copy to Distribution Point.
Please advise.
J.
Jan Hoedt

"Site: Read" is most likely missing.
Torsten Meringer | http://www.mssccmfaq.de

Update distribution point errors updating the boot image....SCCM 2012 r2

Fairly new to SCCM (started on it about a month and a half ago and only been troubleshooting different things). As of this moment I'm attempting to get imaging back up, which it looks as if the drivers did not get injected into the boot image properly
before. This seems to be resolved but when I attempt to update the distro point i end up with this error below. Any help is appreciated.
Error: The wizard detected the following problems when updating the boot image.
• Failed to inject a ConfigMgr driver into the mounted WIM file
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4716;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"SMS00005\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;

What version of Configuration Manager are you running, and are you using MDT?
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

Update Distribution Points & Install pending

Hello All,
I created several Packages and tried to deploy them and they sit with install pending in the state field. I also tried updating a Operating System Image and that is also install pending. I have rebooted the server several times with no change.
The distmgr.log keeps freezing, when I restart the log will run for a while but show nothing useful. The sender.log shows no packages. I have tried a lot of the install pending suggestions but no help.
Any ideas? Thanks

Here is Part of what I am seeing:
~IISPortsList in the SCF is "80". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLPortsList in the SCF is "443". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISWebSiteName in the SCF is "". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLState in the SCF is 0. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:12.874 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Virtual Directory SMS_DP_SMSPKGE$ for the physical path E:\SMSPKGE$ already exists.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:14.574 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~As this is an upgrade Virtual Directory SMS_DP_SMSPKGE$ will be updated with new properties.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:14.636 2014 Eastern Daylight Time><thread=9760 (0x2620)>
target processor architecture is x86~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:14.995 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Enabling Anonymous access for virtual directory SMS_DP_SMSPKGE$. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:15.869 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Successfully created the virtual directory SMS_DP_SMSPKGE$ for the physical path E:\SMSPKGE$.~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:16.789 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Successfully added file extension C:\WINDOWS\system32\inetsrv\smsfileisapi.dll. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:17.772 2014 Eastern Daylight Time><thread=9760 (0x2620)>
for ["Display=\\dcs-nhamptn-01\"]MSWNET:["SMS_SITE=BOS"]\\dcs-nhamptn-01\, machine account is to be used~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.064 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISPortsList in the SCF is "80". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLPortsList in the SCF is "443". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISWebSiteName in the SCF is "". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLState in the SCF is 0. $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:21.220 2014 Eastern Daylight Time><thread=9760 (0x2620)>
CWmi::GetObject(): GetObject() failed. - 0x80070003~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.499 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~Setting HTTPUrl to xxxxx/SMS_DP_SMSPKGE$/BOS0003B/ for package BOS0003B on DP
for ["Display=\\dcs-nhamptn-01\"]MSWNET:["SMS_SITE=BOS"]\\dcs-nhamptn-01\, machine account is to be used~ $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.687 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISPortsList in the SCF is "80". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.843 2014 Eastern Daylight Time><thread=9760 (0x2620)>
~IISSSLPortsList in the SCF is "443". $$<SMS_DISTRIBUTION_MANAGER><Fri Apr 25 07:48:22.843 2014 Eastern Daylight Time><thread=9760 (0x2620)>

Distribution Point Installation Fails

I'm trying to install a DP on a new server build using a template that's been used to build all other servers with no issues. However, the DP role fails to install. It has created the SCCMContentLib and SMS_DP$ folders, but not populated them
and trying to force content to the DP fails. All pre-req's around IIS, BITS, .NET are installed and the networking team have verified that all firewall ports required (445 & 135) are open. Windows Firewall is disabled on all servers.
The site server computer accounts are in the local admin group on the DP server and you can browse via UNC to any $ share on the DP server.
When viewing SMS_DISTRIBUTION_MANAGER alerts, I see:
2370 Distribution Manager failed to install distribution point ["Display=\\xxx.xxx.local\"]MSWNET:["SMS_SITE=PR1"]\\xxx.xxx.local\ on computer xxx.xxx.LOCAL. Possible cause: Distribution Manager does not have sufficient rights to the
computer. Solution: Verify that the site server computer account is administrator of the computer.
2391 Distribution manager failed to connect to the distribution point ["Display=\\xxx.xxx.LOCAL\"]MSWNET:["SMS_SITE=PR1"]\\xxx.xxx.LOCAL\. Check your network and firewall settings.
My DISTMGR.log is showing the below:
Failed to get SMS_DistributionPoint object SMS_DISTRIBUTION_MANAGER 02/07/2012 15:27:45 4332 (0x10EC)
CDistributionManager::ConfigurePXE failed; 0x80041002 SMS_DISTRIBUTION_MANAGER 02/07/2012 15:27:45 4332 (0x10EC)
DP monitoring task is disabed on server xxxxxxxxxxxx.xxxxxxx.local SMS_DISTRIBUTION_MANAGER 02/07/2012 15:27:45 4332 (0x10EC)
Failed to delete DP health monitoring task on uxxxxxxxxxxxx.xxxxxxx.local. error = 0x80041002 SMS_DISTRIBUTION_MANAGER 02/07/2012 15:27:45 4332 (0x10EC)
No need to initialize monitoring task on xxxxxxxxxxxx.xxxxxxx.local SMS_DISTRIBUTION_MANAGER 02/07/2012 15:27:46 4332 (0x10EC)
DP settings have been updated to xxxxxxxxxxxx.xxxxxxx.local. SMS_DISTRIBUTION_MANAGER 02/07/2012 15:27:47 4332 (0x10EC)
Sleep 1808 seconds... SMS_DISTRIBUTION_MANAGER 02/07/2012 15:27:47 4332 (0x10EC)
File '\\xxxxxxxxxxxx.xxxxxxx.local\SMS_DP$\sms\bin\smsdp.dll' is signed and trusted. SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:00 2484 (0x09B4)
File '\\xxxxxxxxxxxx.xxxxxxx.local\SMS_DP$\sms\bin\smsdp.dll' is signed with MS root cert. SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:00 2484 (0x09B4)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x80070005 SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484 (0x09B4)
Translated server name xxxxxxxxxxxx.xxxxxxx.local to xxxxxxxx.local\xxxxxxxxxxx.xxxxxxxxx.local. SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484 (0x09B4)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484 (0x09B4)
CWmi::Connect() failed to connect to
\\xxxxxxxxxxxx.xxxxxxx.local\root\CIMv2. Error = 0x800706BA SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484 (0x09B4)
STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SITESERVERNAME.DOMAIN.local SITE=PR1 PID=1476 TID=2484 GMTDATE=Mon Jul 02 14:28:02.760 2012 ISTR0="["Display=\\xxxxxxxxxxxx.xxxxxxx.local\"]MSWNET:["SMS_SITE=PR1"]\\xxxxxxxxxxxx.xxxxxxx.local\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\xxxxxxxxxxxx.xxxxxxx.local\"]MSWNET:["SMS_SITE=PR1"]\\xxxxxxxxxxxx.xxxxxxx.local\" SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484
(0x09B4)
DPConnection::ConnectWMI() - Failed to connect to Uxxxxxxxxxxxx.xxxxxxx.local. SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484 (0x09B4)
Failed to install DP files on the remote DP. Error code = 1722 SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484 (0x09B4)
STATMSG: ID=2370 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=USITESERVERNAME.DOMAIN.local SITE=PR1 PID=1476 TID=2484 GMTDATE=Mon Jul 02 14:28:02.779 2012 ISTR0="["Display=\\xxxxxxxxxxxx.xxxxxxx.local\"]MSWNET:["SMS_SITE=PR1"]\\xxxxxxxxxxxx.xxxxxxx.local\"
ISTR1="xxxxxxxxxxxx.xxxxxxx.local" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\xxxxxxxxxxxx.xxxxxxx.local\"]MSWNET:["SMS_SITE=PR1"]\\xxxxxxxxxxxx.xxxxxxx.local\" SMS_DISTRIBUTION_MANAGER 02/07/2012
15:28:02 2484 (0x09B4)
Will try again after 20 minutes ... SMS_DISTRIBUTION_MANAGER 02/07/2012 15:28:02 2484 (0x09B4)
I've removed the role and re-installed multiple times but each time with the same result. Any ideas what to try next?

Sorry, missed that. Based on the log snippet, the access denied is on WMI though so you need to verify that and you need to verify that the computer account has permissions so you should test as that account (easily done with psexec:
http://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/)
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Recovery Distribution Point

Hi All
I am busy with creating a recovery plan for our SCCM 2012 related servers
I have a question according to the recovery of a Distribution Point
Is it possible to do a full server recovery in case of a mayor issue (failed) of a server with the role distribution point (and is it supported).
If it is not supported (or possible) what is the best way of removing de failed distribution point from the SCCM environment
Step 1 : Remove failed Distribution Point from Boundary Group
Step 2 : Remove failed Distribution Point from Distribution Point Group
Step 3: How to remove the entries of the failed Distribution Point from the SCCM Console (SCCM environment) , I think the failed Distribution Point cannot be removed from the Console (Remove Rol Distribution Point will not work anymore I think).
I hope someone can help me with completing the steps
Regards,
Johan

A full server backup and restore of a DP site system would be OK, but you would need to ensure that you either have content validation enabled or you re-distribute any changed content to that restored DP.
You can simply delete a failed (server down) distribution point site system, rather than trying to remove the distribution point role. You would need to re-provision that site system and re-send all of the content.
My Personal Blog: http://madluka.wordpress.com

Unable to update distribution server

Hi All
Please help me if anyone resolved the issue before
After installing ( ZESM_41_IR1 ) server SSI and the Management Console in the Windows Server 2003 Enterprise Edition. I run the Management Console and am prompted with the Directory Service Configuration Wizard. I put in all the credentials and then receive
" Failed to update Distribution Server "
I do not see any log files on the server.

nacetech,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Troubleshoot Distribution Point Updates Failing

What are the best logs to look at for determining problems with
distribution points? We have 5 DPs. 2 of the DPs are failing to get
distributed content. Both of these systems are remote sites so it could
be due to network latency, but I need some logs to help narrow this
down.
I am watching the distmgr.log. I see the following entry showing its
retrying. The only other red messages are related to a DP that is
currently offline at the moment. Two of my DPs updated successfully.
The other two keep showing as Failed to distribute content.
Failed to process package BR100013 after 12 retries, will retry 88
more times SMS_DISTRIBUTION_MANAGER 5/14/2014 2:23:08 PM 2904
(0x0B58)

distmgr.log + pkgxfermgr.log
Torsten Meringer | http://www.mssccmfaq.de

Client update not working due to distribution point

Since upgrading from 2012-SP1-R2 i haven't been able to upgrade the clients, im fairly sure now after a fair amount of research this is down to the distribution point. I would assume that if there was an issue with the distribution point the update wouldn't
be sent to the clients.

Im fairly sure i have the automatic updated all done, via the Hierarchy settings. Its only when i went to distribute content on one of my packages i realised that the issue might be with the MP/DP as i get "failed to distribute content details will
be available after server finishes processing"
In distmgr.log i get "package ****00002 does not have a preferred sender.
Used 0 out of 3 allow processing threads
In smsdpmon.log There is nothing for months which was my next check.

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

New Site Server with Distribution Point & Software Update Point Roles not pulling SUGs

I just set up a new server & installed the DP & SUP roles on it. I am getting the following in the log this is just a small sample as its kind of repetative:
Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Retry 10 times SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Start to evaluate all packages ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Start to evaluate package 'FPP00002' version 0 ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x4000094C to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Failed to evaluate package FPP00002, Error code 0x80070002 SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Report status message 0x40000952 to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
DP monitoring finishes evaluation. SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
Failed to evaluate some packages after 10 retry SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
The Console shows for the DP that it's waiting for content and I don't see where I can create a Prestage Package
# When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

D:\SMS_DP$\sms\logs\smsdpmon.log
This is the 2nd server in our SCCM 2012 Sp1 Hierarchy. It is set up with the following Site System Roles:
Component Server
Distribution Point
Site System
Software Update Point
It is Prestaged Enabled. My intent is that the client systems @ the location where this DP is located will use it to pull their Microsoft Updates from as well as content for any Applications we push to them rather than going over the WAN to the Primary
Site Server.
IN Distribution Point Configuration Status. the console shows "Failed to update package" & "Packaget Transfer Manager failed to update the package "yxz00040". Version 3 on Distribution Point server.my.domain.com review pkgxfermgr.log for more information
about this failure."
It also goes on toe list 2 possible causes and solutions
Site servers does not have sufficient rights to the source directory.
(Site server account is a member of local Administrators on Primary)
Not enough disk space available
(I have over 1TB of available space and primary site server has only 150GB available for entire content repository, both applications and sofware updates.)
# When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

Failed to Update Distribution Point

Similar Messages

Maybe you are looking for