Solved: Server Manager Keeps Crashing

Create Account

Windows Server 2016

Questions

Followers

Top Experts

David Johnson, CD🇨🇦

Server Manager Keeps Crashing

Faulting application name: ServerManager.exe, version: 10.0.14393.1737, time stamp: 0x59bafc80
Faulting module name: KERNELBASE.dll, version: 10.0.14393.1770, time stamp: 0x59bf2ba6
Exception code: 0xe0434352
Fault offset: 0x0000000000033c58
Faulting process id: 0x6d84
Faulting application start time: 0x01d3615904b9ea7d
Faulting application path: C:\WINDOWS\system32\ServerManager.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 75df48a2-559e-40ac-af90-d586582aeed3
Faulting package full name:
Faulting package-relative application ID:

I've done the obvious:
dism /online /cleanup-image /restorehealth
sfc /scannow
reboot
.net framework repair tool
clear cache file under “%userprofile%\AppData\Roaming\Microsoft\MMC
deleted C:\Users\david\AppData\Local\Microsoft_Corporation\ServerManager.exe_StrongName_m3xk0k0ucj0oj3ai2hibnhnv4xobnimj
restarted computer

still crashes. See video https://www.screencast.com/t/arBmz977RSe

2 events
Faulting application name: ServerManager.exe, version: 10.0.17763.168, time stamp: 0xc452e206
Faulting module name: KERNELBASE.dll, version: 10.0.17763.802, time stamp: 0x86aa4cf5
Exception code: 0xe0434352
Fault offset: 0x0000000000039129
Faulting process id: 0x524
Faulting application start time: 0x01d5987aca34256d
Faulting application path: C:\Windows\system32\ServerManager.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 6db9a785-353d-4b0c-ba3f-57be62372435
Faulting package full name:
Faulting package-relative application ID:

.Net Framework error
Application: ServerManager.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
at Microsoft.Windows.ServerManager.Common.Data.RoleFeatureRoot..ctor(System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature>)
at Microsoft.Windows.ServerManager.Common.Data.Server.UpdateFeatures(System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature>, System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature> ByRef, System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature> ByRef, System.Collections.Generic.ICollection`1<Int32> ByRef)
at Microsoft.Windows.ServerManager.Common.Data.DataAccessLayer.UpdateFeatures(System.String, System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature>)
at Microsoft.Windows.ServerManager.Common.Refresh.FeatureDataProcessor.OnCompleted(System.Exception)
at Microsoft.Windows.ServerManager.Common.Refresh.DataProcessorService.MethodCompleted(System.String, System.String, System.Exception)
at Microsoft.Windows.ServerManager.Common.Refresh.DataProcessorService.OnMethodCompleted(Microsoft.Windows.ServerManager.Common.Refresh.NodeAccessItem, System.String)
at Microsoft.Windows.ServerManager.Common.Refresh.NodeAccessItem.RaiseOperationCompletedEvent(System.String)
at Microsoft.Windows.ServerManager.Common.Refresh.NodeRefreshItem+<>c__DisplayClass13_0.<InvokeMethod>b__0(System.String, System.String, System.String, System.String)
at Microsoft.Windows.ServerManager.Common.NodeAccess.InvokeMethodOperation.OnCompleted()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncCallbacksReceiverBase.CallUnderOriginalExecutionContext(System.Action)
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncCallbacksReceiverBase.CallIntoUserCallback(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext, System.Action, Boolean, Boolean)
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncObserverProxyBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnCompletedInternal(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext)
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncCallbacksReceiverBase.InvokeWhenOperationIsSet(System.Action`1<Microsoft.Management.Infrastructure.Internal.Operations.CimOperation>)
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncObserverProxyBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ProcessNativeCallback(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext, System.__Canon, Boolean, Microsoft.Management.Infrastructure.Native.MiResult, System.String, Microsoft.Management.Infrastructure.Native.InstanceHandle)
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncMethodResultObserverProxy.InstanceResultCallback(Microsoft.Management.Infrastructure.Native.OperationCallbackProcessingContext, Microsoft.Management.Infrastructure.Native.OperationHandle, Microsoft.Management.Infrastructure.Native.InstanceHandle, Boolean, Microsoft.Management.Infrastructure.Native.MiResult, System.String, Microsoft.Management.Infrastructure.Native.InstanceHandle)
at Microsoft.Management.Infrastructure.Native.ExceptionSafeInstanceResultCallback.InvokeUserCallback()
at UserFilteredExceptionHandling.UserFilteredExceptionMethod(System.Action, System.Func`2<System.Exception,Boolean>, System.Action`1<System.Exception>)
at Microsoft.Management.Infrastructure.Native.ExceptionSafeCallbackBase.InvokeUserCallbackAndCatchInternalErrors()

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Pete Long🇬🇧

It's obviously .net related somehow :)

I'm assuming you've read this.

</P>

David Johnson, CD🇨🇦

ASKER

ran the .net framework cleanup tool ... no change

McKnife🇩🇪

I'd try safe mode for a test.
Or repair windows using an in-place upgrade (much more success as compared to dism /restorehealth), although I never used it on a DC.

Another question for you: you list 2 different versions of servermanager.exe, one from server 2019 and the other from 2016 - what OS is this about? Your screencast shows 2019.

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Philip Elder🇨🇦

When were updates run?

David Johnson, CD🇨🇦

ASKER

Sorry about that it is Server 2019.. The top part was from an unanswered questions on answers.microsoft.com.
I think I've narrowed it down. One server hangs when I add it.. then server manager crashes.

Philip Elder🇨🇦

Make sure Firewall Logging is enabled along with the firewall for the three profiles on the "offending" server. Maybe there's an errant rule in there blocking the Server Manager's poll.

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

David Johnson, CD🇨🇦

ASKER

no dropped packets ... I'd like to reset server manager or at least remove machines one at a time until it works.

Philip Elder🇨🇦

Check Server Manager on each of the remote machines to make sure it's happy there?

David Johnson, CD🇨🇦

ASKER

The problem is user specific .. yet I can't find out where.. tried copying appdata from a working config but still shows the same serverlist and crashes when I log back in.

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

ASKER CERTIFIED SOLUTION

Philip Elder🇨🇦

membership

Signing up is free and takes 30 seconds. No credit card required.

Create Account

David Johnson, CD🇨🇦

ASKER

Thanks to all participants.

David Johnson, CD🇨🇦

ASKER

You read my mind..

Philip Elder🇨🇦

Great minds! ;)

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Windows Server 2016

Questions

Followers

Top Experts

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates. Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.