Registration Expired or Failed Dialog shown when launching Microsoft Dynamics GP

David Meego - Click for blog homepageWe are currently seeing an increase in customer sites reporting the Registration Expired or Failed dialog when launching Microsoft Dynamics GP.

This dialog is to notify users that a Winthrop Development Consultants product is no longer registered and action needs to be taken by the system administrator to fix the subscription and restore the product’s functionality.

An example of the dialog for Visual Studio Integration Toolkit is shown below, but it can also be displayed by GP Power Tools and Batch Posting Service Toolkit.


<Product> registration expired or failed, last recorded as registered on <Date>.
Please contact your system administrator.

This dialog is displayed whenever a previously registered product loses its registration for any reason. The primary reasons why registration will fail are outlined below:

Discontinued Build

The most common reason for this dialog appearing is that the installed build has been discontinued and is no longer able to retrieve subscription keys.

From the end of December 2023, builds subject to the Security Vulnerability, discovered and fixed in August 2022, were discontinued. In addition, builds for non-supported Microsoft Dynamics GP versions were discontinued, with only the final build for those versions of GP being supported.

When the Security Vulnerability was discovered and fixed, all customers and partners were notified by email and requested to install the fixed build. Customer sites running old builds have had many update notification emails sent to them (and to their partners) since August 2022.

Note: The system will start checking for new keys 30 days before the subscription expiry. This means a discontinued build is likely to fail before the actual subscription expiry date is reached.

Invalid Contact Details

When the product is registered, a customer contact for the site must be provided. The email used for this primary contact must be a valid email address on the customer’s domain and go to a person or distribution list. If the subscription system identifies an invalid email, usually due to a bounced email from an update notification, it will automatically suspend the subscription until the email is updated.

If the customer site has a partner associated with it, the partner is contacted to request the contact details be updated.

Note: You will need to contact us to manually remove the suspension and allow the subscription to be registered again.

Expired Subscription

An expiring subscription will display pending expiry warnings to administrator users for 30 days before expiry and, once expired, will display grace period warnings to all users for 30 days before actually ceasing to function. It is unlikely you will see this dialog without a prior warning.

Subscription keys should be renewed automatically via the internet assuming the subscription has been renewed. The following article covers reasons why that might not happen:

Note: The system will attempt to retrieve new keys via the internet BEFORE displaying any dialogs.  If internet connected and the subscription has been renewed by the due date (30 days before expiry), the system will renew automatically and never show any expiry warnings.

Restoring the Subscription

Visual Studio Integration Toolkit contains two free modules which require registration but are provided at no charge as our gift to the Dynamics GP Community. All we ask in return is for the Customer Contact Details and installed build is kept current and valid. If the system has internet access it will renew the free modules automatically each year.

The following steps will ensure that the subscription is renewed and functionality restored:

Install the latest Build

Download and install the latest build for your version of Microsoft Dynamics GP onto all workstations and servers where GP itself is installed.

Winthrop Development Consultants is fully committed to the Dynamics GP product and is actively developing new features and fixes. It is in your best interest to always stay on our latest builds.

Check Customer Contact Details

After updating, from the Registration window, click the Contact Details button and check the information. Make sure that the primary contact name, email and phone are correct. Add additional emails to the email distribution list to ensure that if the primary contact is not available, someone else in the organization will receive emails. It is often a good idea to include a distribution list email to the IT Support or Accounting teams.

If there is the message “(Invalid Email)” or “(Update Required)” please contact us to fix any issues on the Registration Server.

Renew the Subscription

For paid modules, it is recommended to renew the subscription before the expiry warnings would be displayed. This is why your Renewal Invoice sent to partners and direct customers has a Due Date one month before the Expiry Date. If the subscription is renewed by the Due Date and the system is internet connected, you will not see any warnings.

If the subscription Renewal Invoice is paid and processed before the Expiry Date, the subscription will be renewed without end users seeing any dialogs.

Once expired, users will see a grace period warning, but the system will remain functional for 30 days as long as the registration keys are left in the system.

If the keys don’t renew automatically, it could be because the option has been disabled, or the system does not have at least one internet connected workstation. Try clicking Update Keys from the Registration window and if there are still issues, see the article below to troubleshoot.

For systems that are not internet connected, clicking the Update Keys button from the Registration window generates an Offline Registration Request report. Please cut and paste this report as text and contact us to get manual keys and instructions emailed back.

Hiding the Dialog (Not Recommended)

The default setting for this dialog is to display a warning and allow the application to run after it has been dismissed. It can be disabled, but that just hides the failed registration and does not fix the underlying problem. It can also be set to force the application to close after being dismissed (with an Administrator being able to override the exit). The setting is controlled from the product’s Registration window.

The following articles explain where to find the Registration window and why this dialog exists:

More Information

The following articles provide all the details:

The following articles will help with installation (including command line “Silent” or scripted installs) and setting up properly:

Please see the product portal pages for more information:

Stay informed by Subscribing to the Blog (see top right) and Subscribing to our Newsletters.

Hope this explains everything.

David

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

Please post feedback or comments

This site uses Akismet to reduce spam. Learn how your comment data is processed.