Diablo 3 beta – server busy error 37

Get a Diablo 3 guest pass now!

Note: Diablo 3 guest passes allow 30 days of free gameplay.



If you have just got the email announcing the open beta weekend, you’ll probably be pretty disappointed to download the beta client only to be hit repeatedly with error 37 – server is busy.

I just managed to log in and was hit with the next error – error 34200. My guess is the game servers are still down, although the login servers are up.

Anyway, Blizzard are promising that with new update (that required the server restart), the capacity of the server will be increased, so don’t dispair but try again!

I managed to kill the Skeleton King mere minutes before the servers went down, so I guess I was lucky to have “defeated the Diablo III beta“!

Update: Frankly, Blizzard have done a very poor job of this stress test. I don’t remember any such problems 10+ years ago when I participated in the Diablo 2 stress test. Now, I am getting error 33 – Battle.net is down for maintenance (servers are down). How many more servers can there be – between me and the beta?

I notice a strange correlation – the further you go INTO the beta, the longer the errors become. 33 is Battle.net, 37 is servers busy but once you pass the login, it goes to 34200 and I think I even saw 36000+ error.

Update 2: It seems that the server errors have disappeared, so definitely try to login again!


22 Responses to “Diablo 3 beta – server busy error 37”


  1. 1 spltprsona Apr 21st, 2012 at 1:44 pm

    “Frankly, Blizzard have done a very poor job of this stress test.”

    The whole point of the stress test is to test the server limits. Which means that there will be tons of issues with busy servers and maintenance so that the initial launch goes smoothly.

    “I don’t remember any such problems 10+ years ago when I participated in the Diablo 2 stress test.”

    If you look at the numbers, I’m sure you’ll see that the amount of people participating in the open stress test for D3 vs D2 is astronomically higher. More people have computers now then they did back then, and Diablo has earned far more renown since the game was released 10 years ago.

  2. 2 Diablo Apr 21st, 2012 at 3:39 pm

    @spltprsona Of course, the number of people in the D3 beta test is higher.

    How about the fact that Blizzard has grown from 300 people to over 7000 and that Activision-Blizzard is the BIGGEST game company by market capitalization?

    You are forgetting that Blizzard has more servers and system engineers than any other game company. After all, WoW has 10 million subscribers still.

    So they should’ve prepared better for this stress test. People are getting frustrated when they are waiting for hours on end. They should’ve implemented queues to create an orderly system of login and game creation. Now, you need to hit that login button every 5 minutes.

  3. 3 Simon Apr 21st, 2012 at 4:04 pm

    Please read about what stresstesting means and what it’s purpose is….

  4. 4 Kitty81 Apr 21st, 2012 at 4:41 pm

    What is frustrating, is knowing that the beta is only going for one weekend and spending the majority of that time staring at error pop-ups instead of actually getting to play the game. If there are this many issues to work out, I think that the beta should last at least a weekend. More play time means more feedback for them so that they can take care of more bugs before the release.

  5. 5 Kitty81 Apr 21st, 2012 at 4:41 pm

    A week*, sorry about that.

  6. 6 Joe Apr 21st, 2012 at 5:08 pm

    If people are getting THAT frustrated, they can just log off, uninstall the beta client and wait for the release. That’s the whole point of this part is to work out the buts that they knew were inevitable. You’re NOT paying to beta test it, so if it’s stressing you out, just don’t participate, simple as that.

  7. 7 Punkistu Apr 21st, 2012 at 5:13 pm

    Ahh…. :(

  8. 8 Luke Apr 21st, 2012 at 5:16 pm

    Frankly, this article contains far too much whining.

  9. 9 RandomStranger Apr 21st, 2012 at 5:29 pm

    Here’s the thing. They could have setup up more than enough servers to make sure it was completely smooth. Except that would give them zero information.

    What is more likely is that they had enough servers online to be stressed but hopefully cope. That way any lurking errors would be more likely to pop up without triggering expected errors from pure overload.

    Then take into consideration that some of those servers will fail and problems arise (granted this would be an expected issue hence why it doesn’t take too long to swap servers).

    Finally, (or rather to reiterate) they want these issues to occur, they want us to hammer away at the gate because putting a queue there would serve as a solution to the symptom not the problem. If we keep hammering away to get in, it will continue to stress the system and it will continue to reveal errors to blizzard.

    The idea is not for us to have a perfect experience today, its to have (hopefully) a chance to play the game a bit but more so its so that launch day can be perfect.

    I hate to use this argument since I normally despise it, but you did not pay for beta access, you were allowed it, and its a test not a free play.

  10. 10 JUSTGOTIT Apr 21st, 2012 at 11:52 pm

    i just get the download, and started to play. the servers are now down, any idea how long?

  11. 11 gay Apr 22nd, 2012 at 12:42 am

    its soooo GAY

  12. 12 Ixoth Apr 22nd, 2012 at 12:55 am

    I find it rather strange that if you had selected the region to be europe it was almost guaranteed fact you are not able to login. However if you chose region to be US then most likely you were able to login – at least I was during the time of start’ish of the event on friday till to saturday afternoon (my time, gmt+2). After that I was only able to login very few times.

    So reiterate how come the US servers were most of the time online or available if you will and europe server was most of time unavailable? one would think it might be the other way around.

    Anyways, what randomstranger wrote makes sense and I aint complaining I was able to make 3 different toons of different classes, which all defeated skeleton king several times. I was able to get a glimpse whats the game like – I was never invited to closed beta even though I have two battle.net accounts and both of em are been updated/set up so in the account management, what it comes to computer specs and that I’m interested in beta testing diablo 3.

  13. 13 Diablo Apr 22nd, 2012 at 3:54 am

    SERVERS ARE UP! At least in the US, where I play (although I am in the EU, I get error 3003).

    So try again if you get a server busy error. And definitely try multiplayer (public games), once you beat Skeleton King on your own.

  14. 14 Michael M Apr 22nd, 2012 at 8:12 am

    Yeah, I’m actually removing this site from my mailing list. It’s a joke, the opinions on here contain so much personal whining it’s dumb. If you really new about servers and such you’d know that when you have a couple 10,000+ people you are going to run into different problems all the time that need solving. A stress test is also supposed to “stress” the server, it’s not really meant to be played in all honesty. Yes Blizzard is a huge company, but that doesn’t mean that since a stress test didn’t go perfectly, that it was poorly executed. Out of all the stress tests I’ve been in they’ve all been about the same. So you and your reviews seem like a joke to me now.

  15. 15 lavce Apr 22nd, 2012 at 8:48 am

    I managed to get in and play the game after trying repeatedly to log in. You still get error happening even in the game as the game can suddenly disconnect you from play. Overall I liked the game cant wait for the full version. Demon hunter is cool and the monk is crazy any martial artist would love to use him.

  1. 1 Diablo 3 launches with Error 37 Pingback on May 15th, 2012 at 3:58 am
  2. 2 Diablo 3 error 75 Pingback on May 15th, 2012 at 3:25 pm
  3. 3 Diablo 3 launcher problems fix (play button inactive) Pingback on May 15th, 2012 at 3:48 pm
  4. 4 Diablo 3 error 33 – server maintenance Pingback on May 20th, 2012 at 11:58 am
  5. 5 Diablo 3 Error 1 Pingback on May 31st, 2012 at 7:41 pm
  6. 6 Diablo 3 game design blunders « Riftstalker Pingback on Jun 13th, 2012 at 4:47 am
  7. 7 Diablo 3 best gamer – Athene Pingback on Jul 5th, 2012 at 3:53 am

Leave a Reply




Get Diablo 3 guest pass!

Note: Your guest pass gives you 30 days of free Diablo 3 play!


  

Get Diablo News

Enter your email address:




Subscribe via RSS

Vote on the Diablo 3 Top 200
Diablo 3 Top 200 - Diablo 3 Items, Gold, Maps, Quests, Guilds, Guides, Hacks, Cheats

BlogRanks

BlogRankers.com game, diablo, blizzard, diablo 3, release date, characters, beta game, diablo, blizzard, diablo 3, release date, characters, beta