Jump to content


vincelewin

Update deployment package will not distribute to 1 of my 7 DPs

Recommended Posts

Hi All,

 

I have a strange issue with this package on one DP. The status under monitoring is "The content files for package COR00129 have not yet arrived from the source site site COR. Distribution manager will try again later to distribute the content.

 

It stays like this and never changes. Its been at least 5 days since I first distributed it. I have tried removing it from this DP in the properties of the package and then distributing it again to this DP, I've tried "Redistributing" from the properties and also "Validating" but it just gets to the same message.

 

The distmgr.log shows

 

post-19661-0-59877100-1456216325.png

 

post-19661-0-29666100-1456216409.png

 

We are running 2012 R2 SP1 5.00.8239.1000

 

I have 1 parent site and 6 secondary sites. As you can see the package distributed to 6 of the 7 fine but it wont go onto this last one.

 

I can attach any logs you require please just ask.

 

Any help would be gratefully received.

 

Vince

Share this post


Link to post
Share on other sites


A couple more screen shots.

 

These are the drives on the DP that is failing.

post-19661-0-68413400-1456217012.png

 

This shows the size of the package from the Content view under Monitor.

post-19661-0-80291200-1456217012.png

Share this post


Link to post
Share on other sites

Hello,

I am facing the same issue on 3 of our 9 secondary sites

The problem, about 300 dp's depends of those 3 secondary sites for about 500 packages.

I have made Update distribution point for one, and was the solution. But i cant do that for all stucking packages. Any suggestion or solution is wellcome

Also running 2012 R2 SP1 5.00.8239.1000

gvlaarho

Share this post


Link to post
Share on other sites

Are you able to get other content to this DP?

 

Would suggest ensuring firewall rules are open between site server and DP, also check out pkgxfermgr.log and distmgr.log on your primary for the package sending to that DP, see if anything is listed relating to that specific DP in these logs. Sender.log may also hold some clues

Share this post


Link to post
Share on other sites

Hello,

I am facing the same issue on 3 of our 9 secondary sites

The problem, about 300 dp's depends of those 3 secondary sites for about 500 packages.

I have made Update distribution point for one, and was the solution. But i cant do that for all stucking packages. Any suggestion or solution is wellcome

Also running 2012 R2 SP1 5.00.8239.1000

gvlaarho

Is your site Database replication working as expected? no degraded links under Monitoring > Database replication?

Share this post


Link to post
Share on other sites

Are you able to get other content to this DP?

 

Would suggest ensuring firewall rules are open between site server and DP, also check out pkgxfermgr.log and distmgr.log on your primary for the package sending to that DP, see if anything is listed relating to that specific DP in these logs. Sender.log may also hold some clues

Hi Apexes,

 

Yes I can get other content onto this DP, only yesterday I distributed new win 10 boot images successfully.

 

None of the logs help me. I can see the sender.log says "Finished sending SWD package COR00129 version 2 to site THE" but that was on the 23/02/2016 at 08:22am no mention of that package since.

Pkgxfermgr.log just shows multiple waiting for new/rescheduled send requests.

Distmgr.log has this as its last entry relating to this package "Exiting package processing thread for package COR00129." on the 23/02/2016 at 08:20am

 

I've attached below.

 

Everything looks fine from the logs.

PkgXferMgr.log

sender.log

distmgr.log

Share this post


Link to post
Share on other sites

I've had similar before, try this, it may or may not work.

 

1. Remove the content from the DP in configmgr console, give it 10-15 minutes to reflect as showing as removed

2. Log onto your affected site DP and go into your SMS source location drive, and into SCCMContentLib

3. In this folder go into PkgLib, find any .ini file references to your package ID COR00129 and delete them (There may be some with hex codes appended too)

4. Go back up a folder into DataLib, again - delete any folder with the title of COR00129 in

5. Re-add the content in ConfigMgr console and monitor the distribution

Share this post


Link to post
Share on other sites

Hi all,

Thanks for your replies.

So

yes DB Replication are OK

Firewall rules are ok because only some packages are stucking and radomly

I try your topics Apexes and working !

Thanks

Gvlaarho

Share this post


Link to post
Share on other sites

I've had similar before, try this, it may or may not work.

 

1. Remove the content from the DP in configmgr console, give it 10-15 minutes to reflect as showing as removed

2. Log onto your affected site DP and go into your SMS source location drive, and into SCCMContentLib

3. In this folder go into PkgLib, find any .ini file references to your package ID COR00129 and delete them (There may be some with hex codes appended too)

4. Go back up a folder into DataLib, again - delete any folder with the title of COR00129 in

5. Re-add the content in ConfigMgr console and monitor the distribution

Hi Apexes,

 

I followed your instructions at 08:10 this morning and waited until 09:08 when I re-distributed the content.

 

Ive left it all day and its still showing the message "The content files for COR00129 have not yet arrived from the source site COR.

 

:(

Share this post


Link to post
Share on other sites

Hi Apexes,

 

I followed your instructions at 08:10 this morning and waited until 09:08 when I re-distributed the content.

 

Ive left it all day and its still showing the message "The content files for COR00129 have not yet arrived from the source site COR.

 

:(

Odd - the only thing i can think that'd spawn a similar message would be if enable pull distribution point was set on the DP to look elsewhere for it's content source, but that being said other content works fine so i'm at a loss :|

 

Maybe create a whole new package for the content you need and send that out to all DP's to use instead?

Share this post


Link to post
Share on other sites

Hello all,

So unfortunatly it's because the large amount of packages that are distributing at the same time ....

The only thing we have, wait ....

Is there a way to force all Primaries and secondaries to receive first sources when a new package is implemented ? (tool or ...)

Apart the way to distribute first on all Primaries, wait until success then second to all secondaries, wait until success then global DP's

Nice day all

Gvlaarho

Share this post


Link to post
Share on other sites

Ok I removed the package from all DPs and deleted the deployment group, then I navigated to the deployment groups folder on the servers virtual hard drive and deleted the contents.

 

Then I re-created the deployment group and navigated to the updates view and viewed the members, then I re-downloaded them all.

 

I have witnessed the files be re-created in the empty original folder and I have now re-deployed to all DPs.

 

It has failed again on the one DP as before.

 

Does anyone else have any ideas I am ready to throw sccm into the canal.

 

:(

Share this post


Link to post
Share on other sites

This is the second time I have re created the package now.

 

Just getting the same errors with each one on this DP.

 

0x80070002

error code = 2

error code = 8

despool.log

Share this post


Link to post
Share on other sites

Error code 8 is not enough space from what I've looked up, but that'd contradict your previous screenshot of the disk space on the drives, and the fact that you can distribute other content to the server.

 

Sorry if it sounds like i'm teaching to suck eggs - but that server definitely has enough space on it's host drives when you log on to it?

 

I'm at a loss as to where i'd even go now if i was having this problem, from your descriptions i've managed to fix similar issues to this by getting shot of the .ini and content files in the SCCMDataLib, but you've tried that and still nothing.

 

Short of removing the DP role, and re-installing and sending content again - i'm not sure where you'd go from that.

Share this post


Link to post
Share on other sites

How much space is enough space?

 

Isn't there a setting which configures the amount of usable or free space on a disk?

 

post-19661-0-25187800-1457425279.png

Share this post


Link to post
Share on other sites

Ok so this morning I have removed the Distribution Point (DP) from the secondary site server left it half an hour and re-installed the role.

 

I got rid of the problematic deployment package (DPG) and added the patches from it to other previously working DPG's.

 

I then added the DP to the DP group and watched it sync all the packages, except one!

 

I still have one package that will not go over but it is a different, previously sync'd package.

 

I have noticed that on the Parent server I can see error 3 in the SMSDBMON, attached and error 8 on the secondary site servers DP DESPOOL log.

 

Anyone have any ideas?

 

 

smsdbmon.log

despool.log

post-19661-0-61689600-1457440639.png

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...