Career inaccessible - Error 2047

Hello Folks,

I just spent an entire day trying to figure out what’s going on with my FS2024 SU3 career not accessible.

1. THE ISSUE

The starting point is two days ago, I start FS and click on Career, the earth displays and nothing else happened, no button, no possible action. After a timeout of a couple of minutes, this message displays : “Career inaccessible : There seems to be a temporary issue with the server managing the Career mode….”

I searched online to check the state of the services, verified on downdetector also, and saw that no one was complaining.

I’m on a Windows 11 PC, cabled to the internet with a stable internet connexion. Nothing changed on my hw since months. Neither on software, except regular security update.

2. First Troubleshooting

I verified:

  • Eventvwr and found nothing.

Then did this :

  • Xbox App updated
  • Logged out/in
  • Rebooted my PC
  • Checked permissions
  • check for 0-byte files in wgs
  • Rebuild the LocalCache by renaming its folder.

Nothing changed. At this point, SU3 Career Mode remained inaccessible.

3. Joined SU4 Beta for testing

I opt in SU4 Beta to compare behavior using a different branch. As the infrastructure behind is different and I wanted to see the evolution, I thought this would be a good way to eliminate my local installation.

  • SU4 Beta also failed to save activities, but not the same way
  • The game displayed Error 2047: Unexpected Cloud Save Error at the end of any activity
  • This was different from SU3 Career Mode issue
  • The Career mode was accessible on SU4 Beta

4. Repaired Xbox Services and Identity Layer

I performed the following operations:

  • Reinstalled Gaming Services
  • Reinstalled Xbox Identity Provider
  • Forced token renewal (logout/login from Xbox app)
  • Verified permissions on all packages
  • Recreated LocalCache
  • Deleted/Recreated the wgs folder multiple times

Result: Nothing changed, the 2047 error persists.

5. Cloud Reset. Key moment.

I decided to delete my MSFS 2024 Cloud Save data via the Xbox Online “Manage games” page.

Result:

  • After restarting SU4 Beta, it behaved like a fresh installation immediately after the reset
  • It asked again for first-launch preferences
  • Rebuilt a completely new wgs
  • Re-synchronized cloud data successful
  • Error 2047 disappeared
  • Activities saved normally

At this point, SOLVED FOR SU4 Beta

6. Switch back to the SU3 version

Result : The problem remains exactly the same with SU3. Career mode not accessible.

Conclusion

After this journey, I’m back on SU3 having the same problem.

The online game data reset is the action that restored a normal behavior on SU4 Beta.

I suppose that my Gamertag Online Game Data Reset was contextualized to that SU4 Beta branch.

And I’m here now. My feeling is that my online data are corrupted and I’m hesitating to reset them, I don’t want to loose my Carrer progress or nothing else.

  • Except reinstalling from scratch or clear the Online Game Data I don’t have other ideas, Do you ?
  • Do you know what will happen to my progress, logbook, … if I do the Online Game Data Reset while I’m on the SU3 branch ?

Thanks,

FlySafeNFast

Update : 12 days in, daily contact with support, issue confirmed not client-side

Hi all,

I understand this issue doesn’t seem to interest the masses.

I’m posting this update here for two reasons:

  1. If this ever happens to someone else, they will at least find a trace of what was investigated and what was proven.

  2. To express a bit of solitude and frustration: I bought the product, I can no longer use a major part of it (Career on public branch), and the fix now depends on the community voting system among an ocean of other issues that affect far more players.
    Realistically, I’ll probably never reach the priority needed to get this fixed quickly, simply because this bug seems unique to me.

Still, here’s where things stand.

12 Days of daily troubleshooting with support

For fairness: the MSFS support team did their job and followed their procedures.
However, these procedures consumed a huge amount of time, despite the fact that the real root cause was already identified early on, when I reproduced the issue on completely new hardware.

Together we systematically tested:

  • Full reset of cloud saves
  • Reinstall Gaming Services
  • Reset LocalCache, StreamedPackages, CommunityFolders, Xbox Identity Provider
  • Account, Windows, drivers
  • Beta channel work (SU4), public fails (SU3)

But the decisive moment was this:

The key test: Reproduced on a completely new PC

I felt that they were going to investigate a lot on my side while I was sure at 99% the problem was cloud data related. To avoid unnecessary investigation as quick as possible I built a second PC using spare hardware:

  • Brand-new PC (I5 9th, 16Gb, 2x250Gb SSD, GTX1660 Super)
  • Windows 11 25H2
  • Log on this one with my only Microsoft Account
  • MSFS install
  • No peripherals, no mods
  • Connected to a different network (Mobile Access point)

The only common assets are my Microsoft account and the Xbox account associated. And by inheritance everything stored in the cloud data that relates to them.

SU3 Career mode fails EXACTLY the same way on this clean system.

This definitively eliminates:

  • any local corruption
  • Windows problems
  • Gaming Services
  • mods, settings, drivers
  • anything user-side

What I lost “in the battle”, till now

I lost my entire logbook and a lot of time. Most importantly, my real SU3 Career Mode remains inaccessible.

Current Situation

MSFS Support has now officially requalified the case as a Bug Report, because “it appears that the issue you reported does not have straightforward troubleshooting steps that can be applied to resolve it at this time”:

I’ve been advised to stay on SU4 Beta to access Career, but the progress are not linked, it doesn’t help my real progression. And more importantly, it’s not about SU3 or SU4, it’s about Channel, Public or Beta. As soon as SU4 will be released, I’m pretty sure that I’ll still have the same issue on the Public branch, whatever the version.

If anyone else has encountered a similar SU3 Career failure recently, please share

Fly Safe everyone.

FlySafeNFast

The issue has been solved after upgrading to SU4 yesterday.