Upgrade Error 2016 to 2018

(0) Share

Report

Posted on by Sunil Chhabra

1,958

I am getting an error when running Utilities. I am upgrading to 18.2

Current Version 16.00.0814 (R2)

Installed SP 18.2.1036

Below is the upgrade path per KB

I get the following error

Failure encountered ON 10/31/2021 at 9:37:26 PM. Error: Product 0 does not support upgrading from version 16.0.864.
Failure encountered ON 10/31/2021 at 9:37:26 PM. Error: Product 309 does not support upgrading from version 16.0.860.
Failure encountered ON 10/31/2021 at 9:37:26 PM. Error: Product 414 does not support upgrading from version 16.0.861.
Failure encountered ON 10/31/2021 at 9:37:26 PM. Error: Product 1493 does not support upgrading from version 16.0.859.
Failure encountered ON 10/31/2021 at 9:37:26 PM. Error: Product 1632 does not support upgrading from version 16.0.838.
Failure encountered ON 10/31/2021 at 9:37:26 PM. Error: Product 1911 does not support upgrading from version 16.0.13.

I had successfully upgraded this last Oct. in a test version. But due to Covid the project was put on hold. I did encounter these errors but I cannot find my documentation as to how I resolved it.

We are not ready to upgrade so restore the databases, and upon launching utilities - getting this error.

Please advise.

Thanks

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (10)

Answers (3)

Sort by

Richard Wheeler 75,852 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Try applying 16.00.0874 or 16.00.0885 first before going to 18.2.1036. By the way, the 2021 year-end update for 18.4 is scheduled to be released on 11/29/2021 so you may want to wait.

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

As it appears that you're actually on 16.00.0864 for Dynamics GP 2016 per the error (Product 0 does not support upgrading from version 16.0.864), you must be upgrading to 18.3.1200 or later, as mentioned in the 'Upgrading to Microsoft Dynamics GP' hot topic here:

docs.microsoft.com/.../hot_topic_mdgpupgrade_415

Thanks

Was this reply helpful? Yes No
Sunil Chhabra 1,958 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello Derek

I was able to upgrade to version 18.3 by installing the

Service KB4569498-ENU.msp

After successfully upgrading - I noticed there is another later version 18.4 so I installed KB4576796-ENU but I get an error when running Utilities.

Failure encountered ON 11/1/2021 at 10:29:02 PM. Error: Product 4522 does not support upgrading from version 18.3.33.
Failure encountered ON 11/1/2021 at 10:29:02 PM. Error: Product 4522 does not support upgrading from version 18.3.33.

Thanks for your assistance.

Was this reply helpful? Yes No
Verified answer

Derek Albaugh Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

That's actually a 'bug' with the upgrade when you have the HR/Payroll Suite installed with Dynamics GP.

This is scheduled to be fixed in the upcoming year-end release, so you'll want to wait until that release before going to 18.4, if you use the HR/Payroll Suite and have it installed.

I'd also mention this blog that was released yesterday regarding the HR/Payroll Suite:

community.dynamics.com/.../microsoft-dynamics-gp-human-resource-and-payroll-suite-announcement

Let me know if you have any questions. Thanks

Was this reply helpful? Yes No
Sunil Chhabra 1,958 on at

Like
a
(0)

Report
Copy link

Link copied!

Derek

Thanks again for your prompt response. I will upgrade to 18.3 for now.

I do have a question – since I installed 18.4 is there any way to remove 18.4 Service Pak – or do I have to uninstall GP and start all over?

Thanks

Was this reply helpful? Yes No
Verified answer

Derek Albaugh Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

You would need to uninstall Dynamics GP and reinstall with the correct version you are going to use, there isn't any way to back out a service pack once it is applied to a Dynamics GP install.

Thanks

Was this reply helpful? Yes No
Sunil Chhabra 1,958 on at

Like
a
(0)

Report
Copy link

Link copied!

Derek - thanks for all your assistance. I was able to successfully migrate everything to 2018.3. One last question. Is there a KB article as to how to upgrade/migrate integrations from one server to another and upgrade them from 2016 to 2018.

Thanks

Was this reply helpful? Yes No
Suggested answer

Derek Albaugh Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Do you mean integrations from Integration Manager?

If so, there really isn't any type of upgrade process for IM, you just have to remove IM 2016 and install IM 2018, then setup IM 2018 to use your existing IM database where the integrations are held. IM will automatically 'upgrade' the integrations for the 2018 version.

Thanks

Was this reply helpful? Yes No
Sunil Chhabra 1,958 on at

Like
a
(0)

Report
Copy link

Link copied!

Derek

Yes my question is about the Integration manager.

On my old server I have the following 3 databases. This server originally had GP 2013 installed and then it was upgraded to 2016

I have a new server with GP 2018 and IM 2018 – so I need to move the integrations to the new server – so do I move all three databases and then IM will upgrade them?

Thanks

Was this reply helpful? Yes No
Verified answer

Derek Albaugh Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

To clarify, I'll give what is mentioned in the Integration Manager User's Guide:

Converting a database

Use the Database Conversion window to convert a database from a previous

version of Integration Manager to an (newer) Integration Manager.

To convert a database:

1. Open the Database Conversion window.

(Tools > Convert Database)

2. Click Select Database. Browse to the location of the database to convert and

select the database.

3. Click Open.

4. Click Convert Database. The database is converted and a check mark is added

to each step when the conversion for that step is completed successfully. The

new file (Converted_<Name of database>) and a log file (Converted__<Name

of database>.log) are saved to the same folder location as the original database.

If any of the steps in the list were not completed or converted successfully, a warning

icon is displayed by that step. Click the warning icon to find out why the step was not

converted successfully. You can view the log file (Converted__<Name of database>.log)

to find out more information about a conversion that was not completed successfully.

5. Click OK when the conversion complete message is displayed.

6. When you are finished, click Close to close the Database Conversion window.

You can click on the converted database file to open Integration Manager.

You can complete the following optional tasks.

• Rename the database file.

• Change the file extension. You can change the file extension to .mdb.

If the file extension is .imd, you can double click the file to open your

Integration Manager database. If you change the extension to .mdb, you’ll

need to open the database file from Integration Manager.

• Change the path of the converted file (Tools > Options).

Thanks

Was this reply helpful? Yes No