Hi All, On my SCCM secondary server,I have moved SMSPKGH$ from H:\ drive to I:\ drive as per the below link http://blogs.technet.com/b/smsandmom/archive/2008/09/04/moving-the-smspkgc-share-to-a-different-drive.aspx After doing this activity I am getting the below error on this SCCM secondary server. SMS Distribution Manager failed to process package "Adobe Reader" (package ID = GS10014F). Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. 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. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it. SMS Distribution Manager failed to copy package "GS10014F" from "g:\_S Mklib.TMP\" to "MSWNET:["SMS_SITE=NLM"]\\Server2\SMSPKGG$\GS10014F\". 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. Note : Effect of this is no packages are getting pushed to the Distribution point of this SCCM secondary server and it says "Install Retrying" Regards UttamaThanks & Regards Uttam

Did you check the permissions on the share ? what does distmgr.log says ? try to create the NO_SMS_ON_DRIVE.SMS file on the other drives (non DP) to prevent SCCM from placing any components(selects highst avilable free space with NTFS partition) on that drive in the future since you are using standard DP role. //Eswar Koneti @ www.eskonr.com

Hi, I have checked the permission on SMSPKGH$ and SMSPKGI$.The permission on correct. Administrators - Full control and Users - Read and Execute. Both these Distribution share are accessible from other SCCM Servers. I will check dismgr.log from this Server and will update you ASAP. Thanks & Regards Uttam

Hi, As I have told that now as per the movement of DP share, SMSPKGH$ and SMSPKGI$,both are on I:\ drive. Distmgr.log says as follows: RDC:Failed to copy package signature file g:\SMSPKGSIG\NL1002B8.59.tar to \\Server2\SMSSIG$\\GS10014F.59.tar. Error 5 Cannot copy package GS10014F from g:\_S Mlz86.TMP\ to I:\SMSPKGI$\GS10014F\, Win32 Error = 0 Error occurred.Thanks & Regards Uttam

Hi, As I have told that now as per the movement of DP share, SMSPKGH$ and SMSPKGI$,both are on I:\ drive. Distmgr.log says as follows: RDC:Failed to copy package signature file g:\SMSPKGSIG\NL1002B8.59.tar to \\Server2\SMSSIG$\\GS10014F.59.tar. Error 5 Cannot copy package GS10014F from g:\_S Mlz86.TMP\ to I:\SMSPKGI$\GS10014F\, Win32 Error = 0 Error occurred.Thanks & Regards Uttam

Have you restarted the box to make sure the permissions are solid?http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Have you restarted the box to make sure the permissions are solid?http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Hi, As per the distmgr.log which you have post it is 100% sure that it is a access issue on newly created folder for DP. Follow the below step to confirm the same. (just do this steps on temprary base for testing the permission) 1. Go to the newly created folder and add everyone & give full control including child folder & subfolder in it. 2. Now restart the machine and try the proccess package ID = GS10014F one more time. 3.If it get successful that means rights are not configured properly for pervious A/C. ---------------------------------------------- Amarpal Singh Sandhu

Hi, As per the distmgr.log which you have post it is 100% sure that it is a access issue on newly created folder for DP. Follow the below step to confirm the same. (just do this steps on temprary base for testing the permission) 1. Go to the newly created folder and add everyone & give full control including child folder & subfolder in it. 2. Now restart the machine and try the proccess package ID = GS10014F one more time. 3.If it get successful that means rights are not configured properly for pervious A/C. ---------------------------------------------- Amarpal Singh Sandhu

Hi, As per the distmgr.log which you have post it is 100% sure that it is a access issue on newly created folder for DP. Follow the below step to confirm the same. (just do this steps on temprary base for testing the permission) 1. Go to the newly created folder and add everyone & give full control including child folder & subfolder in it. 2. Now restart the machine and try the proccess package ID = GS10014F one more time. 3.If it get successful that means rights are not configured properly for pervious A/C. ---------------------------------------------- Amarpal Singh Sandhu

May be you should try to copy something manually to that share and see if that works from system context. I had same problem, after fixing the permission issue, it all started working!

May be you should try to copy something manually to that share and see if that works from system context. I had same problem, after fixing the permission issue, it all started working!

Yes I have restarted the box but still none of the packages are getting pushed to this Distribution point and it always says Install Retrying.............. Is it possible that there can be 2 Distribution share in single Drive(partition) For example - SMSPKGH$ and SKSPKGI$ in I:\ drive?Thanks & Regards Uttam

Hi Sandhu/All, Do you mean to say that we need to give permission to Everyone in Security tab.Because in Sharing tab->Permission button Everyone is having full control.Thanks & Regards Uttam

Hi All, I would like to explain the situation once more. SMSPKGH$ which was there in H:\ drive has been moved to I:\ drive. In I:\ drive there was already SMSPKGI$. After this H:\ drive has been deleted. Now in I:\ drive there is two Distribution shares ie; SMSPKGH$ and SMSPKGI$. Both the Distribution share has same permission and I am able to access these Distribution share from other Servers from Start->run->\\Servername\SMSPKGH$ and \\Servername\SMSPKGI$ Question - 1. Can there be two Distribution share (SMSPKGH$ and SMSPKGI$) in same drive(partition). After doing the above mentioned activity,none of the packages are getting pushed to Distribution point of this Secondary site server.It always says "Install Retrying" Can any body explain me in detail that how can I solve this issue on priority basis.Thanks & Regards Uttam

Hi All, I would like to explain the situation once more. SMSPKGH$ which was there in H:\ drive has been moved to I:\ drive. In I:\ drive there was already SMSPKGI$. After this H:\ drive has been deleted. Now in I:\ drive there is two Distribution shares ie; SMSPKGH$ and SMSPKGI$. Both the Distribution share has same permission and I am able to access these Distribution share from other Servers from Start->run->\\Servername\SMSPKGH$ and \\Servername\SMSPKGI$ Question - 1. Can there be two Distribution share (SMSPKGH$ and SMSPKGI$) in same drive(partition). After doing the above mentioned activity,none of the packages are getting pushed to Distribution point of this Secondary site server.It always says "Install Retrying" Can any body explain me in detail that how can I solve this issue on priority basis.Thanks & Regards Uttam

Hi, 1. As you have mentioned above that SMSPKGH$ which was there in H:\ drive has been moved to I but the name which you have given to that folder is SMSPKGH$ but folder is located in I drive on server, so it will be looking in to the H drive for SMSPKGH$ not in I drive and as you have deleted it it won't be able to sent that package because there is not SMSPKGH$ present in H drive 2. In order for it to work you have to rename that pacakge to SMSPKGI$ because now it is in I drive not in H drive, so there is no meaning of creating share with name SMSPKGH$ in I drive. and also chage the setting in console as showen below. so that server can make neccesery changes in SQL server for that specific DP server . 3. Change the drive letter where compressed files are stored in the console. In the SMS/SCCM console. Navigate to Site Database | Site Management | <SiteCode> | Site Settings | Component Configuration | Software Distribution and you will see a box for the drive on which to store these compressed files. Simply changing this drive letter does not affect compressed files that have already been placed on the server, but rather all future files will be placed on the new drive/folder. Note : Problem here is that you already have SMSPKGI$ located in I drive so if you make chage in the setting of console then it will sent that new packges to SMSPKGI$ I drive not to SMSPKGH$ .

Hi, 1. As you have mentioned above that SMSPKGH$ which was there in H:\ drive has been moved to I but the name which you have given to that folder is SMSPKGH$ but folder is located in I drive on server, so it will be looking in to the H drive for SMSPKGH$ not in I drive and as you have deleted it it won't be able to sent that package because there is not SMSPKGH$ present in H drive 2. In order for it to work you have to rename that pacakge to SMSPKGI$ because now it is in I drive not in H drive, so there is no meaning of creating share with name SMSPKGH$ in I drive. and also chage the setting in console as showen below. so that server can make neccesery changes in SQL server for that specific DP server . 3. Change the drive letter where compressed files are stored in the console. In the SMS/SCCM console. Navigate to Site Database | Site Management | <SiteCode> | Site Settings | Component Configuration | Software Distribution and you will see a box for the drive on which to store these compressed files. Simply changing this drive letter does not affect compressed files that have already been placed on the server, but rather all future files will be placed on the new drive/folder. Note : Problem here is that you already have SMSPKGI$ located in I drive so if you make chage in the setting of console then it will sent that new packges to SMSPKGI$ I drive not to SMSPKGH$ .

Hi Uttam. Question - 1. Can there be two Distribution share (SMSPKGH$ and SMSPKGI$) in same drive(partition). Answer - NO, I think you are bit confuesed how DP works. 1. There cann't be one DP for 2 Primary servers, I will let you know whatever i know about this. 2. SMS by default install package on the partition where there is more free place unless you define under SMS console in Software Distribution component. 3.So if by default it has created folder under H drive with name SMSPKGH$ and after few months it finds that the disk space on H drive is low then it will automatically start creation packge on some other drive example I drive (NTFS partition) with the different name SMSPKGI$ (note it will not create the folder with same name SMSPKGH$) where there is more space avilable as compare to other drives. 4. It will also update this inforamtion to SQL database so that whenever any new packge created then it will move it to SMSPKGI$. Hello Mates, Please let me know if i missed any thing or My thought's are wrong about DP.

Hi, 1. As you have mentioned above that SMSPKGH$ which was there in H:\ drive has been moved to I but the name which you have given to that folder is SMSPKGH$ but folder is located in I drive on server, so it will be looking in to the H drive for SMSPKGH$ not in I drive and as you have deleted it it won't be able to sent that package because there is not SMSPKGH$ present in H drive 2. In order for it to work you have to rename that pacakge to SMSPKGI$ because now it is in I drive not in H drive, so there is no meaning of creating share with name SMSPKGH$ in I drive. and also chage the setting in console as showen below. so that server can make neccesery changes in SQL server for that specific DP server . 3. Change the drive letter where compressed files are stored in the console. In the SMS/SCCM console. Navigate to Site Database | Site Management | <SiteCode> | Site Settings | Component Configuration | Software Distribution and you will see a box for the drive on which to store these compressed files. Simply changing this drive letter does not affect compressed files that have already been placed on the server, but rather all future files will be placed on the new drive/folder. Note : Problem here is that you already have SMSPKGI$ located in I drive so if you make chage in the setting of console then it will sent that new packges to SMSPKGI$ I drive not to SMSPKGH$ .

Hi Uttam. Question - 1. Can there be two Distribution share (SMSPKGH$ and SMSPKGI$) in same drive(partition). Answer - NO, I think you are bit confuesed how DP works. 1. There cann't be one DP for 2 Primary servers, I will let you know whatever i know about this. 2. SMS by default install package on the partition where there is more free place unless you define under SMS console in Software Distribution component. 3.So if by default it has created folder under H drive with name SMSPKGH$ and after few months it finds that the disk space on H drive is low then it will automatically start creation packge on some other drive example I drive (NTFS partition) with the different name SMSPKGI$ (note it will not create the folder with same name SMSPKGH$) where there is more space avilable as compare to other drives. 4. It will also update this inforamtion to SQL database so that whenever any new packge created then it will move it to SMSPKGI$. Hello Mates, Please let me know if i missed any thing or My thought's are wrong about DP.

Hi Uttam. Question - 1. Can there be two Distribution share (SMSPKGH$ and SMSPKGI$) in same drive(partition). Answer - NO, I think you are bit confuesed how DP works. 1. There cann't be one DP for 2 Primary servers, I will let you know whatever i know about this. 2. SMS by default install package on the partition where there is more free place unless you define under SMS console in Software Distribution component. 3.So if by default it has created folder under H drive with name SMSPKGH$ and after few months it finds that the disk space on H drive is low then it will automatically start creation packge on some other drive example I drive (NTFS partition) with the different name SMSPKGI$ (note it will not create the folder with same name SMSPKGH$) where there is more space avilable as compare to other drives. 4. It will also update this inforamtion to SQL database so that whenever any new packge created then it will move it to SMSPKGI$. Hello Mates, Please let me know if i missed any thing or My thought's are wrong about DP.

Hi Sandhu, In our scenario, there is no drive defined under Site Database | Site Management | <SiteCode> | Site Settings | Component Configuration | Software Distribution.There is only standard DP role installed and confgured for all the SCCM secondary servers that is the reason as you told SCCM is creating the DP share SMSPKGX$ where X is the random drive wherever free space is more with NTFS partition. Now the question is as SMSPKGH$ has been moved from H:\ drive to I:\ drive and already there was SMSPKGI$ on I:\ drive.So as of now there is SMSPKGH$ and SMSPKGI$ both resides on I:\ drive as H:\ drive has been deleted now. Do you think that this will not work and if so what is the reason and what action should be taken as per the above scenario explained.Thanks & Regards Uttam

Hello Uttam, 1. Go to Site Database | Site Management | <SiteCode> | Site Settings | Component Configuration | Software Distribution and select I drive and apply it. 2. In the SMS Administrator console, verify that the site system connection accounts have sufficient privileges to the source and destination directories 3. Now restart the machine. and once it is up and running then retarget Adobe Reader" (package ID = GS10014F) package one more time. 4. Moniter the Distmgr.log and post the whole log if problem still persist. -------------------------------- Regards, Amarpal Singh Sandhu

Hello Uttam, 1. Go to Site Database | Site Management | <SiteCode> | Site Settings | Component Configuration | Software Distribution and select I drive and apply it. 2. In the SMS Administrator console, verify that the site system connection accounts have sufficient privileges to the source and destination directories 3. Now restart the machine. and once it is up and running then retarget Adobe Reader" (package ID = GS10014F) package one more time. 4. Moniter the Distmgr.log and post the whole log if problem still persist. -------------------------------- Regards, Amarpal Singh Sandhu