SMS Distribution Manager failed
Hi,
I am having 1 Central,2 Primary Child and 10 SCCM Secondary Servers. All the SCCM Servers are with SP2 R2.In one of the SCCM Secondary Server, I am getting the below error message in SMS_DISTRIBUTION_MANAGER component for few of the applications.
SMS Distribution Manager failed to copy package "BL10016D" from "G:\_S Mjvxi.TMP\" to "MSWNET:["SMS_SITE=BLA"]\\BLASJNGR01\SMSPKGG$\BL10016D\". The operating system reported error 145: The directory is not empty.
Possible cause: SMS Distribution Manager does not have sufficient rights to read from the package source directory or to write to the destination directory on the distribution point.
Solution: In the SMS Administrator console, verify that the site system connection accounts have sufficient privileges to the source and destination directories.
Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server.
Solution: If users are currently accessing the package files on the distribution point, disconnect the users first. If the package distribution point is located on a Windows NT computer, you can force users to disconnect by clicking on the "Disconnect users
from distribution points" box in the Data Access tab of the Package Properties dialog box.
Possible cause: The distribution point does not have enough free disk space to store the package.
Solution: Verify that there is enough free disk space.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Question - What are the possibilities for this error message and what all the things I can check to resolve this issue.
Thanks & Regards Deepak Kumar
November 27th, 2010 5:06pm
If the DP was working fine earlier, then the most likely cause would be the users are currently accessing the package file on the distribution point. These errors are temporary and once the
user completes executing the program they will disconnect from the DP and package gets updated properly. So, please check after some time. Also, on the DP, open the computer management (compmgmt.msc)
-> System Tools -> Shared Folders -> Open Files. Here check whether the files that you are trying to update are in use or not.
Regards, Madan
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2010 2:16am
If the DP was working fine earlier, then the most likely cause would be the users are currently accessing the package file on the distribution point. These errors are temporary and once the
user completes executing the program they will disconnect from the DP and package gets updated properly. So, please check after some time. Also, on the DP, open the computer management (compmgmt.msc)
-> System Tools -> Shared Folders -> Open Files. Here check whether the files that you are trying to update are in use or not.
Regards, Madan
November 28th, 2010 2:16am
Hi Deepak,
Could you please check distmgr.log and post the error messages in the thread?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2010 10:16pm
Thanks Mohan/Eric,
I checked in Site Systems of the secondary server in which problem was there.Distribution point share drive was dismounted and we have restarted the secondary server.Now the problem has been resolved.
Thanks a lot again and appreciate for the help. Thanks & Regards Deepak Kumar
November 29th, 2010 11:26pm