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 :
Microsoft Dynamics GP (Archived)

Installation GP2013 over existing GP10 instance

(0) ShareShare
ReportReport
Posted on by 12

We have a test system that was on GP10 - and we want to move to GP2013.

First thing I did was to delete the TWO database and re-installed the Lesson data.

When running GP2013 for the first time we encountered the following error.

And then another series of error messages - all seemingly related to POP module

Any thoughts?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Mahmoud Saadi Profile Picture
    32,738 on at
    RE: Installation GP2013 over existing GP10 instance

    I don't really understand the logic behind deleting the two and running GP 2013. How about Dynamics DB ?

    You should have followed the upgrade path to get finally to Dynamics GP 2013, and let the utilities of 2013 upgrade existing companies to the 2013 version. Are you looking to deploy the test environment of Fabrikam only ?

    If so, do a clean installation either by deleting the existing database or changing the Dynamics DB name while installing Dynamics GP 2013.

    Let us know if you have any further concerns,

  • Suggested answer
    Bill Campbell Profile Picture
    12 on at
    RE: Installation GP2013 over existing GP10 instance

    Reason was I did not want to do a 2 hour GP10 to GP2010 to GP2013 update simply for the TEST company  - this is my test computer and I was only 'playing' with this.

    In a real world situation you would be correct, you would never 'just delete a database' and you would never jump an upgrade.

    I posted this to see if anyone else had encountered this kind of an error in their updates and if so, that the cause may have been.

  • Richard Wheeler Profile Picture
    75,848 Moderator on at
    RE: Installation GP2013 over existing GP10 instance

    If all you want is the Test company then why bother with the upgrade at all? Just install GP 2013 R2 and then launch GP Utilities and add the Sample company. Now if you have other companies, I would go into GP 10 and delete the Test company and then upgrade. After this is finished you can add a fresh Sample company.

  • Mahmoud Saadi Profile Picture
    32,738 on at
    RE: Installation GP2013 over existing GP10 instance

    Okay Bill, 

    The error I see above could be tracked back to specific trigger not being registered in the Dynamics.dic, the various series of errors could be all related to the same point.

    I would simply do a clean installation of Dynamics GP 2013 which would take less than 30 minutes.

    As you initially emphasized, time matters. 

  • Bill Campbell Profile Picture
    12 on at
    RE: Installation GP2013 over existing GP10 instance

    Richard the only company on my test system is TWO and I was simply trying a 'quick' update - jumping over GP2010 - it did not fail the update or generate any errors, it only generated the message set shown above, on the launch of what appears to have been a 'clean installation' of GP2013 TWO database.

    I have dumped both the DYNAMICS and TWO databases from the TEST SQL instance and am just finishing the create of the TWO database in GP2013.  So at this time all appears correct and normal.

    As noted, just wondering if anyone else has seen this type of error that does not show as a failure during the update, but at execution it fails.

  • Richard Wheeler Profile Picture
    75,848 Moderator on at
    RE: Installation GP2013 over existing GP10 instance

    My guess the PAPM tables have something to do with Project Accounting and Payables Management. It is possible someone added a trigger or a third party product did.

  • Bill Campbell Profile Picture
    12 on at
    RE: Installation GP2013 over existing GP10 instance

    So, what is interesting is I thought along the same lines - so, in the TWO database I dropped and recreated the PA and PM tables - thought that would remove any triggers created by 3rd parties applied by me back in GP10 - no such luck.

    I dumped the Stored Procs in both Dynamics and TWO - no difference.

    Not until I dumped the coded - from control panel - and did a clean install with no DYNAMICS or TWO database did I get to launch the system and not get any error message.

    As your assessment on the source of the error I would agree -  there must be something in Project and Payables that updates the Dynamics and effects the update even without the TWO database present at the time of the update.

    All is good and the TWO database is now working in GP2013.

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

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…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans