Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, June 29, 2017 2:48 PM
Hi,
i recently updated my windows server 2012 r2 with the last june 2017 packages.
i face now issue when starting server manager.
here is what i see in the event viewer :
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[])*
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: 0xa98
Faulting application start time: 0x01d2f0e2cc42a24c
Faulting application path: C:\Windows\system32\ServerManager.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 0a41a3d0-5cd6-11e7-81b9-a4badb13a99f
*Faulting package full name: *
*Faulting package-relative application ID: *
i looked online multiple solution over the past years but nothing really worked. (machine.config, profile.config, GPO, profile corruption, etc.. )
i created a dump witht ProcDump v9. i can sshare it.
any help would be appreciated.
thanks,
Remi
All replies (11)
Friday, June 30, 2017 7:05 AM
Hi,
Possibly I have the same or similar problem. After the June -17 update, clients using Surface Pro 4, running RDP to Server 2012 R2, sees Server Manager crashing on the server just after logging in. We temporarily fixed this by disabling pen/touch support on the Surface Pro. Later we have concluded that this also happens using other pen/touch enabled clients as well. Also, if running RDP from a Surface Pro to a Server 2016 server, there is no problem.
Is this what you are experiencing?
/Urban
Friday, June 30, 2017 10:22 AM
Hi,
1 Please try to 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.
>>Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f33794
2 Log in as a different User. rename the problem profile. Log in as the original user again. A new profile will get created. If the crash is gone, copy your over your user data from the corrupted one.
3 Unstall the june 2017 packages.
If there is any other concern, please don’t hesitate to let me know.
Best Regards,
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, July 3, 2017 5:56 AM
Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
Best Regards,
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, July 3, 2017 8:16 AM | 2 votes
Hi,
Got this solved by the info here: https://www.stevefenton.co.uk/2017/06/failed-to-load-penimc-dll-and-related-problems/
/Urban
Tuesday, July 4, 2017 12:00 PM
Hi,
i'll perform your recommandations today.
will let you know.
thanks.
Tuesday, July 4, 2017 1:26 PM
@Frank_song
1- i was able to rename the key to old but when is it supposed to recreated the new one ? after a restart ?
2 - it is currently happening with any account im logging on the server, local or domain account. what do you mean by : "rename the problem profile" ?
3 - already uninstalled all the lastest updated i performed. the servermanager still crashing.
@thuben / Urban
i was able to find and remove the KB the acticle mentionned KB3186539, i restarded, installed it manually by downloading the manual installer of the KB : NDP47-KB3186497 (not the same id ?), restarted but still servermanager crashing.
Tuesday, July 4, 2017 2:13 PM
i was also able to notice 2 strange things.
1 - when i open mstsc to rdp into the server with my computer :
surface pro 2 , windows 8.1pro to the windows 2012 rr. When i log as local admin or with domain admin credentials, the server manager instantly crashes with the previous comments.
when i log into that server using rdp from a windows 7 pro sp1 to that server, as local admin or domain admin, server manager starts normally.
2 - when my session is running servermanager normally, i asked one of my collegue to shadow my session. Servermanagers crashes.
Friday, July 7, 2017 11:51 AM
Hi,
just to say that i re-install from scratch. none of the suggested solutions fix my issue.
Monday, July 10, 2017 8:16 AM
Hi，
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, August 1, 2017 2:18 PM
Hello,
Has anyone made any head way on this? I am running into the same issue with 17 new sql servers that were deployed into my environment.
Let me know.
Thanks
Joe
Thursday, August 10, 2017 4:50 PM | 1 vote
The solution you provided from the Steve Fenton blog resolved my issue.
I uninstalled KB3186539 and then reinstalled using the .NET Framework 4.7 offline installer. Problem solved.
Thanks!