{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Awaken Sound:
10/25/2014 3:41:59 AM
4
Getting Marionberry Error Code as of 11:30 PM EST.
Ever since 11:30 pm I have not been able to connect to the Destiny Servers whatsoever, and the Marionberry Error Code appears. I'm not even able to get to the character selection screen. I am on Xbox One. Is anyone else getting this? Or is there a way to fix it? I haven't been able to fix it through turning off my xbox and turning it back on, and if I test the network and multiplayer connections in the xbox settings, both come up saying It's all good. I'm on a wired ethernet connection, however I do have a Strict NAT Type.
-
5 RepliesHi there! Marionberries are local issues primarily, so a strict NAT could cause that, definitely. If you've already gone through a powercycle and it's not resolved, I'd recommend going through the networking options here- http://www.bungie.net/en/Help/Article/11930 There are a few other things that could affect this error you didn't mention trying yet. Hope this helps!
-
DIAMOND DOG1404 Xboxone It was playing fine then 11.30gmt marionberry error.I dont understand it i have 2 xboxones the other is working fine
-
1 ReplyNevermind I guess? It spontaneously fixed itself. I dismissed the error for the millionth time and the next time I hit A to Play it connected like normal. Not sure what happened there but it wasnt working for almost exactly 15 minutes.
-
I am having this problem too
