Thursday, August 31, 2017

Server manager keeps crashing.



πŸ˜‘ 

To the event viewer. 


Faulting application name: ServerManager.exe, version: 6.3.9600.17238, time stamp: 0x53d0b3e7
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f33794
Exception code: 0xe0434352
Fault offset: 0x00000000000095fc
Faulting process id: 0x2b08
Faulting application start time: 0x01d32268e6cec67e
Faulting application path: C:\Windows\system32\ServerManager.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 24fc1112-8e5c-11e7-80ed-000c29f2e9e5
Faulting package full name:
Faulting package-relative application ID:


Application: ServerManager.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException
at MS.Win32.Penimc.UnsafeNativeMethods.CreateResetEvent(IntPtr ByRef)
at System.Windows.Input.PenThreadWorker..ctor()
at System.Windows.Input.PenThreadPool.GetPenThreadForPenContextHelper(System.Windows.Input.PenContext)
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTabletsImpl()
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTablets()
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection..ctor()
at System.Windows.Input.StylusWisp.WispLogic.get_WispTabletDevices() at System.Windows.Input.StylusWisp.WispLogic.RegisterHwndForInput(System.Windows.Input.InputManager, System.Windows.PresentationSource)
at System.Windows.Interop.HwndStylusInputProvider..ctor(System.Windows.Interop.HwndSource) at
System.Windows.Interop.HwndSource.Initialize(System.Windows.Interop.HwndSourceParameters)
at System.Windows.Window.CreateSourceWindow(Boolean)
at System.Windows.Interop.WindowInteropHelper.EnsureHandle() at Microsoft.Windows.ServerManager.Common.ArgumentsProcessor.InitListener(System.Windows.Application, IntPtr)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window) at Microsoft.Windows.ServerManager.SingleInstanceAppLauncher.StartApplication(Microsoft.Windows.ServerManager.Common.ArgumentsProcessor)
at Microsoft.Windows.ServerManager.MainApplication.Main(System.String[])

Wonderful.

.NET Runtime? What's that again? Maybe not relevant but whatever.

A few searches have said that it has to do with an Intel display driver of some sort and that seems to fix it for others but in my case it's a virtual machine. Moving on.

This guy says to rename a registry entry. I hate messing with the registry but this one looks fairly safe. I'll give it a shot.

The first point of solution is to clear the Server Manager. Please follow below steps to clear the Server Manager Cache through registry editor

Rename the registry key HKLM\SOFTWARE\Microsoft\ServerManager\ServicingStorage\ServerComponentCache to ServerComponentCache.old



 

I hope this works....


πŸ‘ΏπŸ‘ΏπŸ‘Ώ

Well it certainly didn't hurt anything but it didn't work.

Okay now what?

So I noticed this:

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Maybe I can copy that file over from one of my other servers but first let's see if Server Manager works on either of the other two.

 

Microsoft what did you do??

This thread might be the ticket. One user mentioned it started happening after the June 2017 rollup. Also here's another thread I looked at that might help.

In that thread Ian Valerio says this:

I manually uninstalled KB3186539 and downloaded the offline .NET 4.7 Installer. After installing the update my issue was resolved. Thank you! Also my PowerShell ISE is opening with no issues. Again Thank you all!

Let's try it. .NET 4.7 Installer



Dammit. Looks like I'll be waiting a bit.



Time to restart. Let's see if that was the issue.

Ta Da!



Now to see if installing that update manually will break it again.


That was it. Thanks again Ian Valerio.


Server manager keeps crashing.



πŸ˜‘ 

To the event viewer. 


Faulting application name: ServerManager.exe, version: 6.3.9600.17238, time stamp: 0x53d0b3e7
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f33794
Exception code: 0xe0434352
Fault offset: 0x00000000000095fc
Faulting process id: 0x2b08
Faulting application start time: 0x01d32268e6cec67e
Faulting application path: C:\Windows\system32\ServerManager.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 24fc1112-8e5c-11e7-80ed-000c29f2e9e5
Faulting package full name:
Faulting package-relative application ID:


Application: ServerManager.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException
at MS.Win32.Penimc.UnsafeNativeMethods.CreateResetEvent(IntPtr ByRef)
at System.Windows.Input.PenThreadWorker..ctor()
at System.Windows.Input.PenThreadPool.GetPenThreadForPenContextHelper(System.Windows.Input.PenContext)
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTabletsImpl()
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection.UpdateTablets()
at System.Windows.Input.StylusWisp.WispTabletDeviceCollection..ctor()
at System.Windows.Input.StylusWisp.WispLogic.get_WispTabletDevices() at System.Windows.Input.StylusWisp.WispLogic.RegisterHwndForInput(System.Windows.Input.InputManager, System.Windows.PresentationSource)
at System.Windows.Interop.HwndStylusInputProvider..ctor(System.Windows.Interop.HwndSource) at
System.Windows.Interop.HwndSource.Initialize(System.Windows.Interop.HwndSourceParameters)
at System.Windows.Window.CreateSourceWindow(Boolean)
at System.Windows.Interop.WindowInteropHelper.EnsureHandle() at Microsoft.Windows.ServerManager.Common.ArgumentsProcessor.InitListener(System.Windows.Application, IntPtr)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window) at Microsoft.Windows.ServerManager.SingleInstanceAppLauncher.StartApplication(Microsoft.Windows.ServerManager.Common.ArgumentsProcessor)
at Microsoft.Windows.ServerManager.MainApplication.Main(System.String[])

Wonderful.

.NET Runtime? What's that again? Maybe not relevant but whatever.

A few searches have said that it has to do with an Intel display driver of some sort and that seems to fix it for others but in my case it's a virtual machine. Moving on.

This guy says to rename a registry entry. I hate messing with the registry but this one looks fairly safe. I'll give it a shot.

The first point of solution is to clear the Server Manager. Please follow below steps to clear the Server Manager Cache through registry editor

Rename the registry key HKLM\SOFTWARE\Microsoft\ServerManager\ServicingStorage\ServerComponentCache to ServerComponentCache.old



 

I hope this works....


πŸ‘ΏπŸ‘ΏπŸ‘Ώ

Well it certainly didn't hurt anything but it didn't work.

Okay now what?

So I noticed this:

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Maybe I can copy that file over from one of my other servers but first let's see if Server Manager works on either of the other two.

 

Microsoft what did you do??

This thread might be the ticket. One user mentioned it started happening after the June 2017 rollup. Also here's another thread I looked at that might help.

In that thread Ian Valerio says this:

I manually uninstalled KB3186539 and downloaded the offline .NET 4.7 Installer. After installing the update my issue was resolved. Thank you! Also my PowerShell ISE is opening with no issues. Again Thank you all!

Let's try it. .NET 4.7 Installer



Dammit. Looks like I'll be waiting a bit.



Time to restart. Let's see if that was the issue.

Ta Da!



Now to see if installing that update manually will break it again.


That was it. Thanks again Ian Valerio.


Unable to read RD Gateway Server settings.


I was just met with this message when trying to connect to the RD Gateway Server (locally). Restarting the server will not fix it.

In my case this is a remote desktop terminal server hosting a remote app for my users. It doesn't seem to be having any affect on their usability.

What's interesting is that the same time that this started happening, I also started to not be able to open my Server Manager without it crashing. I have no idea if these are related yet.

Getting a lot of these errors in my event viewer. Not sure if related.



I just read on another site to re-add the Default Web Site to IIS. Now I already have one called Default Site but who knows, it's worth a shot.

Here's how it said to do it:
  • Open IIS Manager.
  • Right-click Sites node under your machine in the Connections tree on the left side and click Add Website
  • Enter "Default Web Site" as a Site name
  • Set Application pool back to DefaultAppPool
  • Set Physical path to %SystemDrive%\inetpub\wwwroot
  • Leave Binding and everything else as is




Okay? I'll just click Yes and see what happens.



Alright, it's there. Let's see if it did anything....

Yup that did it.

Now to find out why Server Manager won't open.










Unable to read RD Gateway Server settings.


I was just met with this message when trying to connect to the RD Gateway Server (locally). Restarting the server will not fix it.

In my case this is a remote desktop terminal server hosting a remote app for my users. It doesn't seem to be having any affect on their usability.

What's interesting is that the same time that this started happening, I also started to not be able to open my Server Manager without it crashing. I have no idea if these are related yet.

Getting a lot of these errors in my event viewer. Not sure if related.



I just read on another site to re-add the Default Web Site to IIS. Now I already have one called Default Site but who knows, it's worth a shot.

Here's how it said to do it:
  • Open IIS Manager.
  • Right-click Sites node under your machine in the Connections tree on the left side and click Add Website
  • Enter "Default Web Site" as a Site name
  • Set Application pool back to DefaultAppPool
  • Set Physical path to %SystemDrive%\inetpub\wwwroot
  • Leave Binding and everything else as is




Okay? I'll just click Yes and see what happens.



Alright, it's there. Let's see if it did anything....

Yup that did it.

Now to find out why Server Manager won't open.










Featured Post

How to enable WinRM via Group Policy

In order to remotely manage computers via Powershell, you must enable Windows Remote Management. Open Group Policy management. Creat...

Popular Tutorials