[SCCM 2012] Content distribution to DP's successfull status then in progress
Hello,
Had 70 DP on my infrastructure. A distribution group with around 200 contents is created and 70 DP are link to this DP group.
Every day I check the content distribution status, and the global pourcentage go up and down.
IE: Monday a DP is fully synched and the day after 10 contents are "in progress" and I have this thing on all DP's. Looks like that content distribution are done again an again....
Two weeks ago I had 15 DP fully distributed and now only 3... and no changes on the contents...
So I don't know what is the cause of this. Any idea?
Thanks in advance
We seem to be experiencing this issue in our environment and I just want to try and understand whether this is a bug that only reflects on status messages, or if the status messages reflect on the actual content, and thus, application and task sequence deployments?
I believe this is becoming a serious issue.
When the "Content is being distributed to the distribution point" messages first started surfacing, we noticed that certain packages (but not necessarily all), were being sent to all DP's, even when some of those packages weren't assigned to that
particular DP or the Boundary Group set up for content to that DP (we are viewing this in SCCM 2012 Monitoring | Distribution Status | Distribution Point Configuration Status, and the Details tab.) The biggest issue right now is that this recurrence of packages
redistributing, is causing task sequences to fail from distribution points that didn't actually have content redistributed to them.
And yes, validating content individually on those "in progress" packages does remediate the status message and eventually green light the DP. But validating content every time a DP is stood up, or content is distributed is becoming painstaking.
And scheduling Content Validation to occur more frequently only seems to be a band-aid that will not always help.
Is there any additional information on this malformed status message that can be provided? Is Microsoft working on a fix? We have not yet upgraded to SP1. Can anyone confirm the issue is resolved with SP1 or later, or if a hotfix exists to address the problem?
Similar Messages
-
SCCM 2012 Content Distribution monitoring
Hi All
I am trying to enable alerts for content distributions on Primary Site Servers
Example: I have 1 PS server and multiple DPs and i am distributing/validating multiple packages from my PS Server to Multiple DPs on schduled basis.
The issue is for some reason if the content distributions/validations fails then i should get email alert (currently i am behind on Console or Offline Reports).
I tried creating custom Even Logs through status message filters which is not working
please help if anyone have already done alerting for failed content distributions
thanks
ananthYes, I know this is an old post, I'm just trying to clean them up.
Wouldn't this be better suited for OpsMgr?
http://www.enhansoft.com/ -
Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkrNow we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM -
SCCM 2012 software distribution not able to distribute content for chrome
Hi I am using sccm 2012, need some advice, thanks! I tried to deploy chrome exe to a xp pc but the PC software centre shows downloading for very long time, more than a few hours. I created a 64bit chrome for a win7 pc and deployment also not working, it
just failed. Then I downloaded a msi installer to deploy to an xp pc, the downloading also takes forever, I checked the distribution content, it's failed. I then created a DP group and add the single DP into it. but still not working. I did the work before
for firefox and it did work before. Not sure what happened. Not sure where to check the log for software distribution, any advice please?thanks!
Thanks and best regards, -- KFThanks, Narcoticoo!your advice is helpful!
So, does it mean I can use xxxx.exe /install /silent for all other exe installers? And to find out the detection method, do I have to install the exe on a local pc to find out the actual directory it will install it (Then uninstall it)? and xxx.exe /uninstall
is for uninstallation? Can I create a bat file like chrome-install.bat to have one line like "ChromeSetupStandAloneSetup.exe
/silent /install " as the the actual installer? Why there is a package option below application? it confused me ....
Thanks!
Thanks and best regards, -- KF -
SCCM 2012 R2 - Distribution Point
Hello,
I have a SCCM environment configured only one server to handle all the Role MP, DP, etc..
SQL Server 2012 is Remotely installed.
I am using Windows server 2012 R2 Standard with installed SCCM 2012 R2.
I am using VMware vSphere 5.1
I want to use SCCM 2012 R2 for PXE boot to deploy Windows 7 Enterprise 32 bit and 64 bit.
But I am unable to install the Windows 7 Enterprise 32 bit and 64 bit through PXE Boot.
When I am trying to install on VM this error message is:
Downloaded WDSNBP from 10.100.1.178
Pending request ID : 31
Message from Administrator:
Configuration Manager is looking for Policy.
Contacting Server 10.100.1.178
PXE Boot aborted. Booting to next device...
PXE-MOF: Existing Intel PXE ROM.
The operating system was not found. Try Disconnecting.......
And 2nd thing when I am selecting Packages in SCCM 2012 R2 Console and right clicking on User State Migration Tool for Windows 8.1 and Selecting Distribute Content and After clicking next when its asking for Specify the Content destination its now showing
any Distribution Point.
Can someone help me please to fix this issue.
Thanks a lot and help/advise much appreciated.Contacting Server 10.100.1.178
PXE Boot aborted. Booting to next device...
This indicates that there's no task sequence deployed to the computer that was PXE booted.
Torsten Meringer | http://www.mssccmfaq.de -
SCCM 2012 R2 Distribution Point Installs but does not send packet.
I installed SCCM 2012 Primary Site on a server and need to create 18 Dps, could create 12 however I am having trouble creating the last 6, the link from headquarters to branch MPLS is a full 256 Kb, it creates the folders and DPs however the server can not
send the first two packages that are Client Package Configuration Manager and Configuration Manager Client Upgrade package only 6 DPS the other 12 I got.
The computer account is in the Administrators group and Admin Domains;
Already checked the WMI with Wbemtest;
I uninstalled and installed the DP again;
Below is the log, changed the name to contoso by issues of customer privacy.
Sleep 928 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:00:07 2528 (0x09E0)
Sleeping for 60 minutes before content cleanup task starts. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:10:52
5772 (0x168C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:12:13 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40 2528 (0x09E0)
Starting package processing thread, thread ID = 0x14F4 (5364) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40
2528 (0x09E0)
Sleep 60 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.072 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Retrying package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5264 (0x1490)
Thread Handle = 0000000000002330 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5264 (0x1490)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5264 (0x1490)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
DP thread with thread handle 0000000000002330 and thread ID 5264 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Only retrying local DP update for package LAA00003, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
SourceVersion (1) of package LAA00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.684 2014 ISTR0="Configuration Manager Client Package"
ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Failed to process package LAA00003 after 66 retries, will retry 34 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:46 2528 (0x09E0)
Starting package processing thread, thread ID = 0x14D0 (5328) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
2528 (0x09E0)
Sleep 1824 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.300 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
Retrying package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5736 (0x1668)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5736 (0x1668)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5736 (0x1668)
Thread Handle = 0000000000002A50 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
DP thread with thread handle 0000000000002A50 and thread ID 5736 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Only retrying local DP update for package LAA00004, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
SourceVersion (1) of package LAA00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.910 2014 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Failed to process package LAA00004 after 66 retries, will retry 34 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:52 2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:52 2528 (0x09E0)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:42:18 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 2528 (0x09E0)
Starting package processing thread, thread ID = 0x1394 (5012) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
2528 (0x09E0)
Sleep 60 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:23.524 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5012 (0x1394)
Retrying package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5012 (0x1394)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5112 (0x13F8)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5112 (0x13F8)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
5112 (0x13F8)
Thread Handle = 0000000000001CF0 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
DP thread with thread handle 0000000000001CF0 and thread ID 5112 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
5012 (0x1394)
Only retrying local DP update for package LAA00003, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
SourceVersion (1) of package LAA00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:24.068 2014 ISTR0="Configuration Manager Client Package"
ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
Failed to process package LAA00003 after 67 retries, will retry 33 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:24
5012 (0x1394)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:24
5012 (0x1394)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 2528 (0x09E0)
Starting package processing thread, thread ID = 0x176C (5996) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:29.592 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 5996 (0x176C)
Retrying package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 5996 (0x176C)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 4576 (0x11E0)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 4576 (0x11E0)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
4576 (0x11E0)
Thread Handle = 00000000000025F8 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
DP thread with thread handle 00000000000025F8 and thread ID 4576 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
5996 (0x176C)
Only retrying local DP update for package LAA00004, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
SourceVersion (1) of package LAA00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:30.137 2014 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30 5996 (0x176C)
Failed to process package LAA00004 after 67 retries, will retry 33 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30
5996 (0x176C)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30
5996 (0x176C)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:35 2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:35 2528 (0x09E0)
Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA. SMS_DISTRIBUTION_MANAGER 14/08/2014
00:59:32 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 5292 (0x14AC)
Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:32 4008 (0x0FA8)
Processing status update for package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32
4008 (0x0FA8)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 2528 (0x09E0)
Sleep 1048 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 2528 (0x09E0)
Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00003, Status 5
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 4008 (0x0FA8)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:32 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 2528 (0x09E0)
Sleep 1043 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 2528 (0x09E0)
Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39
4008 (0x0FA8)
Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:39 4008 (0x0FA8)
Processing status update for package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39
4008 (0x0FA8)
Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00004, Status 5
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39 4008 (0x0FA8)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:39 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 2528 (0x09E0)
Sleep 1038 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 2528 (0x09E0)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 2528 (0x09E0)
Sleep 1033 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 2528 (0x09E0)
Sleeping for 60 minutes before content cleanup task starts. SMS_DISTRIBUTION_MANAGER 14/08/2014 01:10:52
5772 (0x168C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:28 5292 (0x14AC)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33 5292 (0x14AC)
Found notification for package 'LAA00003' SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Found notification for package 'LAA00004' SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33 2528 (0x09E0)
Starting package processing thread, thread ID = 0x388 (904) SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Starting package processing thread, thread ID = 0x1678 (5752) SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:34
2528 (0x09E0)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:34 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=904 GMTDATE=qui ago 14 04
Lucas Simoes MCTSNo (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 13/08/2014 23:57:10
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
13/08/2014 23:57:10 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Created sending thread (Thread ID = 0xBE8) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Created sending thread (Thread ID = 0x3B4) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:35 3048 (0x0BE8)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:35 948 (0x03B4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:36.046 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 3048 (0x0BE8)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 3048 (0x0BE8)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:36.484 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 948 (0x03B4)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 948 (0x03B4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 3048 (0x0BE8)
PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:45 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 3048 (0x0BE8)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:45.880 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45 3048 (0x0BE8)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45
3048 (0x0BE8)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 948 (0x03B4)
PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:52 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 948 (0x03B4)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:52.923 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52 948 (0x03B4)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52
948 (0x03B4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:52 4004 (0x0FA4)
Created sending thread (Thread ID = 0x1680) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:52
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:53 4004 (0x0FA4)
Created sending thread (Thread ID = 0x18A4) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:53
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:53
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:53 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:16 5760 (0x1680)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:17 6308 (0x18A4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:20.098 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 6308 (0x18A4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:20.111 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 5760 (0x1680)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 6308 (0x18A4)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 5760 (0x1680)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 6308 (0x18A4)
PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:43 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 6308 (0x18A4)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:43.622 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43 6308 (0x18A4)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43
6308 (0x18A4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 5760 (0x1680)
PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:50 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 5760 (0x1680)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:50.708 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50 5760 (0x1680)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50
5760 (0x1680)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Created sending thread (Thread ID = 0xF28) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Created sending thread (Thread ID = 0x11D0) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:15 3880 (0x0F28)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:15 4560 (0x11D0)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:16.990 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:16 3880 (0x0F28)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 3880 (0x0F28)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:17.845 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 4560 (0x11D0)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 4560 (0x11D0)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
Attempted max retry count. The job would be marked for deletion now. SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
Sent status to the distribution manager for pkg LAA00003, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27 3880 (0x0F28)
STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.291 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.305 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27 3880 (0x0F28)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27
3880 (0x0F28)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
Attempted max retry count. The job would be marked for deletion now. SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
Sent status to the distribution manager for pkg LAA00004, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34 4560 (0x11D0)
STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.335 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.337 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34 4560 (0x11D0)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34
4560 (0x11D0)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 01:19:34
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 01:19:34 4004 (0x0FA4)
No (more) send requests found to process.
SMS_PACKAGE_TRANSFER_MANAG
Lucas Simoes Rezende MCP, MCTS , ITIL V3 -
Adding New SCCM 2012 SP1 Distribution Point To Replace Existing Distribution Point
We currently in the process of the doing a site server refresh at all our remote sites. Each remote site currently has a physical 2012 SP1 DP, and will be replaced with a new DP at each location, and will eventually decommission the current one.
What's the best way to introduce a new DP and remove the old one?
Thanks
BernYou can use this method if distributing through the WAN is not an option.
http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx
If you don't care, just add it to SCCM and replicate your content. Modify your boundary once done.
I hope you have a DP Group, if so, just make it member of the group and all your content will be copied. If not, you'll have to go through all your content and add it manually or script the process using PowerShell.
To remove your existing it's simply a matter of removing the "Distribution Point" role on your Server using the SCCM Console. (Administration / Site Configuration /Site Server, select your distribution point, right click Remove)
Benoit Lecours | Blog: System Center Dudes -
SCCM 2012 - Pull distribution point and target PKI or HTTPS DPs
I have spent several days researching this and so far have found only a single page that even takes a stab at offering a solution.
Problem:
Trying to target an HTTPS DP when creating a pull distribution point in SCCM 2012 R2. The link that I'm referring to that does offer a workaround is here(guess I can't post a link, but it ends with the following, how-to-set-an-https-distribution-point-as-a-source-dp-for-pull-dps)
I have several problems with the proposed solution.
Is a script really the only way to proceed with something that has up till now been a built in feature with the rest of the product.
You have to provision the DP to use a self signed cert initially for it to even work, then supposedly you can add the private key to the DP later.
Does that mean I have to unbind the cert from both the pull and target/source push DP in IIS?
Powershell which would be a logical way to go, doesn't seem to make any head way(Mr. Snover I know you don't oversee configman but please push for more documentation, you've taught me to live and die by get-help. A single example for a command as large
as set-cmdistributionpoint or add-cmdistributionpoint is a shame. Perhaps my update help just didn't finish properly and I'm talking prematurely. If that is the case then I apologize!)
Is there no other solution other than build the DP with a self signed cert then run this VB script and then switch the private key later? I have read through a lot of the pull DP documentation and it makes mention of leveraging the SDK but I haven't seen
anything definitive. I would like to at the very least convert this from VB to powershell(if that script is the only option) and I know how to convert the portions where it's interacting with the site's WMI namespace (smsprovider if I'm not mistaken).
What I don't know how to do, rather don't have the chops for is what comes after. The site control file piece, I see it's also WMI and I could spend the time stepping through the different piece and just might to learn more about SCCM in the lab anyhow. I've
spent the last year getting to know powershell and have spent next to no time with VB. I know enough to recognize what a script is doing.
The environment:
The reason this is important for me is I'm about to start the production build(been all lab up till now) that is going to have just under 300 DPs in the field connected via T1 lines. They were all 07 secondary sites. I was thinking about migrating them using
the migration tool but considering the amount of work its going to take if that link is the ONLY path to target a HTTPS DP then I might as well just spend the time and manually uninstall and reinstall the field DPs. The client count in the field is an average
of 50 machines per site where there are on-prem devices... Total client count is around 25k. The primary site in the datacenter will house the majority of the site roles unless I start running into resource issues, at which time I will begin offloading site
roles to one of two more servers that I have slated for the project. No CAS, no Secondaries. SQL is co-located on the primary.
Ramblings:
I'm sure there are more people out there using PKI, and using pull DPs. How have you managed to target your HTTPS enabled DPs? Security wants this to be a HTTPS only environment, and up until now I have successfully done that. If someone could please point
me in the direction of some more thorough documentation I would be very grateful. I understand that this is a somewhat new feature, but there has to be an easier way. Perhaps powershell can cleanly do it with the set-cmdistribution point...but when I update
help and do showwindow for the command I only get one example and so far haven't found any other stories like mine with the exception of the link I posted in the beginning.
While I'm rambling, Wally there are a lot of us in the community that are going to miss your presence at Microsoft and should you read this I wish you luck with your new position. But that is a whole different topic. Thanks in advance for any links or help
you can provide. -K.R.Yes, this is the only way, from
http://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_PlanPullDps: "However, you can use the Configuration Manager SDK to specify a source distribution point that is configured for HTTPS. To use a source distribution point that is configured
for HTTPS, the pull-distribution point must be co-located on a computer that runs the Configuration Manager client. "
Does "why" really matter , who cares? It just is. Whether it was an oversight, a coding bug, or an act of God doesn't change anything. Why does there "have to be" an easier way? And what's wrong with using the VBScripts others have
written? A script is a script is a script particularly if you've been given it already. Just because the hammer is pink doesn't mean it can't hammer the nail in.
Jason | http://blog.configmgrftw.com | @jasonsandys -
SCCM 2012 - Change Distribution Point's Site System Properties Site Code
Hello All,
I'm hoping someone can help me out. Here's what I have and here's what I'm trying to do.
SCCM 2012 R1
Each of our offices has a Windows 7 SP1 Ent PC that is a distribution point for that office's 10-20 machines. A number of these offices and their DPs were setup prior to me setting up a number of Secondary Site Servers. So right now, these DPs' site codes
are the primary site server's. I'd like to change these to one of the Secondary Site Servers.
When I go to the Site System properties of one of these Win7 distribution points, the Site Code is grayed out.
So, the question is, how can I change one of these DPs' site codes?
Thanks in advance to whomever helps!!
BillThat's a strange reason for using Secondary Sites. How many clients are you managing? Have you good WAN links?
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"
I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
Today I migrated one of the DP's which seems to work well.
However all my packages shows now the status "unknown" for this migrated DP.
This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
Any idea how to solve this ? R2 install ?Some additional information:
I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
share......then i guess i can remove the content from the "old" distribution point share ????
I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
--> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
--> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
will become available Successful and the package will become available on the distribution point share
But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
Any help, ideas, tips, hints, recommendations ?
My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first... -
Automaitc Updates through SCCM 2012 not showing up on the updates status
Hi,
I have configured Automatic Update rule on SCCM 2012 and it works fine but on the client machine i see this.
This is the update status it shows which means updates are not being installed since long time.
But when i see the update history it shows me the latest updates installed.
Why would this happen? please suggest.
Regards,
Maqsood
Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation CertifiedHi,
That is as expected as the updates are installed using SCCM and not the Windows Update Agent, if you deploy a client using SCCM OSD and install software updates using SCCM and not WSUS/Windows Update it will actually say:
"Updates were installed: Never"
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
SCCM 2012 R2 - Distribution Point untrusted domain - Not acknowledging Network Access Account (FYI)
Hello!
Scenario
Built a single primary site server in one domain with multiple distribution points. All site servers are member of this one site.
The distribution points in the primary site servers' domain function as expected. The distribution point deployed to an untrusted domain does not. The primary site server can see all objects in the domain, publishes successfully, and CCM client on the
DP in the untrusted domain knows its part of the site, knows its AD site (according to locationservices.log). The DP role is installed properly, logs are populating, queries are being made for application lists and updates. nfortuantely authentication
errors indicate that this software can'tbe downloaded.
In essence the DP in the untrusted domain can't pull down content from the primary site server. The role uses BITS to download content from IIS on the primary site server, but the requests each throw a 401 error. Unauthorised. This should be an easy fix.
Create a Network Access Account in the primary site server's domain, assign it to the site (Software Distribution setting), wait for the DP to pick up the setting and watch it retrieve its content. The DP in the untrusted domain is configured as a Pull DP,
implying it has to use a Network Access Account to download content. It knows the content is available and makes every effort to download it.
Problem
The DP in the untrusted domain doesn't know a Network Access Account (NAA) has been defined for the site.
The account does exist, created in the primary site server's domain and assigned to the site. Its not a password issue. IIS has not been set for Anonymous access as this isn't needed - the NAA should provide the credentials it requires to pull down content.
A manual check using the URL of the package confirms the package is accessible from the DP when using the NAA's credentials. I've allowed enough time (i think) for the DP to acknowledge the NAA. For fun the DP role was removed, and the CCM agent removed. Both
were reinstalled. A fresh install didn't detect the NAA.
Solution
After some soul searching and a little frustration, it came down to this: A Pull DP always uses the Network Access Account. If the DP can't find a Network Access account it will fail to pull down content. This is undisputed. Found an article that states
the Pull DP always uses the CCM client configuration to do its dirty work. At that point the CCM client was checked. It had the classic problem of only displaying two Actions - Machine Policy Retrieval & Evaluation Cycle, User policy Retrieval & Evaluation
Cycle. Most components were installed but not enabled. This is fairly common. Looked at the console, found the device, added the Approval column. Turns out it wasn't auto-approved. Reason being that the client is in an untrusted domain and clients in untrusted
domains aren't approved automatically (by default).
In this case something as simple as an Approving the client fixed these issues.
The DataTransferService.log highlights the issue:
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}' ErrorCode=0x80190191]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="1" thread="3136" file="dtsjob.cpp:3501">
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' URL='http://PRIMARYSERVER.A.B.COM:80/SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68'
ProtType=1]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3136" file="dtsjob.cpp:3504">
<![LOG[Authentication required by the proxy, DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="3" thread="3136" file="dtsjob.cpp:3513">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} in state 'Cancelled'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.h:166">
<![LOG[DTS job {17E0B672-F699-434D-B063-87CC2ACF715C} BITS job
{38B81ADE-55B5-4BD7-A881-DBFF13943EDE} encountered Access Denied error during download. Will retry using Network Access Account.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="2" thread="3136" file="dtsjob.cpp:3652">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} cancelled by client.]LOG]!><time="18:25:54.280+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.cpp:3205">
<![LOG[No network access account info found.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="1"
thread="3136" file="netaccessaccount.cpp:288">
<![LOG[The network access account is not defined.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context=""
type="1" thread="3136" file="netaccessaccount.cpp:858">
<![LOG[DTSJob {17E0B672-F699-434D-B063-87CC2ACF715C} encountered error setting BITS job to use Network Access Account
(0x00000000).]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="3" thread="3136" file="dtsjob.cpp:1885">
The IIS server logs u_ex150219.log captures the request:
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 2 5 1509 2
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 4
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 3
2 x Domains: DomainA and DomainX
- Single domain forests
- No trusts between domains/forests
DomainA\PRIMARYSERVER
- Primary Site Server, MP, DP, IIS, all roles
DomainX\DP1
- Distribution Point, IIS, etc
- CCM client installedBased on the above, you are using a PullDP. If so, have you installed the client agent on this system? The client agent is required on PullDPs in untrusted domains so that they can acquire the NAA.
Jason | http://blog.configmgrftw.com | @jasonsandys -
SCCM 2012 R2 Distribution Query
Hello,
Few weeks back I configured the SCCM server in single machine (SCCM, SQL, DP etc..) and I have created the ADR for Patch deployment.
Today I have configured some Distribution Point (on Windows 2008 R2 and Windows 7 machines).
Question:
How should I point the new DP's (in ADR or deployment package) also to distribute the content, where I have to make the changes. Kindly help.Use the Distribute Content Wizard to distribute the content of the Deployment Package to the new DPs. The next time the ADR will run it will update the package on all the associated DPs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
SCCM 2012 shared distribution point reassignment - old SCCM 2007 folders/files delete
Ok, I've looked, googled, binged, and cannot find any definitive answer on this, I've even asked a Microsoft Engineer, and I fear they are just as confused as I am, please help!
The scenario: I'm migrating from SCCM 2007 to 2012 and of course have shared DP's, I reassign a shared DP and this is what I expected to happen but did not - all the old .pck files from 2007 (in the SMSPKG folder on the OLD DP) should have been deleted AFTER
the content was converted into the single instance store, they are still there! if they are supposed to be there...why then is it called a SINGLE instance store if there are TWO folders containing compressed source files??? Also, the files in my OLD SMSPKGD$
(extracted source for 2007) are still there as well, even though prior to the reassignment of the DP I changed all of my deployments to download/run locally...what gives?
The end result of me reassigning my DP is the new content is essentially doubling the space taken up on the drive...not cool. Can I delete the content of the legacy folders (either the .pck or the folders in SMSPKGD$)?
TerryHi,
"The folder is used to temporarily store PCK files that get transferred to child or secondary sites. If you don't have any of those, the folder won't ever have anything in it. Even if you do have one of those, it'll still be empty most of the time because
PCK file storage in 2012 is temporary only."
For more information:http://social.technet.microsoft.com/Forums/en-US/2c5e6049-8566-4638-8ba8-3768c74c53f6/smspkg-folder-on-primary-site-server-which-is-not-a-dp?forum=configmanagergeneral
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
SCCM 2012: Package distribution fails.
Hi,
We have a package distribution that fails.
What I did: redeploy, fails again and again. So I went to distribution point properties, tab content, then removed the package.
I waited for some time but if fails again (note it is only 2 MB in size but takes like 20 minutes)!
Below the logging of what went wrong. It seems as if it has issues cleaning up the package.
My question: what is causing this/how to avoid?
J.
Failed to delete package file(s) from \\ourserver\ourapplication . Error = 145 SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 3436 (0x0D6C)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 3436 (0x0D6C)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 7772 (0x1E5C)
DP thread with thread handle 00000000000015B0 and thread ID 3436 ended. SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 7772 (0x1E5C)
Only retrying local DP update for package packagecode, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 7772 (0x1E5C)
StoredPkgVersion (5) of package packagecode. StoredPkgVersion in database is 5. SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 7772 (0x1E5C)
SourceVersion (5) of package packagecode. SourceVersion in database is 5. SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 7772 (0x1E5C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=oursccmserver SITE=PRD PID=3944 TID=7772 GMTDATE=Wed Feb 25 17:49:08.982 2015 ISTR0="Fixes" ISTR1="packagecode" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="packagecode" SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08
7772 (0x1E5C)
Failed to process package packagecode after 4 retries, will retry 96 more times SMS_DISTRIBUTION_MANAGER 25/02/2015 18:49:08 7772 (0x1E5C)
Jan HoedtExcluded the packagesource from antivirus,
Is that "\\ourserver\ourapplication?"
Torsten Meringer | http://www.mssccmfaq.de
Maybe you are looking for
-
Can't see conflicts item in iSync menu
Hello, I am using OS X in Swedish, which probably means I will not use the exact English terms in my question - apologies! I have a Nokia N73 which I have been syncronizing with iCal, using bluetooth/iSync 3.0.2. Now changes I make to the phone calen
-
Dolphin 4.8 mounting devices - not shown in Places
Hello guys! "gvfs" is installed. Then I open "/etc/polkit-1/localauthority.conf.d/50-localauthority.conf" and set "AdminIdentities=unix-user:alex" which is my username. Then echo [Mount system internal media for group storage] Identity=unix-user:alex
-
Search within Outlook 2013 will not search subject unless i specify "subject:()"
I am having an issue with Outlook 2013 where if I search for lets say "computer" and I have a message with the word "computer" in the subject line, it does not find it. If i search for "subject:(computer)" then it finds it. It's as if keyword searchi
-
T420s - swapping to extended monitor doesnt work
connecting my laptop to a tv or any other external monitor does work but when i try to swap to extended monitor or any other setting my pc shuts down and reboots. any ideas ?? thank you in advance
-
Sapjup cannot find correct shares on Windows 2008 R2 cluster
Hello Guru's, I have succesfully installed CRM 5 Abap+Java on Windows 2008 R2 based hardware. This is a HA setup. I am now in the process of upgrading to CRM 7.01. Unfortunately, the java upgrade program SAPjup runs into an error (share Host_A\sapmnt