Skip to main content

Notifications

Microsoft Dynamics GP (Archived)

Dynamics GP 2013 R2 Upgrade Crashes on Fixed Assets Tables

Posted on by Microsoft Employee

Hello:

I'm conducting a test upgrade from GP 2010 (11.00.2197) to GP 2013 R2 (12.00.1920).  I have 16 company databases to upgrade.

The DYNAMICS databases and two of the larger databases upgraded successfully.  But, the upgrade has crashed on another large database.  Specifically, GP Utilities crashed on the following fixed asset tables:

FA_Batch_Headers

FA_Financial_Detail_MSTR

FA_Financial_Detail_WORK

FA_GL_Interface_WORK

FA_Transfer_MSTR

When I review the details, most of the messages are "The conversion process encountered an error and the temporary table did not get removed" and "Remove the temporary table at the database level".

Another error says, "Invalid column name 'Ledger_ID'".

Now, I ran the script below before the upgrade and inserted the FA00902.cnk file into the GP 2013 code folder.  My past experience and discussions with other consultants on upgrading showed that this procedure needs to be done in order to prevent another issue that has been reported with upgrading fixed assets tables.

I frankly cannot make heads or tails of what's in the dexsql.log file.

Any ideas?

Thanks!

John

delete from DB_Upgrade where PRODID = 902

insert into DB_Upgrade (db_name,PRODID,db_verMajor,db_verMinor,db_verBuild,db_verOldMajor,db_verOldMinor,
  db_verOldBuild,db_status,start_time,stop_time)
    select DB_Name(),902,12,0,1,12,0,1,0,GetDate(),GetDate()
  
insert into DB_Upgrade (db_name,PRODID,db_verMajor,db_verMinor,db_verBuild,db_verOldMajor,db_verOldMinor,
  db_verOldBuild,db_status,start_time,stop_time)
     select INTERID,902,12,0,1,12,0,1,0,GetDate(),GetDate() from SY01500

*This post is locked for comments

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Dynamics GP 2013 R2 Upgrade Crashes on Fixed Assets Tables

    I opened up a case with Microsoft eSupport.  First, the following script needs to be run prior to the upgrade of the troubled database:  DELETE DU000030.

    Then, backups of the fixed assets tables need to be made.  Next, create scripts that will be used to recreate these four GP 2010 tables.  Afterward, drop these tables.  Run the scripts, next, to recreate the GP 2010 tables.  Continuing, restore the data from the backed up tables into the "new" GP 2010 tables.  Finally, run GP Utilties and all will be well.

    Thanks!

    John

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans