Tag Archives: Error 37

Clearly Diablo III is not Out of the Woods Yet…

I actually got home, had dinner, and was able to log into Diablo III on the first try ever.

Blizzard had the servers down for emergency maintenance earlier in the day, and it appeared to have done some good.  I was able to make my first character, play for a few hours, and form my early impressions of the game.  Those I will cover in another post.

Then after hitting a stopping point, I decided to log out of the game and then try to log back in, just to see how things were holding up deep into the prime time of game play.

That did not go so well.  I did not get error 37, the error that actually trended on Twitter, but another error.  Error 75.

A new error for a new day

I thought to myself how silly it was to log out when things were going smoothly.  But then I heard from a couple of other people that they had been kicked from the game with the same error.  And then Blizzard started announcing that there was a problem on Twitter as well as on the game login screen.

So the peak of prime time, when both coasts in the Americas were heavily invested in the game, seemed to push the system over again.  I went to the forums, to see if just once there might be some more information there, but things seemed to be going badly for the forums as well.

No forums, go check Twitter please

This was the outage that took down World of Warcraft as well as all StarCraft II online play.  The influence of Diablo is vast!

Well, we we are still less than 24 hours from the go-live point, and I have had as much trouble or more playing stand-alone games on launch day in the past.  But these are issues on Blizzard’s side of the fence, and I hope they get them straightened out muy pronto.

I give it until the weekend before somebody starts seriously talking class action lawsuit.

And Then I Missed Out on the Error 37 Party

Diablo III launch day!

However, I wasn’t going to stay up until midnight to play.  I am too old for that sort of thing.  But it sounds like I missed a shared experience.  When I checked Twitter this morning, Error 37 seemed to be the topic of the day.

One theory…

Blizzard’s response is to… well… hang in there and keep trying.

Error 37
We’re aware that some players are experiencing Error 37 when attempting to log in to Diablo III. This error indicates that the Diablo III server is full and is likely the result of high login traffic. If you receive this error message, please wait and try again.

Error 3005 and 3006
Along with Error 37, we’re also aware of players receiving Error 3005 and Error 3006. If you receive either of these messages while playing, please wait and try again.

Error 14009/315300
We’re still looking into these issues; however, a player workaround is available. If you are experiencing either of these issues and are using Windows, create a new user account with administration powers (http://www.wintuts.com/Manage-User-Accounts). From there, log into Diablo III.

Character Creation Issues
While most of the character creation issues have been resolved, it’s possible that if you attempted to create characters previously and did not log out, you may have actually maxed out your character list. If you are still receiving an error creating new characters, log out and log back in and then check your character list.

Hopefully all this will be cleared up by the time I am able to try logging in tonight.

If nothing else, this sure seems to be a sign of sales success.

Overwhelmed by success…

I just still wish that they had not ditched offline and LAN play.

And it seems that not everybody is getting error 37.