Wednesday, 6 September 2017

Destiny 2 error codes: an updating list of issues and how to deal with them

We’ll be updating this as Destiny 2 error codes roll out or affect players.

Destiny 2 seems to be pretty stable on consoles, but release has not been entirely smooth. Check back with this page for regular updates on Destiny 2 error codes, plus solutions and workarounds when we find them.

The error codes and reported issues below are arranged in reverse chronological order by update statues, so you should always find the latest news on Destiny 2 error codes at the top of the page – and get an idea of how long your particular bugbear has gone unactioned, if you don’t have enough reasons to blow a gasket today.

destiny_2_emb_strike_the_arms_dealer_3

PS4 online permissions

Bungie is currently investigating an issue in which PlayStation users are unable to access some parts of Destiny 2 due to a multiplayer permissions change. The error message reads:

“You have lost connection to the Destiny 2 servers. Your permissions to access online content may have changed or your profile may have been signed in elsewhere.”

Resetting your console, signing in and out of the PlayStation Network and changing your password may help here.

PS4 crashes

Some PS4 players are reporting crashes in Destiny 2. We haven’t seen this ourselves despite having the console and game client running for 4 hours or longer at a stretch, but others have been unable to progress through the story as a result. Bungie is investigating.

Cabbage error code

Destiny 2 players are enjoying healthy fibre and vitamins as they experience the Cabbage error code. Judging from posts on Bungie’s forums, the issue seems to mostly effect players using Technicolor modems.

Right now, the exact solution isn’t clear, but Bungie is investigating.

ce-34878-0 error code (PS4)

Several Destiny 2 players are also reporting a ce-34878-0 error code on PlayStation 4 Pro consoles, which is a Sony-specific code. The process for dealing with this code is as follows:

  • Close the application, install the latest System Software and game updates and restart the system.
  • If you have upgraded the Hard Disk Drive (“HDD”) in your system, please re-install the original HDD.
  • If the error occurs again, back up your saved data, and then go to [Settings] > [Initialization] and choose [Initialize PS4].
  • If the error occurs with every application, or as soon as the application starts, please contact PlayStation Support.

Destiny 2 servers at capacity

This may be an issue for some during launch period, as Destiny 2 is going to be popular. Server queues are designed to regulate the Destiny experience and to make sure that stability can be assured. The Bungie Help page notes that:

  • If a player loses connection or is removed from the queue, their placement will not be retained
  • If a player reaches the front of this queue and is unable to connect to Destiny servers, they will have to re-enter the queue to try again
  • Queue times may vary, depending on server traffic and concurrent population

We’ll be updating with workarounds, solutions, and comments from Bungie as they come in, so bookmark this page if you want to stay on top of Destiny’s various error codes post-launch.


Destiny 2 error codes: an updating list of issues and how to deal with them posted first on http://ift.tt/2k0LiGW

No comments:

Post a Comment