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 / Finance | Project Operations, Human Resources, ... / D365F&O GoLive in Jeop...
Finance | Project Operations, Human Resources, ...
Suggested Answer

D365F&O GoLive in Jeopardy- Data Upgrade has failed

(2) ShareShare
ReportReport
Posted on by JM-25022339-0 4
Data Upgrade has failed, fix the data upgrade issue and resume operation 10 or rollback the data upgrade

After a long 4 year project we are currently ready to Go Live with an Ax2012 to D365F&O upgrade.  Once again have been let down by the Microsoft Support Teams lack of support.
 
The data upgrade process has been ran many times over the last 4 years.   It only works without incident 20% of the time.  Now we are at crunch time and need the issue fixed before planned go live 06 March 2025.

Does anyone have any advice on how to get Microsoft to address this issue as a matter of priority.
Hard not get the feeling that me are a small fish floating around a big pond.   
The lack of support is astounding.
 
Any thoughts or suggestions most welcome.
 
Jodie
Categories:
Dynamics 365 Finance
Microsoft Dynamics AX
I have the same question (0)
  • Suggested answer
    Saif Ali Sabri Profile Picture
    Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

    Since your data upgrade is failing at the critical Go-Live stage, here’s a structured approach to resolving it efficiently and escalating with Microsoft for priority support.

    Immediate Steps to Fix the Data Upgrade Failure

    1. Identify the Failure Point in the Upgrade Logs

    • Navigate to LCS (Lifecycle Services) > Environment Monitoring > Logs
    • Check the Upgrade state and errors in:
      • UpgradeAnalyzerReport.html (gives validation results)
      • DataUpgrade.log (shows table/data errors)
      • UpgradeErrors.txt (lists specific failures)
    • Look for issues in:
      • Data model mismatches (e.g., missing fields, incorrect mappings)
      • SQL-related failures (indexes, constraints)
      • Customizations that block upgrade

    💡 Fix: Address the errors directly in AX 2012 before re-running the upgrade.

    2. Use "Resume Operation 10" Instead of Restarting the Entire Process

    If the upgrade process has partially completed, do NOT restart it from scratch. Instead:

    • Use LCS to resume the upgrade from the last checkpoint.
    • Run: 
      sql
      select * from SYSDATABASEUPGRADELOG where STATUS != 'Completed'
      • If errors appear, correct them and mark the step as completed manually, then resume.

    💡 Fix: Avoid unnecessary rollbacks and reduce downtime.

    3. Validate AX 2012 Data Before Retrying

    Since your upgrade works only 20% of the time, inconsistencies in AX 2012 data are likely causing random failures.

    • Run the Data Upgrade Readiness Checks (LCS tool)
    • Use: 
      sql
      exec ReleaseUpdateDB_Version
      • Ensures the correct database version is recognized before upgrade.

    💡 Fix: Clean up data in AX 2012 before running another upgrade.

    4. Fast-Track Microsoft Support Escalation

    If Microsoft is not prioritizing your issue, follow this escalation process:

    🚀 Priority Escalation Steps:

    1. Raise a Microsoft Premier Support Ticket

      • Go to admin.microsoft.com > Support > New Service Request
      • Select “Production Blocker”
      • Attach logs (DataUpgrade.log, UpgradeErrors.txt, screenshots).

    2. Escalate via Your Microsoft Partner

      • If you have a Microsoft Partner, they can escalate it on your behalf.
      • Request a direct Microsoft escalation manager to intervene.

    3. Contact Your Microsoft Account Representative

      • If you have a Microsoft AE (Account Executive), demand a P1 escalation.

    4. Use the Microsoft FastTrack Team (if applicable)

      • If your project was assigned a FastTrack Architect, request direct escalation to Microsoft engineering.

    💡 Fix: Push for immediate escalation as a "Go-Live Blocker."

    5. Contingency Plan: Parallel Upgrade Test with a Recent Backup

    If time allows, clone a UAT environment from a recent AX 2012 backup and attempt the upgrade in parallel to:

    • Validate data cleanup fixes before retrying in PROD.
    • Ensure repeatability of the upgrade process.

    💡 Fix: Provides a backup plan if Microsoft delays the resolution.

    Conclusion: Act Fast to Get Microsoft to Prioritize This

    ✔ Analyze Logs → Fix upgrade errors instead of restarting.
    ✔ Use Resume Operation 10 → Avoid unnecessary rollbacks.
    ✔ Fix AX 2012 Data Issues → Run checks before re-upgrading.
    ✔ Escalate to Microsoft P1 Support → Demand priority handling.
    ✔ Parallel Test in UAT → As a backup option.

    🚨 Your Go-Live is on March 6, 2025—do not wait for Microsoft to respond passively. Escalate aggressively!

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 > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 611 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 529 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 285 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans