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

Similar Messages

Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
point and failed to connect to remote distribution point"
Errors on the package transfer log file.
CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
Failed to connect to the DP WMI namespace on the remote DP

Thanks Sandys for your suggestions.
i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
server is unavailable" from both ends.
error:0x800706ba - The RPC server is unavailable

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

SCCM 2012 distribution point install failes with faild to verify disk drive

I am trying to install remote distribution point on new Windows Server 2012 standard but getting failures. here is the code:
Failed to find a valid drive on the distribution point
Failed to install DP files on the remote DP. Error code = 15
I can created files and folder manually on the server fine on the drive specified during the deployment wizard. I need to know what process SCCM 2012 goes through to verify a disk drive for usage as a remote distribution point

Hi,
Did you ever get this fixed?
In my case, it's a physical server with a 2x 500GB in RAID1.
Server OS is 2012. SCCM Version is 2012 SP1 cu2
The disk has been partitioned into 2 logical drives: C-Drive and D-drive
The distmgr.log states:
failed to find a valid drive on the Distribution Point
Failed to install DP Files on the remote DP. Error Code = 15
Drive D: is not valid. Error = 15
Do you have any ideas of how SCCM evaluates drives to be correct?
I've ran a WMI Query and the partition shows as a Local Hard Disk.
Do you have any more ideas what I can check?
Thanks!
Filip

Distribution Point creation failed. possible cause : distribution manager does not have the sufficient access right to the computer

Hi All,
I had this really disturbing experience with
SCCM 2012 SP1.
OD : 2008r2 Enterprise 64bit
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.
in Distmgr.log says :
DPConnection::Disconnect: Revert to self
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.xxx\, logged-on as ssm\sccmadmin
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.x\, logged-on as ssm\sccmadmin
SMS_DISTRIBUxxx ON_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
Failed to find a valid drive on the distribution point ["Display=\\PNGBRANCHSERVER.xxx"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.myx
DPConnection::Disconnect: Revert to selfxxx
MS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Disconnect: Revert to self SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
GetContentLibLocation() failed SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to get the content library path on server PNGBRANCHSERVER. SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to install DP files on the remote DP. Error code = 16389
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
STATMSG: ID=2370 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCMSVR. SITE=SSM PID=2660 TID=16280 GMTDATE=Sun May 25 23:34:30.428 2014 ISTR0="["Display=\\PNGBRANCHSERVER.ssm.com.my\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.\"
ISTR1="PNGBRANCHSERVER.S" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\PNGBRANCHSERVER.\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.my\"
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
I have tried many of the solution provided unfortunately nothing positive happened.
Appreciate your input before engaging premier support.
Thank you

Hi，
NO_SMS_ON_DRIVE.SMS
This file is used to prevent Configuration Manager from installing binaries to a volume. By default, when you install System Center 2012 Configuration Manager on a remote Site System, the SMS Site Component Manager Service installs the binaries (files and
folders) for the Site System on the NTFS-formatted volume that contains the most free space. You may want to use an NTFS volume other than the default volume for your remote Site Systems by preventing ConfigMgr from enumerating certain NTFS volumes.
In order to prevent CM from enumerating an NTFS volume, on the remote server you can create a text file that is named NO_SMS_ON_DRIVE.SMS and put the this file on the root folder of all NTFS volumes where you do not want to install the binaries (SMS folder)
for the ConfigMgr components.
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 and failed content

Hi I have SCCM 2012 R2 and 5 Pull DPs now when I distribute Packages to these Pull DPs some times i can see some package didn't distributed and giving me failed content but when I redistribute it i can see the SCCM Start to redistribute the package from
the failed point which is will resume the distribution and to be honest this very coll specifically for big packages but on some packages starting from 0,
to be honest I'm Confused when the SCCM will resume and when will not.
Thanks,
Ahmed Ali

Hi,
There might be many files in a package. I think when one file transfers failed, it starts from the failed file.
I suggest you use BITSAdmin to monitor BITS jobs in the transfer queue.
http://msdn.microsoft.com/en-us/library/aa362813(v=vs.85).aspx
Best Regards,
Joyce
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.

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

Distribution Point Offline - how long before SCCM client connects to alternative DP?

Hi, I'm doing some testing on my SCCM 2012 setup and have been attempting to test distribution point resiliency and fall-back.
I have a single primary site with two distribution points. One is in the main datacentre and is in the same boundary group as the clients and tagged as fast connection. The 2nd DP is in the DR datacentre, in a separate boundary group (no client subnets are
in this group) and the distribution point has the allow failback checked. Both DP's have the same content.
After shutting down/taking offline the main distribution point, I've then kicked of an install of a package on a W7 client. It attempts to download and stays in that state for as long as I leave it. Looking in the logs I can see both DP's returned to
the client (the DR tagged as REMOTE), it then attempts to connect to the main DP and just keeps retrying over and over.
I thought if it couldn't connect to the main DP it would then failback to the DR DP, but it doesn't appear to do this. Is there a timeout on this before it would fail back?
I'm also currently trying adding the DR DP to the main boundary group and tagging the connection as slow so the main DP would still be used first. Again both DP's are returned to the client when installing software and the client attempts to connect
to the main DP over and over without using the DR DP which is online.
Is this normal behaviour or do I have a configuration issue?
Appreciate your help.
Carl

Hi, just to update on this thread, I raised a support call with Microsoft and the end result is that SCCM2012 clients wont fall back to an alternative DP where a DP is offline. The fall back is only for when content isn't on a DP. The 8hr timeout doesn't
appear to be in affect anymore.
What I have managed to get to work and test out is removing our production DP (also primary site server) from the production content boundary group, then clients will fall back to the DR DP as this is the only other DP available with content.
I've managed to perform the update to remove the site server from the boundary group while the primary site server is offline, by using a PowerShell script to connect to the SCCM provider on the DR site server (DP/MP/SUP) to perform the update as our site
database is off-box. This works well and the changes replicate to the SQL replica in DR that the DR MP uses and when clients failover to the DR MP they then begin using the DR DP and packages can be installed etc.
How funny, I just fixed this at a Client this week.
This is default client behavior as MS CSS probably told you, the client thinks the Distribution Point is coming back online soon so it waits, for good reasons. For some reason I keep thinking "7 days" not 8 hours, but maybe wrong.
I have a work around for this, it just requires a change to the Distribution Points DNS record. Head to the DNS server, find the record for the Distribution Point that is down, change the IP address to a different member server IP address, this will cause
the client, when it flushes it's DNS cache, to get an updated DNS record for the Distribution Point and it will try to connect to the Distribution Point using the changed IP address, which then induces what the client thinks is a severe error which makes it
go to the next Distribution Point in the list it got from the Management Point. Once you've recovered the Distribution Point and it is back online, change it's IP address back in DNS or just let the Distribution Point update its own DNS record when it boots
up (if configured to do so) and viola, you are back in business.
Test, test and test again before ever putting something from "the web" into your production environment. I just implemented this at a client to solve their issues with their DR procedure.
Rob Marshall | UK | My Blog |
WMUG |
File CM12 Feedback |
CM12 Docs |
CM12 Release Notes

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

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.

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]

Monitoring and troubleshooting in-place distribution point upgrades

I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?

Hi all
I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
12 hours.
I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
article. There seems to be a bug which is currently in a solving process.
For me, there are two solutions for this problem:
1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
after 3 days.
Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
Kind regards Stefan Somogyi

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

Troubleshoot Distribution Point Updates Failing

Similar Messages

Maybe you are looking for