Server Manager Keeps on crashing

Whenever trying to Add\Remove Roles or feature using Server Manager, it Keeps on crashing.
When you check Application Logs, you can see there are some application error with Event ID 1000 and 1026.

Event ID: 1000
Faulting application name: ServerManager.exe, version: 6.2.9200.16384, time stamp: 0x50107b22
Faulting module name: wmidcom.dll, version: 6.2.9200.16384, time stamp: 0x501087fc
Exception code: 0xc0000005
Fault offset: 0x000000000001c665
Faulting process id: 0x13b4
Faulting application start time: 0x01d25ad8eb13bcd7
Faulting application path: C:\Windows\system32\ServerManager.exe
Faulting module path: C:\Windows\system32\wmidcom.dll
Report Id: 2b9e7ef9-c6cc-11e6-9411-0050569f44ee
Faulting package full name:
Faulting package-relative application ID:

Event ID: 1026
Application: ServerManager.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
   at MS.Internal.Threading.ExceptionFilterHelper.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 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 MS.Internal.Threading.ExceptionFilterHelper.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 MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   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[])

Solution:

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
HKLM\SOFTWARE\Microsoft\ServerManager\ServicingStorage\ServerComponentCache.old


The above key will be re-created once you open the server Manager.

Hope this help.

Windows Update Error 80070070

Windows Update Error 80070070


hi Guys!!!

If you face Windows Update Error 80070070 then your C drive or windows drive is running out of space and it cannot download the updates or space required to install the update is not there.

Solution:
simply increase your drive space or if possible to perform some cleanup so that you can have some free space

Hope this helps

Thanks

Bany Singh

How to Fix SFC /SCANNOW There is a System Repair Pending

While running the SFC/ Scannow, if receive below error:

Server Manager "console cannot refresh until computer is restarted"


Then you can follow below steps to resolve it.

There is a file called Pending.XML  located at C:\Windows\winSXS
It contains all the pending transactions which a system will commit at after restart. But due to some reason these transactions are not getting committed.

To resolve the above problem, you can either delete the Pending.xml file or rename it

or

Restart your computer so that pending transactions can be committed. If in case after reboot your are facing the same issue then there is a chance that the file which execute the pending.xml is missing.

Check the below path and see if POQEXEC.EXE is present or not.

C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6

If missing, copy the file from another working server and paste it at above path. Reboot your computer and pending.xml will be gone.

It will fix the problem and you will be able to run the SFC again.

Hope this help :)

Windows Update Error Code 8007007E

You will receive this error as some of your files in WINSXS folder is missing or corrupt. To fix it read below:
In Server 2008 family, download the Checksur and run it.This process can take hours to complete because it check the Windows component store (C:\Windows\Winsxs).
It will create a Checksur.log file at C:\Windows\Logs\CBS\checksur.log At the end of this file you will see corruption or missing file and below it you will see how many of these corruption was fixed by Checksur.
Checksur may not be able to fix or repair all the corruption, for those missing files or corruption you need to manually check the path of file and replace it from the Working system running same windows as your one. Reboot your computer and run the windows update again. Your error will be fixed.

Download CheckSUR for Windows 2008. Click Below
https://support.microsoft.com/en-in/kb/947821
 

PSOD Solution - LINIT1 motherboard interrupt

If you are getting the attached PSOD on ESXi. Try below steps to resolve the issue.

A few customers have been affected by a firmware bug that can cause instability when using Intel’s C-State power-saving functionality. If you are still experiencing instability after verifying that your server is at the most recent recommended BIOS and firmware levels, you may disable C-States using two methods:

BIOS:
 •Reboot the server
 •Press F2 to enter the BIOS configuration menu
 •Select Processor Settings
 •Scroll down to “C States” and “C1E”
 •Use the arrow keys to set both to Disabled
 •Press ESC repeatedly and select “Save changes and exit”

If above steps won't solve your issue then you need to go to the Power Management and set it to minimum.
This will reduce the power usage of the server and your ESXi will be up and running once again.

NOTE: Above steps is the workaround to the attached PSOD. You may need to contact DELL support for a permanent fix.

Thanks for reading. Hope this will be helpful to you.