Some GP Power Tools (GPPT) sites which also have Mekorma MICR have reported an issue where GP Power Tools reports that it is not registered during login, but when you open the About GP Power Tools window it says it is registered.
This article explains the cause of the issue and the resolution.
The dialog displayed after logging into a company says “GP Power Tools is not registered. Do you want to open the About GP Power Tools window?“.
This dialog will be displayed only for the first time a user logs in each day and then will be hidden until the next day.
Even if the dialog has been hidden, you will be able to see the issue occurring if you look in the GPPTools_<User>_<Company>.log file where it will record an entry similar to the one below:
26/02/2016 18:18:06 : GP Power Tools is Not Registered
When you open About GP Power Tools window, it will show as registered (highlighted below).
The effect of this issue (other than the dialog itself) is that any GP Power Tools features that should start after login, don’t. Features such as changing the window Title bar, Company Color schemes, automatic starting triggers, etc. fail to initialize.
The cause of this issue is a timing problem, where GP Power Tools is checking if it is registered before the Mekorma Product Manager has initialized the registration system.
The original approach to fixing the timing issue was to change the Mekorma Product Manager to perform its initialization earlier, AND to ensure it ran before GP Power Tools checked the registration by moving Mekorma Product Manager above GP Power Tools in the Dynamics.set launch file. This worked as long as you had the appropriate build of the Mekorma Product Manager installed.
However, Mekorma MICR sometimes installed a different Mekorma Product Manager (MPM) build which did not include the change made for GPPT. You could get into a loop where the MPM packaged with MICR did not work for GPPT and the MPM packaged with GPPT did not work for MICR. Mekorma Support could provide an updated MICR installer which came with a MPM build that was compatible with both products. But this is no longer required….
While researching a related issue where registration was failing for Batch Posting Service Toolkit (BPST) when called as a Web Service via Service Based Architecture (SBA), it was identified that the Mekorma Product Manager was not initialized as SBA does not log into Dynamics GP with the same scripts as the full client. After a bit of testing, I was able to identify a small change which allows the registration check to work.
This change also fixed the registration issue for GP Power Tools without needing an updated version of the Mekorma Product Manager or needing to change the order of the products in the Dynamics.set launch file.
If you are facing this issue, please make sure you download the latest GP Power Tools build from the Mekorma GP Power Tools page. It will have a Last Modified Date: 26-Feb-2016 (as highlighted on the screenshot above) or later.
This article was originally posted on http://www.winthropdc.com/blog.