|
| |||||||||
| Tags: 0x8019, 0x80244023, clients, wsus |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| wsus clients not contact wsus server error = 0x80244023 and 0x8019
why various of wsus client, not all, did not contact wsus server since last 28 days, below error list in windowsupdate.log ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2009-03-02 15:31:52:242 1876 101c Agent ********* 2009-03-02 15:31:52:242 1876 101c Agent * Online = Yes; Ignore download priority = No 2009-03-02 15:31:52:242 1876 101c Agent * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1" 2009-03-02 15:31:52:242 1876 101c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2009-03-02 15:31:52:242 1876 101c Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab: 2009-03-02 15:31:52:273 1876 101c Misc Microsoft signed: Yes 2009-03-02 15:31:52:648 1876 101c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f8 2009-03-02 15:31:52:648 1876 101c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f8 2009-03-02 15:31:52:882 1876 101c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f8 2009-03-02 15:31:52:882 1876 101c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f8 2009-03-02 15:31:53:148 1876 101c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f8 2009-03-02 15:31:53:148 1876 101c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f8 2009-03-02 15:31:53:320 1876 101c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f8 2009-03-02 15:31:53:335 1876 101c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f8 2009-03-02 15:31:53:335 1876 101c Misc WARNING: DownloadFileInternal failed for http://altiris:8530/selfupdate/wuident.cab: error 0x801901f8 2009-03-02 15:31:53:335 1876 101c Setup FATAL: IsUpdateRequired failed with error 0x80244023 2009-03-02 15:31:53:335 1876 101c Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80244023 2009-03-02 15:31:53:335 1876 101c Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80244023 2009-03-02 15:31:53:335 1876 101c Agent * WARNING: Skipping scan, self-update check returned 0x80244023 2009-03-02 15:31:54:617 1876 101c Agent * WARNING: Exit code = 0x80244023 2009-03-02 15:31:54:617 1876 101c Agent ********* 2009-03-02 15:31:54:617 1876 101c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2009-03-02 15:31:54:617 1876 101c Agent ************* 2009-03-02 15:31:54:617 1876 101c Agent WARNING: WU client failed Searching for update with error 0x80244023 2009-03-02 15:31:54:617 1876 11fc AU >>## RESUMED ## AU: Search for updates [CallId = {5267A692-AE8B-4851-88BA-E1F5EE0A3A2B}] 2009-03-02 15:31:54:617 1876 11fc AU # WARNING: Search callback failed, result = 0x80244023 2009-03-02 15:31:54:617 1876 11fc AU # WARNING: Failed to find updates with error code 80244023 2009-03-02 15:31:54:617 1876 11fc AU ######### 2009-03-02 15:31:54:617 1876 11fc AU ## END ## AU: Search for updates [CallId = {5267A692-AE8B-4851-88BA-E1F5EE0A3A2B}] 2009-03-02 15:31:54:617 1876 11fc AU ############# 2009-03-02 15:31:54:617 1876 11fc AU AU setting next detection timeout to 2009-03-02 18:29:11 2009-03-02 15:31:54:617 1876 11fc AU Setting AU scheduled install time to 2009-03-03 15:00:00 2009-03-02 15:46:25:685 1876 101c PT WARNING: Cached cookie has expired or new PID is available 2009-03-02 15:46:25:685 1876 101c PT Initializing simple targeting cookie, clientId = d99edd47-3265-414c-b14a-e2a65fa35c55, target group = , DNS name = mv-oap-ws085.nonstoptv.com.ar 2009-03-02 15:46:25:685 1876 101c PT Server URL = http://altiris:8530/SimpleAuthWebSer...impleAuth.asmx 2009-03-02 15:46:25:919 1876 101c PT WARNING: GetAuthorizationCookie failure, error = 0x80244023, soap client error = 10, soap error code = 0, HTTP status code = 504 2009-03-02 15:46:25:919 1876 101c PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244023 2009-03-02 15:46:25:919 1876 101c PT WARNING: PopulateAuthCookies failed: 0x80244023 2009-03-02 15:46:25:919 1876 101c PT WARNING: RefreshCookie failed: 0x80244023 2009-03-02 15:46:25:919 1876 101c PT WARNING: RefreshPTState failed: 0x80244023 2009-03-02 15:46:25:919 1876 101c PT WARNING: PTError: 0x80244023 2009-03-02 15:46:25:919 1876 101c Report WARNING: Reporter failed to upload events with hr = 80244023 Please anyone can help to solve my problem? |
|
#2
| |||
| |||
| Re: wsus clients not contact wsus server error = 0x80244023 and 0x8019
"mcantalupi" <mcantalupi@discussions.microsoft.com> wrote in message news:459FD1ED-284B-4F06-831F-F87693B3F293@microsoft.com... > DownloadFileInternal failed for > http://altiris:8530/selfupdate/wuident.cab: > error 0x801901f8 0x801901F8 -2145844744 BG_E_HTTP_ERROR_504 The request was timed out waiting for a gateway. Can typically be a DNS issue > 2009-03-02 15:46:25:685 1876 101c PT Server URL = > http://altiris:8530/SimpleAuthWebSer...impleAuth.asmx > 2009-03-02 15:46:25:919 1876 101c PT WARNING: > GetAuthorizationCookie failure, error = 0x80244023, soap client error = > 10, > soap error code = 0, HTTP status code = 504 0x80244023 WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT HTTP 504 - the request was timed out waiting for a gateway. Looks to me like the client can't find the WSUS Server as named. Either hostname 'altiris' is not in the DNS service, or the IP Address given by the DNS for 'altiris' is on an unreachable network. -- Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009) MS WSUS Website: http://www.microsoft.com/wsus My Websites: http://www.onsitechsolutions.com; http://wsusinfo.onsitechsolutions.com My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin |
|
#3
| |||
| |||
| Re: wsus clients not contact wsus server error = 0x80244023 and 0x
thanks Lawrence, but when I ping the "altiris" from the wsus client, the dns returns me the correct ip (192.168.0.8) and when I come to http://altiris:8530 by the browser, I have no problem. So I do not understand where is the problem. "Lawrence Garvin (MVP)" wrote: > "mcantalupi" <mcantalupi@discussions.microsoft.com> wrote in message > news:459FD1ED-284B-4F06-831F-F87693B3F293@microsoft.com... > > > DownloadFileInternal failed for > > http://altiris:8530/selfupdate/wuident.cab: > > error 0x801901f8 > > 0x801901F8 -2145844744 BG_E_HTTP_ERROR_504 The request was timed out waiting > for a gateway. Can typically be a DNS issue > > > > 2009-03-02 15:46:25:685 1876 101c PT Server URL = > > http://altiris:8530/SimpleAuthWebSer...impleAuth.asmx > > 2009-03-02 15:46:25:919 1876 101c PT WARNING: > > GetAuthorizationCookie failure, error = 0x80244023, soap client error = > > 10, > > soap error code = 0, HTTP status code = 504 > > 0x80244023 WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT HTTP 504 - the request was > timed out waiting for a gateway. > > Looks to me like the client can't find the WSUS Server as named. > > Either hostname 'altiris' is not in the DNS service, > or the IP Address given by the DNS for 'altiris' is on an unreachable > network. > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus > My Websites: http://www.onsitechsolutions.com; > http://wsusinfo.onsitechsolutions.com > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin > |
|
#4
| |||
| |||
| Re: wsus clients not contact wsus server error = 0x80244023 and 0x
I change the DNS name for the ip adress and wsus client connected ok with wsus server. I don“t know Why stopped working one day to the other? Thanks! "mcantalupi" wrote: > thanks Lawrence, but when I ping the "altiris" from the wsus client, the > dns returns me the correct ip (192.168.0.8) and when I come to > http://altiris:8530 by the browser, I have no problem. So I do not understand > where is the problem. > > > > "Lawrence Garvin (MVP)" wrote: > > > "mcantalupi" <mcantalupi@discussions.microsoft.com> wrote in message > > news:459FD1ED-284B-4F06-831F-F87693B3F293@microsoft.com... > > > > > DownloadFileInternal failed for > > > http://altiris:8530/selfupdate/wuident.cab: > > > error 0x801901f8 > > > > 0x801901F8 -2145844744 BG_E_HTTP_ERROR_504 The request was timed out waiting > > for a gateway. Can typically be a DNS issue > > > > > > > 2009-03-02 15:46:25:685 1876 101c PT Server URL = > > > http://altiris:8530/SimpleAuthWebSer...impleAuth.asmx > > > 2009-03-02 15:46:25:919 1876 101c PT WARNING: > > > GetAuthorizationCookie failure, error = 0x80244023, soap client error = > > > 10, > > > soap error code = 0, HTTP status code = 504 > > > > 0x80244023 WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT HTTP 504 - the request was > > timed out waiting for a gateway. > > > > Looks to me like the client can't find the WSUS Server as named. > > > > Either hostname 'altiris' is not in the DNS service, > > or the IP Address given by the DNS for 'altiris' is on an unreachable > > network. > > > > -- > > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > > Principal/CTO, Onsite Technology Solutions, Houston, Texas > > Microsoft MVP - Software Distribution (2005-2009) > > > > MS WSUS Website: http://www.microsoft.com/wsus > > My Websites: http://www.onsitechsolutions.com; > > http://wsusinfo.onsitechsolutions.com > > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin > > |
|
#5
| |||
| |||
| Re: wsus clients not contact wsus server error = 0x80244023 and 0x
Lawrence, here is the output from altiris (wsus server) WSUS Client Diagnostics Tool Checking Machine State Checking for admin rights to run tool . . . . . . . . . PASS Automatic Updates Service is running. . . . . . . . . . PASS Background Intelligent Transfer Service is not running. PASS Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS This version is WSUS 2.0 Checking AU Settings AU Option is 4: Scheduled Install . . . . . . . . . . . PASS Option is from Policy settings Checking Proxy Configuration Checking for winhttp local machine Proxy settings . . . PASS Winhttp local machine access type <Direct Connection> Winhttp local machine Proxy. . . . . . . . . . NONE Winhttp local machine ProxyBypass. . . . . . . NONE Checking User IE Proxy settings . . . . . . . . . . . . PASS User IE Proxy 192.168.0.11:3128 User IE ProxyByPass. . . . . . . . . . . . . . NONE User IE AutoConfig URL Proxy . . . . . . . . . NONE User IE AutoDetect AutoDetect not in use Checking Connection to WSUS/SUS Server WUServer = http://altiris:8530 WUStatusServer = http://altiris:8530 UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS VerifyWUServerURL() failed with hr=0x801901f8 No Error description could be found "Lawrence Garvin (MVP)" wrote: > "mcantalupi" <mcantalupi@discussions.microsoft.com> wrote in message > news:D41080BF-F410-4825-BBC8-A8F05BD69313@microsoft.com... > > > and when I come to http://altiris:8530 by the browser, I have no problem. > > Well, here's an interesting situation. You *should* have problems attempting > to access http://altiris:8530 from the browser, since there is *no* web > browsable content in a WSUS installation. > > Perhaps your WinHTTP configuration is incorrect, and is routing the WinHTTP > traffic someplace other than where it should. > > What happens if you run the Client Diagnostic Tool on this system? Please > post the output. > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus > My Websites: http://www.onsitechsolutions.com; > http://wsusinfo.onsitechsolutions.com > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin > |
|
#6
| |||
| |||
| Re: wsus clients not contact wsus server error = 0x80244023 and 0x
In this moment using the ip is working ok, but in my pc y have one problem, here is the log 2009-03-06 15:46:32:249 1884 14fc PT Server URL = http://192.168.0.8:8530/SimpleAuthWe...impleAuth.asmx 2009-03-06 15:48:00:765 1884 14fc PT +++++++++++ PT: Synchronizing extended update info +++++++++++ 2009-03-06 15:48:00:765 1884 14fc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.0.8:8530/ClientWebService/client.asmx 2009-03-06 15:48:03:593 1884 14fc Agent * Added update {27C76C3D-F3DC-4C45-9A87-189F4AB4C52C}.100 to search result 2009-03-06 15:48:03:593 1884 14fc Agent * Added update {0975455F-D040-4EEC-9013-81D19BF3DD0A}.102 to search result 2009-03-06 15:48:03:593 1884 14fc Agent * Found 2 updates and 47 categories in search; evaluated appl. rules of 460 out of 897 deployed entities 2009-03-06 15:48:03:593 1884 14fc Agent ********* 2009-03-06 15:48:03:593 1884 14fc Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2009-03-06 15:48:03:593 1884 14fc Agent ************* 2009-03-06 15:48:03:609 1884 11c0 AU >>## RESUMED ## AU: Search for updates [CallId = {13ED8A4B-D3E8-4446-8917-B16714191C46}] 2009-03-06 15:48:03:609 1884 11c0 AU # 2 updates detected 2009-03-06 15:48:03:624 1884 11c0 AU ######### 2009-03-06 15:48:03:624 1884 11c0 AU ## END ## AU: Search for updates [CallId = {13ED8A4B-D3E8-4446-8917-B16714191C46}] 2009-03-06 15:48:03:624 1884 11c0 AU ############# 2009-03-06 15:48:03:624 1884 11c0 AU AU setting next detection timeout to 2009-03-06 18:41:58 2009-03-06 15:48:03:624 1884 11c0 AU Setting AU scheduled install time to 2009-03-07 15:00:00 2009-03-06 15:48:08:593 1884 14fc Report REPORT EVENT: {D37917AB-CA44-475A-BB78-7F7445D8A73D} 2009-03-06 15:48:03:593-0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 2 updates. 2009-03-06 15:48:08:593 1884 14fc Report REPORT EVENT: {382A5B99-5789-408B-B368-6CE1F175FEF5} 2009-03-06 15:48:03:593-0200 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status. 2009-03-06 15:52:30:923 1884 14fc Report Uploading 2 events using cached cookie, reporting URL = http://192.168.0.8:8530/ReportingWeb...ebService.asmx 2009-03-06 15:52:30:985 1884 14fc Report Reporter successfully uploaded 2 events. 2009-03-06 15:58:34:894 1884 11c0 AU AU checked download status and it changed: Downloading is not paused 2009-03-06 15:58:34:894 1884 11c0 AU AU setting pending client directive to 'Download Progress' 2009-03-06 15:58:41:066 1884 534 DnldMgr Error 0x80244023 occurred while downloading update; notifying dependent calls. 2009-03-06 15:58:41:066 1884 11c0 AU AU checked download status and it changed: Downloading is paused 2009-03-06 15:58:44:831 1884 11c0 AU AU checked download status and it changed: Downloading is not paused 2009-03-06 15:58:44:831 1884 11c0 AU AU setting pending client directive to 'Download Progress' 2009-03-06 15:58:49:925 1884 8b0 AU Launched new AU client for directive 'Download Progress', session id = 0x0 2009-03-06 15:58:50:113 3592 1580 Misc =========== Logging initialized (build: 7.2.6001.788, tz: -0200) =========== 2009-03-06 15:58:50:113 3592 1580 Misc = Process: C:\WINDOWS\system32\wuauclt.exe 2009-03-06 15:58:50:113 3592 1580 AUClnt Launched Client UI process 2009-03-06 15:58:50:332 3592 1580 Misc =========== Logging initialized (build: 7.2.6001.788, tz: -0200) =========== 2009-03-06 15:58:50:332 3592 1580 Misc = Process: C:\WINDOWS\system32\wuauclt.exe 2009-03-06 15:58:50:332 3592 1580 Misc = Module: C:\WINDOWS\system32\wucltui.dll 2009-03-06 15:58:50:332 3592 1580 CltUI AU client got new directive = 'Download Progress', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000 2009-03-06 15:58:50:332 3592 1580 CltUI AU client creating default WU/WSUS UI plugin 2009-03-06 15:58:56:347 1884 534 DnldMgr Error 0x80244023 occurred while downloading update; notifying dependent calls. 2009-03-06 15:58:56:347 1884 11c0 AU AU checked download status and it changed: Downloading is paused 2009-03-06 15:58:56:441 3592 1580 CltUI AU client got new directive = 'Shutdown', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return = 0x00000000 2009-03-06 15:58:56:738 1884 8b0 AU AU received handle event Thanks! "Lawrence Garvin (MVP)" wrote: > "mcantalupi" <mcantalupi@discussions.microsoft.com> wrote in message > news:D41080BF-F410-4825-BBC8-A8F05BD69313@microsoft.com... > > > and when I come to http://altiris:8530 by the browser, I have no problem. > > Well, here's an interesting situation. You *should* have problems attempting > to access http://altiris:8530 from the browser, since there is *no* web > browsable content in a WSUS installation. > > Perhaps your WinHTTP configuration is incorrect, and is routing the WinHTTP > traffic someplace other than where it should. > > What happens if you run the Client Diagnostic Tool on this system? Please > post the output. > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus > My Websites: http://www.onsitechsolutions.com; > http://wsusinfo.onsitechsolutions.com > My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin > |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "wsus clients not contact wsus server error = 0x80244023 and 0x8019" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| WSUS 3.0 Clients are not showing in wsus admin console | Rock41 | Windows Update | 7 | 25-09-2009 01:28 AM |
| wsus client not contact wsus server | kurni | Server Update Service | 1 | 26-02-2009 06:50 PM |
| WSUS 3.0 Clients are not showing in wsus admin console - different twist | troy04 | Windows Update | 3 | 07-01-2009 10:45 AM |
| Clients cannot contact the WSUS 3.0 SP1 Server | Deza | Server Update Service | 1 | 25-02-2008 04:49 PM |
| Migrating WSUS Clients from one WSUS server to another | Mark Baker | Server Update Service | 4 | 09-02-2007 01:58 AM |