Error Code List - Got an Error? Check Here!

#1 - Dec. 9, 2011, 3:14 a.m.

So I thought I'd make a little post with all the error codes and what we think they mean. Feel free to contribute and I'll edit original post!

SERVERS ARE DOWN RESOLUTION:

What to do: Be glad you have an invite to the Diablo 3 beta, go do something else, and come back and try again later. =D

YOUR GAME CLIENT DOESN'T YET REALIZE THE SERVERS ARE DOWN RESOLUTION:

What to do: Exit completely out of the game (alt F4 if you have to) and then attempt to log in. If you get a different error code, see that error code.

1

If you see this message when trying to log in, it means the servers are down. It's speculated that this error also seems to indicate the servers are about to come back up after being down, don't know this for sure, though. So feel free to try again in 3-5 minutes or less.

Because of error overlap, this error is also a miscellaneous default error for other things as well when you are in the game, such as errors in the friend invite system.

33

Servers are down for maintenance.

35

Servers are down.

37

Servers are up, however they have reached maximum capacity. http://us.battle.net/d3/en/forum/topic/3711332258

What to do: Keep trying to log in and maybe you'll get lucky.

1008

I seem to get this error whenever I try to inspect someone's profile either in a party or using the friends system.

3003

Servers are down.

3005

Happens when attempting to log in - This seems to be a message indicating your firewall may not be set correctly.

What to do: Check out this thread: http://us.battle.net/d3/en/forum/topic/3657444425

24000

Game client doesn't realize the servers are down. (Creating a game.)

24001

Game client doesn't realize the servers are down. (Joining a game or using Auction House.)

25016

Game client doesn't realize the servers are down. (Not in game or AH, such as stats or banner settings.)

300005

Game client doesn't realize the servers are down. (Character creation screen.)

300008

You've been disconnected.

What to do: Try to reconnect. If you get a different error message, see that code.

317000

Game client doesn't realize servers are down. (Actually in a game, but for some reason did not get a disconnect from battle.net message as usual. Can also happen if your internet cuts out while you're in a game.)

-- This error code needs more research.

34200

Servers are down.

315300

Incorrect username/password.

What to do: Retype your username and password. And get it right this time! =P If you know your username/password is correct but you consistently get this error more than 3 times in a row, contact Blizzard support.

317002

Servers are down.

395000

Servers are down.

~

Some other useful links:

Current Known Issues: http://us.battle.net/d3/en/forum/topic/3530363469

Blizz Tracker: http://us.battle.net/d3/en/forum/blizztracker/

How to Look for Similar Threads Before Posting: http://us.battle.net/d3/en/forum/topic/3657444979

~

If you like this thread, feel free to click 'like' or 'request sticky'! =D

Vasadan

Quality Assurance

#6 - Dec. 9, 2011, 3:33 a.m.

It would be better if Blizzard made this list.

For instance we had the 24000 error a while ago and it meant something totally different - it meant that our accounts were locked out of the game and thus we weren't allowd to make a game. It essentially locked us out for up to 2 weeks at a time.

Thanks for this suggestion, I'll definitely keep it in mine for D3 retail launch. The problem right now is that since it is still in production, Battle.net and D3 are using the same Error message for different things because these bugs *shouldn't* happen at launch.

However, once things are more set in stone, I will definitely try to compile a list :)

Nimda

#11 - Dec. 9, 2011, 3:54 a.m.

I just got a 300008. Request timed out. (just after I lost connection to the server.)