SOLVED CContentDefinition TotalFileSizes failed Error 0x80070003

[Paul Johnson]

Hello
I've recently installed our SCCM 2012 R2 Site with the DP role on a separate server to the Site Server and the Central Content Library has ended up on the same drive as the main SCCM program folder - so disk space is disappearing fast.

Is it possible to move the Central / Site Content Library to it's own drive using the Content Library Transfer tool without causing any problems or is it best to delete the DP role, then delete the Content Library folders from the Site Server. Then re-install the DP role using the no_sms file on the Site Server to control where the Central Content Library is placed.

 

[Prajwal Desai]

You could try using Content Library Transfer tool in your case. I am not sure what amount of content do you have in the content library, so deleting DP role is something I cannot suggest at this point of time.

Please read some important things before you use the CTT.

1. The tool must run locally on the distribution point, it cannot be run from a remote machine.

2. The tool must run only when the distribution point is not actively being accessed by client computers. If the tool is run while client computers are accessing the content, the content library on the destination drive may have incomplete data or the data transfer might fail altogether leading to an unusable content library.

3. The tool must only run when no content is being distributed to the distribution point. If the tool is run while content is being written to the distribution point, the content library on the destination drive may have incomplete data or the data transfer might fail altogether leading to an unusable content library.

 

[Paul Johnson]

Hi Prajwal, thanks for your reply.

I have very little content on the DP's as we haven't gone live yet.

I've seen these CTT conditions before and it's the first one that concerns me as it says that the tool must run on the Distribution Point and our Site Server doesn't have that role.

 

[Prajwal Desai]

Oh you are correct. If you have little content, go ahead with Plan B

 

[Paul Johnson]

Thanks. If I go for Plan B the only Package that is left on the DP is the Configuration Manager Client Package and I'm unable to remove it from the DP, I guess because it is a System / Built-in Package. Will I be able to re-distribute it when the new DP's are setup?

 

[Prajwal Desai]

Will I be able to re-distribute it when the new DP's are setup? - Yes you should be able to do that.

 

[Paul Johnson]

Thanks for your help

 

[Prajwal Desai]

@Paul Johnson - Let me know how it goes.

 

[Paul Johnson]

@Paul Johnson - Let me know how it goes.

Hello, I've managed to re-create the DP's and get the Content Library in the location that I want it to be. However, I'm now left with one problem regarding the system generated Configuration Manager Client Upgrade Package which won't re-distribute to any of the DP's. I've tried setting up a Client Upgrade package manually using the Microsoft Configuration Manager\ClientUpgrade\ccmsetup.exe file as the source and that works fine. The error I'm getting with the system generated package in the PkgXferMgr.log

CContentDefinition::TotalFileSizes failed; 0x80070003
CSendFileAction::SendFiles failed; 0x80070003
CSendFileAction::SendContent failed; 0x80070003

which appears to be either it can't find the source or permissions (Everyone has access to the above folder including the SCCMSiteServer machine account). I've tried PowerShell to re-distribute the package and placing client.acu in the HMAN Inbox folder but neither work.

Have you got any other ideas and is it possible to see the soruce folder for the package if it doesn't appear in the SCCM Console?

Thanks in advance.

 

[Prajwal Desai]

Okay, could you try the below steps -
1) Open an empty notepad and save it as client.acu
2) Copy the client.acu to the inboxes\hman.box folder at the top-level site.
3) Monitor the hman.log to check whether the Client Upgrade package gets updated.

 

[Paul Johnson]

Hello, thanks for getting back to me.

I've previously tried the Client.acu trick but have done it again this morning and it doesn't look to have worked. In content status the package compliance on the DP's is 0%. However, hman.log says it has successfully added the package to all DP's and it looks to have been saying the same thing for a while. An extract from the log is


INFO: Successfully added client package (ID=DON00003) to all DPs (count 2) SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)INFO: Successfully added client package (ID=DON00002) to all DPs (count 2) SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)INFO: All client auto upgrade related objects exists. No objects are to be created. SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)INFO: Staging client folder doesn't exist. SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)INFO: Client upgrade program advertisement (ID=DON20000) exists. SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)INFO: Client upgrade program exists and its currently disabled. SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)INFO: Detected the client upgrade package (ID=DON00003) with upgrade package flag 1 SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)INFO: Detected the full client package (ID=DON00002) SMS_HIERARCHY_MANAGER 27/01/2016 02:34:41 2536 (0x09E8)

and after Client.acu it says

INFO: Client upgrade package content hasn't been changed. Skip updating. SMS_HIERARCHY_MANAGER 27/01/2016 09:21:41 2536 (0x09E8)Creating hash for algorithm 32780 SMS_HIERARCHY_MANAGER 27/01/2016 09:21:40 2536 (0x09E8)INFO: Full client package content hasn't been changed. Skip updating. SMS_HIERARCHY_MANAGER 27/01/2016 09:21:40 2536 (0x09E8)Creating hash for algorithm 32780 SMS_HIERARCHY_MANAGER 27/01/2016 09:21:34 2536 (0x09E8)INFO: Current client upgrade settings are: FullClientPackageID=DON00002, StagingClientPackageID=(null), ClientUpgradePackageID=DON00003, ClientUpgradeAdvertisementID=DON20000, ClientPilotingAdvertisementID=(null), ClientUpgradeVersion=5.00.8239.1000. SMS_HIERARCHY_MANAGER 27/01/2016 09:21:34 2536 (0x09E8)INFO: client.acu file was found. client upgrade packages need to be updated. SMS_HIERARCHY_MANAGER 27/01/2016 09:21:34 2536 (0x09E8)

Just wondering if I deleted too much when I got rid of the old content libraries. For example I can't find a TAR file for this package.

 

[Paul Johnson]

Just trying an SCCM 1511 Upgrade to see if that will re-create the package.

 

[Paul Johnson]

Just trying an SCCM 1511 Upgrade to see if that will re-create the package.

Hello
The 1511 upgrade sorted out the problem with the Client Upgrade Package.

Thanks

 

[Prajwal Desai]

That's great. I am marking this thread as Solved. This will surely help a lot of people.