none
Distribution problem RRS feed

  • Question

  • Dear all,

    Since a couple of days there is a problem with replicating Task Sequences and Packages one of my primary child server. The hierarchy exists of a central site with site code NL1 and two primary child sites named NL2 and NL3.

    I see the following in the distmgr.log on the NL2 site:

    Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\A9U81BYH.PKG. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Failed to insert SMS Package NL100024 because SDM Type Content 856a007a-27cf-41f4-bd15-4901cd9e2202 is not present in the CI_Contents table. Will try later. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Cannot update the package NL100024 in the package source, error = 3 SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\K5LYMVN6.PKG. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding these contents to the package NL10002C version 1. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Updated replicated package info for package NL10002C SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Failed to insert SMS Program ID 191 because the referenced program NL100032-* is not present in the PkgPrograms table. Will try later. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Cannot update the package program for package NL10002C in the package source, error = 40 SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\1Q3FJZ61.PKG. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding these contents to the package NL100036 version 1. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Updated replicated package info for package NL100036 SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Failed to insert SMS Program ID 192 because the referenced program NL100032-* is not present in the PkgPrograms table. Will try later. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Cannot update the package program for package NL100036 in the package source, error = 40 SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\EXZGQHKS.PKG. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    StoredPkgVersion (1) of package NL100032. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Distribution Manager will not update the StoredPkgVersion in the Database as Despooler will. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding these contents to the package NL100032 version 1. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content CE8A900B-D7B4-4D65-B59C-BFC84D092966. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 2ACF86C3-908C-4A01-9489-1F39488855EB. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 2ACF86C3-908C-4A01-9489-1F39488855EB. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 2ACF86C3-908C-4A01-9489-1F39488855EB. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 7163EEBF-50D6-4BF2-8014-B169C297EAF8. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content A6D37951-70A6-4300-837D-AB7AF2100D49. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 8AF79ED1-2D93-4F09-A2B0-6839B6F53A1E. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 3427E43D-00D9-4BE9-8103-72A6408F4427. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 770CCC24-DCB5-4E75-8328-468661B78015. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 5862B6D1-1C6C-4795-9FC2-005974964F18. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 5862B6D1-1C6C-4795-9FC2-005974964F18. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Adding content 656FFC0A-E331-4FAA-93FA-22563AF40F74. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Failed to insert SMS Package NL100032 because SDM Type Content 2ACF86C3-908C-4A01-9489-1F39488855EB is not present in the CI_Contents table. Will try later. SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)
    Cannot update the package NL100032 in the package source, error = 3 SMS_DISTRIBUTION_MANAGER 7/17/2009 4:03:06 PM 6980 (0x1B44)

    NL100036 and NL10002C are Task Sequences
    NL100032 is a driver package

    The problem is occuring on the NL2 site only. When looking in the CI_Contents table it is indeed missing rows which are present at the NL3 site.

    I already detached the site and performed a re-install with same site code and fresh DB but the problem persists.

    Thanks!

    Please mark posts as Answered if appropriate.
    • Edited by Jannes12345 Friday, July 17, 2009 2:27 PM typo
    Friday, July 17, 2009 2:23 PM

Answers

  • Hi,

    Today I was on site to investigate the issue further. First look in the status messages of the DP was good, also the log looked okay.

    When investigating the log further I saw several failed attempts at the beginning of the log. Last failed attempt was at 4:12 PM and then eventually a success at 4:13.

     

    So it looks like the issue is solved over time on the same day I detached and re-installed the site. Today I tested multiple distribution scenario’s today, driver package, regular package, update package. All successful including a large batch of 10 packages.

     

    I have no idea what was causing this issue and how it got solved. 


    Please mark posts as Answered if appropriate.
    • Marked as answer by Jannes12345 Wednesday, July 22, 2009 6:54 PM
    Wednesday, July 22, 2009 6:53 PM

All replies

  • Can you update DPs for NL100032?  So that the package ver changes from 1 to 2?  I've seen that kick packages into replicating correctly on SMS03--may still be true for ConfigMgr07.
    Standardize. Simplify. Automate.
    Tuesday, July 21, 2009 12:31 AM
    Moderator
  • You could try to "resync" the child site (drop a file called <SiteCodeOfChildsite>.SHA in objmgr.box of the parent site. Attention: causes a lot of traffic!).
    Tuesday, July 21, 2009 7:39 AM
    Moderator
  • Hi,

    Thanks for the replies.

    @ Sherry
     I updated the distribution point but with no luck.

    @ Torsten
    Have tried that one as well, was indeed generating a lot of traffic and files in replmgr.box but these were processed succesfully. Problem persists.

    My guess is that the driver package is corrupt since this one is also used in the TS which reports the same problem. Tomorrow I will try to create a new driver package to see what happens.

    Thanks!



    Please mark posts as Answered if appropriate.
    Tuesday, July 21, 2009 8:25 AM
  • Hi,

    Today I was on site to investigate the issue further. First look in the status messages of the DP was good, also the log looked okay.

    When investigating the log further I saw several failed attempts at the beginning of the log. Last failed attempt was at 4:12 PM and then eventually a success at 4:13.

     

    So it looks like the issue is solved over time on the same day I detached and re-installed the site. Today I tested multiple distribution scenario’s today, driver package, regular package, update package. All successful including a large batch of 10 packages.

     

    I have no idea what was causing this issue and how it got solved. 


    Please mark posts as Answered if appropriate.
    • Marked as answer by Jannes12345 Wednesday, July 22, 2009 6:54 PM
    Wednesday, July 22, 2009 6:53 PM