WHS 2011 Health Status not available
-
2011年5月9日 9:28
Recently my WHS 2011 (release) server has stopped reporting health status. I've tracked it down to the "Windows Server Health Service" having stopped running. Both this and the "Windows Server Domain Name Management service" seems to stop now and again. I'm not sure if the two are related, but they are both set to start "Automatically" and restart on the first two fail attemps. When the Windows Server Health Service stops the other one seems to stop around the same time as well.
Manuall staring the services fixes the problem for the time being, but some hours/days later I notice the server is not reporting healt status anymore.
From the system event log: Log Name: System Source: Service Control Manager Date: 07.05.2011 16:11:57 Event ID: 7034 Description: The Windows Server Health Service service terminated unexpectedly. It has done this 3 time(s). Log Name: System Source: Service Control Manager Date: 07.05.2011 16:11:57 Event ID: 7034 Description: The Windows Server Domain Name Management service terminated unexpectedly. It has done this 3 time(s). In the Application log I find this error at the same time Log Name: Application Source: .NET Runtime Date: 07.05.2011 16:11:57 Event ID: 1026 Keywords: Classic Description: Application: SharedServiceHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ServiceModel.CommunicationException Stack: Server stack trace: at System.ServiceModel.Channels.StreamConnection.Read(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout) at System.ServiceModel.Channels.SessionConnectionReader.Receive(TimeSpan timeout) at System.ServiceModel.Channels.SynchronizedMessageSource.Receive(TimeSpan timeout) at System.ServiceModel.Channels.FramingDuplexSessionChannel.Receive(TimeSpan timeout) at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceive(TimeSpan timeout, Message& message) at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.KeepaliveInputChannelInnards.<TryReceive>b__c(TimeSpan t) at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.InputChannelRequeuer`1.<>c__DisplayClass28.<TryReceive>b__27() at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.InputChannelRequeuer`1.DoReceive(Func`1 innerReceive) at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.InputChannelRequeuer`1.TryReceive(TimeSpan timeout, TResult& result, Func`2innerTryReceive) at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.WindowsServerSolutions.RemoteAccess.Domains.IDomainMaintenanceManager.ValidateCredentials() at Microsoft.WindowsServerSolutions.Connectivity.Jobs.DomainNameProviderCredentialsDiagnosticsJob.OnRun(DiagnosticsResult result, ConnectivityEnvironment environment) at Microsoft.WindowsServerSolutions.Connectivity.DiagnosticsJob.RunAndCatch(DiagnosticsResult result, ConnectivityEnvironment environment) 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.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(System.Runtime.Remoting.Messaging.Message, Boolean) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(System.Object, System.Runtime.Remoting.Proxies.MessageData ByRef) at Microsoft.WindowsServerSolutions.Connectivity.DiagnosticsJob+RunHandler.EndInvoke(System.IAsyncResult) at Microsoft.WindowsServerSolutions.Connectivity.DiagnosticsJob.Run(Microsoft.WindowsServerSolutions.Connectivity.ConnectivityEnvironment) at Microsoft.WindowsServerSolutions.Connectivity.DiagnosticsRunner.RunOneTest(System.Object) at System.Threading.ExecutionContext.runTryCode(System.Object) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() Log Name: Application Source: Application Error Date: 07.05.2011 16:11:57 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic Description: Faulting application name: SharedServiceHost.exe, version: 6.1.1839.0, time stamp: 0x4d38a956 Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c78c Exception code: 0xe0434352 Fault offset: 0x000000000000a49d Faulting process id: 0x488 Faulting application start time: 0x01cc0cb87aae1f16 Faulting application path: C:\Program Files\Windows Server\Bin\SharedServiceHost.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: f74cb329-78b3-11e0-8682-000ae48708c7 Log Name: Application Source: Application Error Date: 07.05.2011 16:11:56 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic Description: Faulting application name: SharedServiceHost.exe, version: 6.1.1839.0, time stamp: 0x4d38a956 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x80131623 Fault offset: 0x000007ff00176eee Faulting process id: 0x1ac4 Faulting application start time: 0x01cc0cb87a5aaabb Faulting application path: C:\Program Files\Windows Server\Bin\SharedServiceHost.exe Faulting module path: unknown Report Id: f6e3c975-78b3-11e0-8682-000ae48708c7 Log Name: Application Source: .NET Runtime Date: 07.05.2011 16:11:55 Event ID: 1025 Task Category: None Level: Error Keywords: Classic Description: Application: SharedServiceHost.exe Framework Version: v4.0.30319 Description: The application requested process termination through System.Environment.FailFast(string message). Message: Unhandled exception from operation: Service type: Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainProviderManager Operation: [http://tempuri.org/] IDomainMaintenanceManager.ValidateCredentials Async: False Parameters: System.IO.FileNotFoundException: Could not load msidcrl40.dll from C:\Program Files\Common Files\Microsoft Shared\Windows Live\msidcrl40.dll at Microsoft.WindowsServerSolutions.Identity.WindowsLive.ManagedIDCRL.Initialize(String proxy, Int32 version) at Microsoft.WindowsServerSolutions.RemoteAccess.Domains.WindowsLiveProviderBase.GetLiveRpsToken(DomainProviderCredentials credentials) at Microsoft.WindowsServerSolutions.RemoteAccess.Domains.WindowsLiveProviderBase.ValidateCredentials() at Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainProviderManager.ValidateCredentials() at SyncInvokeValidateCredentials(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.ExceptionScreener._ScreenForExceptions(GeneralInvoker invokeMe, Object instance, Object[] inputs, Object[]& outputs) Stack: at System.Environment.FailFast(System.String, System.Exception) at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.ExceptionScreener._ScreenForExceptions(GeneralInvoker, System.Object, System.Object[], System.Object[] ByRef) at Microsoft.WindowsServerSolutions.Common.ProviderFramework.Internal.ExceptionScreener.Invoke(System.Object, System.Object[], System.Object[] ByRef) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(System.ServiceModel.Dispatcher.MessageRpc ByRef) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(System.ServiceModel.Dispatcher.MessageRpc ByRef) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean) at System.ServiceModel.Dispatcher.MessageRpc+Wrapper.Resume(Boolean ByRef) at System.ServiceModel.Dispatcher.ThreadBehavior.CleanThreadCallback(System.Object) at System.Runtime.IOThreadScheduler+ScheduledOverlapped.IOCallback(UInt32, UInt32, System.Threading.NativeOverlapped*) at System.Runtime.Fx+IOCompletionThunk.UnhandledExceptionFrame(UInt32, UInt32, System.Threading.NativeOverlapped*) at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
すべての返信
-
2011年5月9日 11:33Oh, by the way. It's been reported to connect already. Just wanted to post here as well because of the 5.000 character limit on reports in connect.
HP MediaSmart EX475, 3 TB storage, 2 GB ram and dual core CPU (BE2300) upgrade. Author of WHS File Manager Add-In, WHS Jungle Disk Add-in and WHS Media Connect Configuration Add-in. http://blog.codewrench.net/whs-add-ins/ -
2011年5月9日 11:40
I found the problem. I'm a Boxee Box (d-link) owner and it was suggested in the Boxee forums to remove any remnants of Live Messenger on the PC/server you shared media from in order to solve some connection issue I had. Since I don't use live messenger on my WHS box I uninstalled "Windows Live Login assistant".
That's what causing the Windows Server Domain Name Management service to crash since it uses Windows Live-ID to authenticate. The file
was uninstalled causingC:\Program Files\Common Files\Microsoft Shared\Windows Live\msidcrl40.dll
to crash, also bringing downSharedServiceHost.exe
Windows Server Health Service.
Why the two services are hosted in the same "sharedservicehost" I don't know. One service should not be able to bring down another like this. Anyway I just downloaded and installed the live messenger login assistant from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9ba199ef-3086-4f12-970d-8745be104600
Now it seems the service is stable again.
HP MediaSmart EX475, 3 TB storage, 2 GB ram and dual core CPU (BE2300) upgrade. Author of WHS File Manager Add-In, WHS Jungle Disk Add-in and WHS Media Connect Configuration Add-in. http://blog.codewrench.net/whs-add-ins/- 回答の候補に設定 Pål Andreassen 2011年5月9日 11:40