Sign in
Microsoft.com
 
System Center Configuration Manager TechCenter
 
 
 
System Center Configuration Manager TechCenter > System Center Configuration Manager Forums > Configuration Manager Software Distribution > Destribution of backages fails
Ask a questionAsk a question
Search Forums:
 

AnswerDestribution of backages fails

  • Monday, October 26, 2009 6:44 PMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I am running simple infrastructure as a test/learning lab, one DC 2003, SCCM installed on Win2003 R2 and only few XP computers. There is only one LAN, no branch points.

    Any package I publish, I always get this error in site status;

    SMS Distribution Manager failed to process package "Reader" (package ID = 00200004).

    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.

    I gave as full access rights I can to the SCCM machine account and domain admins. I managed destribution point all over again, but no. I tried different settings of the package, how to enter the path of source files. I still think, the problem is about DP cannot access the source. How can I check it for sure? Meaning, how can I do this; Verify that distribution manager can access the package source directory/distribution point.

    State of package is "install pending".

     

Answers

  • Monday, October 26, 2009 11:09 PMBhaskarK - MSFTModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Basically the site server uses the machine account to connect to the share. You will need to add the site server's computer account to the share permissions so that distmgr can connect to that share.

    Thanks,

    bhaskar
     

All Replies

  • Monday, October 26, 2009 7:03 PMKent Agerlund Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Check the distmgr.log file, it contains more detailed information. Make sure that the configmgr. server computer account has read access to the package share. Where did you store the source files? Is the share accessable?
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
     
  • Monday, October 26, 2009 9:05 PMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Check the distmgr.log file, it contains more detailed information. Make sure that the configmgr. server computer account has read access to the package share. Where did you store the source files? Is the share accessable?
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

    Here is the line which might be instrested from distmgr.log -

     \\SCCM\MSI\ADOBE READER is not a valid share name, cannot install package 00200004 to any distribution points. SMS_DISTRIBUTION_MANAGER 26.10.2009 22:44:11 4956 (0x135C)

    But this share link is valid from every host or workstation. How can I make sure, if the configmgr has the access?
     
  • Monday, October 26, 2009 11:09 PMBhaskarK - MSFTModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Basically the site server uses the machine account to connect to the share. You will need to add the site server's computer account to the share permissions so that distmgr can connect to that share.

    Thanks,

    bhaskar
     
  • Tuesday, October 27, 2009 6:00 AMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Basically the site server uses the machine account to connect to the share. You will need to add the site server's computer account to the share permissions so that distmgr can connect to that share.

    Thanks,

    bhaskar

    Yes, I already did that, no help.
     
  • Tuesday, October 27, 2009 7:31 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    \\SCCM\MSI\ADOBE READER
    Can you browse to that location using Windows explorer?
    You can also start a cmd in system context and see if you can reach it in that context.
     
  • Tuesday, October 27, 2009 8:02 AMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    \\SCCM\MSI\ADOBE READER
    Can you browse to that location using Windows explorer?
    You can also start a cmd in system context and see if you can reach it in that context.

    Yes, it really is accasseble, also from the Windows XP host, where to I try to install this advertised program.
     
  • Tuesday, October 27, 2009 8:32 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Even in SYSTEM context? IOW have you really tried to access that share using a cmd in system context?
    The XP workstation will never touch the package source files, because it will use the copy on the DP(s).
     
  • Thursday, October 29, 2009 3:31 PMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Is it possible, that this destribution fails, because I don't use any command to lauch the installation? In software destribution, the "program" value is only set as "adoberdr9.msi". There is no "msiexec /i ado...msi."
     
  • Friday, October 30, 2009 2:50 PMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I recreated the package system.

    1. I deleted all excisting package setups
    2. I created install.bat for every software, which contains command "msiexec /i package.msi /quiet". I tested this by running the command from a client XP machine, by mapping the SCCM server's share. It works from command promt perfectly.
    3. I used a destribution wizard for package, which creates every component, the package, advertisment, and the collection. (earlier I did every step manually).
    4. I re-installed the sccm client of XP machine.

    Now I get this error in package status;

    The content for "0020000A" - "1" could not be located. This SMS client will no longer attempt to locate this content.
    Possible cause: The content source might not be available on any distribution servers, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point.
    Solution: Use the Manage Distribution Points wizard to distribute the content to a distribution point. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.

    Additional question - where can I find group policy template for SCCM? I can't find it..
     
  • Saturday, November 14, 2009 9:17 AMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Even in SYSTEM context? IOW have you really tried to access that share using a cmd in system context?
    The XP workstation will never touch the package source files, because it will use the copy on the DP(s).

    Sorry for stupid question, but how can I enter the network share using command promt? Sure I can first use "net use X: \\server\share" command and then move to X: but is there another way, using single command?

    I have everything in one host, MS SQL 2005, SCCM server and DP is also the same. I noticed, that in conf mgr console it displays a package location as \\server\smspkg$\0000111 or something like that. I can also access this share from Windows XP machine, where destribution still fails.

    I don't see any errors in package status log, when creating new package and advertisment at once.
     
  • Monday, November 16, 2009 7:15 AMTorsten [MVP]MVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    You could use "dir \\server\share". distmgr.log is still the place to look for errors.
     
  • Monday, November 16, 2009 8:07 PMyannara Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Distmgr does not write any errors during running advertisment, but here is something I dig up;

    execmgr.log from client computer;

    Content availability verification for package 0020000F program MSN Messenger is in progress execmgr 16.11.2009 21:51:37 1792 (0x0700)
    OnCheckContentAvailabilityResult Content not available. The location request ID is {5964A69B-921E-499E-9D4F-EE93DB7DC77C} execmgr 16.11.2009 21:51:37 164 (0x00A4)
    CancelCheckContentAvailability, content not available for program MSN Messenger package 0020000F execmgr 16.11.2009 21:51:38 1792 (0x0700)

    smscliui.log from client computer

    CUIEvents::RunInstallProgram - event received. smscliui 16.11.2009 21:51:37 2596 (0x0A24)
    CUIEventHandler::RunInstallProgram - program MSN Messenger, package 0020000F smscliui 16.11.2009 21:51:37 2428 (0x097C)
    Could not find the policy in WMI for package  program  smscliui 16.11.2009 21:51:37 2428 (0x097C)

    Advertisment Status of current package from SCCM console

    Severity Type Site code Date / Time System Component Message ID Description
    Error Milestone 002 16.11.2009 21:51:49 ACERXP Software Distribution 10051 The content for "0020000D" - "1" could not be located. This SMS client will no longer attempt to locate this content.   Possible cause: The content source might not be available on any distribution servers, or the advertisement may have been marked not to run program when no local Distribution Point is available and this SMS client is in remote roaming boundaries of the site. Content source might not be available because the advertisement is configured with the option Run program from distribution point on one or more branch distribution points and is not available on a standard distribution point. Branch distribution points do not support advertisements that are configured with the option Run program from distribution point.  Solution: Use the Manage Distribution Points wizard to distribute the content to a distribution point. If this SMS client is expected to stay in remote roaming binderies then change the advertisement to allow running program from remote Distribution Point. Use the Manage Distribution Points wizard to distribute the content to a standard distribution point if you want to use the option Run program from distribution point.

    ccm.log from sccm logs

    ---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:48:50 3088 (0x0C10)
    ---> Attempting to connect to administrative share '\\ACERXP\admin$' using account 'MALMI\sccm' SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:48:50 3088 (0x0C10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account MALMI\sccm (000004b3) SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:49:16 3088 (0x0C10)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account MALMI\sccm (000004b3) SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:49:16 3088 (0x0C10)
    ---> Attempting to connect to administrative share '\\ACERXP\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:49:16 3088 (0x0C10)
    ---> Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:49:16 3088 (0x0C10)
    ---> ERROR: Failed to connect to the \\ACERXP\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:49:16 3088 (0x0C10)
    ---> ERROR: Unable to access target machine for request: "VHGSKLDU", machine name: "ACERXP", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 16.11.2009 21:49:16 3088 (0x0C10)