SCCM - Permissions Issues or Networking?
Could you give me an idea of which logs would be the most helpful for you to look at and I'll post them up. I've gone thru a long series of logs and status message queries I'm not quite sure which ones would be the best to post first.Rick Don Client Systems Administrator Palm Beach County Sheriff's Office
January 24th, 2012 3:38pm

1) People couldn't PXE; someone attempted to remove the roles from the MDT Server and then reinstall but we keep getting errors that say we can't copy the files over to the D:\SMS directory that we don't have rights or sometimes instead it will say that the network path isn't found (mind you I'm pinging the MDT machine while it's saying it can't find it). 2) Computers that should have downloaded their Software Updates are sitting there on that first software update just saying downloaded. Checking the logs they keep saying the download location is "empty". 3) Some of our packages we can update and some we can't where we keep getting a "can't access either the source or the distribution point"... Well, when the first DP is the SCCM Server itself that leads me to believe I've got a networking issue but still... -> 1): smspxe.log from the PXE service point. Plus the log where it says: "errors that say we can't copy the files over to ..." -> 2): the logfile were it says "the download location is "empty"." -> 3): distmgr.log No need to post hundreds of lines from various logfiles. Just pick the parts that contain errors.Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2012 7:52am

SiteComp.log from the SCCM primary server (where is says it can't copy the files): Note that I had a ping -t running the entire time, never timed out, was always able to find the MDT server where we are attempting to install PXE. There is NO smspxe.log on the MDT machine that we are trying to install the PXE service point back onto. Drive 'D:\' is the best drive for the SMS installation directory. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) There is not a connection to the install drive. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Attempting to connect to install drive '\\MDT-SERVER\D$\'. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Testing connectivity to this path using NAL INetworkObject::IsAccessible()... SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) NAL INetworkObject::IsAccessible() succeeded. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Making this new connection the current install drive connection. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) The install drive path is accessible. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Successfully created and to set permissions on the SMS installation directory. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Created SMS installation directory D:\SMS. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Wrote HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Identification key to server's registry. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Wrote HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing key to server's registry. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Installation complete. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=1026 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:32.128 2012 ISTR0="\\MDT-SERVER" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=1040 SEV=I LEV=D SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:32.237 2012 ISTR0="\\MDT-SERVER" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=1046 SEV=I LEV=D SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:32.258 2012 ISTR0="\\MDT-SERVER" ISTR1="6.1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=1051 SEV=I LEV=D SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:33.436 2012 ISTR0="\\MDT-SERVER" ISTR1="D:\SMS" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=554 SEV=I LEV=D SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:33.481 2012 ISTR0="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Identification" ISTR1="MDT-SERVER" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=554 SEV=I LEV=D SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:33.621 2012 ISTR0="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing" ISTR1="MDT-SERVER" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=1027 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:33.687 2012 ISTR0="\\MDT-SERVER" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Testing connectivity to this server using NAL INetworkObject::IsAccessible()... SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) NAL INetworkObject::IsAccessible() succeeded. The server is accessible. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Installing component SMS_EXECUTIVE... SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) LogEvent(): Successfully logged Event to NT Event Log (4, 13, 1073742838, (null)). SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) STATMSG: ID=1014 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_EXECUTIVE" SYS=MDT-SERVER SITE=HQ2 PID=4020 TID=8516 GMTDATE=Tue Jan 24 12:48:33.954 2012 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) Writing component specific registry values. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:33 AM 8516 (0x2144) The "\\MDT-SERVER\D$\SMS" directory has 54534942720 bytes free out of 370287833088 total bytes. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) The "\\MDT-SERVER\ADMIN$" directory has 10417864704 bytes free out of 68157435904 total bytes. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) 9312184 bytes are required in the "\\MDT-SERVER\D$\SMS" directory for this component's files. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) 2020519 bytes are required in the "\\MDT-SERVER\ADMIN$" directory for this component's files. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\scripts\00000409\perf\SMS_EXECUTIVE.h. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\scripts\00000409\perf\SMS_EXECUTIVE.ini. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\scripts\00000409\perf\SMS_EXECUTIVE_smscfg.ini. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\scripts\StatusReportingCtrl.ct0. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\bin\i386\smsexec.exe. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\bin\i386\baseutil.dll. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\bin\i386\smssvreh.dll. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\bin\i386\dumpexcp.exe. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:48:34 AM 8516 (0x2144) Could not copy file E:\Microsoft Configuration Manager\bin\i386\baseobj.dll to \\MDT-SERVER\D$\SMS\bin\i386\baseobj.dll: Could not create directory \\MDT-SERVER\D$\SMS\bin\i386. The operating system reported error 64: The specified network name is no longer available. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:50:11 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\bin\i386\basesql.dll. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:50:11 AM 8516 (0x2144) Could not copy file E:\Microsoft Configuration Manager\bin\i386\basesvr.dll to \\MDT-SERVER\D$\SMS\bin\i386\basesvr.dll: Could not create directory \\MDT-SERVER\D$\SMS\bin\i386. The operating system reported error 64: The specified network name is no longer available. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:51:35 AM 8516 (0x2144) Installed file \\MDT-SERVER\D$\SMS\bin\i386\mfc80.dll. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:51:35 AM 8516 (0x2144) Could not copy file E:\Microsoft Configuration Manager\bin\i386\mfc80enu.dll to \\MDT-SERVER\D$\SMS\bin\i386\mfc80enu.dll: Could not create directory \\MDT-SERVER\D$\SMS\bin\i386. The operating system reported error 64: The specified network name is no longer available. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:52:59 AM 8516 (0x2144) Could not copy file E:\Microsoft Configuration Manager\bin\i386\Microsoft.VC80.CRT.manifest to \\MDT-SERVER\D$\SMS\bin\i386\Microsoft.VC80.CRT.manifest: Could not create directory \\MDT-SERVER\D$\SMS\bin\i386. The operating system reported error 64: The specified network name is no longer available. SMS_SITE_COMPONENT_MANAGER 1/24/2012 7:53:59 AM 8516 (0x2144) ---------------------------------------------------------------------- Distmgr.log from SCCM Primary Server Odd thing is these packages already updated back on the 17th, they shouldn't still be attempting to update and this set of messages just keeps repeating every 10 seconds. If I try a very small package to update (say that only needs a few KB to update) it seems like it slipped in, but anything else is either on hold or in the status message queries gives a failure. Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:29 AM 4396 (0x112C) Used 5 out of 5 allowed processing threads. SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) No more available threads left to process any more packages. SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) The last source update time for pkg HQ200034 is 1/17/2012 10:12:25 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) The next start time for pkg HQ200034 is 2/21/2012 10:00:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) The last source update time for pkg HQ20003A is 1/17/2012 7:04:48 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) The next start time for pkg HQ20003A is 2/21/2012 7:00:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) The last source update time for pkg HQ20003E is 1/10/2012 7:58:05 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) The next start time for pkg HQ20003E is 2/14/2012 7:30:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:39 AM 4396 (0x112C) The last source update time for pkg HQ200043 is 1/17/2012 6:08:16 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ200043 is 2/21/2012 6:00:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ200044 is 1/17/2012 6:52:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ200044 is 2/21/2012 6:30:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ200045 is 1/17/2012 10:36:06 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ200045 is 1/24/2012 8:06:40 AM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ200046 is 1/17/2012 5:13:44 AM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ200046 is 2/21/2012 5:00:00 AM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ200047 is 1/17/2012 9:39:30 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ200047 is 2/21/2012 9:30:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ200048 is 1/17/2012 2:34:38 AM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ200048 is 2/21/2012 2:30:00 AM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ20006B is 1/17/2012 8:37:45 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ20006B is 2/21/2012 8:30:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ200080 is 1/17/2012 8:09:45 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ200080 is 2/21/2012 8:00:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ20008B is 1/17/2012 10:34:10 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ20008B is 2/21/2012 10:30:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ2000B9 is 1/17/2012 9:09:16 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ2000B9 is 2/21/2012 9:00:00 PM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The last source update time for pkg HQ20013B is 1/17/2012 6:05:31 AM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) The next start time for pkg HQ20013B is 2/21/2012 6:00:00 AM Eastern Standard Time SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 1/24/2012 8:06:40 AM 4396 (0x112C) Relevant status message queries from one of the packages that fails to process (the above lines are all for OS images that already finished distributing)... After about 6PM is just said one last retrying and never said anything else... Severity Type Date / Time System Component Message ID Description Information Milestone 1/23/2012 4:47:01 PM SCCM1 SMS_DISTRIBUTION_MANAGER 2304 SMS Distribution Manager is retrying to distribute package "HQ2001D7". Wait to see if the package is successfully distributed on the retry. Error Milestone 1/23/2012 4:35:28 PM SCCM1 SMS_DISTRIBUTION_MANAGER 2302 SMS Distribution Manager failed to process package "CF-30_MK2_W7x86" (package ID = HQ2001D7). 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. Information Milestone 1/23/2012 4:24:22 PM SCCM1 SMS_DISTRIBUTION_MANAGER 2304 SMS Distribution Manager is retrying to distribute package "HQ2001D7". Wait to see if the package is successfully distributed on the retry. Error Milestone 1/23/2012 4:24:00 PM SCCM1 SMS_DISTRIBUTION_MANAGER 2302 SMS Distribution Manager failed to process package "" (package ID = HQ2001D7). 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. Information Audit 1/23/2012 3:40:33 PM 57716SO Microsoft.ConfigurationManagement.dll 30068 User "PBSO\GertsikA-a" updated a package named "Panasonic CF-30_MK2_W7x86 (Test)" (HQ2001D7) to the site distribution points. ------------------------------------------------- ContentTransferManager.log from one of the machines that is stuck on "Downloading" the first software update. Oddly, it seems the machines at our offsite locations are having no issues downloading from their distribution points. It's only the machine's using the primary server (which hosts a DP) that are having this issue: CCTMJob::UpdateLocations({4701006C-6EE6-43C3-9732-D96E9F47923F}) ContentTransferManager 1/24/2012 8:29:38 AM 4792 (0x12B8) CTM_NotifyLocationUpdate ContentTransferManager 1/24/2012 8:29:38 AM 4792 (0x12B8) CCTMJob::UpdateLocations - Received empty location update for CTM Job {4701006C-6EE6-43C3-9732-D96E9F47923F} ContentTransferManager 1/24/2012 8:29:38 AM 4792 (0x12B8) CTM job {4701006C-6EE6-43C3-9732-D96E9F47923F} suspended ContentTransferManager 1/24/2012 8:29:38 AM 4792 (0x12B8) CCTMJob::_DeleteLocations ContentTransferManager 1/24/2012 8:29:38 AM 4792 (0x12B8) CCTMJob::UpdateLocations({4701006C-6EE6-43C3-9732-D96E9F47923F}) ContentTransferManager 1/24/2012 8:29:44 AM 716 (0x02CC) CTM_NotifyLocationUpdate ContentTransferManager 1/24/2012 8:29:44 AM 716 (0x02CC) CCTMJob::UpdateLocations - Received empty location update for CTM Job {4701006C-6EE6-43C3-9732-D96E9F47923F} ContentTransferManager 1/24/2012 8:29:44 AM 716 (0x02CC) CTM job {4701006C-6EE6-43C3-9732-D96E9F47923F} suspended ContentTransferManager 1/24/2012 8:29:44 AM 716 (0x02CC) CCTMJob::_DeleteLocations ContentTransferManager 1/24/2012 8:29:44 AM 716 (0x02CC)Rick Don Client Systems Administrator Palm Beach County Sheriff's Office
January 28th, 2012 8:39am

Another thing I'm noticing is that the primary server is showing multiple copies of SMS_COMPONENT_MONITOR, SMS_MP_FILE_DISPATCH_MANAGER and SMS_OUTBOX_MONITOR when looking into the ConfigMgr Service Manager. Something else brought to my attention; one of the sys admins installed a number of updates to the server last weekend as it looks like the server's OS hadn't been updated in nearly two years. I noted one update (Service Pack 1 for Server 2008 R2) made note about not being able to access various shares after installation. After removing the Service Pack, our software updates started working immediately. Are there any security or software updates that are known to cause issues with SCCM in regards to accessing remote shares that it normally has been able to access? I'm also realizing the distmgr.log is just simply showing a ton of messages due to schedule checking, those packages auto-distribute the third Tuesday of every month. So it's just showing... I did get some other information from the log though that finally slipped thru between all the schedule checks..... RDC:Successfully created RDC signatures for source \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7 for package HQ2001D7 version 1 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:19:41 AM 12084 (0x2F34) GetPackageSignature() called for package HQ2001D7 with version 1. UnpackedSignature = 1 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:19:41 AM 12084 (0x2F34) Starting to hash \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7 for package HQ2001D7 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:19:41 AM 12084 (0x2F34) Aquired context SMS_DISTRIBUTION_MANAGER 1/24/2012 10:19:41 AM 12084 (0x2F34) Created MD5 hash SMS_DISTRIBUTION_MANAGER 1/24/2012 10:19:41 AM 12084 (0x2F34) TreeRecurser failed at FindFirstFile \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7\, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12084 (0x2F34) HashDirectoryFiles failed at TreeRecurser \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12084 (0x2F34) Removing all the signatures for package HQ2000F7 with version at or lower than 6 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12096 (0x2F40) Starting to new hash \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7 for package HQ2001D7 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12084 (0x2F34) DeletePackageSignatures() called for package HQ2000F7 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12096 (0x2F40) Aquired context SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12084 (0x2F34) RDC:Successfully created RDC signatures for source \\pbso.org\isdata\Packages\Drivers\Hardware Apps\HP\ProBook\HP ProtectTools Security Manager for package HQ2000F7 version 8 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12096 (0x2F40) Created SHAhash SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12084 (0x2F34) GetPackageSignature() called for package HQ2000F7 with version 8. UnpackedSignature = 1 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12096 (0x2F40) Starting to hash \\pbso.org\isdata\Packages\Drivers\Hardware Apps\HP\ProBook\HP ProtectTools Security Manager for package HQ2000F7 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12096 (0x2F40) Aquired context SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12096 (0x2F40) Created MD5 hash SMS_DISTRIBUTION_MANAGER 1/24/2012 10:20:51 AM 12096 (0x2F40) TreeRecurser failed at FindFirstFile \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7\, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:03 AM 12084 (0x2F34) HashDirectoryFiles failed at TreeRecurser \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:03 AM 12084 (0x2F34) Getting provider type for algorithm 32780 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:03 AM 12084 (0x2F34) Aquired context SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:03 AM 12084 (0x2F34) Creating hash for algorithm 32780 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:03 AM 12084 (0x2F34) Created hash for version 3 and algorithm 32780 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:03 AM 12084 (0x2F34) Starting to new hash \\pbso.org\isdata\Packages\Drivers\Hardware Apps\HP\ProBook\HP ProtectTools Security Manager for package HQ2000F7 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:13 AM 12096 (0x2F40) Aquired context SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:13 AM 12096 (0x2F40) Created SHAhash SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:13 AM 12096 (0x2F40) VerifyContentPackages: thread stopped SMS_DISTRIBUTION_MANAGER 1/24/2012 10:22:31 AM 1204 (0x04B4) TreeRecurser failed at FindFirstFile \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7\, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:03 AM 12084 (0x2F34) HashDirectoryFiles failed at TreeRecurser \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:03 AM 12084 (0x2F34) Getting provider type for algorithm 32772 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:03 AM 12084 (0x2F34) Aquired context SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:03 AM 12084 (0x2F34) Creating hash for algorithm 32772 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:03 AM 12084 (0x2F34) Created hash for version 3 and algorithm 32772 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:03 AM 12084 (0x2F34) TreeRecurser failed at FindFirstFile \\pbso.org\isdata\packages\drivers\hardware apps\hp\probook\hp protecttools security manager\x64\preboot\, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:15 AM 12096 (0x2F40) HashDirectoryFiles failed at TreeRecurser \\pbso.org\isdata\Packages\Drivers\Hardware Apps\HP\ProBook\HP ProtectTools Security Manager, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:15 AM 12096 (0x2F40) Getting provider type for algorithm 32780 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:15 AM 12096 (0x2F40) Aquired context SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:15 AM 12096 (0x2F40) Creating hash for algorithm 32780 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:15 AM 12096 (0x2F40) Created hash for version 3 and algorithm 32780 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:23:15 AM 12096 (0x2F40) TreeRecurser failed at FindFirstFile \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7\, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) HashDirectoryFiles failed at TreeRecurser \\mdt-server\d$\Distribution\Applications\Drivers\Panasonic\CF-30F_W7, Win32 error = 64 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) DeleteUnpackedSignature() called for package HQ2001D7 with version 1 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) Failed to generate hash of package HQ2001D7 SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) Package HQ2001D7 uses the source directory directly. SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCM1 SITE=HQ2 PID=4060 TID=12084 GMTDATE=Tue Jan 24 15:24:03.469 2012 ISTR0="CF-30_MK2_W7x86" ISTR1="HQ2001D7" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="HQ2001D7" SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) Failed to process package HQ2001D7 after 5 retries, will retry 5 more times SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 1/24/2012 10:24:03 AM 12084 (0x2F34) Rick Don Client Systems Administrator Palm Beach County Sheriff's Office
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2012 10:50am

Sounds like you need the DP hotfix:http://blogs.technet.com/b/configurationmgr/archive/2010/09/22/fix-the-configmgr-2007-database-grows-excessively-large-and-dps-do-not-honor-the-quot-number-of-retries-quot-and-quot-delay-before-retrying-minutes-quot-retry-settings.aspx Okay, here is where it gets more fun. We have tracked this out of SCCM. What we are seeing is that *only* while we are on this one server, if we attempt to access other computer's shares (workstation or server), sometimes we can get into the shares and folders and sometimes we can't. If I were to copy a series of files, the first four might copy, on the fifth we'd get a "network path not found", but on the 6th (in the case of going thru say SCCM which continues to attempt to copy the files) that one goes thru. It seems like the server is having issues enumerating for read/write purposes. If a folder is empty it has no problem accessing it, or if it only has one file, or a bunch of small files. But if I have a folder with 300 megs of data broken across a couple of files. I'll watch the progress bar that goes across the address bar take about 30 - 60 seconds and sometimes it gets in, sometimes it doesn't do anything when the progress bar finishes, and sometimes it errors out with "network path not found". To check, we added a partition and put a second copy of windows on the partition for (dual-boot) for a clean copy of Windows 2008 Server R2 and we have no issues. So this is definitely an OS issue it seems and not an SCCM issue unfortunately. I'll repost my question in the 2008 server forum I guess.Rick Don Client Systems Administrator Palm Beach County Sheriff's Office
January 28th, 2012 11:32am

Distmgr.log from SCCM Primary Server Odd thing is these packages already updated back on the 17th, they shouldn't still be attempting to update and this set of messages just keeps repeating every 10 seconds. If I try a very small package to update (say that only needs a few KB to update) it seems like it slipped in, but anything else is either on hold or in the status message queries gives a failure. Rick Don Client Systems Administrator Palm Beach County Sheriff's Office Sounds like you need the DP hotfix:http://blogs.technet.com/b/configurationmgr/archive/2010/09/22/fix-the-configmgr-2007-database-grows-excessively-large-and-dps-do-not-honor-the-quot-number-of-retries-quot-and-quot-delay-before-retrying-minutes-quot-retry-settings.aspx
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2012 1:57pm

Sounds like you need the DP hotfix:http://blogs.technet.com/b/configurationmgr/archive/2010/09/22/fix-the-configmgr-2007-database-grows-excessively-large-and-dps-do-not-honor-the-quot-number-of-retries-quot-and-quot-delay-before-retrying-minutes-quot-retry-settings.aspx Okay, here is where it gets more fun. We have tracked this out of SCCM. What we are seeing is that *only* while we are on this one server, if we attempt to access other computer's shares (workstation or server), sometimes we can get into the shares and folders and sometimes we can't. If I were to copy a series of files, the first four might copy, on the fifth we'd get a "network path not found", but on the 6th (in the case of going thru say SCCM which continues to attempt to copy the files) that one goes thru. It seems like the server is having issues enumerating for read/write purposes. If a folder is empty it has no problem accessing it, or if it only has one file, or a bunch of small files. But if I have a folder with 300 megs of data broken across a couple of files. I'll watch the progress bar that goes across the address bar take about 30 - 60 seconds and sometimes it gets in, sometimes it doesn't do anything when the progress bar finishes, and sometimes it errors out with "network path not found". To check, we added a partition and put a second copy of windows on the partition for (dual-boot) for a clean copy of Windows 2008 Server R2 and we have no issues. So this is definitely an OS issue it seems and not an SCCM issue unfortunately. I'll repost my question in the 2008 server forum I guess. Rick Don Client Systems Administrator Palm Beach County Sheriff's Office Read the KB, the DP spamming status messages is a known issue. Good luck fixing the OS!
January 28th, 2012 4:59pm

I've been on vacation and have come back to a bit of a nightmare. We currently have the following: SCCM 2007 R2 loaded up on our primary site server (2008 Server), using it as a Distribution Point along with about 20 other DP's. We have a DFS share that we use to host our source files \\xxx.org\isdata\packages\etc... We have a Microsoft Deployment Toolkit installed on a separate server that has a script that autobuilds our images once a month, puts in the latest updates (has its own WSUS separate from the one on our SCCM Server that we use to push out updates to existing clients). We have about 3700 active clients. The MDT Server also was serving as our PXE role since it doesn't do much else during the month. Our various subnets all point towards it on our main campus. Here is what is going on.. While I was away on vacation our SQL Database Administrator noticed that he kept dropping his connection to the SCCM Server. After updating the NIC driver, changing which NIC is being used and doing all the system updates to get the system current, our Network Manager realized there was a problem between the server and the management card the NIC was connecting to. So he switched things around and even put the server on a different subnet. During all of this the following has started occurring: 1) People couldn't PXE; someone attempted to remove the roles from the MDT Server and then reinstall but we keep getting errors that say we can't copy the files over to the D:\SMS directory that we don't have rights or sometimes instead it will say that the network path isn't found (mind you I'm pinging the MDT machine while it's saying it can't find it). 2) Computers that should have downloaded their Software Updates are sitting there on that first software update just saying downloaded. Checking the logs they keep saying the download location is "empty". 3) Some of our packages we can update and some we can't where we keep getting a "can't access either the source or the distribution point"... Well, when the first DP is the SCCM Server itself that leads me to believe I've got a networking issue but still... All this seems to have started occurring almost simultaneously... Any help would be appreciated...
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2012 7:58pm

You have to provide relevant logs; troubleshooting is impossible without them.Torsten Meringer | http://www.mssccmfaq.de
January 29th, 2012 3:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics