{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/8/2014 7:30:41 AM
5
Xbox1 Every Error Code Every Hour
Sunday December 7th
Logged into my Xbox one around 11am central time and immediately got error code marionberry. Complete boot from game. Reloaded game got error code weasel. [u]This was the first time I had ever been KTO. [/u]
Tested connection, live and Internet were good open NAT. Followed error code instructions power cycled everything. Retested same results.
Loaded destiny started playing everything was fine for an hour. Error code canary. Then immediately followed by weasel. Xbox party chat stayed connected live never disconnected. However destiny said I had no internet connection.
So every hour or less for twelve hours all three players in the fire team members were consistently being booted. With various error codes bee, weasel, canary, marionberry and more I can't remember. Sometimes error codes stacked up to three or four for a single boot.
I have also received a 75mb update once a day for the last five days.
I have never had issues with Destiny and other players in my fire team have never had issues to this extent before.
Anyone else having issues with Xbox One please post here.
Thanks,
I337Spartan.
-
1 ReplyWeasel to Marionberry to Wasp I am hardwired from my xfinity modem is this a bungie server issue?
-
I had the same problem. Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, Caterpillar, Baboon, Weasel, etc, etc, etc, etc... I can confirm that this is nothing to do with my connection. This is a Bungie issue: http://www.bungie.net/en/Forum/Post/83558854/0/0
-
Edited by wickedwifey20: 12/9/2014 4:50:07 AMI can't even get on due to marionberry. I've restarted everything, did the port forwarding, and checked my connections. Everything is fine on my end. I can play all my other games just not destiny.
-
1 ReplyWiFi connection? Have you tried Ethernet?
-
I'm receiving error code "canary" despite the fact that my connection's perfectly fine and despite having an Open NAT. These issues truly spoil Destiny, even more so when you spend nearly £100 on the game at release and still experience similar problems. I, however, receive this error code every five to ten minutes for some reason and it really makes gameplay unpleasant and tedious as I spend more time resetting my game than I do playing it.
