none
Server Manager crashes on every Server OS (2012 R2, 2016, 2019) RRS feed

  • Question

  • Hi All,
    today I observed a strange behavior of our first Hyper-V 2012 R2 Cluster (26 Hyper-V Cluster Nodes). As soon as I start the Servermanager (ServerManager.exe) on one of this Nodes, it crashes when enumerating / doing the inventory of the "All Servers" Group.
    All Hyper-V Servers are fully patched (Patchday 13th of August 2019). So I tried to connect to one of the 26 Hyper-V-Cluster Nodes from one Standalone Server (OS Server 2016, fully patched on 13th of August 2019) and I get the same errors, as soon as the Servermanager on the 2016 Server enumerates the "All Servers" Group.

    I gave it one more try and did the same on a Standalone 2012 R2 Server (patched in July 2019) and even here I got the same errors.

    On our second Hyper-V 2012 R2 Cluster (same OS, same Config as our first Hyper-V Cluster) but with only 4 Nodes, fully patched on 13th of August 2019, everything works fine when opening Servermanager...


    Any Ideas? Are the 26 Hyper-V Nodes producing too much Info causing Servermanager to crash?

    I´ve tried everthing, creating a new ServerComponentCache, clearing the user.config in "...\AppData\Local\Microsoft_Corporation\ServerManager.exe_StrongName_m3xk0k0ucj0oj3ai2hibnhnv4xobnimj\6.3.0.0",
    creating a new ServerList.xml in "...\\AppData\Roaming\Microsoft\Windows\ServerManager", installed .net Framework 4.8 including all security patches on one of the Hyper-V nodes...

    I dont´t think, this has to do with Hyper-V itself...

    BUT:

    When I log in to one of our our first Hyper-V 2012 R2 ClusterNodes with only local admin rights (No Domain Admin Account), ServerManager works as expected, because he can´t get any Information from the other Hyper-V Cluster Nodes...!

    Are the 26 Hyper-V Nodes producing too much Info causing Servermanager to crash?

    Regards

    Juergen

    See Logs below:

    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: ServerManager.exe
      Problem Signature 02: 6.3.9600.17238
      Problem Signature 03: 53d0b3e7
      Problem Signature 04: Microsoft.Windows.ServerManager.Common
      Problem Signature 05: 6.3.9600.17238
      Problem Signature 06: 53d0b3ba
      Problem Signature 07: 1373
      Problem Signature 08: 1c6
      Problem Signature 09: System.ArgumentException
      OS Version: 6.3.9600.2.0.0.400.8
      Locale ID: 3079
      Additional Information 1: 50a0
      Additional Information 2: 50a0262852fbe0932493067405e0a59f
      Additional Information 3: 8b35
      Additional Information 4: 8b35aaccfbd87d8f369ca03b7e605722
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=280262
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    Log Name:      Application
    Source:        .NET Runtime
    Date:          22.08.2019 13:20:18
    Event ID:      1026
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XXXXXXXXXXXX
    Description:
    The description for Event ID 1026 from source .NET Runtime cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    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__DisplayClass4.<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()

    The handle is invalid
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1026</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2019-08-22T11:20:18.000000000Z" />
        <EventRecordID>876181</EventRecordID>
        <Channel>Application</Channel>
        <Computer>XXXXXXXXXXX</Computer>
        <Security />
      </System>
      <EventData>
        <Data>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&lt;Microsoft.Windows.ServerManager.Common.Data.IFeature&gt;)
       at Microsoft.Windows.ServerManager.Common.Data.Server.UpdateFeatures(System.Collections.Generic.ICollection`1&lt;Microsoft.Windows.ServerManager.Common.Data.IFeature&gt;, System.Collections.Generic.ICollection`1&lt;Microsoft.Windows.ServerManager.Common.Data.IFeature&gt; ByRef, System.Collections.Generic.ICollection`1&lt;Microsoft.Windows.ServerManager.Common.Data.IFeature&gt; ByRef, System.Collections.Generic.ICollection`1&lt;Int32&gt; ByRef)
       at Microsoft.Windows.ServerManager.Common.Data.DataAccessLayer.UpdateFeatures(System.String, System.Collections.Generic.ICollection`1&lt;Microsoft.Windows.ServerManager.Common.Data.IFeature&gt;)
       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+&lt;&gt;c__DisplayClass4.&lt;InvokeMethod&gt;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&lt;Microsoft.Management.Infrastructure.Internal.Operations.CimOperation&gt;)
       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&lt;System.Exception,Boolean&gt;, System.Action`1&lt;System.Exception&gt;)
       at Microsoft.Management.Infrastructure.Native.ExceptionSafeCallbackBase.InvokeUserCallbackAndCatchInternalErrors()
    </Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Application Error
    Date:          22.08.2019 13:20:18
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XXXXXXXXXX
    Description:
    The description for Event ID 1000 from source Application Error cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ServerManager.exe
    6.3.9600.17238
    53d0b3e7
    KERNELBASE.dll
    6.3.9600.19425
    5d26b6e9
    e0434352
    000000000000908c
    2090
    01d558db910e2803
    C:\Windows\system32\ServerManager.exe
    C:\Windows\system32\KERNELBASE.dll
    d1d0f033-c4ce-11e9-811b-0017a477280e
    The handle is invalid
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2019-08-22T11:20:18.000000000Z" />
        <EventRecordID>876182</EventRecordID>
        <Channel>Application</Channel>
        <Computer>XXXXXX</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ServerManager.exe</Data>
        <Data>6.3.9600.17238</Data>
        <Data>53d0b3e7</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>6.3.9600.19425</Data>
        <Data>5d26b6e9</Data>
        <Data>e0434352</Data>
        <Data>000000000000908c</Data>
        <Data>2090</Data>
        <Data>01d558db910e2803</Data>
        <Data>C:\Windows\system32\ServerManager.exe</Data>
        <Data>C:\Windows\system32\KERNELBASE.dll</Data>
        <Data>d1d0f033-c4ce-11e9-811b-0017a477280e</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Windows Error Reporting
    Date:          22.08.2019 14:09:14
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      xxxxxxxxxxxxx
    Description:
    Fault bucket , type 0
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: ServerManager.exe
    P2: 6.3.9600.17238
    P3: 53d0b3e7
    P4: Microsoft.Windows.ServerManager.Common
    P5: 6.3.9600.17238
    P6: 53d0b3ba
    P7: 1373
    P8: 1c6
    P9: System.ArgumentException
    P10:
    Attached files:
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ServerManager.ex_e1484b7fdd6fa16594f5f75d461e448c5927fa8_cba6274c_22c0aaad
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 1f82320a-c4d5-11e9-811b-0017a477280e
    Report Status: 2048
    Hashed bucket:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Error Reporting" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2019-08-22T12:09:14.000000000Z" />
        <EventRecordID>876204</EventRecordID>
        <Channel>Application</Channel>
        <Computer>xxxxxxxx</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>CLR20r3</Data>
        <Data>Not available</Data>
        <Data>0</Data>
        <Data>ServerManager.exe</Data>
        <Data>6.3.9600.17238</Data>
        <Data>53d0b3e7</Data>
        <Data>Microsoft.Windows.ServerManager.Common</Data>
        <Data>6.3.9600.17238</Data>
        <Data>53d0b3ba</Data>
        <Data>1373</Data>
        <Data>1c6</Data>
        <Data>System.ArgumentException</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ServerManager.ex_e1484b7fdd6fa16594f5f75d461e448c5927fa8_cba6274c_22c0aaad</Data>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>1f82320a-c4d5-11e9-811b-0017a477280e</Data>
        <Data>2048</Data>
        <Data>
        </Data>
      </EventData>
    </Event>














    • Edited by J. Juergen Friday, August 23, 2019 6:43 AM
    Thursday, August 22, 2019 11:44 AM

Answers

  • Today I started Servermanager on all of our 26 Hyper-V Nodes and you can´t belive it, everythings works fine!


    So I guess, If there are many Servers delivering lots of serivce states and event states in the "All Servers" Group in ServerManager, they produce this ugly .net error above. As I said, I didn´t change anything since Friday, August 23, 2019 1:26 PM, and today everthing (concerning ServerManager) looks good !??!

    regards
    Juergen


    Monday, August 26, 2019 6:48 AM

All replies

  • Hi ,

    Based on my research, event ID 1000 and event ID 1026 of .NET are usually caused by .NET version. 

    >>installed .net Framework 4.8 including all security patches on one of the Hyper-V nodes...

    However, based on your description, you already install the .net Framework 4.8 and the issue still occurs.

    Please understand, to solidly troubleshoot the crash issue, we generally need to debug the crash dump files. Unfortunately, debugging is beyond what we can do in the forum. We can only provide some general suggestions here. 

    If the issue still occurs, a support call to our product service team is needed for the debugging service. We'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers 

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Friday, August 23, 2019 3:50 AM
  • Thanks for your reply, I hope this has nothing to do with my incident…:

    https://www.veritas.com/support/en_US/article.100045500

    Regards

    Juergen



    • Edited by J. Juergen Friday, August 23, 2019 1:26 PM
    Friday, August 23, 2019 1:25 PM
  • Hi ,

    >>installed .net Framework 4.8 including all security patches on one of the Hyper-V nodes

    Did you mean that you install Veritas Backup Exec on this node? 

    From the above article , it seems that Veritas Backup Exec might crash after installing .net framework 4.8.

    In order to prevent Veritas Backup Exec from crashing , I would suggest you contact Veritas support to confirm if you should uninstall .net framework 4.8.

    For server manager crashing problem, I would suggest you open a case with Microsoft to debug the dump file.

    If you have further information during this period, you could post it on the forum.

    By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

    Best Regards,

    Candy



    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   


    Monday, August 26, 2019 2:46 AM
  • Today I started Servermanager on all of our 26 Hyper-V Nodes and you can´t belive it, everythings works fine!


    So I guess, If there are many Servers delivering lots of serivce states and event states in the "All Servers" Group in ServerManager, they produce this ugly .net error above. As I said, I didn´t change anything since Friday, August 23, 2019 1:26 PM, and today everthing (concerning ServerManager) looks good !??!

    regards
    Juergen


    Monday, August 26, 2019 6:48 AM
  • Hi ,

    I am glad to hear that the issue has been gone!

    It's really strange.....But you finally got a good result.

    Have a nice day!

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Monday, August 26, 2019 7:03 AM