GP2016 Upgrade – Missing Security Roles & Tasks


When upgrading to GP2016 RTM, it looks like upgrade process would skip creating new security roles and tasks, to ensure that the old ones are not messed up.

According to Dynamics GP Support & Services blog, this is intentional and we have been provided with an INSERT script that would create the new GP2016 roles and tasks. It’s more like on-demand insert.

A fresh GP2016 installation would hence be different from an upgrade.

VAIDY

GP2016 Upgrade – Modified Dictionary Upgrade & Upgrade Troubleshooting


Over at Dynamics GP Support & Services blog, couple of posts discussing about following are available:

Both posts discuss in detail about how to upgrade modified dictionary and how to troubleshoot upgrade issues. In particular, the upgrade troubleshooting post is crucial for obvious reasons.

Just about 10 days to get my hands on Microsoft Dynamics GP 2016. It’s gonna be fun.

VAIDY

IMPORTANT – GP 2016 Database Upgrade Details


Dynamics GP Support & Services blog has got the information on GP 2016 database upgrade.

Most important information among all that’s been posted, is the fact that we cannot perform a direct upgrade to GP 2016 from any version that’s lower than 12.00.1826. Not even those who are currently on GP 2013 R2 (12.00.1745). It has to be a two-step upgrade for all of them.

VAIDY

GP2016 – Known Upgrade Issues


Latest post from Dynamics GP Support & Services Blog has listed down all known GP2016 upgrade issues.

Some interesting ones, in my opinion, are:

  1. Account Framework Table Conversion – Tables getting converted are listed. This one’s crucial.
  2. Database Compatibility – Make sure to change the compatibility level of all DBs (system & company DBs) to the version of upgraded SQL Server (SQL Server 2012 or SQL Server 2014). To my surprise, they have not mentioned about SQL Server 2016 yet. I know, SQL Server 2016 has not been released yet, however, I would have expected some kind of note somewhere that says GP2016 would support SQL Server 2016 once it is released.
  3. Workflow Documents Must Be Final Approved – Please make sure that all workflow documents are final approved before running the upgrade. Would fail otherwise.
  4. Overlapping Fiscal Periods – Make sure that you don’t have any overlapping fiscal periods by any chance.

One thing that I noticed (and got happy about) is that there’s no known issue mentioned about GP Web Client. I don’t know if we would have a separate post discussing the known issues. So far, I haven’t seen one, so I am happy that things would go well with HTML5 web client.

Let’s plan the upgrades well, people.

VAIDY

GP2015 R2 Upgrade – GP Utilities “SynchronizeTableData()” Error & Fix


This issue has already been reported and it’s also been addressed. I would like to post this still. To act more like a pointer. It’s quite crucial in nature.

I have been testing GP2015 R2 upgrade on my test environment when I faced the following error message:

Screen Shot 2015-07-27 at 6.10.32 PM

Quite evidently, upgrade didn’t go through after. I remembered this being posted on our GP Support & Services blog. Dug the post and got the solution.

Here’s the post: Known Upgrade Issues When Upgrading To Microsoft Dynamics GP 2015 R2

Please note that this has been fixed already and is available with June 2015 Update.

Vaidy

GP 2015 R2 Upgrade Issues & Possible Solutions


There is a GP community forum question that discuss about GP 2015 R2 upgrade errors. As always, contributors have poured in their thoughts and possible solutions to fix these issues.

Read the question here: GP 2015 R2 errors during update & Fixes

I recommend this post to everyone who are planning to upgrade to GP2015 R2 soon. This may save a lot of time.

Thank you GP community for being selfless, informative and helpful.

Vaidy

GP 2015 DYNAMICS DB Upgrade – Issue & Resolution


This issue is probably remote and may not be faced by many of you out there. But I thought I would share this information with you all, just in case.

Issue: I was upgrading my GP 2013 to GP 2015. By the time, GP Utilities (almost) finished, it got stuck with an error while updating the table SY_Company_MSTR (Company Master) as shown below. I have tried to capture the entire error details on one screen:

Screen Shot 2015-01-03 at 8.34.42 PM

Error Explanation on Table Error Details had more information that I could not capture above. Below is that additional information. I’d rather say, that’s the exact error message:

Screen Shot 2015-01-03 at 8.35.16 PM

While that greyed portion denotes a company DB name.

Reason: I copied one company database (out of 8) backup from my production environment, restored it on my test machine and ran the utilities to upgrade to GP 2015. When Utilities tried to update Company Master table (SY01500, SY_Company_MSTR), it found records pertaining to companies other than one that’s existing on my test machine while it could not find the respective databases physically.

Resolution: If you are going to have less companies on your upgrade scheme than what’s there on your original GP environment, then you must run Clear Companies script. This script will clear all records pertaining to companies that are not physically available on your SQL instance.

Once I cleaned up the company records, my upgrade process went on successfully.

VAIDY