locked
Problems with server share DP RRS feed

  • Question

  •  

    Hey guys,

     

    I'm having some trouble copying a deployment package containing updates to a newly created server share distribution point. I'm sure it's a permissions issue, but I can't see where I'm going wrong.

    I've created a new share on the target server and given the SCCM computer account full control of this. I've also given the SCCM computer account full control on the NTFS permissions. The target server is a DC so I can't add the SCCM computer account to the local admins group, but I have added it to the Domain Admins group (advice on a suitable group with less permissions would be awesome). The DP does not currently allow BITS, HTTP, HTTPS transfers so IIS/WebDAV shouldn't come into it, right?

    But still, I'm getting errors and the package isn't copying over. When checking the SMS_DISTRIBUTION_MANAGER component, it is starts to distribute the package, fails with Message ID 2302 and retries:

     

    SMS Distribution Manager failed to process package "Microsoft Critical Updates" (package ID = PER0000E).
    
    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.
    
    

    The path length should be fine, there is plenty of disk space available, and I removed the current deployment so rule out the fact that files were in use.



    I'm seeing errors when checking SMS_SITE_SYSTEM_STATUS_SUMMARIZER pointing to permissions as well; Message ID 4700 & 4701:

     

     

    SMS Site System Status Summarizer still cannot access storage object "\\targetserver\targetshare" on site system "\\targetserver\targetshare". The operating system reported error 2147942405: Access is denied. 
    
    
    
    Possible cause: The site system is turned off, not connected to the network, or not functioning properly.
    
    Solution: Verify that the site system is turned on, connected to the network, and functioning properly.
    
    
    
    Possible cause: SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object.
    
    Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system and access the storage object.
    
    
    
    Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the site system.
    
    Solution: Investigate and correct any problems on your network.
    
    
    
    Possible cause: You took the site system out of service and do not intend on using it as a site system any more.
    
    Solution: Remove the site system from the list of site systems used by this site; this list appears under Site Systems in the SMS Administrator console.
    
    
    
    Possible cause: You accidentally deleted the storage object or took the storage object out of service.
    
    Solution: The SMS components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other SMS components to verify that this occurs properly.
    
    
    
    The storage object has been inaccessible since "18/10/2011 6:58:32 AM". When you correct the problem and SMS Site System Status Summarizer successfully accesses the storage object, SMS Site System Status Summarizer will set the storage object's status to OK, providing that the storage object has sufficient free space.

     

     

    distmgr.log reports that "no connection account is available", though I understand connection accounts were used in SMS, not SCCM?

     

     

     

    Used 0 out of 3 allowed processing threads.	SMS_DISTRIBUTION_MANAGER	3840 (0x0F00)
    
    Starting package processing thread,thread ID = 2840	SMS_DISTRIBUTION_MANAGER	3840 (0x0F00)
    
    Sleep 3600 seconds...	SMS_DISTRIBUTION_MANAGER	3840 (0x0F00)
    
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Source Server SITE=PER PID=2484 TID=10304 GMTDATE=Mon Oct 17 23:16:07.411 2011 ISTR0="PER0000E" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PER0000E"	SMS_DISTRIBUTION_MANAGER	10304 (0x2840)
    
    Retrying package PER0000E	SMS_DISTRIBUTION_MANAGER	10304 (0x2840)
    
    No action specified for the package PER0000E.	SMS_DISTRIBUTION_MANAGER	10304 (0x2840)
    
    Start adding package to server ["Display=\\targetserver\targetshare\"]MSWNET:["SMS_SITE=PER"]\\targetserver\targetshare\...	SMS_DISTRIBUTION_MANAGER	10304 (0x2840)
    ["Display=\\targetserver\targetshare\"]MSWNET:["SMS_SITE=PER"]\\targetserver\targetshare\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 10304 (0x2840)
    No action specified for the package on server ["Display=\\SourceServer\"]MSWNET:["SMS_SITE=PER"]\\SourceServer\. SMS_DISTRIBUTION_MANAGER 10304 (0x2840) Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 10304 (0x2840) Thread Handle = 14460 SMS_DISTRIBUTION_MANAGER 10304 (0x2840) Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 11632 (0x2D70) for ["Display=\\targetserver\targetshare\"]MSWNET:["SMS_SITE=PER"]\\targetserver\targetshare\, no connection account is available SMS_DISTRIBUTION_MANAGER 11632 (0x2D70)
    STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SourceServer SITE=PER PID=2484 TID=11632 GMTDATE=Mon Oct 17 23:16:07.426 2011 ISTR0="Microsoft Critical Updates" ISTR1="["Display=\\targetserver\targetshare\"]MSWNET:["SMS_SITE=PER"]\\targetserver\targetshare\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="PER0000E" AID1=404 AVAL1="["Display=\\targetserver\targetshare\"]MSWNET:["SMS_SITE=PER"]\\targetserver\targetshare\" SMS_DISTRIBUTION_MANAGER 11632 (0x2D70)

    RDC:This is a Share Type DP. Will use the Share Name SCCMupdates for RDC signature SMS_DISTRIBUTION_MANAGER 11632 (0x2D70) Cannot establish connection to ["Display=\\targetserver\targetshare\"]MSWNET:["SMS_SITE=PER"]\\\targetserver\targetshare\ SMS_DISTRIBUTION_MANAGER 11632 (0x2D70)
    Error occurred. SMS_DISTRIBUTION_MANAGER 11632 (0x2D70) Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 11632 (0x2D70) DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 10304 (0x2840) DP thread with thread handle 14460 and thread ID 11632 ended. SMS_DISTRIBUTION_MANAGER 10304 (0x2840) Updating package info for package PER0000E SMS_DISTRIBUTION_MANAGER 10304 (0x2840) Only retrying local DP update for package PER0000E, no need to replicate package definition to child sites or DP info to parent site. SMS_DISTRIBUTION_MANAGER 10304 (0x2840) StoredPkgVersion (0) of package PER0000E. StoredPkgVersion in database is 0. SMS_DISTRIBUTION_MANAGER 10304 (0x2840) SourceVersion (2) of package PER0000E. SourceVersion in database is 2. SMS_DISTRIBUTION_MANAGER 10304 (0x2840) STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=PER-SCCM01 SITE=PER PID=2484 TID=10304 GMTDATE=Mon Oct 17 23:16:07.583 2011 ISTR0="Microsoft Critical Updates" ISTR1="PER0000E" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PER0000E" SMS_DISTRIBUTION_MANAGER 10304 (0x2840) Failed to process package PER0000E after 60 retries, will retry 40 more times SMS_DISTRIBUTION_MANAGER 10304 (0x2840) Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 10304 (0x2840)

    So yeah, I'm pretty sure it's permissions. Anyone else see where I'm going wrong?
    Cheers

     


    • Edited by michael248 Monday, October 17, 2011 11:23 PM making logs clearer
    Monday, October 17, 2011 11:22 PM

Answers

All replies