Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 9 to GP 10 Erro: co...
Microsoft Dynamics GP (Archived)

GP 9 to GP 10 Erro: code 0, Other Error (135)

(1) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

I keep getting an error when upgrading from V9 to V10. It's an error
code 0, Other Error (135):
The conversion process encountered an error and the temporary table
did not get removed.

It's in reference to table CN00600 (collections query master). For some companies, this table is blank, so I drop it, continue with with the upgrade, and add it from GP after it's complete. I've exported the data from the table, gone into GP and drop/add the table, and reimported the data. This seems to work, but I'd like to know what caused the problem, and if this "fix" will cause issues. I'm working on a test server, but need to do the real upgrade this month.


Thanks

*This post is locked for comments

  • Tracy Morris Profile Picture
    Tracy Morris 165 on at
    Re: GP 9 to GP 10 Erro: code 0, Other Error (135)

    I ended up having to get scripts from MS support to recreate the tables for CM00101, CM20202 and CM20203. Once we recreated these, the upgrade continued. None of those tables had records in them.

  • Tracy Morris Profile Picture
    Tracy Morris 165 on at
    Re: GP 9 to GP 10 Erro: code 0, Other Error (135)

    George,

    Thanks for the update. I did Google and found another post where someone used SQL mgt studio to find a company that was good, script that table as CREATE TO then changed it the script to use the bad database name and recreate the table. This worked for the SY06000 but I'm still stuck with CM00101. I'm working through it. Thanks.

    Tracy

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP 9 to GP 10 Erro: code 0, Other Error (135)

    Tracy, I'm not sure. I identified the problem on a test server and fixed the problem on the production server before I started the upgrade using the drop/add from the GP interface. There is probably a stored procedure that creates the tables or if you have another company that is not converted, you could copy the structure from it. Sorry I cannot be of more assistance.

  • Tracy Morris Profile Picture
    Tracy Morris 165 on at
    Re: GP 9 to GP 10 Erro: code 0, Other Error (135)

    I am getting this same error on an upgrade (9.0.385 to 2010 SP 1) and do not know how to drop and re-add the table in SQL. I'm getting this on Sy06000 and CM00101 which are both blank. I'm in the middle of the upgrade. Can I leave it on the screen, fix it in SQL, then click the Update Again button? Thanks for any help.

    Tracy

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP 9 to GP 10 Erro: code 0, Other Error (135)

    Yes, I know there is a table difference. As stated in my original post, I had already done as you suggested. It works.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP 9 to GP 10 Erro: code 0, Other Error (135)

    If you drop the table and re-create it before doing the upgrade (ie upgrade with the newly created table)...does the upgrade fail? If it doesn't fail, then there is probably a difference in the table structures. I.e. receating the table resolves the issue.

    Run a select * query on the table before you drop it, and paste the results into GL (incuding the Column Headers.)...then drop and recreate the table...export to XL again and compare the numbers of columns and column names - any differences?

    Try applying the latest service packs - it may change table structures etc.

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: GP 9 to GP 10 Erro: code 0, Other Error (135)

    It might be an issue with the module tables at your company database, could be an issue when you performed your last upgrade long time ago! An error that did not stop the upgrade that time but missed this table.

    However, it looks like the table structure does not match the required structure. To fix this up you might need to drop and recreate the table using "SQL Maintenance" and then reimport back the records to the table.

    Hope that helps.

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