System Status- Site Status- Distribution Points Missing

Quick question,
I seem to be missing some DP's from Site Status, if a DP is installed and running, I'm presuming that it should appear in the Monitoring\system Status\Site Status workspace....only I have some DP's that don't appear, what would cause this?
many thanks

They should show-up there eventually. Did you check the Distribution Point Configuration Status
node to see if the distribution points are up-and-running already?
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

  • Replace secondary site with distribution point

    I have a client that would like to remove some unnecessary secondary sites and replace them with distribution points on the same hardware. Is there a built-in way of doing this from the SCCM console? What should be taken into consideration before doing
    such a thing?
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    No there is no built in way to do this. It's essentially an uninstall (of the Secondary site components) and an fresh install of the DP. Content and boundaries are the only real considerations; you may want to use pre-staged content to essentially
    cache a local copy so that it doesn't have to be replicated across the WAN. Technically, if you leave the sccmcontentlib in place, it may be able to reuse this but that's not supported so it may or may not work.
    Jason | http://blog.configmgrftw.com

  • Last Status Update in Distribution Point Configuration Status after 2012 R2 Upgrade not updating

    I am having the oddest problem, and I was wondering if anyone had some pointers or knows how I can get this working. After I upgraded from
    2012 SP1 CU3 to 2012 R2, the status update date on the DP config status will not update at all, even though under each DP it is updating? I can still push content to them, but instead of getting a % of transfer that is complete I get the generic 'Detail will
    be available after the server finishes processing the messages'. I have tried to remove and re add the DP role to the DP's and am met with the same problem. I am assuming it's something is SQL but where to begin to look I have no idea.

    Yes, I know this is an old post, but I’m trying to clean them up.
    Did you solve this problem, if so what was the solution?
    BTW I find that most of these type of things take ~ 24 hours to update.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • New Site Server with Distribution Point & Software Update Point Roles not pulling SUGs

    I just set up a new server & installed the DP & SUP roles on it.  I am getting the following in the log this is just a small sample as its kind of repetative:
    Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
    Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
     SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Retry 10 times SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Start to evaluate all packages ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Start to evaluate package 'FPP00002' version 0 ... SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x4000094C to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Failed to evaluate package FPP00002, Error code 0x80070002 SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report state message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report Body: <ReportBody><StateMessage MessageTime="20140328183445.000000+000" SerialNumber="0"><Topic ID="FPP00002" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters
    Flags="0" Count="2"><Param>FPP00002</Param><Param>["Display=\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\"]MSWNET:["SMS_SITE=FPP"]\\FPPSCCM02.FPP.WUCON.WUSTL.EDU\</Param></UserParameters></StateMessage></ReportBody>
     SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x8000094F to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Report status message 0x40000952 to MP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Status message has been successfully sent to MP from remote DP SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    DP monitoring finishes evaluation. SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    Failed to evaluate some packages after 10 retry SMS_Distribution_Point_Monitoring 3/28/2014 1:34:45 PM 6444 (0x192C)
    The Console shows for the DP that it's waiting for content and I don't see where I can create a Prestage Package
    # When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

    D:\SMS_DP$\sms\logs\smsdpmon.log
    This is the 2nd server in our SCCM 2012 Sp1 Hierarchy.  It is set up with the following Site System Roles:
    Component Server
    Distribution Point
    Site System
    Software Update Point
    It is Prestaged Enabled.  My intent is that the client systems @ the location where this DP is located will use it to pull their Microsoft Updates from as well as content for any Applications we push to them rather than going over the WAN to the Primary
    Site Server.
    IN Distribution Point Configuration Status. the console shows "Failed to update package" & "Packaget Transfer Manager failed to update the package "yxz00040". Version 3 on Distribution Point server.my.domain.com review pkgxfermgr.log for more information
    about this failure."
    It also goes on toe list 2 possible causes and solutions
    Site servers does not have sufficient rights to the source directory.
    (Site server account is a member of local Administrators on Primary)
    Not enough disk space available
    (I have over 1TB of available space and primary site server has only 150GB available for entire content repository, both applications and sofware updates.)
    # When I wrote this script only God & I knew what I was doing. # Now, only God Knows! don't retire technet http://social.technet.microsoft.com/Forums/en-US/e5d501af-d4ea-4c0f-97c0-dfcef0192888/dont-retire-technet?forum=tnfeedback

  • Monitoring (Site Status)

    Hi
    I installed SCCM 2012, no problem, when i go to Monitoring, System Status, Site Status
    i view a Critical, I corrects errors.
    My problem: when i right-clic on Critical, Reset Counts, All, all messages disappear but the
    Status not change, (the icon is still red
    even if there are more errors, the icon
    does not change even after 48 hours
    of waiting, i reboot a server, no change)
    Thanks

    but the Status not change, (the icon
    is still red
    even
    if there are
    more errors, ...)
    That's expected then (I guess that more errors occured after having resetted the count)
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 Distribution Point without IIS

    Hello. My environment is SCCM 2012 SP1. I need to set up distribution points on several Windows Server 2003 machines. These machines have certain security requirements. One of which is no IIS. In SCCM 2007, I was able to create DPs without installing IIS.
    This prevented the use of BITS extensions but was acceptable. I cannot seemed to do the same with SCCM 2012.
    As a test, I performed three steps to test a DP without IIS on a Windows Server 2003 machine 1) Made the primary server a local administrator on the Windows Server 2003 machine, 2) Installed RDC using the msrdcoob_x86.exe file, 3) in the admin console, I
    created a new site system server with the distribution point role. I did not check allow it to install IIS to install/configure during the setup. The distribution point reports a successful installation status but I get three errors when I try to distribute
    a package. The first error message is Failed to create virtual directory on the defined share or volume of the distribution point. The second error is Distribution Manager failed to connect the the distribution point. The third error is Distribution Manager
    failed to process package "Package Name". I know that installing IIS with BITS extensions and WebDav support would fix this problem. However, I would like to use the DP without IIS like I did in SCCM 2007.
    Looking at the supported configurations, I see the below. This leads me to below that it is possible. Does anyone know if this is possible? If so, what I am missing in my steps.
    With System Center 2012 Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution
    point computer is not used to facilitate the download of content by clients that use BITS

    BITS is a client side technology and has nothing to do with the server side of a DP or IIS and thus is irrelevant.
    WebDAV was built into the relevant components of ConfigMgr obviating the need for the Windows Server WebDAV component so that's not needed for 2012 at all and thus N/A.
    Ultimately, no, this is not possible. IIS is required on a DP in ConfigMgr 2012. This is clearly listed at http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SiteSystemRolePrereqs.
    Jason | http://blog.configmgrftw.com

  • Branch Distribution Point 'Install Pending'

    I'm having a tough time getting a package to copy to a BDP (our first one).  I think I'm following all the correct steps (adding the remote server as a SCCM Site System as a branch distribution point / adding the new BDP to the package / specify that the contents of the package are automatically copied to the BDP etc), but when I go to the Package Status area, it shows a state of 'Install Pending' for the BDP.  The SMSPKGC$ share is also not getting created on the BDP server.  It's been like that for hours now.  I've also tried manually created the SMSPKGC$ share on the remote server and specify the drive letter to use, but that didn't work either, so I'm obviously missing something.
    Is there any simple checklist to go through when setting up a BDP to make sure I've set up everything properly? 
    Thanks for any help you can provide.
    Aaron

    I suspect what might be happening here is that you’ve protected the standard DP but excluded the branch DP when you configured the protected boundaries.  If you protect the standard DP, you must make sure the branch DP falls within the protect boundaries, or it won’t be able to download content from the standard DP.
    If you want to protect both the standard DP and the branch DP such that the branch DP can download the content from the standard DP, but clients only download it from the branch DP - then you might need to reconfigure your boundaries and be very careful that you don’t end up with overlapping boundaries. Normally boundaries are well-connected networks, but in this case you need to separate your branch DP from the clients it will serve.  You might have to do this by IP addresses rather than the more convenient method of AD sites, so that you get the granularity you need. 
    Can you try this in your test lab? Make sure the clients (but not the branch DP computer) that will use the branch DP are in one boundary, and this boundary is configured as a protected boundary on your branch distribution point site system.  Make a new boundary that contains just your branch DP and add it to the standard DP's protected boundaries.
    - Carol
    This posting is provided “AS IS” with no warranties and confers no rights.

  • Monitoring and troubleshooting in-place distribution point upgrades

    I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
    through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
    the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
    But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
    Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?

    Hi all
    I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
    Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
    points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
    12 hours.
    I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
    point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
    local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
    If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
    article. There seems to be a bug which is currently in a solving process.
    For me, there are two solutions for this problem:
    1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
    2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
    I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
    SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
    after 3 days.
    Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
    As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
    during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
    the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
    Kind regards Stefan Somogyi

  • 2012 SCCM SP1 Distribution Point Certificate store error on Server 2003 R2

    Has anyone had this issue on Server 2003 R2 where you are getting this error listed below? All content is being distributed ok. But, monitoring is showing errors with all my Distribution points and I want these errors to go away so I don't have to sift through
    all the darn errors.
    Thanks for your help. Daniel.
    Report status message 0x40000952 to MP
    Failed to create certificate store from encoded certificate.. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)
    Status message has been successfully sent to MP from remote DP

    I have found the error message in the smsdpmon.log on a Windows Server 2003 SP2 system acting as a Distribution Point (only).  The error shows up when / during a scheduled content validation on that server and is repeated after each package is "validated".
    From the smsdpmon.log:
    - Start to evaluate package share for package 'XXX0004F' version 5 ...
    - Package XXX0004F is verified successfully
    - Report state message 0x40000950 to MP
    - Failed to create certificate store from encoded certificate.. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows)
    - Report Body: <ReportBody><StateMessage MessageTime="20140315150802.000000+000" SerialNumber="5"><Topic ID="XXX0004F" Type="901" IDType="0"/><State ID="2384" Criticality="0"/><UserParameters Flags="0" Count="2"><Param>XXX0004F</Param><Param>["Display=\\DPSERVNAME.domain.com\"]MSWNET:["SMS_SITE=XXX"]\\DPSERVNAME.domain.com\</Param></UserParameters></StateMessage></ReportBody>
    - Report status message 0x40000950 to MP
    - Failed to create certificate store from encoded certificate.. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows)
    - Status message has been successfully sent to MP from remote DP
    - Report status message 0x80000954 to MP
    - Failed to create certificate store from encoded certificate.. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows)
    - Status message has been successfully sent to MP from remote DP
    I tried to pretty up the above - not sure that I was successful.
    The site server is a Windows Server 2012 R2 Standard running SCCM 2012 R2.

  • Distribution point shows 0 items.

    SCCM 2012 SP1 with 6 DPs.
    We had 6 distribution points. The Primary Site server D drive got full while installing new DP. We reboot the server and now Administration->Distribution Points show 0 items.
    Distribution point shows 0 items.
    Distribution Point group shows ALLDPGroup however members show 0 items.
    Content Status shows 0 items
    Distribution Point Group Status 0 items
    Distribution Point Configuration Status 0 items
    MP could not complete a task when processing Relay.
    Check the logs for clues. Possible cause: Out of disk space.
    Solution: Increase the disk space, remove unprocessable files.

    If you can get into the Console do you have maintenance task set-up to clean up and delete old records?  if so do that. 
    Why should that help in that case?
    @Parvinder_Randev: were you able to free up some disk space? Have you already examined the site and component status? Are there other errors? Site systems should not vanish just because of the disk being full.
    Torsten Meringer | http://www.mssccmfaq.de

  • Critical Errors SCCM 2012 (Distribution Point and Reporting services point)

    Hello,
    We are getting errors under the Site Status for the Distribution Point and Reporting services point. Was running fine and have not really made any changes but all of a sudden we have these critical errors.
    The report server service is not running on Reporting Service Point server "XXXXXXXXXXX"; start the service to enable reporting.
    We have stopped and restarted the SQL 2012 reporting service point with no errors. What else should we look at for this error? And are these related?
    Thanks,
    Bobby

    Hi,
    Have you checked the log file SRSRP.log?
    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 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 MCTS

    No (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

  • Ports Required for SCCM 2012 Distribution point

    I think below are the port need to open for distribution point instalaltion
    Site Server -- > Distribution Point
    SMB 445 TCP
    RPC Endpoint Mapper 135 UDP and TCP
    RPC dynamic TCP
    my question here is for install Distribution point instalaltion , only
    Site Server -- > Distribution Point one way port open  is enough? or do we need to open both ways?

    One way is enough for a standard Distribution Point. All distribution is initiated by your Primary site server by the Package Transfer Manager.
    Regards,
    Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

  • Ports Required for SCCM Distribution point

    Hi All,
    Can anybody tell me the ports required for distribution point. as in I have a site server with distribution point in HO, i want to have a distribution point server on a remote site. i went through the microsoft document which says u require port 445 open between site server and distribution point and it says u only require port 80 or 443 open between distribution point and branch distribution point. little confused!!!. which ports i require to be open between site server with distribution and remote site distribution point.
    Cheers.

    Hi,
    Regarding the doc here:
    http://technet.microsoft.com/en-us/library/bb632618.aspx
    Site Server -- > Distribution Point
    SMB 445 TCP
    RPC Endpoint Mapper 135 UDP and TCP
    RPC dynamic TCP
    Site Server < -- > Site Server
    SMB 445 TCP
    Point to Point Tunneling Protocal (PPTP) 1723 TCP
    Follow me through my blog and Twitter!

  • Software Updates using distribution points

    Hi,
    I have primary site and configured all settings well. Also I installed SUP on the primary site. I have 3 other sites with slow connection. I need to plan SU for them. is it better to create secondary site on the 3 sites or Distribution points will be
    enough for them?
    Thanks,
    Kareem Behery

    I agree with Wally. Adding 3 Seconday Sites with a SUP, will add both administrative overhead and make the installation more complex.
    As a general rule, I always recomend to go with the simple solution. Then you can always "upgrade" one or more of the sites if you later finds out that you need to.
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
    @ronnipedersen

Maybe you are looking for

  • GRN and SRN report

    Dear SAP MM, Can you please tell me where can I extract the GRN and SRN in a certain period? Any report or table? please help. thanks zhie.

  • Error in EA00 - EITR Billing Document No. does not exist

    Hi Experts, I am tryign to Final bill a moved out contract for the dates 16.05.2007 to 31.12.2008. The joint invoicing condition is 1. When I try to bill these billing documents through EA00 I am getting the Error "EITR <Billing Do. no.> A does not e

  • How to get higher resolution previews in HDR Pro

    I often make HDR images by exporting a bracket from lightroom into photoshop via right click>merge to HDR in photoshop.  When the dialog comes up it is always a very low resolution preview.  When I go to zoom in (cmd +) the resolution remains the sam

  • OS Authentication in Solaris while using JDBC

    hi, I am trying to Authenticate a user, who is already connected to the database from a simple java class. Here in this case i am using Oracle 10g. My query is : Authenticate the user from the Java program without providing the password. The OS that

  • Brand New mobo (P6NGM) with IRQ Conflicts, PLEASE help

    I've posted multiple times in another well respected PC forum and have not resolved my issue yet. Would GREATLY appreciate assistance. Here's my story and attempts: I'm building a new PC for my parents: mobo: MSI P6NGM cpu: Pentium dual core e2200 (8