Eu reinstalei o WSUS há alguns meses em um novo servidor como parte de uma atualização de hardware do servidor. Está funcionando normalmente baixando, autorizando e fornecendo patches para as estações de trabalho.
Especificação do sistema:
- HP DL360 G5
- Quad 2.5 Zeon
- 6 GB de RAM
- Não virtualizado
- WSUS 3.2.7600.3226
- SQL 2005 Express
- Windows 2003 R2 SP2
- SSL do WSS ativado
A cada seis horas, cinco eventos são registrados no log de eventos do aplicativo:
Source | Category | ID | Description
--------------------------------------------------------------------------------------
Windows Server Update Services | Web Services | 12052 | The DSS Authentication Web Service is not working.
Windows Server Update Services | Web Services | 12042 | The SimpleAuth Web Service is not working
Windows Server Update Services | Web Services | 12022 | The Client Web Service is not working
Windows Server Update Services | Web Services | 12032 | The Server Synchronization Web Service is not working
Windows Server Update Services | Web Services | 12012 | The API Remoting Web Service is not working
Além disso, o Rastreamento de pilha do .NET a seguir é registrado em C:\Program Files\Update Services\LogFiles\SoftwareDistribution.log
cada rastreamento de pilha é idêntico, exceto pelos nomes dos serviços:
2009-11-27 11:56:52.757 UTC Error WsusService.10 HmtWebServices.CheckApiRemotingWebService ApiRemoting WebService WebException:System.Net.WebException: The request failed with HTTP status 403: Forbidden.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.Internal.ApiRemoting.Ping(Int32 pingLevel)
at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckApiRemotingWebService(EventLoggingType type, HealthEventLogger logger)
at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckApiRemotingWebService(EventLoggingType type, HealthEventLogger logger)
at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger)
at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.Execute(EventLoggingType type)
at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.Execute(EventLoggingType type)
at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.Execute(Boolean waitIfNecessary, EventLoggingType loggingType)
at Microsoft.UpdateServices.Internal.HealthMonitoring.RemotingChannel.PrivateLogEvents()
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(IMessage reqMsg)
at System.Runtime.Remoting.Lifetime.LeaseSink.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)
at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(Object[] args)
at System.Runtime.Remoting.Channels.ChannelServices.DispatchMessage(IServerChannelSinkStack sinkStack, IMessage msg, IMessage& replyMsg)
at System.Runtime.Remoting.Channels.SoapServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.Ipc.IpcServerTransportSink.ServiceRequest(Object state)
at System.Runtime.Remoting.Channels.SocketHandler.ProcessRequestNow()
at System.Runtime.Remoting.Channels.SocketHandler.BeginReadMessageCallback(IAsyncResult ar)
at System.Runtime.Remoting.Channels.Ipc.IpcPort.AsyncFSCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
Até agora eu tentei o seguinte:
- Garantir a precisão das configurações de acordo com TechNet .
- Verificou-se que havia uma ligação adequada à ligação 127.0.0.1 no IIS.
- Passamos e verificamos as configurações no IIS de acordo com o TechNet .
Descobri que você pode executar o comando wsusutil checkhealth
para forçar a execução da verificação, wsusutil
pode ser encontrado em C:\Program Files\Update Services\Tools
. Quando este executável lhe dirá para verificar o log do aplicativo.