Removing Modules from GP 2010

(0) Share

Report

Posted on by rhousz

415

I cannot find the process for removing modules from GP. We are testing Revenue/Expense Deferrals and were wondering how to remove it after testing should it be decided that we are not going to continue using it?

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (2)

Community Member on at

Like (0)

Report

RE: Removing Modules from GP 2010

Back-up first for a roll back plan.

Computer Management >Add Change Programs> Dynamics GP> Unselect it from the install and continue through the process. Essentially the reverse of when you installed the module.

Then edit it out of your Dynamics.set file.

support.microsoft.com/.../872087

Was this reply helpful? Yes No
Suggested answer

Mahmoud Saadi 32,738 on at

Like (0)

Report

RE: Removing Modules from GP 2010

Just go to Control Panel > Add remove features.

The same steps provided on an old support article, How to uninstall a feature in Microsoft Dynamics

If you just testing, I recommend creating a test environment for that instead of trying features on an up and running Dynamics GP environment.

Never hesitate to share any further inquiries,

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

RE: Removing Modules from GP 2010

While the add/remove programs options will remove it from your dynamics.set file, I'm not sure it will remove the extra tables from your database. Also, I'd check my DU tables and DB_UPGRADE table in the Dynamics database to see if there is any reference to the module.

If you are not going to use it, please be sure to remove it completely. If you don't, I can guarantee you will have problems because of it at some point.

Kind regards,

Leslie

Was this reply helpful? Yes No
rhousz 415 on at

Like (0)

Report

RE: Removing Modules from GP 2010

I'd found the Microsoft article and figured removing would be done via Add/Remove Programs.

My concern is for the database. Is there a uninstall script for removing a module that is no longer used from the Database? I know having previously used features tables present can cause issues when doing major version upgrades. I'd rather not set up my future self or successor for failure if we decide to upgrade and encounter issues due to orphaned tables.

Was this reply helpful? Yes No
rhousz 415 on at

Like (0)

Report

RE: Removing Modules from GP 2010

Well it seems someone already installed RED in 2008 and abandoned it. So I am getting:

Failure encountered ON 4/19/2014 at 10:04:01 AM. Error: Product 1045 does not support upgrading from version 10.0.901.

Failure encountered ON 4/19/2014 at 10:04:02 AM. Error: Product 1045 does not support upgrading from version 10.0.901.

Failure encountered ON 4/19/2014 at 10:04:02 AM. Error: Product 1045 does not support upgrading from version 8.0.0.

I imagine I would have to delete PRODID 1045 from DB_Upgrade, DU000020, DU000030 tables in DYNAMICS database. Would I have to drop the tables or leave them since I am installing again?

Was this reply helpful? Yes No
Verified answer

L Vail 65,271 on at

Like (0)

Report

RE: Removing Modules from GP 2010

Hi Rhousz,

Yep, this is exactly the kind of error you will run into. You can just delete those records referencing that product from the tables you listed. Based on your error message, it looks like you have three companies that think they are using that product.

I'm not sure what you're asking with "Would I have to drop the tables or leave them since I am installing again?" I'll forge ahead with a couple of possibilities. If you are referring to the DB_Upgrade and 'DU' tables, do not drop them, just take out the records referencing the product. The tables to drop would be those tables associated with the products you want to get rid of.

The easiest way I have found to drop tables from uninstalled dictionaries is to install the dictionary, go into SQL Maintenance in GP, pull up the undesired dictionary, check off all of the tables, stored procs, etc. and drop them. After that, uninstall the dictionary and make sure their aren't any records in the DB_Upgrade or DU tables. If that isn't a good answer for you, simply get the list of tables for that dictionary and delete them using Studio Manager.

If you have any other error messages let us know.

Kind regards,

Leslie

Was this reply helpful? Yes No
Verified answer

Derek Albaugh on at

Like (0)

Report

RE: Removing Modules from GP 2010

Hello,

I think you have the information you need, please let us know if you need anything else.

As mentioned, when you remove a module from Dynamics GP through Add/Remove Programs, it just removes the module from that install's Dynamics.set and DynUtils.set file as well as the dictionary files for that module. It does not remove anything from the tables or databases.

If you get version errors like you mentioned, trying to reinstall the module anew, such as Revenue/Expense Deferrals in this example, you will want to remove the records for PRODID 1045 from the DB_Upgrade, DU000020 and DU000030 table.

***Note: By doing this, it'll cause Dynamics GP Utilities to reinstall the module anew at the new version, meaning any data for this module in the databases will be lost, so make sure we're only doing this if the customer wants a completely new installation of the module.

Lastly, each and every module has sub-feature tables in the DYNAMICS/system database and/or company databases that Utilities also looks for along with the above mentioned system tables, when it attempts to verify whether a module is installed.

For the Revenue Expense Deferrals module, that table is PP000001 in each company database. Before you can do a new install of RED, you'll need to remove PRODID 1045 from the above system tables and drop this table from each and every company database, otherwise, if Utilities sees this PP000001 table, it will think the module is installed for that company database and attempt to upgrade it, which will also lead to version errors such as you mentioned, though the version mentioned will be something like 8.0 or lower.

Thank you,

Was this reply helpful? Yes No
rhousz 415 on at

Like (0)

Report

RE: Removing Modules from GP 2010

I am going to do these steps this weekend. Thank you for your help. I imagine similar tasks would need to be done for any unused modules? Looks like whoever did our initial installation installed everything.

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

RE: Removing Modules from GP 2010

Each module/feature does have its own set of sub-feature tables, which are really only a concern if you plan to re-install the module anew for Dynamics GP.

If you're just uninstalling the module(s) with no plans to install them again in the near future, normally you would only need to uninstall through Add/Remove Programs so the module is removed from the Dynamics.set and DynUtils.set files, as well as the dictionary files are removed.

If the module isn't listed in the Dynamics.set file, it won't be loaded when the application is launched.

If the module isn't listed in the DynUtils.set file, it won't be updated or installed when Utilities is launched.

Thank you,

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

RE: Removing Modules from GP 2010

Thanks Derek,

I ran into a similar issue where we had once installed the RED in GP on our TEST bed system, but later then restored the company databases from the LIVE system, thus making some of the GP companies out of sync... I tried to un-install and re-install the RED module thru the add/remove option in Windows, which up to a certain point worked, but then asked to run GP Utilities to complete the installation... and there is where I started to run into issues.. GP Utilities wouldn't let me complete the installation, returning all the time the error about asserting the version of the modules, and the DU_Install.log would always point back to the module 1045 (RED) not being upgradable from version 8.0.0.

My grip is that I had cleaned out everything from the DUxxx & DB_Upgrade tables where it refered to no longer existing companies and outdated product versions. Every time I was attempting to run the GP Utilities, it would re-add the entries for 4 companies in the DB_Upgrade table with a Major Version 8, thus I had to figure out why... and the answer was the remaining PPxxxx tables from the previous installation of RED in those companies (turned out to be companies that we hadn't restored from the LIVE system).

What I find rather annoying is that the addition of a new module just deploys it to every company, even the one you don't use actively (i.e. consolidation & test companies).

Thanks again for the hint... great life-saver.

@GP_Beat

Was this reply helpful? Yes No