none
Problem with "stuck" distribution points RRS feed

  • Question

  • Hi
     
    I have a 3 tier SCCM R2 site (central site, child primary and a number of secondary sites) and I am having problems with 'stuck' distribution points. I have turned off 'send package from the nearest site in the hierarchy' on the central site as suggested in KB936465, refreshed the stuck distribution points and still the distribution manager log reports that The compressed files for package PSA00002 hasn't arrived from site PSA yet, will retry later. This secondary site's parent is the child primary site (PSB) so I assume that the 'send package from the nearest site in the hierarchy' has applied as the package hasn't arrived from the central site (rather than the child primary).

    Deleting the package from the distribution point and re-adding it, refreshing the distribution point or updating the distribution point does not resolve the issue. I can get around this issue by using PreloadPkgOnSite however I have some large PCK files that I need to transfer over slow WAN links to secondary sites so this is not a viable option.

    Does anyone have any suggestions on how to resolve this issue? I would prefer not to edit the PkgStatus table if possible.

    Thanks

    Sam
    Wednesday, February 4, 2009 2:56 AM

Answers

  • Hi Torsten

    After speaking with Microsoft, unfortunately at this stage the only way to resolve this issue is to modify the PkgStatus table on the central site server SQL database, and then refresh the affected distribution points. The SQL query that Microsoft got me to run for each affected distribution point is:

    update pkgstatus set Status = 2 where id = '<package ID>' and sitecode = '<site code>' and type = 1
    update pkgstatus set SourceVersion = 0 where id = '<package ID>' and sitecode = '<site code>' and type = 1

    Microsoft stated that this issue can randomly occur in larger SCCM environments with large packages and slow WAN links, and they are unable to exactly pinpoint the problem due to its random nature. Hopefully a hotfix will be released one day to fix this problem!

    Cheers

    Sam
    • Marked as answer by slewis1310 Tuesday, February 10, 2009 12:37 AM
    Tuesday, February 10, 2009 12:37 AM
  • slewis1310 said:

    Does anyone have any suggestions on how to resolve this issue? I would prefer not to edit the PkgStatus table if possible.


    There are no other methods as those you already mentioned as far as I know.
    • Marked as answer by slewis1310 Tuesday, February 10, 2009 12:37 AM
    Thursday, February 5, 2009 7:52 AM
    Moderator

All replies

  • slewis1310 said:

    Does anyone have any suggestions on how to resolve this issue? I would prefer not to edit the PkgStatus table if possible.


    There are no other methods as those you already mentioned as far as I know.
    • Marked as answer by slewis1310 Tuesday, February 10, 2009 12:37 AM
    Thursday, February 5, 2009 7:52 AM
    Moderator
  • Thanks for the reply Torsten

    I've raised a PSS with Microsoft so it'll be interesting to see what they suggest
    Friday, February 6, 2009 12:23 AM
  • Please update this thread after you got an answer from PSS.
    Friday, February 6, 2009 8:54 AM
    Moderator
  • Hi Torsten

    After speaking with Microsoft, unfortunately at this stage the only way to resolve this issue is to modify the PkgStatus table on the central site server SQL database, and then refresh the affected distribution points. The SQL query that Microsoft got me to run for each affected distribution point is:

    update pkgstatus set Status = 2 where id = '<package ID>' and sitecode = '<site code>' and type = 1
    update pkgstatus set SourceVersion = 0 where id = '<package ID>' and sitecode = '<site code>' and type = 1

    Microsoft stated that this issue can randomly occur in larger SCCM environments with large packages and slow WAN links, and they are unable to exactly pinpoint the problem due to its random nature. Hopefully a hotfix will be released one day to fix this problem!

    Cheers

    Sam
    • Marked as answer by slewis1310 Tuesday, February 10, 2009 12:37 AM
    Tuesday, February 10, 2009 12:37 AM
  • Hi Sam

    I'm having the exactly same problem as described above in more or less exactly the same environment.

    Have you got an answer from PSS?

    Thanks
    Soren
    Tuesday, June 2, 2009 12:06 PM
  • Hi Soren

    The answer I got from PSS was to modify the PkgStatus table on the central site server's SQL database. My post above states the 2 SQL queries they got me to run for each of the affected sites and it fixed the issue. Microsoft didn't have an explanation as to why it happens so hopefully it's fixed in SP2.

    Good luck

    Cheers

    Sam
    Wednesday, June 3, 2009 2:39 AM
  • Hi all,

    I know this thread hasn't been posted to in nearly six months, but I am having the same issue in my SCCM infrastructure.

    I have a two-tier heirarchy (central and nine primaries) and aprox. 8000 packages - which are being distributed almost non-stop.

    It seems fairly random and affects the StoredPkgPath column in the SMSPackages table - i.e. on some down-level primaries this column is blank.  This PCK file does eixst however, so to fix it I just run the following query:

    UPDATE SMSPackages SET StoredPkgPath = <StoredPkgPath> WHERE pkgID = <packageID>

    On the primary with the problem.

    I get this in my despool.log

    STATMSG: ID=4407 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DESPOOLER" SYS=XXX SITE=XXX PID=64744 TID=56828 GMTDATE=Tue Nov 17 08:21:44.887 2009 ISTR0="GLB02694" ISTR1="1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="GLB02694" SMS_DESPOOLER 17/11/2009 08:21:44 56828 (0xDDFC)
    
    Received package GLB02694 version 1 SMS_DESPOOLER 17/11/2009 08:21:44 56828 (0xDDFC)
    
    Insert package GLB02694 to the distribution source. SMS_DESPOOLER 17/11/2009 08:21:44 56828 (0xDDFC)
    
    *** insert SMSPackages (PkgID, Name, Version, Language, Manufacturer, Description, Hash, NewHash, Source, SourceSite, StoredPkgPath, RefreshSchedule, LastRefresh, StoredPkgVersion, ShareName, PreferredAddress, StorePkgFlag, ShareType, HashVersion,Architecture, ImagePath,Permission, UseForcedDisconnect, ForcedRetryDelay, DisconnectDelay, IgnoreSchedule, Priority, PkgFlags, MIFFilename, MIFPublisher, MIFName, MIFVersion, SourceVersion, SourceDate, SourceSize, SourceCompSize, ImageFlags, PackageType, AlternateContentProviders, SourceLocaleID,  UpdateMask, UpdateMaskEx, Action) values ("GLB02694", "AppName", "", "", "", "AppFullName", "4F8B11C2AE05D89FB412CC360D5D9EF3", "02FC5C5771FA6A6A0730A6C21E832BFA62454BFA", "AppSourceLocation", "GLB", "PCKLocation", "", "11/17/2009 08:20:55", 1, "AppDestinationLocation", "Standard", 3, 2, 2, "", "", 15, 0, 2, 5, 0, 2, 1073741827, "", "", "", "", 1, "11/17/2009 08:20:36", 636, 289, 0, 0, "", 2057, 0, 0, 2) SMS_DESPOOLER 17/11/2009 08:21:44 56828 (0xDDFC)
    
    *** [23000][2627][Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'SMSPackages_PK'. Cannot insert duplicate key in object 'dbo.SMSPackages'. SMS_DESPOOLER 17/11/2009 08:21:44 56828 (0xDDFC)
    
    Stored Package GLB02694. Stored Package Version = 1 SMS_DESPOOLER 17/11/2009 08:21:48 56828 (0xDDFC)
    
    Error in storing Package GLB02694. Old Version = 1, New Version = 1, Error Code = 3 SMS_DESPOOLER 17/11/2009 08:21:48 56828 (0xDDFC)
    
    Forward package status for pkg GLB02694 to site GLB SMS_DESPOOLER 17/11/2009 08:21:48 56828 (0xDDFC)
    
    STATMSG: ID=4400 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DESPOOLER" SYS=XXX SITE=XXX PID=64744 TID=56828 GMTDATE=Tue Nov 17 08:21:48.965 2009 ISTR0="GLB02694" ISTR1="PCKLocation" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="GLB02694" SMS_DESPOOLER 17/11/2009 08:21:48 56828 (0xDDFC)
    


    Looking forward to an answer from MS on this one.

    Steve.


    Just a good old boy, never meaning no harm
    Monday, November 30, 2009 11:53 AM
  • There's something messed up with the database. I would call PSS to get assistance, because manually editing the database is not supported and might make things worse.
    Monday, November 30, 2009 12:32 PM
    Moderator
  • Hi All

    I am having the same problem on 2 of the packages on our 2 tier SCCM SP2 R2 production site. The errors "The compressed files for package XXX00117 hasn't arrived from site XXX yet, will retry later" is showing up on 2 primary sites but a refresh of the 2 packages to other primary site DPs works fine.

    I have tried deleting and refreshing packages without luck. Deleting and recreating the packages is not an option.

    Just wanted to know if here a hotfix for this problem before I log a PSC call. I do not want to run scripts on the SCCM database without logging a call.

    Thanks

    Nilanga


    Nilanga
    Wednesday, May 19, 2010 1:53 AM
  • Just wanted to know if here a hotfix for this problem before I log a PSC call. I do not want to run scripts on the SCCM database without logging a call.
    There's no hotfix available as far as I know.
    Wednesday, May 19, 2010 6:29 AM
    Moderator
  • Just wanted to know if here a hotfix for this problem before I log a PSC call. I do not want to run scripts on the SCCM database without logging a call.

    Hi Nilanga

    As Torsten said it doesn't appear that a hotfix has been released to resolve this issue. PSS will most likely to tell you to modify the SQL database which resolved the issue for me.

    Good luck!

    Cheers

    Sam

    Wednesday, May 19, 2010 10:49 PM
  • Same issue here and getting thousands of informational messages on my Secondary Site.  I have refreshed several packages and I see .pkn files flying through my \inboxes\distmgr.box.

    Any help would be great.

    Monday, May 24, 2010 5:50 PM
  • Modifying the DB is unsupported unless under the direction of PSS
    Monday, May 24, 2010 6:46 PM
    Moderator
  • getting thousands of informational messages on my Secondary Site. 

    Any chance that you are running into the issue described in http://support.microsoft.com/kb/978021/en-us?
    Tuesday, May 25, 2010 6:05 AM
    Moderator
  • I am only getting this errors on 2 packages. I am able to refresh and distribute other packages to the afftected primary site. Will let you know the outcome of the PSC. 


    Nilanga
    Tuesday, May 25, 2010 11:36 PM
  • The hot fix mentioned above

    http://support.microsoft.com/kb/978021/en-us?

    does resolve the issue below most of the time:

    getting thousands of informational messages on my Secondary Site. 

    These informational messages are in the SMS Distribution Manager Component Status in the console.

    Another thing I noticed on the servers with the distribution point issues is nearly all of them have delayed-write errors on the screen in front of the CTRL+ALT+DEL log on screen. I just clicked through quite a few of these delayed-write errors where essentially the SCCM .pck file is lost while trying to copy it from the primary server.

    I think this is a Windows issue or an Ethernet setting issue, but am not certain of that. We had a problem open several years ago with Microsoft regarding the delayed-write errors and never figured out why they cleared up. Now they are back. 


    • Edited by SandyJCty Thursday, March 15, 2012 7:53 PM
    Thursday, March 15, 2012 7:52 PM