none
Configmgr Client Upgrade Package (CAS00003) - Pending to install on a Specific DP RRS feed

  • Question

  • Hi All,

    Recently we build a new SCCM Secondary Site server, during the package distribution all package successfully distribute but the client upgrade package not distributed to the new DP and it freeze at content being distributed for days.

    There is no issue with client upgrade package, it can be distributed to all other DPs, The problem is only with this DP.

    Distmgr.log

    The contents for the package CAS00003 hasn't arrived from site CAS yet, will retry later. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:47:22 AM 3456 (0x0D80)
    STATMSG: ID=2372 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SSCSVA006. SITE=F16 PID=3216 TID=3456 GMTDATE=Mon Apr 18 06:47:22.401 2016 ISTR0="CAS00003" ISTR1="CAS" ISTR2="F16" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CAS00003" SMS_DISTRIBUTION_MANAGER 4/18/2016 8:47:22 AM 3456 (0x0D80)
    Package CAS00003 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:47:22 AM 3456 (0x0D80)
    CDistributionSrcSQL::UpdateAvailableVersion PackageID=CAS00003, Version=6, Status=2301 SMS_DISTRIBUTION_MANAGER 4/18/2016 8:47:22 AM 3456 (0x0D80)
    StoredPkgVersion (0) of package CAS00003. StoredPkgVersion in database is 0. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:47:22 AM 3456 (0x0D80)
    SourceVersion (6) of package CAS00003. SourceVersion in database is 6. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:47:22 AM 3456 (0x0D80)
    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SSCSVA006.=F16 PID=3216 TID=3456 GMTDATE=Mon Apr 18 06:47:22.979 2016 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="CAS00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CAS00003" SMS_DISTRIBUTION_MANAGER 4/18/2016 8:47:22 AM 3456 (0x0D80)
    Found notification for package 'CAS00003' SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:37 AM 4368 (0x1110)
    STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS= SITE=F16 PID=3216 TID=6624 GMTDATE=Mon Apr 18 06:49:38.135 2016 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="CAS00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CAS00003" SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    No action specified for the package CAS00003. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    The contents for the package CAS00003 hasn't arrived from site CAS yet, will retry later. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    STATMSG: ID=2372 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SSCSVA006.=F16 PID=3216 TID=6624 GMTDATE=Mon Apr 18 06:49:38.198 2016 ISTR0="CAS00003" ISTR1="CAS" ISTR2="F16" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CAS00003" SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    Package CAS00003 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    CDistributionSrcSQL::UpdateAvailableVersion PackageID=CAS00003, Version=6, Status=2301 SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    StoredPkgVersion (0) of package CAS00003. StoredPkgVersion in database is 0. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    SourceVersion (6) of package CAS00003. SourceVersion in database is 6. SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)
    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS==F16 PID=3216 TID=6624 GMTDATE=Mon Apr 18 06:49:38.744 2016 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="CAS00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CAS00003" SMS_DISTRIBUTION_MANAGER 4/18/2016 8:49:38 AM 6624 (0x19E0)

    Also we have tried to redistribute the package like mentioned in this link - https://social.technet.microsoft.com/Forums/en-us/11df0f63-d146-434d-91f3-c4e826fee92c/redistribute-configuration-manager-client-upgrade-package-xxx00003?forum=configmanagermigration 

    but no luck still its struck in the same state.

    Is there any work around for this issue?

    Creating a new client upgrade package is supported? Is so how would we create it?

    Thanks

    Tuesday, April 19, 2016 4:07 AM

Answers

  • Non of the troubleshooting steps help, finally reinstalled the Secondary site :( now CAS00003 distributed successfully.
    • Marked as answer by Kalyan Sundar Thursday, April 28, 2016 5:10 AM
    Thursday, April 28, 2016 5:10 AM

All replies

  • Creating a prestaged content file and using extractcontent.exe on the target usually fixes it.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 19, 2016 6:34 AM
    Moderator
  • Thanks Torsten,

    How do i create a presaged content for Client upgrade package (CAS00003) , its not available anywhere in the packages filed. 

    I can see only the content status.

    Tuesday, April 19, 2016 8:26 AM
  • Do you have bandwidth or or throttling controls set on the DP?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, April 19, 2016 12:42 PM
  • No, all other packages are distributed without a problem. The problem is only with this package.

    Is there a way to make this package distribute or i need to create a new package for client upgrade.

    Wednesday, April 20, 2016 5:14 AM
  • Dear Sir,

        Are there anything useful in the sender.log and despool.log in your site server?

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 20, 2016 8:59 AM
    Moderator
  • There is no errors in Sender and despool logs... everything seems to be ok.

    Now i am trying to re-build the DP...Lets see

    Wednesday, April 20, 2016 12:02 PM
  • sender.log and despool.log in your site server?
    Send and despool have nothing to do with content distribution to a DP.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, April 20, 2016 12:41 PM
  • Do you have a CAS in your environment or is CAS just the site code of your primary?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, April 20, 2016 12:42 PM
  • sender.log and despool.log in your site server?

    Send and despool have nothing to do with content distribution to a DP.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Hi Jason,

        Thank you for pointing out my mistake, you are always my teacher:)

    Regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 28, 2016 2:51 AM
    Moderator
  • Non of the troubleshooting steps help, finally reinstalled the Secondary site :( now CAS00003 distributed successfully.
    • Marked as answer by Kalyan Sundar Thursday, April 28, 2016 5:10 AM
    Thursday, April 28, 2016 5:10 AM