Skip to main content

Notifications

Announcements

Dynamics 365 Community / Blogs / Dynamics GP Support and Services Blog / Seeing Microsoft Dynamics G...

Seeing Microsoft Dynamics GP recently start crashing?

Lucas Miller Profile Picture Lucas Miller

UPDATE:

It appears that the Windows team has released a new patch, KB4550929, that addresses printing issues in certain applications.  If this hasn't been pushed out in your application and you're seeing the issue we'd recommend you install it to take care of the issue for you.

Hello GP Community!

We’ve recently received reports of users working in Microsoft Dynamics GP and experiencing sudden application crashes, affecting both the desktop and web client.  Sometimes the users are performing an operation involving printing, but that doesn't seem to always be the case.

When you look in Event Viewer you may see an error with details like the following:

Faulting application name: Dynamics.exe, version: 12.0.311.0, time stamp: 0x5363afe4

Faulting module name: WINSPOOL.DRV, version: 10.0.14393.3595, time stamp: 0x5e6afb45

Exception code: 0xc0000005

Fault offset: 0x0000d8db

Faulting process id: 0x2f40

Faulting application start time: 0x01d60450394df553

Faulting application path: C:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.exe

Faulting module path: C:\Windows\SYSTEM32\WINSPOOL.DRV

Report Id: fa1fa42e-e844-4520-9020-198719e9d07d

Faulting package full name:

Faulting package-relative application ID:

 

Another indication that there is an issue in some of these cases is that you are unable to get to Control Panel > Devices and Printers because it also closes.  

It appears that this behavior is due to a recent Windows patch, KB4541329.  If you uninstall that patch then the reported experience that we've seen with affected customers is that you'll able to both use GP and access Devices and Printers without any crashing.

We’re keeping eye on this to see if a new Windows patch is released and we will update this article as necessary.

Thanks!

Comments

*This post is locked for comments

  • Steven Vallarian Profile Picture Steven Vallarian 394
    Posted at
    This is caused by stale printers in the user's registry key. I stole this script from reddit, but if you run it in the user's session, you can get around not having to uninstall that gigantic patch. -------------------------------------------------------------------------------------------------------------------------------------- $RootKey='HKCU:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' $CurrentPrinters=Get-Printer foreach ($SubKey in @('Devices','PrinterPorts')) { (Get-Item "$RootKey\$SubKey").GetValueNames() | ` Where-Object {$CurrentPrinters.Name -notcontains $_} | ` Foreach-Object {Remove-ItemProperty -Path "$RootKey\$SubKey" -Name $_} }
  • Lucas Miller Profile Picture Lucas Miller
    Posted at
    Thanks for your question Victoria, I haven't seen that this is isolated to any one version of Dynamics GP. We are still gathering information as we take more cases on the issue though. Please feel free to let us know if you are seeing any trends with your own environments/customers as well.
  • Victoria Yudin Profile Picture Victoria Yudin 22,766
    Posted at
    Hi Lucas, Is this limited to older versions of Dynamics GP - or do you see this reported for all GP versions? Asking because you have GP 2013 in your example. Thanks, Victoria Yudin