Does upgrade from GP 2015 to year-end update with R2 need new registration keys?

(0) Share

Report

Posted on by jbeck2014

365

I installed the year-end update for GP 2015 which included the upgrade to GP 2015 R2. We were previously on GP 2015 RTM. After upgrading the databases with GP Utilities on the server, I launched GP Dynamics and clicked "Yes" to install the new code. I upgraded our terminal server client and also clicked "Yes" to install the new code. However, when anyone logs into GP Dynamics, it still pops up with the message: "New code must be included in the :C:Program Files (x86)/Microsoft Dynamics/GP2015/Dynamics.set dictionary. Do you wish to include new code now? If the user selects Yes, the message pops up "Unable to include new code". If the users select No, they are able to get into Great Plains Dynamics successfully and work.

*This post is locked for comments

All responses (6)

Answers (1)

Verified answer

jbeck2014 365 on at

Like (0)

Report

RE: Does upgrade from GP 2015 to year-end update with R2 need new registration keys?

I was able to solve the problem by uninstalling the application on the server and the terminal server and reinstalling it. I ran with elevated permissions and logged into GP Utilities as sa.
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

RE: Does upgrade from GP 2015 to year-end update with R2 need new registration keys?

You mention you're running off a TS.... When you upgrade the GP client and add new code (or update existing dictionaries), you need to run the first time the GP client with elevated permissions (read Run As Admin...) in order to properly integrate the new code.

Once the new code is included, the users still need to have read/write access to the program folder in order to be able to run correctly the GP client, but there should be no need to run with elevated rights.

One thing you need to keep in mind on a shared environment like a TS/RDP server, is the fact that the DEX.INI file will be shared among all the users, unless you adopt a different approach to keep a separate DEX.ini for each user (what I do in our environment).. There are various blog posts that talk about shared user environment with GP client on TS... starting with GP2013, there even has been a new feature about shared user DEX.ini... but be careful and read about the pros & cons.

http://dynamicsgpblogster.blogspot.ca/2014/05/working-with-dexini-settings-in.html

https://dyngpbeat.wordpress.com/tag/dex-ini/
jbeck2014 365 on at

Like (0)

Report

RE: Does upgrade from GP 2015 to year-end update with R2 need new registration keys?

I installed GP into the same folder as previously. I looked at the security for that folder and the users have permission.

I looked at the Dex.ini file and it says Synchronize=FALSE. Should I change it to TRUE?
Suggested answer

Bill Campbell 12 on at

Like (0)

Report

RE: Does upgrade from GP 2015 to year-end update with R2 need new registration keys?

Did you happen to install the GP into a new folder or location? if so, have a look at the security for that folder and ensure that your users have permissions.

Alternatively you can change the setting in the Dex.ini to tell the system that the files are already in sync - setting the SYNC line to FALSE ( I believe ) will allow the application to launch without trying to run the Utilities.

Sorry, really late at night and I doing this on the fly off the top of my head. I will look at this in the morning and adjust the comments as needed.
jbeck2014 365 on at

Like (0)

Report

RE: Does upgrade from GP 2015 to year-end update with R2 need new registration keys?

I have full admin rights on the server and the terminal server. I did the two command prompt commands you suggested on the terminal server and I'm still getting the message asking to add new code on both the server and the terminal server.
Richard Wheeler 75,848 Moderator on at

Like (1)

Report

RE: Does upgrade from GP 2015 to year-end update with R2 need new registration keys?

Make sure you are logged into the server with an account that has full admin rights. The account needs to be able to read/write to the GP program folder. On your T/S do this after hours and make sure no sessions are running GP. Also, prior to applying the update go out the command prompt and type change user/install and then change user/execute after you have launched GP and all new code has been included.