Forgot password
Enter the email address you used when you joined and we'll send you instructions to reset your password.
If you used Apple or Google to create your account, this process will create a password for your existing account.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Reset password instructions sent. If you have an account with us, you will receive an email within a few minutes.
Something went wrong. Try again or contact support if the problem persists.

Marionberry Destiny 2 Error Code – What is This?

Been encountering the Marionberry Destiny 2 error code but not quite sure why? Hopefully we can shed a little bit of light on your problem.
This article is over 4 years old and may contain outdated information

If you’ve been encountering some difficulty with cracking into the latest of what Destiny 2 has to offer, then don’t fret. The community as a whole has been encountering some hiccups lately, whether it’s connectivity errors or bugs that Bungie has to chew through, but here’s what we know about the Marionberry Destiny 2 error code.

Recommended Videos

Marionberry Destiny 2 Error Code – What is This?

It seems like only yesterday that Bungie pushed through the update for the EDZ Obelisk issue that was plaguing us. However, it seems like we just can’t catch a break what with this Marionberry error code resurfacing. If you’ve been encountering it, it looks like it doesn’t really matter which console you’re playing on – all seem to be affected indiscriminately, whether you’re Team PlayStation or Team Xbox. 

According to Bungie’s Help forums, the Marionberry error code in Destiny 2 is encountered by players who have an issue with their networking setup. The following may be reasons why you’re getting this particular code, though we wouldn’t consider this an exhaustive list:

  • WiFi outage
  • Network settings changing
  • Parental Control settings
  • Faulty router firmware
  • Player to Player connectivity issues

The fix that’s been suggested by Bungie for moments like this appears to be power-cycle any networking hardware before attempting to restart the game. One reason that the forums are giving for the Marionberry error code is also just general issues with one’s router and its hardware. For those who aren’t getting relief out of the above-suggested fix, maybe checking out the Network Troubleshooting Guide that Bungie has kicking around for Guardians to look at while they peer closely at any issues on their end will help. 

Need a hand with something else that isn’t the Marionberry Destiny 2 error code? This looks like something which is affected by the connectivity settings of individual players as opposed to something on the Bungie server side, so give a few methods a crack before having a go online. In the meantime, we’ve got some other tips and tricks that Guardians might find useful:


Prima Games is supported by our audience. When you purchase through links on our site, we may earn a small affiliate commission. Learn more about our Affiliate Policy
Author
Image of Ginny Woo
Ginny Woo
Ginny hails from just south of Mordor, and when she's not debating others about the One Ring then she's probably glued to an MMO or a JRPG. With Final Fantasy XIV, Destiny 2, and World of Warcraft on her plate, she's always got something to chat about and a sneaky guide up her sleeve. If writing's not on the cards, then she's probably drinking way too much coffee.