web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 2013 Module upgrade...
Microsoft Dynamics GP (Archived)

GP 2013 Module upgrade fails

(0) ShareShare
ReportReport
Posted on by Community Member

The following modules display the previous version after upgrade to 2013.

1157

Collections Management

1472

EFT for Receivables Management

3107

Extender

Upgraded from GP 10 SP5 to 2013 version 12.00.1920

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    L Vail Profile Picture
    L Vail 65,271 on at
    RE: GP 2013 Module upgrade fails

    Hi,

    Collections Management and Extender have been returned to the original developers. The OEM contract has terminated and those products are no longer on the GP install. To upgrade them, you'll need to download the code and get reg keys from the originating company. For Collections Management it's Professional Advantage (profad.com), for Extender it's eOne Solutions (eonesolutions.com). The EFT for Receivables Management module is no longer a separate module as it has been embedded in the RM function that lives in the Dynamics.dic

    Kind regards,

    Leslie

  • Community Member Profile Picture
    Community Member on at
    RE: GP 2013 Module upgrade fails

    Is there a process to remove the deprecated modules if we have no intention of keeping them? If the EFT for Receivables module has been integrated into another module shouldn't it have been removed from the DB_ Upgrade table?

  • Suggested answer
    L Vail Profile Picture
    L Vail 65,271 on at
    RE: GP 2013 Module upgrade fails

    Hi,

    Perhaps it should have been removed, but it wasn't. I just (today) completed an upgrade from 2013 to 2015 and had Collections Management, SmartList Builder and Extender in the DB_Upgrade table and it did not bark at me at all. So, I wouldn't worry about it. Now, what I did do was install the current versions of those softwares from the new vendors. My client is going to continue using them. I do not know if it made any difference, but I had a problem before with SmartList Builder during the transition back to the OEM, so I didn't take any chances. You'll know soon enough if you get the 'we can't determine the version' error when you launch utilities. That's not the exact text of the error message, but you'll recognize it if you get it. The good thing is that you will be presented with the error right away; it won't start the table update until you clear that error. In my past I have cleared the error by removing the offending record from both the db_upgrade table and the DU000020 table.

    Kind regards,

    Leslie

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans