Package has multiple "SMS Distribution Manager" entries on DP it is not published to.

I have an issue with packages seeming to deploy to DPs they are not being published to.
We have an aging SCCM 2007 system, which is currently being wound down, so we can migrate to Config Manager 2012.
The 2007 system currently has 3 servers acting as DPs - one for general software distribution (DP1), one for OSD deployments (DP2) and one for Patch Deployment (DP3).
DP settings for each package are configured so that general software packages are only published to DP1, all packages related to OSD are only published to DP2, and all Software Updates packages are only published to DP3.
For historical reasons, DP1 is also a  secondary site server, however, this now manages site boundaries for the full estate, prior to migration to SCCM 2012
I have just returned from a very pleasant annual leave to find that DP1 is flooded with site status messages for the SMS_DISTRIBUTION_MANAGER component; these are repetitions of the same three messages:
"SMS Distribution Manager is beginning to process package ..."
"SMS Distribution Manager is starting to distribute package ..."
"SMS Distribution Manager successfully processed package ..."
The package in question is an OS Image, which is only published to DP2. I am at a loss to understand why it is continually trying to publish to DP1 (over 33,000 entries for this component as I write this)
Note that these messages are "information" level messages, not errors, but are causing the Site Status for DP1 to continually "red flag"
Are there any logs etc I can check on this server to debug and diagnose why this rogue package is trying to process itself on this server? And any steps I can take to kill this?
Thanks
Stan

Looking at the error message "The Network Adapter could not establish the connection" , It appears hostname and port may be incorrect. Review the targets.xml under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\emd and
emoms.properties under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\config folder to make sure host ( sap_solman) and port (1527) are correct.
As far as setting the environment variables goes, you can go to control panel -> system -> advanced -> environment variables and set the ORACLE_HOME and ORACLE_SID
-Ramesh

Similar Messages

  • Contacts with Multiple Backup Assistant + Contacts Entries

    I have read others with these same issues.  Unfortunately, the responses they are getting have to do with having multiple contacts and joining those contacts.  That is not the issue.  The issue is that each contact has MULTIPLE Backup Assistant + Contact entries.  Meaning, when you you start typing a name to send a text message to, it shows you multiple phone numbers for that person (only, they are all the same phone number).  For example, if I start typing Zoe, it will show you contacts that match, it will have Zoe 555-555-5555 listed 6, 7, 8, or more times.  But wait, that is the home number, how you keep scrolling them until you get to the mobile number which is also listed 6, 7, 8 or more times.  When you go into you contacts and select Zoe, and then go to Edit, you see why - There are 6, 7, 8 or more Backup Assistant + Contacts entries!!!  These duplicates are what we are wanting to know how to remove.  My daughter has only one phone number, but when I click on the her picture in the favorite contacts widget, it shows 2 and they are both the same.  Even the BAL #225 shows up EIGHT times!!!!!   When you go online (to the Backup Assistant), they are all listed there too.  HELP!!!!!!!

    I have no prblem syncing multiple mobile numbers so I don't think it's a universal issue with iOS. The only difference I see is I am using CardDav instead of using the Exchange option. Have you tried it that way? You can urn off contacts in the Exchange account and add the CardDav account separately.

  • Distribution Manager failed to process package triggers an update of the packages

    Hi all,
    we have randomly following issue:
    SCCM 2012 Sp1 CAS, takes a snapshot of a Windows update package in the morning (not sure how the frequency of this check is done). If for any reason it fails, SCCM automatically redistributes the package to all sites. This happened this morning again for 5
    Windows updates packages. You understand that this means GB sent to all Secondary sites (66) with an useles amount of data sent out.
    From the Status messages I see
    Information Milestone RC0 06.11.2014 07:12:11 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2300 Distribution Manager is beginning to process package "SUP-2014.09" (package ID = RC00017B).
    Then lot of updates lists with comment taking a snapshot and finally
    Error Milestone RC0 06.11.2014 07:12:29 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2302 Distribution Manager failed to process package "SUP-2014.09" (package ID = RC00017B).    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.
    This triggers immediately an update of all DPs
    Information Milestone RC0 06.11.2014 07:43:52 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2304 Distribution Manager is retrying to distribute package "RC00017B".    Wait to see if the package is successfully distributed on the retry.
    Any idea
    How this can be avoided, since nobody changed the package and we suppose it was a temp connection issue between the CAS and the package repository server
    If this check can be set up to once a week for instance or even less?
    Thanks,
    Marco

    Hi Daniel,
    thanks for the prompt answer. Actually I saw it yesterday at least for 1 package (the last one). The error is generate by SQL killing a task 
    Adding these contents to the package RC00010D version 347.
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:23
    7796 (0x1E74)
    Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER
    06.11.2014 07:12:23 3652 (0x0E44)
    *** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 152) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
    5460 (0x1554)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=5460 GMTDATE=jeu. nov. 06 06:12:25.422 2014 ISTR0="SUP-2012.Q4" ISTR1="RC000068" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC000068"
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
    5460 (0x1554)
    Failed to process package RC000068 after 0 retries, will retry 100 more times
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
    5460 (0x1554)
    Exiting package processing thread. SMS_DISTRIBUTION_MANAGER
    06.11.2014 07:12:25 5460 (0x1554)
    Used 4 out of 5 allowed processing threads.
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:26
    3300 (0x0CE4)
    Starting package processing thread, thread ID = 0x894 (2196)
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
    3300 (0x0CE4)
    Used all 5 allowed processing threads, won't process any more packages.
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
    3300 (0x0CE4)
    Sleep 1828 seconds... SMS_DISTRIBUTION_MANAGER
    06.11.2014 07:12:27 3300 (0x0CE4)
    STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=2196 GMTDATE=jeu. nov. 06 06:12:27.716 2014 ISTR0="SUP-2014.M05" ISTR1="RC00011D" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC00011D"
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
    2196 (0x0894)
    Start updating the package RC00011D... SMS_DISTRIBUTION_MANAGER
    06.11.2014 07:12:27 2196 (0x0894)
    CDistributionSrcSQL::UpdateAvailableVersion PackageID=RC00011D, Version=14, Status=2300
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
    2196 (0x0894)
    *** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 154) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
    1424 (0x0590)
    Taking package snapshot for package RC00011D
    SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
    2196 (0x0894)
    Now as I mentioned it was probably an SQL (more likely) or networ issue, however the question was more about how to avoid that. Finally the packages were not changed and if possible I would avoid any automatic SCCM action on packages unless an operator manually
    triggers them.
    I didn't see any error today, so it should not be a configuration issue.
    Is this possible?

  • Multiple duplicate Configuration Manager Client (Upgrade) Packages

    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!

    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)

  • SQL Server deadlocks when distribution manager is updating content

    Hi
    I have a ConfigMgr 2012 environment which consists of a single Primary Site running on SQL Server 2008 R2 SP2 CU8. The environment has been upgraded to SP1 CU3 and I'm noticing that the following deadlock error is occasionally being logged in distmgr.log
    when a package or application is distributed or updated on all distribution points. After the deadlock ends the content successfully distributes.
    An extract of the error from distmgr.log is below
    user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (LABCM01.lab.local) is submitting SDK changes from site(LAB) SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:46 PM 11952 (0x2EB0)
    *** IF NOT EXISTS (select 1 from vSMS_SC_SysResUse_Properties where ID = 72057594037927944 and Name = N'AvailableContentLibDrivesList' ~) insert into vSMS_SC_SysResUse_Properties (ID, Name, Value1, Value2, Value3) values (72057594037927944, N'AvailableContentLibDrivesList', N'FFEDC', N'', 0)~ ELSE update vSMS_SC_SysResUse_Properties set ID = 72057594037927944, Name = N'AvailableContentLibDrivesList', Value1 = N'FFEDC', Value2 = N'', Value3 = 0 where ID = 72057594037927944 and Name = N'AvailableContentLibDrivesList' SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:47 PM 1432 (0x0598)
    *** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 115) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. : spUpdateSiteControl SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:47 PM 1432 (0x0598)
    CSCItem_Base_Source::UpdateItem: Failed to save item (["Display=\\LABCM01.lab.local\"]MSWNET:["SMS_SITE=LAB"]\\LABCM01.lab.local\,SMS Distribution Point) properties SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:47 PM 1432 (0x0598)
    CSiteSettings::SubmitChanges: Failed to update item(["Display=\\LABCM01.lab.local\"]MSWNET:["SMS_SITE=LAB"]\\LABCM01.lab.local\,SMS Distribution Point) SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:47 PM 1432 (0x0598)
    CSiteSettings::SubmitDeltaSCFToDatabase:Failed to submit changes made from (LAB) SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:47 PM 1432 (0x0598)
    CSiteControlEx::SubmitDeltaSCFFromServerComponent:Failed to submit site control file changes made by componenet SMS_DISTRIBUTION_MANAGER SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:47 PM 1432 (0x0598)
    user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (LABCM01.lab.local) is submitting SDK changes from site(LAB) SMS_DISTRIBUTION_MANAGER 3/10/2013 2:08:47 PM 1432 (0x0598)
    Any ideas as to why the occasional deadlocks are occurring? 
    Cheers
    Sam

    Thanks guys, I've managed to capture a deadlock using SQL Profiler and the graph is below.
    Additionally the deadlock XML output is below
    <deadlock-list>
    <deadlock victim="process769288">
    <process-list>
    <process id="process769288" taskpriority="0" logused="1476" waitresource="KEY: 8:72057594111983616 (47c4361ec2ad)" waittime="484" ownerId="273355729" transactionname="user_transaction" lasttranstarted="2013-10-08T21:03:59.523" XDES="0x10b357270" lockMode="U" schedulerid="2" kpid="14220" status="suspended" spid="147" sbid="0" ecid="0" priority="0" trancount="2" lastbatchstarted="2013-10-08T21:03:59.527" lastbatchcompleted="2013-10-08T21:03:59.527" clientapp="SMS_DISTRIBUTION_MANAGER" hostname="SHDEPLOY2012" hostpid="4004" loginname="NT AUTHORITY\SYSTEM" isolationlevel="read committed (2)" xactid="273355729" currentdb="8" lockTimeout="4294967295" clientoption1="671287392" clientoption2="128056">
    <executionStack>
    <frame procname="CM_LAB.dbo.spUpdateSiteControl" line="12" stmtstart="622" stmtend="1400" sqlhandle="0x0300080041e141055d1bc40049a200000100000000000000">
    MERGE INTO SiteControl AS T
    USING (
    SELECT @SiteCode AS SiteCode, GETUTCDATE() AS DateLastModified
    ) AS S(SiteCode, DateLastModified)
    ON S.SiteCode = T.SiteCode
    WHEN MATCHED THEN
    UPDATE SET T.DateLastModified = S.DateLastModified
    WHEN NOT MATCHED THEN
    INSERT (SiteCode, DateLastModified)
    VALUES(S.SiteCode, S.DateLastModified); </frame>
    <frame procname="CM_LAB.dbo.tr_SC_SysResUse_Property_ins_upd_del" line="22" stmtstart="1594" stmtend="1672" sqlhandle="0x03000800a1e81749c924c40049a200000000000000000000">
    EXEC spUpdateSiteControl @SiteCode </frame>
    <frame procname="CM_LAB.dbo.tr_vSMS_SysResUse_Properties_upd" line="12" stmtstart="728" stmtend="1374" sqlhandle="0x03000800c63fcf7aa431c40049a200000000000000000000">
    update rel
    set rel.Value1=ins.Value1,
    rel.Value2=ins.Value2,
    rel.Value3=ins.Value3
    from SC_SysResUse_Property as rel
    inner join inserted as ins on rel.Name=ins.Name and rel.SysResUseID=ins.ID
    where rel.Value1!=ins.Value1 or rel.Value2!=ins.Value2 or rel.Value3!=ins.Value3 </frame>
    <frame procname="adhoc" line="3" stmtstart="228" sqlhandle="0x02000000a88e68210a5e17dbd208c883c5925dc10fd661eb">
    UPDATE [vSMS_SC_SysResUse_Properties] set [ID] = @1,[Name] = @2,[Value1] = @3,[Value2] = @4,[Value3] = @5 WHERE [ID]=@6 AND [Name]=@7 </frame>
    <frame procname="adhoc" line="3" stmtstart="586" stmtend="1026" sqlhandle="0x0200000089cc65023756c15d75189d92931f875bffb8980b">
    update vSMS_SC_SysResUse_Properties set ID = 72057594037927953, Name = N&apos;AvailableContentLibDrivesList&apos;, Value1 = N&apos;DDC&apos;, Value2 = N&apos;&apos;, Value3 = 0 where ID = 72057594037927953 and Name = N&apos;AvailableContentLibDrivesList&apos; </frame>
    </executionStack>
    <inputbuf>
    IF NOT EXISTS (select 1 from vSMS_SC_SysResUse_Properties where ID = 72057594037927953 and Name = N&apos;AvailableContentLibDrivesList&apos;
    ) insert into vSMS_SC_SysResUse_Properties (ID, Name, Value1, Value2, Value3) values (72057594037927953, N&apos;AvailableContentLibDrivesList&apos;, N&apos;DDC&apos;, N&apos;&apos;, 0)
    ELSE update vSMS_SC_SysResUse_Properties set ID = 72057594037927953, Name = N&apos;AvailableContentLibDrivesList&apos;, Value1 = N&apos;DDC&apos;, Value2 = N&apos;&apos;, Value3 = 0 where ID = 72057594037927953 and Name = N&apos;AvailableContentLibDrivesList&apos;
    </inputbuf>
    </process>
    <process id="process8fa5a748" taskpriority="0" logused="3160" waitresource="KEY: 8:72057595436728320 (d51fef0ca10c)" waittime="206" ownerId="273355664" transactionname="user_transaction" lasttranstarted="2013-10-08T21:03:59.493" XDES="0x12b176e90" lockMode="U" schedulerid="4" kpid="3812" status="suspended" spid="102" sbid="0" ecid="0" priority="0" trancount="2" lastbatchstarted="2013-10-08T21:03:59.800" lastbatchcompleted="2013-10-08T21:03:59.800" clientapp="SMS_DISTRIBUTION_MANAGER" hostname="SHDEPLOY2012" hostpid="4004" loginname="NT AUTHORITY\SYSTEM" isolationlevel="read committed (2)" xactid="273355664" currentdb="8" lockTimeout="4294967295" clientoption1="671156320" clientoption2="128056">
    <executionStack>
    <frame procname="adhoc" line="1" sqlhandle="0x02000000dd107007806e2488472b44e8e2cb235ae39d3ffb">
    delete [vSMS_SC_SysResUse_Properties] where ID=72057594037927955 and Name not in (N&apos;ADSiteName&apos;, N&apos;AllowInternetClients&apos;, N&apos;AvailableContentLibDrivesList&apos;, N&apos;AvailablePkgShareDrivesList&apos;, N&apos;BindPolicy&apos;, N&apos;BITS download&apos;, N&apos;CertificateContextData&apos;, N&apos;CertificateExpirationDate&apos;, N&apos;CertificateFile&apos;, N&apos;CertificatePFXData&apos;, N&apos;CertificateType&apos;, N&apos;DPDrive&apos;, N&apos;DPMonEnabled&apos;, N&apos;DPMonPriority&apos;, N&apos;DPMonSchedule&apos;, N&apos;DPShareDrive&apos;, N&apos;IdentityGUID&apos;, N&apos;IISConfigCheckTimeInterval&apos;, N&apos;InstallInternetServer&apos;, N&apos;IPSubnets&apos;, N&apos;IPv6Prefixes&apos;, N&apos;IsActive&apos;, N&apos;IsAnonymousEnabled&apos;, N&apos;IsMulticast&apos;, N&apos;IsPXE&apos;, N&apos;LastIISConfigCheckTime&apos;, N&apos;MinFreeSpace&apos;, N&apos;PreStagingAllowed&apos;, N&apos;PXEPassword&apos;, N&apos;RemoveWDS&apos;, N&apos;ResponseDelay&apos;, N&apos;Server Remote Name&apos;, N&apos;Server Remote Public Name&apos;, N&apos;SslState&apos;, N&apos;SupportUnknownMachines&apos;, N&apos;UdaSetting&apos;) </frame>
    </executionStack>
    <inputbuf>
    delete [vSMS_SC_SysResUse_Properties] where ID=72057594037927955 and Name not in (N&apos;ADSiteName&apos;, N&apos;AllowInternetClients&apos;, N&apos;AvailableContentLibDrivesList&apos;, N&apos;AvailablePkgShareDrivesList&apos;, N&apos;BindPolicy&apos;, N&apos;BITS download&apos;, N&apos;CertificateContextData&apos;, N&apos;CertificateExpirationDate&apos;, N&apos;CertificateFile&apos;, N&apos;CertificatePFXData&apos;, N&apos;CertificateType&apos;, N&apos;DPDrive&apos;, N&apos;DPMonEnabled&apos;, N&apos;DPMonPriority&apos;, N&apos;DPMonSchedule&apos;, N&apos;DPShareDrive&apos;, N&apos;IdentityGUID&apos;, N&apos;IISConfigCheckTimeInterval&apos;, N&apos;InstallInternetServer&apos;, N&apos;IPSubnets&apos;, N&apos;IPv6Prefixes&apos;, N&apos;IsActive&apos;, N&apos;IsAnonymousEnabled&apos;, N&apos;IsMulticast&apos;, N&apos;IsPXE&apos;, N&apos;LastIISConfigCheckTime&apos;, N&apos;MinFreeSpace&apos;, N&apos;PreStagingAllowed&apos;, N&apos;PXEPassword&apos;, N&apos;RemoveWDS&apos;, N&apos;ResponseDelay&apos;, N&apos;Server Remote Name&apos;, N&apos;Server Remote Public Name&apos;, N&apos;SslState&apos;, N&apos;SupportUnknownMachines&apos;, N&apos;UdaSetting&apos;) </inputbuf>
    </process>
    </process-list>
    <resource-list>
    <keylock hobtid="72057594111983616" dbid="8" objectname="CM_LAB.dbo.SiteControl" indexname="SiteControl_PK" id="lockf8de5880" mode="X" associatedObjectId="72057594111983616">
    <owner-list>
    <owner id="process8fa5a748" mode="X"/>
    </owner-list>
    <waiter-list>
    <waiter id="process769288" mode="U" requestType="wait"/>
    </waiter-list>
    </keylock>
    <keylock hobtid="72057595436728320" dbid="8" objectname="CM_LAB.dbo.SC_SysResUse_Property" indexname="SC_SysResUse_Property_AK" id="lock187f4f680" mode="U" associatedObjectId="72057595436728320">
    <owner-list>
    <owner id="process769288" mode="U"/>
    </owner-list>
    <waiter-list>
    <waiter id="process8fa5a748" mode="U" requestType="wait"/>
    </waiter-list>
    </keylock>
    </resource-list>
    </deadlock>
    </deadlock-list>
    Any ideas? Again this only occasionally happens when content is updated on the distribution points. 
    Thanks
    Sam

  • Software packages are not distribution to a SCCM 2007 secondary site - not decompressing

    Hello,
    I have a secondary site in my SCCM 2007 which is not de-cpompressing packages.
    the packages are coming down to the 'SMSPKG' folder as .pkg files, but it is not de-compressing into the SMSPKGS$ folder.
    I updates one of the smaller packages to re-push the package down and this is what I have seen in the despool.log on the child site
    STATMSG: ID=4407 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DESPOOLER" SYS=P-DC-PKF-CMDP01 SITE=PKF PID=2304 TID=1260 GMTDATE=Wed Apr 23 13:58:49.908 2014 ISTR0="PR100155" ISTR1="162" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PR100155" SMS_DESPOOLER 23/04/2014 14:58:49 1260 (0x04EC)
    Received package PR100155 version 162 SMS_DESPOOLER 23/04/2014 14:58:49 1260 (0x04EC)
    Drive D is not a fixed drive on \\servername, therefore it cannot be used as the compressed package storage direcotry, use the default directory SMS_DESPOOLER 23/04/2014 14:58:49 1260 (0x04EC)
    Use drive S for storing the compressed package. SMS_DESPOOLER 23/04/2014 14:58:49 1260 (0x04EC)
    Package PR100155 (version 161) exists in the distribution source, save the newer version (version 162). SMS_DESPOOLER 23/04/2014 14:58:50 1260 (0x04EC)
    Waiting for ready instruction file.... SMS_DESPOOLER 23/04/2014 14:58:54 2952 (0x0B88)
    Stored Package PR100155. Stored Package Version = 162 SMS_DESPOOLER 23/04/2014 14:58:54 1260 (0x04EC)
    Forward package status for pkg PR100155 to site PR1 SMS_DESPOOLER 23/04/2014 14:58:54 1260 (0x04EC)
    STATMSG: ID=4400 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DESPOOLER" SYS=P-DC-PKF-CMDP01 SITE=PKF PID=2304 TID=1260 GMTDATE=Wed Apr 23 13:58:54.978 2014 ISTR0="PR100155" ISTR1="\\servername\S$\SMSPKG\PR100155.PCK"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="PR100155" SMS_DESPOOLER 23/04/2014 14:58:54 1260 (0x04EC)
    This is happening for all packages on this child site so its not really package related, please could someone provide some insight to what I can do to fix this.
    thanks
    Nazir

    There should be  some more entries in the log file between use Drive and forward package status.
    did you check the status of the package from system status--SM_distribution manager ? any clue 
    can you try preloading one package and see what does it say ? instructions here
    http://blogs.technet.com/b/configurationmgr/archive/2009/05/07/configmgr-2007-the-preload-package-tool-preloadpkgonsite-exe-explained.aspx
    Eswar Koneti | Configmgr blog:
    www.eskonr.com | Linkedin: Eswar Koneti
    | Twitter: Eskonr

  • SCCM Distribution Manager Failed to access source directory...

    Hi guys....
    Im in a desperate position at the moment. I joined a small company  a short while ago as an infrastructure engineer but have never had hands on experience with sccm 2012. The guy I was working with left
    at short notice and never had time to show me the system.
    I am now trying to image some new systems but for some reason I keep getting the above error message. I have checked share and NTFS permissions and ensured that all the SMS accounts have a minimum of modify
    if not full rights including the local administrator account. The drives also have sufficient disk space. I am finding it impossible to update the distribution point (even though the wizards says successful).
    Each time i try to run the task from the client I get Failed to run Task sequence, "This task sequence cannot be run because the program files for DI100005 cannot be located on a distribution point."
    I have also ensured that Site system installation account is set to
    Use the site server's computer account to install the site system
    Please can someone point me in the right direction and help me to resolve this issue.
    Many Thanks

    Hi Torsten, 
    I have checked the log but not really sure what i am looking for. It tells me that a task has filed but not sure why?  Is SMS_Distribution _Manager a generic name used for whatever account its supposed to be using? 
    Here is a snippet of the log from this morning. If you could please decypher it for me I would be very grateful. 
    ---------Log Start ----------
    Found package properties updated notification for package 'DI100005'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:01.967-60><thread=7128 (0x1BD8)>
    Found notification for package 'DI100005'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:06.969-60><thread=7128 (0x1BD8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.032-60><thread=7128 (0x1BD8)>
    ~Starting package processing thread, thread ID = 0xCC0 (3264)  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.550-60><thread=7128 (0x1BD8)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.552-60><thread=7128 (0x1BD8)>
    STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:07.720 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
    ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.720-60><thread=3264 (0xCC0)>
    Start updating the package DI100005...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.721-60><thread=3264 (0xCC0)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=14, Status=2300  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.728-60><thread=3264 (0xCC0)>
    Taking package snapshot for package DI100005 from source \\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.115-60><thread=3264 (0xCC0)>
    ~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.120-60><thread=3264 (0xCC0)>
    ~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.].  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.189-60><thread=3264 (0xCC0)>
    ~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.190-60><thread=3264 (0xCC0)>
    ~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.191-60><thread=3264 (0xCC0)>
    Failed to get the content library path.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
    SnapshotPackage() failed. Error = 0x80004005  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
    STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.201 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim" ISTR1="Boot image
    (x64)" ISTR2="DI100005" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=13, Status=2302  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.363 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
    ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.363-60><thread=3264 (0xCC0)>
    ~Failed to process package DI100005 after 0 retries, will retry 100 more times  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.364-60><thread=3264 (0xCC0)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.381-60><thread=3264 (0xCC0)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.018-60><thread=8392 (0x20C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.566-60><thread=7128 (0x1BD8)>
    ~Sleep 1826 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.591-60><thread=7128 (0x1BD8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.611-60><thread=7128 (0x1BD8)>
    ~Sleep 1821 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.621-60><thread=7128 (0x1BD8)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:42.490-60><thread=8392 (0x20C8)>
    Found package properties updated notification for package 'DI100004'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:47.491-60><thread=7128 (0x1BD8)>
    Found notification for package 'DI100004'  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.425-60><thread=7128 (0x1BD8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.450-60><thread=7128 (0x1BD8)>
    ~Starting package processing thread, thread ID = 0xE0C (3596)  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.950-60><thread=7128 (0x1BD8)>
    ~Sleep 585 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.952-60><thread=7128 (0x1BD8)>
    STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.072 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
    ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.072-60><thread=3596 (0xE0C)>
    Start updating the package DI100004...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.073-60><thread=3596 (0xE0C)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=5, Status=2300  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.074-60><thread=3596 (0xE0C)>
    Taking package snapshot for package DI100004 from source \\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.104-60><thread=3596 (0xE0C)>
    ~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.108-60><thread=3596 (0xE0C)>
    ~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.].  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
    ~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
    ~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.122-60><thread=3596 (0xE0C)>
    Failed to get the content library path.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
    SnapshotPackage() failed. Error = 0x80004005  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
    STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.131 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim" ISTR1="Boot image
    (x86)" ISTR2="DI100004" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=4, Status=2302  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.132-60><thread=3596 (0xE0C)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.221 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
    ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004"  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.221-60><thread=3596 (0xE0C)>
    ~Failed to process package DI100004 after 0 retries, will retry 100 more times  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.439-60><thread=8392 (0x20C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.965-60><thread=7128 (0x1BD8)>
    ~Sleep 580 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.966-60><thread=7128 (0x1BD8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.979-60><thread=7128 (0x1BD8)>
    ~Sleep 575 seconds...  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.980-60><thread=7128 (0x1BD8)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:42:35.263-60><thread=3480 (0xD98)>
    ---------Log Finish ----------
    Cheers, 
    Aaron

  • Distribution manager failed to connect to the distribution point

    After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
    I see the following error.
    source: SMS Server
    Component: SMS_DISTRIBUTION_MANAGER
    message id 2391
    Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
    The firewall is not enabled. 
    wbemtest is able to connect to the remote server that has the distribution point role installed.
    The network access account is working.
    How do I fix this?

    but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
    I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
    I have the same issue as described above.
    The IT guys from LukOIL

  • Distribution Manager Failed To Access The Source Directory

    Hello All,
    I have this issue distributing content to my Distribution Points for months now. I keep running into this error below:
    Distribution Manager Failed to Access the source directory (\\share\folder\file.wim)
    Possible Cause: Distribution Manager does not have sufficient rights to the source directory.
    Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.
    Possible Cause: There is not enough disk space available on the site server.
    Solution: Verify that there is enough free disk space available on the site server.
    I checked the distmgr.log file and received these messages: 
    GetTempFileNameA failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    CFileLibrary::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    CContentDefinition::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    Failed to add the file. Please check if this file exists.    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    SnapshotPackage() failed. Error = 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    Failed to take snapshot of package CSU0006A    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    There is enough space on the site server and the site server has full control over the source directory. I wish I can give you more information but I'm hoping this is enough info to get some assistance. If more information is needed please let me know!

    We usually give the DP's computer account and the site server computer account read access to these shares in our environment.
    ... which is not enough for drivers and updates (as there will also files be added).
    Torsten Meringer | http://www.mssccmfaq.de
    ... And for capture Image too if your capture destination points on that share

  • DP's have Warning "Failed to retrieve the package list on the distribution point" - How to Clear it?

    All but one of my DP's (A new one I just created) have this Warning Message:  "Failed to retrieve the package list on the distribution point".  They all seem to be working, I can update and push new content to them.
    When I go to the smsdpmon.log, it has an error for a package, but I've since redistributed it, and it is working fine. (Items below are snips from the smsdpmon.log)
    CContentDefinition::LibraryPackagesWmi: The package data in WMI is not consistent to PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
    CContentDefinition::LibraryPackagesWmi: Package PS10011B can't be found in PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
    CContentDefinition::LibraryPackagesWmi failed; 0x80004005 SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
    Failed to evaluate package PS10011B, Error code 0x80070002 SMS_Distribution_Point_Monitoring 11/16/2013 6:29:50 PM 3920 (0x0F50)
    Since then, after redistributing the package, it clears up the logs... but not the warning in Monitoring:
    Start to evaluate package share for package 'PS10011B' version 0 ... SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
    Package PS10011B is verified successfully SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
    So since everything appears to be working fine, how do I clear out that Warning, so I have nice Green Check Mark Icons in my Monitoring Tab, so when something actually does go wrong, I won't just ignore it since it's always been set to Warning?

    I'll have to review this. The script
    here, alone did not solve the my issue. Interesting that it say I do not have any inconsistencies on any my DP's now, but I run the other one on a single DP, it states I have inconsistencies still.
    $WMIPkgList = Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib | Select -ExpandProperty PackageID | Sort-Object
    $ContentLib = (Get-ItemProperty HKLM:SOFTWARE\Microsoft\SMS\DP).ContentLibraryPath
    $PkgLibPath = ($ContentLib) + "\PkgLib"
    $PkgLibList = (Get-ChildItem $PkgLibPath | Select -ExpandProperty Name | Sort-Object)
    $PkgLibList = ($PKgLibList | ForEach-Object {$_.replace(".INI","")})
    $PksinWMIButNotContentLib = Compare-Object -ReferenceObject $WMIPkgList -DifferenceObject $PKgLibList -PassThru
    ##### section 1 #######################
    Write-Host Items in WMI but not the Content Library
    Write-Host ========================================
    $PksinWMIButNotContentLib
    Foreach ($Pkg in $PksinWMIButNotContentLib){
    Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib -Filter "PackageID = '$Pkg'" | Remove-WmiObject -Confirm
    I wonder if the first script is not looking for INI's whereas the second one is. I verified that the INI's do exist...
    I'll run the second on all of my DP's, remove the left over INI's, and report back again next week on status.
    -Tony

  • All DPs read "Failed to retrieve the package list on the distribution point"...

    About 2 weeks ago all 10 of my DPs started reporting the following warning (roughly 2 weeks after upgrading to R2):
    "Failed to retrieve the package list on the distribution point ["Display=\\<server.FQDN>\"]MSWNET:["SMS_SITE=<code>"]\\<server.FQDN>\. Or the package list in content library doesn't match the one in WMI. Review
    smsdpmon.log for more information about this failure.
    This warning has appeared in my environment once before and I've read a number of posts regarding it. In the previous situation I found the problematic package ID recorded in smsdpmon.log and followed the standard procedure of redistributing and then proceeded
    with a validation check on the affected DP. These steps resolved the issue originally.
    This time around the package ID is not referenced in smsdpmon.log. It had the same error but the ID was not listed. Unfortunately the logs have already rolled over and I forgot to save a copy so I don't have anything to reference. I'm curious if anyone else
    has seen this behavior and what the recommended fix is. 
    As always, appreciate the help!

    I used the following process to clean up these warnings on my DPs:
    Setup content validation checks for each of my affected DPs to run every morning (previously only set to weekends). I did this so when I made a change I could validate whether or not it worked the following day. It would be great if there was a way to force
    these checks manually but I haven't found a method yet.
    After the content validation check completed I filtered through the smsdpmon.log on each affected DP. This revealed the package ID that was causing the issue.
    In my environment the package in question was not needed so I deleted it. If it is required I suspect re-distributing it would work as well.
    At this stage the problem was still not fully resolved for me. Even though I had deleted the package WMI was still inaccurate. I used this script to scrub WMI on all affected DPs and it picked up the problematic package ID:
    http://gallery.technet.microsoft.com/Powershell-script-to-fix-81dc4e69
    My content validation checks are now passing and the warnings are being cleared. YEAH!
    As a final note - After running the PS script Nickolaj posted I ran started seeing dozens of error checks on my packages (Distribution Manager failed to process package "Laptop Drivers" (package ID = XYZ00123).) After doing some research
    I found I was prone to this issue:
    Failed to start DP health monitoring task. In my case the suspect file was called "Microsoft". I moved it to another location and the errors cleared immediately.
    Hope this info is helpful to others!

  • Unable to install Adobe CS5 64 bit package created using Adobe Application Manager on Windows 7 64

    I am unable to install Adobe CS5 64 bit package created using Adobe Application Manager on Windows 7 64 bit.Basically installation rollback on Win 7 64 bit image.
    MSI Log File :-
    Property(S): ProductToBeRegistered = 1
    MSI (s) (5C:D4) [17:59:21:784]: Note: 1: 1708
    MSI (s) (5C:D4) [17:59:21:784]: Product: Adobe_CreativieSuite_5_MNT -- Installation operation failed.
    MSI (s) (5C:D4) [17:59:21:784]: Windows Installer installed the product. Product Name: Adobe_CreativieSuite_5_MNT. Product Version: 1.2.0000. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Installation success or error status: 1603.
    Please let me how to install 64 bit package on Win7 64 bit.
    Thanks in Advance.

    Ok so I downloaded the most current installer CS5.1, My previous installer was version 5.0. It did install fine fully updated to my license version. I just wanted to update in case anyone in the future has a similiar experience. Too bad this advice was not offered by the "experts" here.

  • Looking for Script Exchange-2007: Import-Mailbox Calendar Folder on multiple mailboxes {Distribution Group}

    Hi,
    I'm looking for a PowerShell script which will import a Calendar events into student's mailbox (Calendar). Those students are located in a distribution group and I would like to target the distribution group; I'm trying to simulate what I want to achieve
    in the below code example, I would appreciate if anyone jump in and advise.
    $Users = Import-Csv C:\users.csv | ForEach-Object{Get-DistributionGroup -Identity SC-1213} | Import-Mailbox -Identity $Users -PSTFolderPath c:\Calendar.pst -IncludeFolders '\Calendar' -StartDate -EndDate
    Much appreciated..
    Hussain

    The logic doesn't work unless you are using StartDate and EndDate for the period when you change the item.  As I said above, StartDate and EndDate are not the times when the meeting starts and ends - they are the times that the item was either added
    or modified in the mailbox.  Your filter was trying to pull items that were in the future.
    And as I also said above, if you import a modified item, the original is
    not going to be updated.  You will have a duplicate meeting
    on the calendar.  You would have to remove the original
    and import the updated item if this was how you wished to manage the updates.  This is not nearly as effective as
    sending meeting requests and updating those meetings.
    For example, if we do things the way you are doing them, and we add a "Student Appreciation Bonfire" meeting to the calendar for April 12 at "The Quad", we would do the following:
    On February 1, you get information for the meeting that needs to be imported
    You create this new meeting in the PST calendar - "Student Appreciation Bonfire"; Date April 12, start 8:00 AM, end 12:00 noon; Location The Quad
    You import the PST into everyone's calendar
    You receive a note on March 12 saying the venue has changed to The River Beach, so you update this meeting in your PST
    Since there are other calendar items in the PST, you import the update using StartDate of March 12 and EndDate of March 13 - the date that you changed the item, not the date the item occurs
    At this point, all users have two meetings on their calendar - the original and the update
    If, instead of doing it this way, you create a Student Actvities Calendar mailbox, you would handle it this way:
    On February 1, you get information for the meeting that needs to be imported
    You create this new meeting in the Corporate calendar - "Student Appreciation Bonfire"; Date April 12, start 8:00 AM, end 12:00 noon; Location The Quad
    You invite everyone to the meeting
    You receive a note on March 12 saying the venue has changed to The River Beach, so you update this meeting in that calendar and send out the update
    At this point, all users have only the one meeting on their calendar - the update
    Using the PST as the source for the meetings would work only for items that
    will not be changed - holidays are a good example.

  • I am running Lightroom 6 in conjunction with 64 bit Photoshop CS6. I need to install Camera Raw 9 plus other relevan updates for the Adobe Design and Web Premium CS6 package. Running Adobe Application manager finds the relevant updates but won't download

    I am running Lightroom 6 in conjunction with 64 bit Photoshop CS6. I need to install Camera Raw 9 plus other relevan updates for the Adobe Design and Web Premium CS6 package. Running Adobe Application manager finds the relevant updates but won't download / install them. Clicking the update button results in an error message "Application Manager has stopped working". This is a windows system running 64 bit Windows 7

    update manually:
    pre cc updates:  http://www.adobe.com/downloads/updates/
    cc updates:  http://prodesigntools.com/adobe-cc-updates-direct-links-windows.html
    cc 2014 updates:  win (http://prodesigntools.com/adobe-cc-2014-updates-links-windows.html) / mac (http://prodesigntools.com/adobe-cc-2014-updates-links-mac.html)

  • Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

    We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
    point and failed to connect to remote distribution point"
    Errors on the package transfer log file.
    CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
    CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
    Failed to connect to the DP WMI namespace on the remote DP

    Thanks Sandys for your suggestions.
    i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
    server is unavailable" from both ends.
    error:0x800706ba - The RPC server is unavailable

Maybe you are looking for

  • APS Daemon.exe has encountered a problem and needs to close the computer

    On my Lenovo laptop at home, I am getting a message:  " APS Daemon.exe has encountered a problem and needs to close the computer". This message appears after my computer (lap-top at home)  gets automatically shut down and is restarted by me. I believ

  • How to crete the source system for the SQL Server 2000 to BI 7.1

    Dear All, We want to extract data from  SQL server 2000 data base to BI 7.1 Please provide us the step-by-step procedure to be followed in BI as well as SQL server 2000 BD Thanks & Regards, sarasu

  • Deleting a locked folder

    I have an external hard drive I want to use with time machine so I am cleaning it out. It has a bunch of stuff from my PC that I backed up when I got my iMac. How do I unlock locked folders that I no longer need. I want to delete them. I have tried t

  • Installing Workshop Studio on Vista jdk1.5.0_09

    Hi all, I'm hoping someone who has been through this can help. I've followed all of the instructions on setting the path, tried to run the exe from the console, but nothing works. The installer fails and gives me "invalid runtime". WHen I queried my

  • Query related to obiee 11g cluster

    Hi Gurus, We have setup the cluster envirnment in production. In that envirornment, we can see 1) two console 2) One EM. 3) two analytics In the cluster envirnment, do we have only one EM? Is there anything went wrong in installation? Any response wo