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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / the conversion process...
Microsoft Dynamics GP (Archived)

the conversion process encountered an error and the temporary table did not get removed

(0) ShareShare
ReportReport
Posted on by Community Member

Hello,

Upgrading from Microsoft Dynamics GP 10 to 2010.  I am receiving the error message "the conversion process encountered an error and the temporary table did not get removed" on the following tables: GL10110, GL10111, GL70500, GL70501.

The error explanation is: The converstion process encountered an error and the temporary table did not get removed.

Recommended Action: Remove the temporary table at the database level.

I ran all pre-upgrade scripts prior to starting the conversion process.  I saw in another post that dropping the temporary tables what not necessary to the upgrade and that I could set the status to complete in the DU00030 table. Does anyone know if that would work and how to complete?

Any suggestions to resolve would be most appreciated.

 

 

*This post is locked for comments

I have the same question (0)
  • Melissa Sandrovich Profile Picture
    Melissa Sandrovich on at

    I ran into the same issue recently.  The only thing I did to make it work was to log in to the old version before upgrade.  In the SQL maintenance, I dropped and recreated the tables and auto procs for these tables.  The GL70500 and 501 are report options.  The other are summary tables.  The summary tables get recreated by runiing reconcile in the GL.  The report options would have to be recreated.  After spending almost one day trying to get this to work, this is the route I went.  

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Thank you for the suggestion, Melissa.

    It took a little while to figure out, but here is what I ended up doing to resolve the issue.  Hopefully this can help someone going forward.

    1) Ran the failed table script to verify what failed:

    SELECT b.fileOSName, a.fileNumber, a.PRODID, a.Status, a.errornum, a.errordes, c.CMPANYID, c.INTERID

    FROM DYNAMICS.dbo.DU000030 a

    JOIN

    DYNAMICS.dbo.DU000010 b

    ON a.fileNumber = b.fileNumber AND a.PRODID = b.PRODID

    JOIN

    DYNAMICS.dbo.SY01500 c

    ON a.companyID = c.CMPANYID

    WHERE (a.Status <> 0 or a.errornum <> 0) and a.Status <>15

    2) Then ran:

    delete DYNAMICS..DU000030 WHERE Status <> 0 and Status <>15

    3) Then ran:

    delete dynamics..duLCK

    4) Opened the Dex.ini file and set "Synchronize=TRUE" and saved changes

    5) Re-ran GP Utilities and the companies upgraded successfully.

  • Community Member Profile Picture
    Community Member on at

    I am having the same problem.  I upgrading from gp10.0 to gp2013 and when it goes to upgrade the company I get the same error and in the details it says rm00102. I have a dexsql.log also but I not sure what to look for in it.

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…

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)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans