Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

Upgrade from 18.4 to 18.5 failing on PM00300 and PM40100 tables

Posted on by 5

Has anyone experienced upgrade failure on PM00300 and PM40100?   The upgrade error details indicate the temp table couldn't be deleted and the recommendation is to remove it manually, however, after attempting to 'upgrade" the table again, the PM00300 ends up totally removed from the database, as does the PM40100 when performing the same attempted re-upgrade.  I have no other applications running.  Any recommendations on how to troubleshoot and resolve would be greatly appreciated. 

Categories:
  • GinaBothun Profile Picture
    GinaBothun 5 on at
    RE: Upgrade from 18.4 to 18.5 failing on PM00300 and PM40100 tables

    I ended up creating a new GP company with the 18.5 code before restoring, so that I had the proper table structures. Then restored my Dynamics and TWO companies.  Upgraded again and again until it got down to 1 PM setup table and 2 workflow tables, when it finally finished with success.  Then I dropped the 3 bad tables and created new with the proper structures from the new company I had created.  I inserted 1 row of data back into the PM setup table and was good to go.  8 hours of fun.

  • Suggested answer
    RE: Upgrade from 18.4 to 18.5 failing on PM00300 and PM40100 tables

    The Utilities error messages are rarely accurate, especially when it mentions having to delete temp tables, which Utilities will do 99% of the time when the upgrade fails on a table.

    This 'failed tables' script is better at giving us information as to why a table is failing and why:

    SELECT b.fileOSName, a.fileNumber, a.PRODID, a.Status, a.errornum, a.errordes, c.CMPANYID, c.INTERID FROM DU000030 a JOIN DU000010 b ON a.fileNumber = b.fileNumber AND a.PRODID = b.PRODID JOIN SY01500 c ON a.companyID = c.CMPANYID WHERE (a.Status <> 0 or a.errornum <> 0) and a.Status <>15

    Additional information can also be found in the dexsql.log as needed.

    If you're still working on this upgrade and need help, I'd recommend a support case, as upgrades are usually a little more complex than what can be worked on via these forums.

    Thanks

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,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans