Destiny 2 beta error codes: what to do about Olive, Moose, Weasel, crashes and known issues

The Destiny 2 beta is not without its problems. Here's the latest on error codes and known issues.

If you're having a problem with the Destiny 2 beta, it could be an error, or it could just be the fact that you're helping to test an unfinished product. In either case, it's not unexpected and you should anticipate some interruptions to gameplay.

That doesn't mean you just have to live with it, though. Prior to the Destiny 2 beta start, Bungie provided a list of known issues it expected players to run into. You can consult that below, or scroll down further for current error codes and solutions.

Destiny 2 beta known issues

The biggest and most obvious problem Bungie has highlighted in advance is networking issues, something you're bound to run into in a stress test like this. Other issues include location names not appearing in Crucible matches, bugs related to joining an in-progress game of the Inverted Spire strike, missing localisation for some content, and more.

Here's the full list as of the time of writing:

• Players may experience a variety of networking error codes when attempting to play the beta
• Bungie will be testing server stability throughout the beta, which may cause error codes to appear periodically
• Location names sometimes do not appear during Crucible gameplay
• Players sometimes are kicked to orbit after witnessing a black screen when entering a Countdown match
• Players may sometimes be placed at the beginning of the Inverted Spire strike when joining in progress
• Sandbox balancing is still taking place: some weapons or abilities may have higher or lower damage than intended
• Not all content has been localised in all languages
• If you encounter any network related issues during the Destiny 2 beta, please follow our network troubleshooting guide to ensure proper network settings for Destiny gameplay

As of July 20, Bungie has also acknowledged the infinite super and infinite ammo exploits discovered by beta testers - so don't expect them to last.

Bungie suggested that players report any issues not listed above in the help forum if and when they run into any.

Destiny 2 beta error codes

Now that the Destiny 2 open beta has kicked off, we've seen a crop of error codes and crashes. Here's what to do if you encounter each one:

• Client crashes

  If your Destiny 2 beta client crashes while playing or when logging in, uh - sorry? Open it again. Bungie is investigating this issue.

• Moose error code

  This error crops up while playing various activities. The latest update from Bungie suggests restarting the activity.

• Weasel error code

  This error occurs after a player is returned to orbit during an activity or when inspecting gear. Bungie does not yet have a solution, but redditors discovered a workaround related to clan invites. Bungie has disabled clan invites for the rest of the beta to squash this bug.

• Olive error code

  If this error pops up, relaunch the beta and retry that activity again and resume what you were doing before the error occurred. Per Bungie, if you encounter this error again, exit Destiny then relaunch. If you continue to see this error, it’s likely due to testing on the studio's end.

• PlayStation Network error code CE-34878-0

  This error code is related to language settings, so you can workaround it by changing your console's language setting to English. That's not ideal if English is your second language, but at least you can get into the gameplay.

• Termite error code [resolved]

  The Termite error prevented players from connect to the Destiny 2 beta, but seems to have been resolved on PS4, but affected Xbox One players until the initial demand of beta launch died down. Restart the client if you're still stuck.

The Destiny 2 beta started first on July 18 for pre-order customers on PS4, then a day later on Xbox One. It became open to everyone on July 21.

The beta includes access to a single-player mission, a strike, and two PvP maps and modes.