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

Notifications

Announcements

Season of Giving Solutions is Here!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Upgrade 9.0 - 10.0 err...
Microsoft Dynamics GP (Archived)

Upgrade 9.0 - 10.0 errors with invalid column name pamccurncyid

(0) ShareShare
ReportReport
Posted on by Bill Songstad 35

I am attempting to upgrade a GP 7.5 installation to something current.  I researched an upgrade path of

7.5 - 9 on MSDE2000 sp4

9 - 10 on MSDE2000 SP4

10 - 10 on SQL express 2008

Things go well on the first upgrade, but the upgrade from 9 -10 errors out while upgrading the companies. 

The error occurs while upgrading stored procedures; in the section for taPoLine.  Specifically: "the following SQL statement produced an error: create procedure dbo.taPoLine"...  Inside the error box is a rather lengthy SQL statement.  Clicking OK reveals an apparent detail on the error:  "ERROR [Microsoft][SQL Native Client][SQL Server] Invalid column name 'PAMCCURNCYID'

GP Utilities Shuts down at that point.

What I did:

From GP 9 I ran the scripts to check the database indicated in the Upgrade Instructions Release 10.0 November 15, 2010.  No errors. (other than the one produced due to an error in the instructions that has you run a script intended for the company database on the dynamics database).

I then installed the GP 10.0 base installer.  Then I installed the latest update for GP 10: KB2716825

All apparently good.  I run GP utilities, they churn for a good long time and it ends up with the errors described above. 

Can anyone shed any light on this?  There is very little reference to PAMCCURNCYID on the web and even less with reference to my actual error.

Thanks in advance for any assistance,

Bill

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Hi Bill,

    Thanks for raising this with us. What is happening here is that eConnect is trying to create stored procedures to link to Project Accounting, but is finding that the Project table structure is not correct.

    Do you use project accounting? If not then the fix for this is to drop all project accounting tables with the exception of the following:

    PA00001

    PA00002

    PA00010

    PA50100

    PA50102

    PA50103

    PA50105

    paActvty

    palb*

    Once you have dropped the project tables restart utilities and the upgrade should now continue for you. By dropping the Project Accounting tables eConnect will not attempt to create PA stored procedures.

    If you are using project accounting I suggest that you contact your partner or log a support incident so

    that we can look into this issue further.

    Regards

    Rob

  • Bill Songstad Profile Picture
    Bill Songstad 35 on at

    Thanks Robert.  That has got me through the error.  That is a lot of drop table commands...  Now I'm off to upgrade SQL and try to step up to GP2010.

    Bill

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

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

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

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November 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