Here is a list of known errors and bugs for the Diablo III release version including login issues, and how to fix (bypass) them. Diablo III release Error number: 12, 37, 315300, 3005/3003, 3006, 300008, 3004. Basically for Europe players, change to US region in your battle.net account and u will get this error and maybe with luck you can get into the game. Remember its a stress test, to stress the servers, so there is no guarantee of gameplay.

The Diablo 3 release has begun and we’ve been extremely successful in that we’ve already managed to break a few things. Here is some works around for stability and service issues, and until it’s resolved you will likely see an Error 37 when attempting to log in.

  •  This is an error we’re still investigating, but should only be appearing for Korean accounts which are not able to participate in the release. If you do not have a Korean account, we’re still investigating this issue but suspect it may simply be due to the Battle.net Account services being slammed by the high volume of traffic or a communication issue between the game and account services. (account doesn’t have Diablo III attached to it.)
  • Bashiok: Cool! Error 12 is fixed by changing your password. If you’re seeing Error 37 it just means the servers are full right now. Keep trying! Make sure to choice US region also, and update your battleTag / RealID.
  • Error 31500 – (account name or password incorrect)
  • Error 315300 – Your account name or password are incorrect. Please try again. (ERROR_315300)
  • Possible Fix – changing email and/or password several times on battle.net
    – try to login with totaly wrong email/pw
    – delete the “Battle.net” and/or “Blizzard Entertainment” folder
    – granting full permission for the “Blizzard Enterteinment” folder to my account
  • There is a fix for these errors 3003 & 3005 by changing region to USA.
  • Error 3003 – Click Options, under Account change your region to The Americas. The open beta is only being held on US hardware (Us Servers)
  • Error 3005 – Player has been disconnected (Error 3005) (Europe servers)
  • All these errors are in same family Error 33, 35 & 37 and mainly to server is busy, means the server is full. There is no fix, keep trying to login, is the only fix here.
  • Error 33 – Battle.net maintenance
  • Error 35 – Please try again later. Server busy.
  • Error 37 – The servers are busy right now. Please try again later. (Error 37)
  • Error 75 – When changing to US region in battle.net Try again.
  • Error 307-  The servers are busy at this time, please try again later (error 307)
  • Mostly crash issues, fixes: try to login again.
  • Error 24000 – Character cannot be created. Issues with character creation.
  • Error 82 – The client does not match the account’s native language. Please use the game’s original client. (Error_82)”.Russia Only)
  • Error 316921 – this player does not have valid diablo III profile.
  • ERROR 317002 – Ingame specific error client crash on kill.
  • Error 24100 (The game servers are currently busy. Please try again later) 
  • These errors are in game specific after you logged into battle.net account and server but cannot get into ingame. Keep trying to login is the only fix currently.
  • Error 3006 Connection time out. Game creation Issue. Try again.
  • Error 300008 Connection Timeout while creating a new game. (Cannot Start Game)
  • Error 3004 – Creating a game or join game error 3004. No quest available in level range.
  • Error BLZAPPBTS00002 cannot connect to patching service.
  • Gray login button – You need to use your Battle.net email address as your account name. Your BattleTag is a nickname, not your account name.

source <http://bit.ly/JeXNd0>

Advertisements