I had a similar issue at a customer and they had a MS case open for 5 weeks on 
it with no resolution. I ended up just rebuilding their environment because 
they did not have the time for MS to resolve and it was a fairly new 
implementation with a primary and 2 DPs.

For troubleshooting, are you able to set up a new test DP and distribute a new 
package (in other words, is the problem isolated to the 4 DPs). You will want 
to attempt to isolate a patch issue, network issue, configuration issue with 
the existing DP's vs. your new test DP.

If I remember, I think there are 5 logs to monitor when you transfer, however, 
I found none of them to capture/report enough information as to why a failure 
occurred. You can ping me if you want and bounce some stuff off me to see if 
that helps.


Jason Condo | Bennett Adelson<http://www.bennettadelson.com/> | Cleveland Region
Principal Consultant - Systems Management & Operations
(M) 234.380.9214

From: [email protected] [mailto:[email protected]] On 
Behalf Of Carr, Robert
Sent: Thursday, June 13, 2013 10:11 AM
To: [email protected]
Subject: Re: [mssms] RE: Issue sending or receiving packages to DPs

Ah. Ha. One of the other Admins used the move content library tool. I reversed 
the process but still getting same error.

On Jun 13, 2013, at 9:13, "Carr, Robert" <[email protected]<mailto:[email protected]>> 
wrote:
I can't even create new packages, same errors.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Daniel Ratliff
Sent: Wednesday, June 12, 2013 17:24
To: '[email protected]<mailto:[email protected]>'; 
'[email protected]<mailto:[email protected]>'
Subject: RE: [mssms] RE: Issue sending or receiving packages to DPs

What about the content source? It share a location that could have had 
permissions or something change for all 4 packages?

-----Original Message-----
From: Carr, Robert [[email protected]<mailto:[email protected]>]
Sent: Wednesday, June 12, 2013 04:35 PM Eastern Standard Time
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Issue sending or receiving packages to DPs



Not to my knowledge. I replaced all permissions on the share to be sure (trust 
me, I've been looking all over for a solution). There was a NO_SMS_ON_Drive, 
and I removed it, yesterday evening.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Bruce Hethcote
Sent: Wednesday, June 12, 2013 16:25
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Issue sending or receiving packages to DPs

Did anything change as far as drive configuration where your package source is 
located?  Is there a NO_SMS_ON_DRIVE.SMS file anywhere it shouldn't be?

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Carr, Robert
Sent: Wednesday, June 12, 2013 3:17 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Issue sending or receiving packages to DPs

Guys,

Having an issue sending packages to my 4 DPs. These were all working fine the 
other day, don't know what occurred. Regardless, when I try to update the dist 
points, I get the entries below in PkgXferMgr.log. I've torn down one DP 
completely, and rebuilt it, readded it to the site, no improvement there. I'm 
believing there is an issue sending files to the DPs, rather than the DPs 
trying to copy it.

CContentDefinition::GetFileProperties failed; 0x80070003            
SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 16:07:00               724 (0x02D4)
CContentDefinition::TotalFileSizes failed; 0x80070003     
SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 16:07:00                724 (0x02D4)
Redistribute=0, Related=             SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 
16:07:00          724 (0x02D4)
CSendFileAction::SendFiles failed; 0x80070003   SMS_PACKAGE_TRANSFER_MANAGER 
6/12/2013 16:07:00          724 (0x02D4)
CSendFileAction::SendFiles failed; 0x80070003   SMS_PACKAGE_TRANSFER_MANAGER 
6/12/2013 16:07:00          724 (0x02D4)
Notifying pkgXferJobMgr             SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 
16:07:00          724 (0x02D4)
Sending failed. Failure count = 3, Restart time = 6/12/2013 4:37:00 PM Eastern 
Daylight Time                SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 16:07:00    
      724 (0x02D4)
Sending legacy content XXX00097.7 for package UKY00097           
SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 16:07:00               5556 (0x15B4)
CContentDefinition::GetFileProperties failed; 0x80070003            
SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 16:07:00               5556 (0x15B4)
CContentDefinition::TotalFileSizes failed; 0x80070003     
SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 16:07:00                5556 (0x15B4)
Redistribute=0, Related=             SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 
16:07:00          5556 (0x15B4)
CSendFileAction::SendFiles failed; 0x80070003   SMS_PACKAGE_TRANSFER_MANAGER 
6/12/2013 16:07:00          5556 (0x15B4)
CSendFileAction::SendFiles failed; 0x80070003   SMS_PACKAGE_TRANSFER_MANAGER 
6/12/2013 16:07:00          5556 (0x15B4)
Notifying pkgXferJobMgr             SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 
16:07:00          5556 (0x15B4)
Sending failed. Failure count = 3, Restart time = 6/12/2013 4:37:00 PM Eastern 
Daylight Time                SMS_PACKAGE_TRANSFER_MANAGER 6/12/2013 16:07:00    
      5556 (0x15B4)





________________________________


DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of 
this email address. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.



The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.





Reply via email to