Content files for package have not yet arrived

Is there a way to tell if progress is being made on a large package deployment to remote DPs? I have a large package ( 11 GB) that has been successfully sent to 4 DPs, but one still lingers with " Content files for package have not yet arrived". I don't know if I need to restart it, or if progress is being made.  The last status update was two days ago. 

I downloaded the Toolkit for 2012 R2, but the DP Job manager tool will only see a DP in the same site as the primary, and in this particular case, the DP belongs to a secondary site. 

I see no In process sending SWD package messages to this DP in sender.log   Anything related to this must have been overwritten already. 

Should I just cancel it and send it again do you think? 

February 26th, 2015 9:51am

distmgr.log and pkgxfermgr.log would be useful to get some information about the content distribution.

Jeff

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 10:15am

The sender.log is for site server to site server traffic. If it is showing idle, then that means the package has been transferred to the secondary site server itself. To checked site server to DP traffic, you need to check pkgxfermgr.log on the secondary site server.
February 26th, 2015 10:31am

The DP that I am trying to send to is a secondary site in this case.  

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 1:45pm

Honestly, that doesn't make sense.

A DP is a role. It can be on the site server (which is what I presume that you actually mean) or on a remote site system. In the case of the DP role being installed on the site server, then the content is still delivered from the parent site server to the secondary site server. However, because the DP role on the site server shares the same content library with the site server itself, nothing more needs to be done file transfer wise for the DP to "have" the content.

February 26th, 2015 1:58pm

Then what do you see in pkgxfermgr.log on the secondary site server?

Jeff

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 1:59pm

Yes, the DP in this case is a role on a secondary site sever. That is what I meant, sorry if that was not clear. The pkgxfermgr log shows a failed transfer to a remote DP in this site for that package. Which makes sense since it cannot be expected to send it if it doesn't have it yet. ( I had assumed delivery when I tried to push the package to the non site server DP in that site).   But for the original attempt to push the package to the secondary site server, I cannot find anything in the logs.  I think it has been overwritten.
February 26th, 2015 2:21pm

Could be. As mentioned though pkgxfermgr.log has nothing to do with site server to site server content transfer. You need to check distmgr.log and sender.log on the parent site server for that.
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 2:30pm

I see this on the 24th in the distmgr.lo_ 

Package CHR00019 is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 2/24/2015 1:56:07 PM 25252 (0x62A4)

And the no mention of it in the current distmgr.log   The sender log shows no mention of it for that site. I can see it going to another secondary site, but not the one in question. Bot the lo_ and the sender.log only have entries from today though.


  • Edited by dpmaker 16 hours 34 minutes ago
February 26th, 2015 2:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics