My friends game crashed every 30 min and now he can’t start the game because “Game servers are unavailable ERROR CODE: 34202”. Anyone got a fix for this?
2 Likes
Me too. It’s been like an hour…
I woke up like three hours before I had too. I’m hoping I at least get to make a character.
I have the same issues as well. Was playing, got DC’d, now Code 34202 when trying to log back in. I’ve scanned/repaired the files in the launcher, flushed DNS, release/renew, and reset PC and modem… nothing worked.
Anyone figure anything out yet?
My friend tried all the things you did aswell still no fix.
Your client may still be out of date, even though it reports as being up to date in bnet. I just saw my client was still at 1.0.2.41917 on the splash screen, even though bnet is reporting it as 1.0.2.42016. Recent patch must have screwed it up and not applied. However bnet won’t repair the files if it thinks the client is up to date! I’m going to try to get around this with some fiddling. Full re-install might do the trick but who has time.
You may want to selectively delete data blocks to force a repair, if that continues to fail there will be a manifest somewhere that should be able to be forced back to the real client version. Anyway this will be a byproduct of the patch today, so hopefully the next patch will resolve this as the client will get forced up to the latest versions
He tried full re-install 3 times now and still dont work so I don’t think that is the problem 
what does his splash screen client version say?
My versions say the same. I guess bliz could have forgot to update it in game. I’m trying a full reinstall now. Will let you know when it’s done.
Same as battle.net version 1.0.2.42016
Damn sorry to hear that man. I just deleted some data block files and did a scan and repair and it changed the runtime version back to 1.0.2.42016. Not to get too far into doing someone else’s job, but could you check the FenrisDebug.txt file in your install dir for a line with ProcessClientRequest RPC failed? That will have more info
I had same issue. Splash ver was different to client ver. I modified install to remove the high-resolution asset and now im in.
A full uninstall (I also uninstalled server slam), then reinstall worked for me. I’m back in. It now has 42016 in game and launcher.
He got into the game now after the third re-install. Lets see how long it lasts.
Logged into the game about 5 hours ago, created a char, got to the first village and stopped there. Took my laptop with me to play on the go and have been sitting with this error for the past 3,5 hours. Good old Blizzard launches are back. Guess they didn’t expect people to actually play the game during EA.
I wonder if we will have a bigger laugh when the game goes live for the rest of the players on June 6 and servers won’t work at all.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.