#GPPT: Resolved: Registration fails followed by Microsoft Dynamics GP has stopped working

With the release of the GP Power Tools build 28.6 hotfix, a couple of sites have reported that GP Power Tools says it is not registered and then causes Microsoft Dynamics GP to crash if you attempt to open the registration window.

The cause of the issue has been identified and a simple solution is available. We are working with the 3^rd party developers involved to prevent the situation occurring in future.

The Problem

The screenshot below shows the “GP Power Tools is not registered. Do you want to open the About GP Power Tools window to check registration?” dialog overlaid with the “Microsoft Dynamics GP has stopped working” dialog.

The Explanation

If you are not interested in the technical description of the cause, please skip to the next section.

Winthrop Development Consultants Products use Quick License Manager from Soraco to handle the product registration and subscriptions via calls to QLMLicenseLib.dll. In a recent update to this DLL (included with GPPT build 28.6) logging functionality was added using the common Log4Net library. The updated QLMLicenseLib.dll embeds the library in its code, but for some reason if an external Log4Net.dll is found, it is used instead. If the Log4Net.dll file found is old, it may attempt to use an out of date .Net Framework version that might not be available on the system and so generate an error.

For example: The event log for one of the crash dumps included the information: Event Name: CLR20r3, Response: Not available. This indicates that the old DLL was looking for .Net Framework 2.0 which was not installed.

If you check the properties of the DLL, the version number of the DLL that uses Log4Net included with Build 28.6 was 14.1.21047.2.

The Solution

We have found that old copies of Log4Net.dll were installed by legacy applications and left behind even when the applications were uninstalled.

Scan the Microsoft Dynamics GP application folder and subfolders as well as the Windows folder and subfolders for the file Log4Net.dll and rename it as Log4Net.dll.bak to disable it.

Hope this helps.

David

This article was originally posted on http://www.winthropdc.com/blog.