Install/Upgrade Error: Input string was not in a correct format


I had to apply GP 2016 YE2016 (16.00.0579) on my GP2016 R2 environment. I had several customisations deployed and wanted to remove them before applying the YE2016 patch.

Obviously, I’d upgrade my customisations to 16.00.0579 once my GP is upgraded. However, while trying to apply YE2016, following error message popped up out of nowhere.

Screen Shot 2017-04-27 at 03.32.02 pm

I had never seen this error before. It was certainly a bit baffling. Not even Google is good compared to our GP community forum to find answers. I came up with this: Installation error ‘Input string was not in a correct format’

Apparently, it was my DYNAMICS.SET that was causing this issue. I removed my customisation dictionaries from GP folder, removed all necessary entries from my SET file. However, I totally forgot to reduce the number of dictionaries at the top of my SET file. Silly me!

Once I corrected my SET file, I was able to apply the YE2016 patch. All was well.

One thing I would like to emphasise here: Those who post questions on our GP forum, please mark the response as “answer” without fail. You would help others who search for an answer. You’d also give due credit to the person who shared his/her knowledge.

Vaidy

Advertisements

GP 2016 – Upgrading Web Client


Dynamics GP Support & Services team has posted a detailed article on GP 2016 Web Client Upgrade.

One of the important things that I noticed on this post is the instruction on Service Based Architecture (SBA) inclusion/exclusion. Though it’s not covered separately on this post, we are however cautioned on how to handle the options with regards to SBA.

Happy upgrading…

VAIDY

GP2016 – Feature of the Day – Power BI Integration & Budget Import Enhancement


Another set of feature of the day posts reveal that Power BI is coming to GP.  Also we have got Budget Import enhancement. Links to the posts are below:

  • Duplicate Accounts Import Exception Report
  • Power BI Reports on Home Page – I would rather like to see Dynamics GP being added to the Power BI Connector Services. Don’t get me wrong. I love this feature, it’s great to have Power BI report widgets on GP home page. However, the ideal integration would be to see Dynamics GP Connector Service. I think that would possibly happen soon, considering the next feature.
  • Dynamics GP OData Service – This is going to be another important feature (HTML5 Web Client being the first one) that I have been waiting for. This will enable us to have an excellent Power BI integration. I am happy to see Power BI reports on GP Home Page, no doubt, but I am super excited about OData Service.

VAIDY

Time to say Good Bye to FRx…


If anyone out there still using FRx as their financial reporting tool, it’s time to migrate to Management Reporter.

Dynamics GP Support team has posted an article, Microsoft Dynamics GP 2016 is upgraded – What’s next?, on which they have announced that FRx is no longer supported with Microsoft Dynamics GP 2016.

Time to say good bye to FRx…

VAIDY

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