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!
