I can ping fine. One thing I noticed in the WindowsUpdate.log, the server URL listed in my email below is our normal management point. But we have a distribution point in our area. Shouldn't it be using that instead? The computer is getting an IP in the range of the boundary for that DP.
From: [email protected] [mailto:[email protected]] On Behalf Of Bradnan, Jerry Sent: Wednesday, January 21, 2015 10:51 AM To: [email protected] Subject: [mssms] RE: InstallSWUpdate step hanging Can you ping that server from the client? Is there any significant latency? It seems as though the client is having trouble communicating with the SUP. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, January 21, 2015 1:38 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: InstallSWUpdate step hanging I found some errors near the beginning of the WindowsUpdate.log file (attached, errors shown below). That led me to this post, which is really old: http://blogs.technet.com/b/sus/archive/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010.aspx No solution there. :/ 2015-01-21 08:56:40:465 532 934 PT WARNING: Cached cookie has expired or new PID is available 2015-01-21 08:56:40:746 532 934 Agent Created new random SusClientId b4c6e016-afdc-4468-81d2-b4f44c2847d3. Old Id: c4e492ae-ee40-46ab-9a23-59fa54982f29. 2015-01-21 08:56:40:746 532 934 PT Initializing simple targeting cookie, clientId = b4c6e016-afdc-4468-81d2-b4f44c2847d3, target group = , DNS name = nurscow02.csuchico.edu 2015-01-21 08:56:40:746 532 934 PT Server URL = http://cm-mp01.csuchico.edu:8530/SimpleAuthWebService/SimpleAuth.asmx 2015-01-21 08:58:01:909 532 934 PT WARNING: Exceeded max server round trips: 0x80244010 2015-01-21 08:58:01:909 532 934 PT WARNING: Sync of Updates: 0x80244010 2015-01-21 08:58:01:909 532 934 PT WARNING: SyncServerUpdatesInternal failed: 0x80244010 2015-01-21 08:58:01:909 532 934 Agent * WARNING: Failed to synchronize, error = 0x80244010 2015-01-21 08:58:01:909 532 934 Agent * WARNING: Exit code = 0x80244010 2015-01-21 08:58:01:909 532 934 Agent ********* 2015-01-21 08:58:01:909 532 934 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2015-01-21 08:58:01:909 532 934 Agent ************* 2015-01-21 08:58:01:909 532 934 Agent WARNING: WU client failed Searching for update with error 0x80244010 2015-01-21 08:58:01:940 532 894 AU >>## RESUMED ## AU: Search for updates [CallId = {2F0F1EEE-C99F-4189-AB79-C2CC66DEA94A}] 2015-01-21 08:58:01:940 532 894 AU # WARNING: Search callback failed, result = 0x80244010 2015-01-21 08:58:01:940 532 894 AU # WARNING: Failed to find updates with error code 80244010 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, January 21, 2015 10:19 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: InstallSWUpdate step hanging Check c:\windows\WindowsUpdate.log and see if you can nail down what hung it up? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Wednesday, January 21, 2015 12:54 PM To: '[email protected]' Subject: [mssms] RE: InstallSWUpdate step hanging Make sure you're not installing one of those double reboot updates. http://support.microsoft.com/kb/2894518 Also, too many updates "wears out" the process and I think it gives up, or it's waiting for a response that will never happen. It's really hard to troubleshoot it though. Sadly, because of this issue, I stopped wrestling with SCCM TS' for building and capturing and moved to MDT. It's faster and because it uses Microsoft Update double reboot patches don't affect it. Todd From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, January 21, 2015 11:43 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] InstallSWUpdate step hanging After this month's updates, our image process hangs while downloading updates. Attaching the smsts.log file. I use the console to add updates to the WIM, but it still does it. Any ideas? Waiting for job status notification ... InstallSWUpdate 1/21/2015 9:21:32 AM 3940 (0x0F64) Waiting for job status notification ... InstallSWUpdate 1/21/2015 9:22:32 AM 3940 (0x0F64) Waiting for job status notification ... InstallSWUpdate 1/21/2015 9:23:32 AM 3940 (0x0F64) Waiting for job status notification ... InstallSWUpdate 1/21/2015 9:24:32 AM 3940 (0x0F64) Waiting for job status notification ... InstallSWUpdate 1/21/2015 9:25:32 AM 3940 (0x0F64) Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357 [email protected]<mailto:[email protected]> The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
