You're browsing the GameFAQs Message Boards as a guest. Sign Up for free (or Log In if you already have an account) to be able to post messages, change how messages are displayed, and view media in posts.
  1. Boards
  2. Destiny
  3. All Error Codes and How to Fix

User Info: mitchellfoxx

mitchellfoxx
4 years ago#1
So, with the release of Destiny I figured that people would be getting these error codes at one point or another. And, instead of having to search them up on Destiny's website, I figured that I would make a thread for you guys to simply browse through when you see one of these error codes pop up on your screen.

Centipede- Probably one of the most common errors that seems to be happening amongst college campuses. Simply put, it's a network issue. There is currently no fix for the college people, however if you're at home and get the error, head to the link below to see if you can fix the solution.

http://www.bungie.net/en/Help/Article/11930

Pear- This is simply an Xbox One party issue that can happen from time to time. Simply restart your console then launch Destiny to see if that fixes the issue.

Urchin- Urchin only pops up when you have had a restriction placed on your account due to modding or other purposes. Try choosing a different activity, or visit this page here and see if you can't fix your issue. If all else fails, call them.

Cat- The simplest error to fix out of all of them. There's an update that you missed somewhere along the lines. Restart your console, reboot the game and try downloading the update again.

Marionberry- This is another error that is usually associated with your network connection. It often occurs after a WiFi "blip" or when you have changed your network settings. Simply visit this link here and follow the instructions given to fix it.

Blackbird/Chipmunk/Lime- All three of these errors are caused by the same problem. For those of you that are getting this, you will have to delete Destiny altogether from your Hard Drive and re-install it. Another vital option that has proved useful is simply deleting the game data then restarting Destiny. If that doesn't fix it, you'll probably have to contact Sony or Microsoft for further support.

Buck/Camel/Cattle- Again, all three of these errors are caused by the same problem. If you accidentally got kicked off of XBL or PSN and had your account signed out, you'll probably see this issue. Simply just sign back in and you should be good to go. If all else fails, exit the game and restart it.

Butterfly/Stingray- These occur when you have attempted to play Destiny while not signed in to XBL or PSN. Simply sign in and the error should go away. If you're unable to connect, it's either your connection or something on XBL/PSN's end. I'd check up from time to time to see if the servers are down for XBL/PSN, which you can do with the URLs below:

http://support.xbox.com/en-US/xbox-live-status

https://support.us.playstation.com/app/answers/detail/a_id/237/~/psn-status%3A-online
XBox 360 GT: FirebornWarlock
(edited 4 years ago)

User Info: mitchellfoxx

mitchellfoxx
4 years ago#2
Chicken/Chimpanzee- There is currently no explanation for these nor is there a solution for this. So, you're only option here is to post on the support forums of Bungie, which can be found in the link below:

http://www.bungie.net/en/Forum/Topics/0/Default/None/Help

Buzzard/Vulture- This error is rather well known, as it was highly present in the Beta when it was released. It's simple: No Gold, no play.

Bull- If you accidentally sign out while mid-game, you will see this pop up. You will need to exit Destiny and re-launch it as either the new user that just signed in or the previous user that just signed out.

Caribou- Ahh, those blasted parental controls. If this error pops up, your parental controls on your Xbox is blocking some features of Destiny from working properly. Simply turn them off in your Xbox settings and you should be good to go (that is, if you can figure out the pass code your parents set :wink:)

Beagle- This is another error that is caused with the game, except this is for the digital users only. If you get this, it simply means that you will need to delete the game and re-install it again (There's no work around on this one, sorry folks.)

Penguin- Luckily, this is only a PS4 problem at the moment, so you don't have to worry about seeing it if you don't own the console. It is associated with the parental controls restricting access to voice chat or messages. In order to fix this, you will need to change your settings to allow you to talk in game and send messages. For those of you who don't know how, visit this page:

https://support.us.playstation.com/app/answers/detail/a_id/5097

Pelican- If you happen to come across this error, you actually shouldn't (if that makes any sense). It is a problem with the User Generated Content, which you do not have access to. When you do happen to come face to face with this, simply make a thread in the Destiny help forums section and see if anybody that has had a similar issue can help you. Alternatively, it can also be caused by parental controls being set. Simply try turning them off and see if that fixes it.

Carp- If you've been away for a certain period of time (Only applies to Xbox One and PS4 Gamers) and you got kicked back to the home screen, simply log-out and log back in and you should be good to go.

Catfish- Simply accept the User License agreement and that should fix it.

Pineapple- Another networking error that is either on your part or Bungie's. If it does happen, it will get reported to Bungie immediately. Simply restart your Xbox and see if that does the trick.

Leopard- This is an issue on Bungies end and doesn't have a workaround ATM. Try resetting your console and see if that helps.

Turtle- Network issue that can be fixed by changing your ports to these:

Destiny Port Range Direction
7500-17899 (TCP) Outbound
30000-40399 (TCP) Outbound
35000-35099 (UDP) Inbound and Outbound
3074 (UDP) Inbound and Outbound
XBox 360 GT: FirebornWarlock
(edited 4 years ago)

User Info: mitchellfoxx

mitchellfoxx
4 years ago#3
Anteater/Viper- Both are common networking issues (there seems to be a lot of these) that can be fixed probably by turning your Xbox off and back on again. If that doesn't work, you can always try the Networking Troubleshooting page that I have listed above to see if that solves your problem. Or check out:

http://www.bungie.net/en/Help/Article/11930

Monkey- You will probably only get this when Bungie is doing work on their end, but it could also happen randomly too. Simply resume what you were doing and everything should be fine from there. If you are still having this problem, make a thread on their support forums with the link I have provided above.

Bee/Fly/Lion- Caused by disconnects between your router and Bungie's servers. It can also be caused by certain WIFI setups or faulty in-home wiring, as well as other devices such as your phone or tablet being on the WIFI the same time you are trying to play Destiny. There have been several tests done regarding this issue, and it seems they come and go. I would highly recommend reading the spoiler below for more information on this:

**During investigation, Bungie has seen users hitting these errors in geographic clusters in different places at different times. For example, we recently detected 25% packet loss from the UK at the same time a number of users located there saw errors. These Internet conditions usually pass quickly, and the errors often go away on their own when this happens.

If you have performed all of the troubleshooting steps called out above and are still hitting these errors, you may not be able to resolve this issue by changing your home network configuration. Bungie is carefully monitoring BEE, FLY, and LION issues preventing players from having a quality Destiny experience, and we are working very hard to investigate and address these issues. You can read about our ongoing progress below. Making this experience better for everybody is a top priority at Bungie.

Recent updates on our investigations for users hitting repeated BEE/FLY/LION errors:
[9/30] Our server-side configuration changes have shown a dramatic reduction in BEE/FLY/LION errors. Error reporting data shows a drop of 53% since our last update on the 25th. We are still exploring other methods of reducing the frequency of these errors.
[9/26] No major updates on our BEE/FLY/LION investigation, but we are continuing to work towards reducing how often players hit these errors.
[9/21] We made a configuration change today that reduced the number of BEE/FLY/LION errors by 50%. If you were hitting BEE/FLY/LION errors that made it hard to enjoy the game, please try again as your situation may have improved. We understand people are still hitting these issues so we will continue to work hard on this top priority issue to do whatever we can to improve the player experience.**

Also, I've noticed something else that's been happening, getting randomly disconnected from XBL. If this does happen, there's multiple ways you can possibly fix this, such as doing a quick reset on your console or clearing your system cache. If that doesn't work, try starting up Destiny disconnected from XBL and signing in once you're on the home screen.

Currently working on the thread and will continue to update as more errors are found. If you have one that I have not listed, please share it so I can add it to this thread!

Source: Tried to get an exact link, but all links seemed broken, or moved to a page that's not viewable. So cred goes out to original poster.
XBox 360 GT: FirebornWarlock
(edited 4 years ago)

User Info: IWU

IWU
4 years ago#4
Sticky requested! Good job
Irregardless, for all intensive purposes I could care less if you take me for granite. If given free reign, I'll continue to tow the line so it's a mute point.

User Info: mitchellfoxx

mitchellfoxx
4 years ago#5
IWU posted...
Sticky requested! Good job


Thank you! :)
XBox 360 GT: FirebornWarlock

User Info: rvnender

rvnender
4 years ago#6
sticky requested.
"Not everybody has tube TVs without input lag. Tube TVs now banned online" -Maverick_McCain in reply to why turbo is frowned upon

User Info: toxicxcookie

toxicxcookie
4 years ago#7
What about hawk?
GT: TOXICxCOOKIE
add me for Raids

User Info: mitchellfoxx

mitchellfoxx
4 years ago#8
rvnender posted...
sticky requested.


Thank you!

toxicxcookie posted...
What about hawk?


I'm getting these put out as fast as I can find the solutions to them. If anyone happens to find it first, post it here and I will add it to the main post.
XBox 360 GT: FirebornWarlock

User Info: rvnender

rvnender
4 years ago#9
Who ever the mods are for this board need to get on the ball. This was the second topic that was really helpful and still no sticky.

The Ps4 board has like 3 stickies.
"Not everybody has tube TVs without input lag. Tube TVs now banned online" -Maverick_McCain in reply to why turbo is frowned upon

User Info: JiZjAz

JiZjAz
4 years ago#10
Sticky requested!

Thanks for the info.
[I broke the dam at the request of a moderator or administrator]
  1. Boards
  2. Destiny
  3. All Error Codes and How to Fix