Beta 6 Error code=24000 anytime I hit start game

RedAlert,

Please post your D3Debug.txt file (found in your main Diablo III Beta folder) on pastebin.com. Don't forget to remove your e-mail address.

Once it is posted, link the pastebin link here.

Hello everyone,

Thank you for your continued patience with this issue. We added additional logging to the game between Beta 5 and Beta 6 to help isolate this issue, so your logs are even more valuable than they were last time. The Battle.net team believes they have a fix for the bug, but we didn't want to push a bad fix to Beta 6.

A server restart will fix temporarily fix this issue for everyone, but I do not know when the next one will be. Thank you again for your patience.

11/23/2011 11:54 AMPosted by Cujo

With abosultely no communication from Blizzard about this situation for over a week now

My response was posted two days ago in this thread.

Hello everyone,

Thank you for your continued patience with this issue. We added additional logging to the game between Beta 5 and Beta 6 to help isolate this issue, so your logs are even more valuable than they were last time. The Battle.net team believes they have a fix for the bug, but we didn't want to push a bad fix to Beta 6.

A server restart will fix temporarily fix this issue for everyone, but I do not know when the next one will be. Thank you again for your patience.

I'm very sorry your accounts are locked, but this is part of any Beta process, especially one with brand new servers and online environments.

Hey guys,

Our servers were restarted this morning because of a server crash, so all of your accounts should be working now.

Because this was an unintentional restart, I do not know if the bug is fixed yet or not because the servers weren't restarted to fix this bug.

However, I still encourage you all to keep playing, use the Auction House, and test away. These are not your final retail accounts, so having them locked from this bug helped us debug issues now instead of later :)

We have enough logs to know what the issue is, thank you though. If this happens again, it's because we haven't pushed a fix yet.

Like I said above, we were planning on restarting the servers when we had a fix, but since this was accidental, I am out of the loop as well :(

It looks like this has not been fixed yet (as I predicted earlier this morning).

For now, I would say do not use Public Games.

My message was for people who can still play, I'm sorry if that wasn't clear.

With the server restart, everyone who has experienced these errors should have their accounts unlocked. I do not have word yet if the error has been officially fixed.

If the error is not fixed, we will make a new thread about it. Thank you all.