Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Server Update Service
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



wsus clients not contact wsus server error = 0x80244023 and 0x8019

Server Update Service


Reply
 
Thread Tools Search this Thread
  #1  
Old 03-03-2009
Member
 
Join Date: Aug 2006
Posts: 253
wsus clients not contact wsus server error = 0x80244023 and 0x8019

I have checked out different of my WSUS client but not all, that do not contact WSUS server since last 30 days or so and the below error list are generating in the 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

Can anyone please help me sort out this problem?

Reply With Quote
  #2  
Old 03-03-2009
Member
 
Join Date: Dec 2004
Posts: 419
Re: wsus clients not contact wsus server error = 0x80244023 and 0x8019

The error 0x801901F8 - 2145844744 BG_E_HTTP_ERROR_504 the request was timed out waiting for a gateway can be typically a DNS issue. The error 0x80244023 WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT HTTP 504, looks to me like the client will not be able to find the WSUS server as named. Either hostname is not in the DNS service or the IP Address given by the DNS is on an not reachable network.
Reply With Quote
  #3  
Old 03-03-2009
Member
 
Join Date: Aug 2006
Posts: 253
Re: wsus clients not contact wsus server error = 0x80244023 and 0x

Thanks for the reply but if I am trying to ping the hostnam from the WSUS client, then the dns returns me the correct ip and if I am opening the hostname by the browser then I dont get the problem. So, I cant understand what is the issue here.
Reply With Quote
  #4  
Old 06-03-2009
Member
 
Join Date: Aug 2006
Posts: 253
I have now changed the DNS name for the ip address and WSUS client connected ok with WSUS server. But I cannot understand why it stopped working one day to the other?
Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Server Update Service


Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "wsus clients not contact wsus server error = 0x80244023 and 0x8019"
Thread Thread Starter Forum Replies Last Post
Clients not reporting to WSUS server Leland Server Update Service 10 10-11-2009 09:35 PM
WSUS 3.0 Clients are not showing in wsus admin console Rock41 Windows Update 7 25-09-2009 01:28 AM
WSUS 3.0 Clients are not showing in wsus admin console - different twist troy04 Windows Update 3 07-01-2009 10:45 AM
Error: 'you do not have permissions required to access the wsus server' while connecting wsus server via console HudSon Server Update Service 2 15-08-2008 01:18 AM
clients not reporting status after updating WSUS 2 to WSUS 3.0 Dhananjay Server Update Service 4 17-07-2007 10:37 PM


All times are GMT +5.5. The time now is 11:14 PM.