none
Multiple duplicate Configuration Manager Client (Upgrade) Packages RRS feed

  • Question

  • We have 14x Configuration Manager Client Package / Configuration Manager Client Upgrade Packages in our SCCM2012R2cu1 environment.

    We tried deleting all of the packages that were not linked to deployments/task sequences, but a few days later these were re-created with new PackageIDs.

    Any ideas what could be causing this? are there some logs we should be checking?

    http://oi61.tinypic.com/5nx4.jpg

    Thanks!



    Monday, June 30, 2014 5:25 AM

Answers

All replies

  • This is caused by a stuck file in an inbox (distmgr.box?) if I recall correctly. Distmgr.log should unveil details.

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

    Monday, June 30, 2014 6:44 AM
    Moderator
  • thanks for the reply Torsten,

    We checked \inboxes\distmgr.box and identified quite a few old INS, PKN & SHA files - which we have now moved to a different location.

    checking the distmgr.log, it shows those newly generated packages going through the usual process of:

    • Found package properties updated notification for package 'XX1001D5'
    • Found notification for package 'XX1001D5'
    • Start adding package XX1001D5...
    • CDistributionSrcSQL::UpdateAvailableVersion PackageID=XX1001D5, Version=1, Status=2300
    • Taking package snapshot for package XX1001D5 from source \\aucolo-sccm.com\SMS_XX1\Client
    • The size of package XX1001D5, version 1 is 186336 KBytes
    • Successfully created RDC signatures for package XX1001D5 version 1
    • CDistributionSrcSQL::UpdateAvailableVersion PackageID=XX1001D5, Version=1, Status=2376
    • Created policy provider trigger for ID XX1001D5
    • ...


    After moving the old INS, PKN & SHA files, we have now re-deleted the duplicate Configuration Manager Client (Upgrade) Packages. We will monitor to see if these are re-created again..

    thanks

    Tuesday, July 1, 2014 5:13 AM
  • Ok so looks like there is some kind of process or task that occurs on a Sunday that is generating these packages.

    When I posted on this thread last, we had deleted all but the two most recent packages (XX1001DB and XX1001DB).  Now after the weekend, we have two additional packages (XX1001EB and XX1001EC) - see screenshot here: http://i62.tinypic.com/5ahor9.png

    the distmgr inbox does not show any corresponding entries for those package IDs and the distmgr.log shows normal distribution logs.


    also, the hman.log seems to be referring to these packages (see next post). Unfortunately the log has rolled over so we are unable to see the packages being created. we have increased the maximum log size for this service to be 20mb so we hopefully can capture it in future

    Are there any other ideas where we can look to troubleshoot this? thanks!

    Monday, July 7, 2014 12:21 AM
  • FROM hman.log:

    CheckSQLServiceRestart : SQL Service hasn't been restart since last time we check, skip it.    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:54 AM    1936 (0x0790)
    Handle auto-upgrade client configuration changes    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:54 AM    1936 (0x0790)
    Update auto-upgrade client configurations    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:54 AM    1936 (0x0790)
    INFO: Full client package id XX1001EB exists.    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:55 AM    1936 (0x0790)
    INFO: Client upgrade package id XX1001EC exists and upgrade package flag is set to 1.    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:55 AM    1936 (0x0790)
    INFO: Client upgrade program Configuration Manager Client Upgrade Program in package id XX1001EC exists and its currently disabled.    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:55 AM    1936 (0x0790)
    INFO: Client upgrade advertisement id XX1203B8 exists for package XX1001EC and program Configuration Manager Client Upgrade Program. Deployment is targeted to collection SMS00001.    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:55 AM    1936 (0x0790)
    INFO: All client auto upgrade related objects exists. No objects are to be created.    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:55 AM    1936 (0x0790)
    INFO: Successfully added client upgrade packages XX1001EC and XX1001EB to all 31 distribution points from site XX1.    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:55 AM    1936 (0x0790)
    Wait for site control changes for maximum 3600 seconds...    SMS_HIERARCHY_MANAGER    7/07/2014 6:03:55 AM    1936 (0x0790)




    Monday, July 7, 2014 12:24 AM
  • Yes, I know this is an old post, did you get this fixed, if so what was the solution?


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Saturday, March 21, 2015 3:18 PM
    Moderator
  • Same Problem here,

    every Weekend a new Client Package / Configuration Manager Client Upgrade Packages is generated.

    But no solution until now...

    Tuesday, June 16, 2015 7:37 AM
  • Here are the Messages from the hman.log

    INFO: Client upgrade program Configuration Manager Client Upgrade Program in package id XXX00266 exists and its currently disabled. SMS_HIERARCHY_MANAGER 6/13/2015 5:22:50 PM 22752 (0x58E0) WARN: Failed to read all objects for client auto upgrade. Will delete and re-configure objects for client auto-deployment. SMS_HIERARCHY_MANAGER 6/13/2015 5:22:50 PM 22752 (0x58E0) Status for client upgrade program deletion is 0

    SMS_HIERARCHY_MANAGER 6/13/2015 5:22:50 PM 22752 (0x58E0) Status for client upgrade package deletion is 0 

    SMS_HIERARCHY_MANAGER 6/13/2015 5:33:19 PM 22752 (0x58E0) Wait for message forwarding notification timed out. SMS_HIERARCHY_MANAGER 6/13/2015 6:12:15 PM 23716 (0x5CA4) Wait for message forwarding notification timed out. SMS_HIERARCHY_MANAGER 6/13/2015 6:12:15 PM 8128 (0x1FC0) Wait for Site Reassign notification timed out. SMS_HIERARCHY_MANAGER 6/13/2015 6:12:15 PM 29764 (0x7444) Waiting for CFD changes for maximum 3600 seconds... SMS_HIERARCHY_MANAGER 6/13/2015 6:12:15 PM 8128 (0x1FC0) *** exec dbo.spDBMONGetRunningQueries SMS_HIERARCHY_MANAGER 6/13/2015 6:31:54 PM 30860 (0x788C) ***

    [HYT00][0][Microsoft][SQL Server Native Client 11.0]Query timeout expired SMS_HIERARCHY_MANAGER 6/13/2015 6:31:54 PM 30860 (0x788C) Failed to capture current running queries. It will retry in next polling cycle. SMS_HIERARCHY_MANAGER 6/13/2015 6:31:54 PM 30860 (0x788C) running queries will be polled in 600 seconds... SMS_HIERARCHY_MANAGER 6/13/2015 6:31:54 PM 30860 (0x788C) running queries will be polled in 600 seconds... SMS_HIERARCHY_MANAGER 6/13/2015 6:31:54 PM 30860 (0x788C) running queries will be polled in 600 seconds... SMS_HIERARCHY_MANAGER 6/13/2015 6:31:54 PM 30860 (0x788C) *** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Query timeout expired SMS_HIERARCHY_MANAGER 6/13/2015 6:33:19 PM 22752 (0x58E0) Status for full client package deletion is 3 SMS_HIERARCHY_MANAGER 6/13/2015 6:33:19 PM 22752 (0x58E0) INFO: All objects related to client auto upgrade are removed. SMS_HIERARCHY_MANAGER 6/13/2015 6:33:19 PM 22752 (0x58E0) INFO: Recreating all objects related to client auto upgrade. SMS_HIERARCHY_MANAGER 6/13/2015 6:33:19 PM 22752 (0x58E0) INFO: Successfully created full client package BXX00267. SMS_HIERARCHY_MANAGER 6/13/2015 6:33:19 PM 22752 (0x58E0)

    Wednesday, June 17, 2015 6:38 AM
  • The error is clear, there is a problem with your SQL server setup.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Wednesday, June 17, 2015 9:35 AM
    Moderator
  • I also think that the Problem is located on the SQL Server e.g. Backup. The Error only occurs on the Weekend, the only think is that at this time no backup process or something else is runing.
    Wednesday, June 17, 2015 10:01 AM
  • How exactly are you backing up CM12?

    BTW, I generally recommend daily backups.


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Wednesday, June 17, 2015 2:26 PM
    Moderator
  • The Customer back up the Server with Maintanence Task and also on Weekend with additional Backup Software
    Friday, June 19, 2015 7:37 AM
  • The Customer back up the Server with Maintanence Task and also on Weekend with additional Backup Software
    The CM12 maintenance task will not cause this issue. What exactly is the additional backup software? Do these error coincide with the other backup software? How exactly is the other backup software backing up SQL server?

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Friday, June 19, 2015 10:21 AM
    Moderator
  • Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Saturday, August 22, 2015 3:33 PM
    Moderator