Windows update failure code 0x80244017 Win2016Server - no WSUS
hello,
i setting windows 2016 server standard user experience on vm. server has fixed ip address , belongs lan. when attempting run windows update, without setting wsus, getting error code 0x8024417. used powershell log, here (sorry, of messages in french think it's still readable) :
2017.02.17 09:03:23.9676043 948 2404 comapi * start * init search clientid = updateorchestrator
2017.02.17 09:03:23.9676122 948 2404 comapi * start * search clientid = updateorchestrator
2017.02.17 09:03:23.9963092 948 2404 agent * start * queueing finding updates [callerid = updateorchestrator id = 2]
2017.02.17 09:03:23.9963186 948 2404 agent removing service 00000000-0000-0000-0000-000000000000 sequential scan list
2017.02.17 09:03:23.9963249 948 2404 agent added service 00000000-0000-0000-0000-000000000000 sequential scan list
2017.02.17 09:03:23.9963784 948 2404 comapi search clientid = updateorchestrator
2017.02.17 09:03:24.0060183 948 1544 agent * end * queueing finding updates [callerid = updateorchestrator id = 2]
2017.02.17 09:03:24.0150655 948 1544 agent * start * finding updates callerid = updateorchestrator id = 2
2017.02.17 09:03:24.0150689 948 1544 agent online = yes; allowcachedresults = no; ignore download priority = no
2017.02.17 09:03:24.0150713 948 1544 agent criteria = isinstalled=0 , deploymentaction='installation' or ispresent=1 , deploymentaction='uninstallation' or isinstalled=1 , deploymentaction='installation' , rebootrequired=1 or isinstalled=0 , deploymentaction='uninstallation' , rebootrequired=1""
2017.02.17 09:03:24.0150777 948 1544 agent serviceid = {00000000-0000-0000-0000-000000000000} third party service
2017.02.17 09:03:24.0150796 948 1544 agent search scope = {machine}
2017.02.17 09:03:24.0150854 948 1544 agent caller sid applicability: s-1-5-21-2716271610-3083772117-2409260311-500
2017.02.17 09:03:24.0150872 948 1544 agent processdriverdeferrals set
2017.02.17 09:03:24.0150888 948 1544 agent registerservice set
2017.02.17 09:03:24.0198106 948 1544 misc got 9482f4b4-e343-43b6-b170-9a65bc822c77 redir secondaryserviceauth url: 117cab2d-82b1-4b5a-a08c-4d62dbee7782""
2017.02.17 09:03:24.0225073 948 1544 sls cocreateinstance failed: hr = 0x80040154
2017.02.17 09:03:24.0225135 948 1544 agent failed retrieve sls response data service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x80040154
2017.02.17 09:03:24.0225188 948 1544 agent caller service recovery failed opt in service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0x80040154
2017.02.17 09:03:24.0245796 948 1544 misc got 9482f4b4-e343-43b6-b170-9a65bc822c77 redir client/server url: https://fe2.update.microsoft.com/v6/clientwebservice/client.asmx""
2017.02.17 09:03:24.4093421 948 1544 protocoltalker serviceid = {9482f4b4-e343-43b6-b170-9a65bc822c77}, server url = https://fe2.update.microsoft.com/v6/clientwebservice/client.asmx
2017.02.17 09:03:24.4095643 948 1544 protocoltalker ok reuse existing configuration
2017.02.17 09:03:24.4095713 948 1544 protocoltalker existing cookie valid, use it
2017.02.17 09:03:25.3905411 948 1544 webservices auto proxy settings web service call.
2017.02.17 09:03:25.7227646 948 1544 webservices ws error: une erreur s??est produite lors de la communication avec le point de terminaison sur ?? https://fe2.update.microsoft.com/v6/clientwebservice/client.asmx ??.
2017.02.17 09:03:25.7227682 948 1544 webservices ws error: le serveur renvoy?? un code d????tat http ?? 403 (0x193) ?? avec le texte ?? forbidden ??.
2017.02.17 09:03:25.7227701 948 1544 webservices ws error: le serveur compris la demande mais il ne peut pas la satisfaire.
2017.02.17 09:03:25.7227720 948 1544 webservices ws error: l??op??ration n??a pas pu ??tre effectu??e car le canal ??t?? annul??.
2017.02.17 09:03:25.7227791 948 1544 webservices web service call failed hr = 80244017.
2017.02.17 09:03:25.7227807 948 1544 webservices current service auth scheme=0.
2017.02.17 09:03:25.7227953 948 1544 webservices current proxy auth scheme=0.
2017.02.17 09:03:25.7228076 948 1544 protocoltalker pterror: 0x80244017
2017.02.17 09:03:25.7228095 948 1544 protocoltalker syncupdates_withrecovery failed. 0x80244017
2017.02.17 09:03:25.7228170 948 1544 protocoltalker syncupdates round trips: 1
2017.02.17 09:03:25.7228195 948 1544 protocoltalker sync of updates 0x80244017
2017.02.17 09:03:25.7228329 948 1544 protocoltalker syncserverupdatesinternal failed 0x80244017
2017.02.17 09:03:25.7329087 948 1544 agent failed synchronize, error = 0x80244017
2017.02.17 09:03:25.7691754 948 1544 agent exit code = 0x80244017
2017.02.17 09:03:25.7691781 948 1544 agent * end * finding updates callerid = updateorchestrator id = 2
2017.02.17 09:03:25.7732369 948 1000 comapi *resumed* search clientid = updateorchestrator
2017.02.17 09:03:25.7740324 948 1000 comapi updates found = 0
2017.02.17 09:03:25.7740349 948 1000 comapi exit code = 0x00000000, result code = 0x80244017
2017.02.17 09:03:25.7740369 948 1000 comapi * end * search clientid = updateorchestrator
2017.02.17 09:03:25.7744935 948 2404 comapi isusinternal:: disconnectcall failed, hr=8024000c
2017.02.17 09:03:34.3375944 1004 1652 comapi * start * sls discovery
2017.02.17 09:03:34.3432090 1004 1652 comapi *queued* sls discovery
2017.02.17 09:03:34.3539584 1004 4864 comapi *resumed* discovery
2017.02.17 09:03:34.3541231 1004 4864 api * end * discovery clientid
2017.02.17 09:03:34.3809235 1004 1652 comapi * start * sls discovery
2017.02.17 09:03:34.3826397 1004 1652 comapi *queued* sls discovery
2017.02.17 09:03:34.3865387 1004 980 comapi *resumed* discovery
2017.02.17 09:03:34.3866640 1004 980 api * end * discovery clientid
2017.02.17 09:03:34.3880104 1004 1652 comapi isusinternal:: disconnectcall failed, hr=8024000c
when try url https://fe2.update.microsoft.com/v6/clientwebservice/client.asmx on server, here getting:
this windows© communication foundation service.
metadata publishing service disabled.
if have access service, can enable metadata publishing completing following steps modify web or application configuration file:
1. create following service behavior configuration, or add <servicemetadata> element existing service behavior configuration:
<behaviors> <servicebehaviors> <behavior name="myservicetypebehaviors" > <servicemetadata httpgetenabled="true" /> </behavior> </servicebehaviors> </behaviors>
2. add behavior configuration service:
<service name="mynamespace.myservicetype" behaviorconfiguration="myservicetypebehaviors" > note: service name must match configuration name service implementation.
3. add following endpoint service configuration:
<endpoint contract="imetadataexchange" binding="mexhttpbinding" address="mex" /> note: service must have http base address add endpoint.
following example service configuration file metadata publishing enabled:
<configuration> <system.servicemodel> <services> <!-- note: service name must match configuration name service implementation. --> <service name="mynamespace.myservicetype" behaviorconfiguration="myservicetypebehaviors" > <!-- add following endpoint. --> <!-- note: service must have http base address add endpoint. --> <endpoint contract="imetadataexchange" binding="mexhttpbinding" address="mex" /> </service> </services> <behaviors> <servicebehaviors> <behavior name="myservicetypebehaviors" > <!-- add following element service behavior configuration. --> <servicemetadata httpgetenabled="true" /> </behavior> </servicebehaviors> </behaviors> </system.servicemodel></configuration>
i little stumped. me? tia
might try running troubleshooter.
regards, dave patrick ....
microsoft certified professional
microsoft mvp [windows server] datacenter management
disclaimer: posting provided "as is" no warranties or guarantees, , confers no rights.
Windows Server > Windows Server 2016 General
Comments
Post a Comment