Close Menu
    Facebook X (Twitter) Instagram
    Sunday, October 12
    X (Twitter) LinkedIn Reddit RSS
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»CM2012»SCCM Configmgr the source directory doesn’t exist or the SMS service cannot access it, Win32 last error = 5

    SCCM Configmgr the source directory doesn’t exist or the SMS service cannot access it, Win32 last error = 5

    Eswar KonetiBy Eswar KonetiNovember 07, 12:33 pm1 Min Read CM2012 15,075 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Setting up new SCCM Configmgr Current Branch 1606 in production environment .As part of it ,have created source folder (repository for content store) and placed couple of packages/applications for testing . while trying to distribute the packages, all failed with same error code.

    The source directory \\servername\sources$\Applications\Microsoft\SCUPCert doesn't exist or the SMS service cannot access it, Win32 last error = 5

    Win32 last error = 5 translates to access denied .I made sure ,SCCM site Server account, user account /group had full access to the source folder location but missed to add System account.

    To see if the system account have enough read permission to the above share ,simply use sysinternal tools and access the share if that works or not.

    PSEXEC -i -s -d CMD

    In my case ,it says access denied but am able to access using user account.

    image

    To fix this ,you need to provide permissions to SYSTEM account as well both in sharing and security tabs (NTFS Sharing).

    image

    Hope it helps!

    cannot distribute configmgr Current branch How to troubleshoot Package failed SCCM SMS service cannot access it Win32 last error = 5
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    SCCM SQL Report – Compare Installed Apps on TWO Different Computers

    July 13, 10:35 am

    Optimize Your Intune Workflow with a Powerful Browser Extension

    March 22, 10:39 am

    Migrate Microsoft 365 Updates from SCCM/MECM to Intune for Co-Managed Devices

    February 11, 9:50 pm

    4 Comments

    1. Harender Jangra on May 5, 2022 9:47 PM

      I was also facing this issue then I found there were two updates in that folder and one of the updates had been deleted by me manually from its source location but it did not delete from deployment package, once I removed that particular updates from Deployment package and then i did distribute the content and it got distributed successfully.

      Reply
    2. George on June 4, 2019 12:40 AM

      Thanks it worked for me

      Reply
    3. yuvaraj on August 2, 2018 12:32 AM

      I am facing similar issue, but i am able to see the system account has full permission on the file.

      Reply
      • Eswar Koneti on September 2, 2018 6:35 PM

        how about SCCM server computer account ,it also need full permissions.

        Thanks,
        Eswar

        Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2025 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.