SCCM Remote Content Library Error 0x80070002

Question

Hello,

I have set up a SCCM remote content library to achive Site Server HA. Everything worked fine, content was moved, 2 sites server working as active/passive mode.

I have added Windows 10 Image, SUGs and got them distributed to other DPs succesfully.

On the past few days, I have been trying to add a Windows 8.1 Application to promote an upgrade to Windows 8 machines and them to Windows 10, since it is not supported going 8 to 10 directly. There was my problems started. Distmgr.log is showing errors related to the W8.1 package as follows:

_wfopen_s() failed for \s-san3-file\ContentFolder\SCCMContentLib\DataLib\Content_243e822e-e7b5-42c7-ac0e-c8e129c72d45.1\sources\sxs\amd64_microsoft-windows-n..5linqcomp.resources_31bf3856ad364e35_6.3.9600.16384_pt-br_aa90556ed5ecdaea\microsoft.build.conversion.v3.5.resources.dll.INI with error 2 SMS_DISTRIBUTION_MANAGER 14/12/2022 13:48:31 9700 (0x25E4)
GetPrivateProfileStringW failed for File, Hash, \s-san3-file\ContentFolder\SCCMContentLib\DataLib\Content_243e822e-e7b5-42c7-ac0e-c8e129c72d45.1\sources\sxs\amd64_microsoft-windows-n..5linqcomp.resources_31bf3856ad364e35_6.3.9600.16384_pt-br_aa90556ed5ecdaea\microsoft.build.conversion.v3.5.resources.dll.INI SMS_DISTRIBUTION_MANAGER 14/12/2022 13:48:31 9700 (0x25E4)
ProfileReadStringEx failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 14/12/2022 13:48:31 9700 (0x25E4)
CContentDefinition::GetFileTrueName failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 14/12/2022 13:48:31 9700 (0x25E4)
CContentDefinition::OpenFile failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 14/12/2022 13:48:31 9700 (0x25E4)
CContentDefinition::HashContent failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 14/12/2022 13:48:31 9700 (0x25E4)

My first thought was corrupted ISO file, tried another one and the same error appeared. Doing some internet research I found people reporting that it could be a problem related to the directory/file name length may exceed 255 character limit and the 8DOT3NAMES should be enabled on the volume.

In the article Configure a remote content library for the site server Microsoft does not mention anything about that.

My questions: Has anybody faced this problem? Is it related to file name lenght? Does the 8DOT3NAMES must be enabled to prevent such errors?

Thanks!

Thiago

Answer 1

Hi @Thiago B Andrade ,

> since it is not supported going 8 to 10 directly.

1, About “not supported going 8 to 10 directly”, Are you getting any errors other than logs? Could you please upload a screenshot for our reference?

> I have been trying to add a Windows 8.1 Application to promote an upgrade to Windows 8 machines and them to Windows 10,

2, Did you implement it by deploying the task sequence? Did the client receive the content or is the server deployed successfully?

3, What version of SCCM and ADK are you using? Which version of Windows 10 are you ready to deploy? In my experience, you can upgrade the OS version from windows 8 to windows 10 directly, but we need to implement it by deploying the task sequence. Besides, the version of SCCM and ADK are supported the windows version of you want upgrade to.
The following links for your reference:
Deploy Windows 7 to Windows 10 with SCCM Task Sequence Upgrade (systemcenterdudes.com)
Perform in-place upgrade to Windows 10 via Configuration Manager - Windows Deployment | Microsoft Learn

Deploy Windows 10 21H1 Upgrade using SCCM / MEMCM (systemcenterdudes.com)
Note: Microsoft provides third-party contact information to help you understand the problem. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

4, About the logs you provided, I found several similar cases for your reference. Besides, I noticed that your directory/filename length is 261 characters.
http://www.freetechanswers.com/2021/06/moving-microsoft-endpoint-configuration.html#google_vignette:~:text=Moving%20the%20Site%20Content%20Library%20to,kofax.com/Capture/Kofax_Capture/Scan/Enable_8dot3_File_Name_Creation

https://happysccm.com/moving-the-content-library-to-remote-share-tips/
https://www.walshamsolutions.com/sccm-1902-package-distribution-error
https://happy3178.rssing.com/chan-36088662/all_p4.html#:~:text=Post%20Move,is%20too%20long
Note: Microsoft provides third-party contact information to help you understand the problem. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Looking forward to your feedback.

Best regards
Cherry

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi Cherry,

Thanks for your response!

About 1,2 e 3:

Accordingly to Microsoft , going from 8 to 10 is not supported. And with that, I have not given a try. Here is the statement : "Windows 8.0: You can't upgrade directly from Windows 8.0 to Windows 10. To upgrade from Windows 8.0, you must first install the Windows 8.1 update."

About 4:

I have consulted these sources, and I am almost sure that this is the problem I am facing right now. What I found frustrating is that Microsoft document about the requisites to move the Content Library to a remote share does not mention any tips or advices about directory/file name length and how to avoid it. So, now we are consulting our storage support to check if it is possible to enable 8DOT3NAMES parameter. Otherwise I will probably have to dismantle the remote Content Library and the Site Server HA feature.

Thanks for your attention!

Thiago

Answer 3

Hi Cherry,

Interesting, I haven't seen that document, my mistake. thanks for it. I am going to deploy a tasks sequence to Windows 8 then and see what happens. Apparently, the upgrade error is related with language mismatch, so the team is provisioning another W8.1 installation for me to test.

But, my concern about the file/directory name length still persists and I am probably revert the remote content library and stop the Site Server Active/Passive node feature.

I will let you know as soon as possible.

thanks for you attention.

Best regards,

Thiago

Answer 4

Hi Cherry,

Just to inform that the upgrade TS from 8 to Windows 10 has worked like a charm.

On another hand, the issue with Remote Content Library still persists. I am still using it, but if we face the character length limit again, I will probably abandon the Active/Passive feature.

Thanks for your support.

Best regards,

Thiago