WoW #114 Error

Technical Support
Prev 1 8 9 10 Next


Hmm i got it working.I changed both my IP4 and IP6IPV4- 8.8.8.8/4.4.4.4IPV6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844Then went into CMD and ran a release/renew and a dns flush..Press windows "R" and then type in "cmd" in the run.exe boxIn the command prompt type in the belowipconfig /releaseipconfig /renewipconfig /flushdnstry wow now.. worked for me

Yivarn:

Thankyou so much Letthiswork!I followed your instructions exactly and in addition deleted:C:\ProgramData\Battle.netC:\ProgramData\Battle.netBlizzard EntertainmentIt then had a bit of a think about it and finally asked me for my authenticator upon login instead of #114!@ rejecting me.



Thankyou both Yivarn and who ever you quoted off, FIXED MY PROBLEM STRAIGHT UP, am now logged in on my desktop.

Thankyou so much!!!
After reinstalling windows 7 on a different hard drive and copying wow over from another hard drive, I have been getting the WoW @114 Error message every time I try to log in.
I managed to temporarily fix this issue by deleting my WTF and Interface folders, but it is still happening on occasion, and I am limited by some of the things I can do, such as switch to 32 bit client or modify my addons.
I have already tried running wow as admin, I have tried the repair tool, I have tried deleting the battle.net cache folder.

ISP - Telstra
Location - Sydney, Australia
Realm - Barthilas
Traceroute -

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 172.16.0.1
2 10 ms 5 ms 9 ms 10.240.192.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15
Provider: Slingshot
Country: NZ palmerston north
Server: 63.240.104.93

Tracing route to domain.com [65.254.244.180]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms RTA1025W.home [192.168.1.1]
2 19 ms 18 ms 19 ms 202.180.81.30
3 19 ms 18 ms 19 ms p85.pool-82.callplus.net.nz [202.180.82.85]
4 69 ms 18 ms 18 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 43 ms 55 ms 47 ms x7-1-0-101.akbr5.global-gateway.net.nz [202.50.2
34.61]
6 46 ms 43 ms 43 ms xe3-1-0.tkbr9.global-gateway.net.nz [202.50.232.
74]
7 186 ms 184 ms 180 ms ae2-3.labr5.global-gateway.net.nz [203.96.120.14
2]
8 178 ms 176 ms 177 ms ae1-3.labr5.global-gateway.net.nz [203.96.120.93
]
9 176 ms 171 ms 174 ms ae0-3.lebr6.global-gateway.net.nz [203.96.120.86
]
10 157 ms 154 ms 153 ms 205.158.79.141.ptr.us.xo.net [205.158.79.141]
11 605 ms 399 ms 508 ms 207.88.14.217.ptr.us.xo.net [207.88.14.217]
12 257 ms 251 ms 253 ms te0-5-4-0.rar3.denver-co.us.xo.net [207.88.12.85
]
13 225 ms 226 ms 223 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21
]
14 251 ms 248 ms 249 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]

15 272 ms 501 ms 259 ms 216.156.7.22.ptr.us.xo.net [216.156.7.22]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
srsly still haven the problem idone all wat it says to do and nufthings workon wtf this is bull!@#$
Hi there,

I am experiencing the same issue #114. I accepted a scroll of res from a friend last week and have been trying everything to work around this. I really want to be able to use that free game time to check out the new stuff!!

I gave up using my own computer and tried on my sister's because she has been playing wow just fine (on a paid time card, not 7day free). When I tried to log in on her computer I got the same error, so obviously not a network problem. She was able to log back in and kept playing moments later.
EDIT: We tried all most all of the fixes on her pc too (delete cache for example) and I could still not log in, but she could.

ISP - Internode
Location - Tasmania, Australia
Realm/s - Silver Hand
Trace:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 2 ms 2 ms 192.168.1.254
2 25 ms 26 ms 25 ms loop0.lns20.hba1.internode.on.net [203.33.255.118]
3 24 ms 24 ms 25 ms gi0-0-5.cor1.hba1.internode.on.net [203.33.255.9]
4 203 ms 203 ms 202 ms gi0-2-805.bdr1.mel6.internode.on.net [203.33.255.169]
5 202 ms 203 ms 202 ms te2-0-0.bdr1.cbr1.internode.on.net [150.101.160.173]
6 202 ms 203 ms 203 ms xe-0-0-1.br1.syd4.on.ii.net [150.101.160.170]
7 48 ms 47 ms 75 ms xe-2-0-2.br1.syd7.on.ii.net [150.101.197.5]
8 203 ms 203 ms 203 ms te0-2-0-3.br2.sjc2.on.ii.net [203.16.213.158]
9 203 ms 203 ms 203 ms xe-0-0-0-5.r07.snjsca04.us.bb.gin.ntt.net [129.250.11.97]
10 209 ms 208 ms 206 ms

Can I get another scroll of res? I accepted this one but I haven't been able to play because of this error :(
Follow the instructions on this forum, fixed everything for me.
http://us.battle.net/wow/en/forum/topic/7709861874
Everyone, if you have downloaded wow recently this is the reason to your problems. The only people that are getting the 114 are the ones who recently downloaded it including me.
So... yeah... A friend convinced me to rejoin, I played perfectly fine at his place and now I can't on mine? Even bought a few months of gametime so I could log back in (was two days off the requirements for a Scroll).

Blizzard, This is not an ISP problem; this is a coding problem. Admit it and fix it. YOU screwed it up, so it's in YOUR power to solve it. Just because those affected aren't in the States doesn't mean we're any less important.
Beige,you are spot on,Recently downloaded too after my friend gave me a scroll of res,Didnt even get to use one god forsaken day of it due to this fault.
All they keep saying is its an ISP issue when it clearly isnt,all the people having the issue are reporting the same lead up to error 114.
Of course they wont care cause its a handful of people in australia
01/28/2013 10:53 PMPosted by Asgood
Everyone, if you have downloaded wow recently this is the reason to your problems. The only people that are getting the 114 are the ones who recently downloaded it including me.


Untrue. I have not recently downloaded WoW, I've used the same copy I've had since Mists was released.

01/28/2013 11:43 PMPosted by Beige
This is not an ISP problem; this is a coding problem.


There's no logical reason why Blizzard would purposely leave hundreds of players with no fix, unable to play, effectively losing themselves money. That would be an idiotic business move, don't you agree?

When I tried to log in on her computer I got the same error, so obviously not a network problem. She was able to log back in and kept playing moments later.
EDIT: We tried all most all of the fixes on her pc too (delete cache for example) and I could still not log in, but she could.


Did you try copying her Battle.net & Blizzard entertainment folders to your computer? Or the DNS change/flush?
01/25/2013 03:59 AMPosted by Chokwedge
12 223 ms 228 ms 222 ms 192.205.37.145


I would be checking that part of the trace out. Try a lookup on the IP and then find the reams of threads on latency.


i looked it up and it's AT&T servers. so it's getting stuck there.

edit: i tried logging in with my other account and same issuse, 114 error.



What DID work:
- Went to a computer that did work and could log in to wow
- Go to C:\ProgramData on a computer that could log in fine (this is a hidden folder so you may need to type it manually to get there)
- Copied "Battle.net" and "Blizzard Entertainment" to a USB Key
- Went to C:\ProgramData on my computer that previously didn't work
- Deleted the existing "Battle.net" and "Blizzard Entertainment" folders
- Copied "Battle.net" and "Blizzard Entertainment" from the USB key in to the C:\ProgramData
- Run WoW Launcher and I could now log in.

I hope this helps others - assuming you can get hold of working version of those folders


can't do that. mine is the only comp with WoW on it.

01/28/2013 11:43 PMPosted by Beige
Blizzard, This is not an ISP problem; this is a coding problem. Admit it and fix it. YOU screwed it up, so it's in YOUR power to solve it. Just because those affected aren't in the States doesn't mean we're any less important.


01/28/2013 10:53 PMPosted by Asgood
Everyone, if you have downloaded wow recently this is the reason to your problems. The only people that are getting the 114 are the ones who recently downloaded it including me.


since the latest patch this has been happening. last time i played back in September it was working fine. so it's this patch that has screwed things up.

Beige,you are spot on,Recently downloaded too after my friend gave me a scroll of res,Didnt even get to use one god forsaken day of it due to this fault.
All they keep saying is its an ISP issue when it clearly isnt,all the people having the issue are reporting the same lead up to error 114.
Of course they wont care cause its a handful of people in australia


maybe they'll take notice when they're profits drop.

if this isn't fixed by the weekend i think a lot of oceanic players will quit for good. we are sick of being treated as second class citizens.
I think I'm unique in that I tried the DNS fixes and they worked allowing me to log in, but now the game disconnects me after 30 sec or so of being in game. Just today I activated a Scroll of Resurrection and tried to play. Pretty unfortunate as I doubt I'll buy any game time having experienced this.

I've tried all the workaround options and none seem to get rid of the disconnects/crashes. Maybe this will be resolved sometime soon.
01/30/2013 05:14 AMPosted by Vesuvan
I think I'm unique in that I tried the DNS fixes and they worked allowing me to log in, but now the game disconnects me after 30 sec or so of being in game.
\

Since no one else has reported having this issue, I think it's safe to assume it's unrelated to the error 114 problem. You might want to consider making your own thread and explaining in detail, along with posting a dxdiag.
Well, I originally had the #114 error and I'm currently abroad in Taiwan. Blizzard's first response was to try the Google DNS fix (which worked), but now I'm getting the disconnects/crashes after about 30 seconds of gameplay. I'm pursuing this with a reopened ticket so we'll see.
Update:

Our network admins, along with our backbone server network admins have looked into this issue, and it doesn't look like anything on our end is causing this. You guys will want to contact your ISP to have them look into this issue further.
______________________________________________________
I'm available Monday through Friday from 11AM to 8PM Pacific Time
[url="https://us.battle.net/support/en/article/contact"]Support Contact Information[/url]


This is just not true. I have ruled out absolutely everything on my end, up to and including totally abusing my computer's warranty to have a tech support guy come out and look at it from that end, and paying to have guys from Telstra come out and check the lines in person. None of them found any problems, neither did my ISP in any checks they made from their end which I have had them do multiple times. I am having zero problems with anything online or with my computer generally except accessing the wow servers, which I have been unable to do for two weeks now.

I have tried:
- reinstalling windows.
- redownloading and reinstalling wow
- three different computers
- two different ISPs (TPG home and Vodaphone wireless)
- three different modems
- updating every single possible driver
- running the game as an admin
- running the game in compatibility mode
- running the game with the 32 bit client
- deleting the cache
- disabling firewall and other security that might impede a connection
- a near endless amount of restarting, checking internet connections etc.
- all of the suggested workarounds on threads linked in this post.
- Everything suggested in the Error 114 support page
- having a computer repair guy come out and check there were no issues with my main computer.
- having repair guys come out and check my physical lines.
- a whole bunch of tests conducted by my main ISP, including having them run the same tests several times.
- tickets, which have been unable to do anything other than suggest I read this thread and try the workarounds I have already tried.

Seriously about the only thing left I can do is move house. This is not on my end as far as I, or the increasingly long list of professionals I have pestered about every aspect of my computer and internet service, can identify.

The one and only oddity in all of this that I have noticed has occurred when changing my IPv4 address as is suggested in several workarounds. This completely cuts of my internet access. changing the IPv6 has no effect. Could this in some way be indicative of the issue?

Beyond that to answer the rest of your questions:
ISP: TPG
OS: Win7 x 64
Server: Bronzebeard, Bloodlust (12.129.209.68)

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 54 ms 105 ms 99 ms dsldevice.lan [192.168.1.254]
2 49 ms 49 ms 77 ms 10.20.21.72
3 77 ms 53 ms 73 ms bri-sot-wic-csw1-tengi-4-4.tpgi.com.au [202.7.173.245]
4 59 ms 78 ms 62 ms bri-sot-wic-crt2-gi-1-1-0.tpgi.com.au [202.7.171.41]
5 54 ms 82 ms 88 ms bri-nxg-alf-crt2-pos-8-0.tpgi.com.au [203.29.135.169]
6 49 ms 48 ms 49 ms syd-sot-ken-crt3-te-13-1.tgpi.com.au [202.7.171.125]
7 78 ms 90 ms 76 ms syd-sot-ken-bdr1-gi-0-0-0.tpgi.com.au [203.26.22.18]
8 274 ms 273 ms 270 ms te0-3-0-4.ccr21.sjc03.atlas.cogentco.com [38.104.138.93]
9 313 ms 295 ms 299 ms te0-7-0-6.ccr22.sjc03.atlas.cogentco.com [154.54.86.110]
10 275 ms 301 ms 320 ms te0-3-0-3.ccr22.sjc01.atlas.cogentco.com [154.54.6.101]
11 307 ms 285 ms 326 ms te0-4-0-2.ccr22.lax01.atlas.cogentco.com [154.54.85.33]
12 269 ms 270 ms 300 ms te0-6-0-4.ccr22.lax05.atlas.cogentco.com [154.54.82.154]
13 309 ms 376 ms 310 ms 192.205.37.157
14 312 ms 317 ms 342 ms cr1.la2ca.ip.att.net [12.122.84.202]
15 309 ms 308 ms 310 ms gar20.la2ca.ip.att.net [12.122.128.181]
16 313 ms 305 ms 305 ms 12-122-254-234.attens.net [12.122.254.234]
17 308 ms 310 ms 314 ms 206.16.68.46
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Hey Guys,

Had this problem for a few days now (just reloaded my computer). It has been driving me nuts. I've tried everything in this post and the only thing that fixed it was by grabbing a friends copy of the following;

C:\ProgramData\Battle.net
C:\ProgramData\Blizzard Entertainment

As soon as I deleted mine and replaced it with theirs everything works.

Happy days :)
http://us.battle.net/d3/en/forum/topic/7392969288

This worked for me. I hope it can help all of you <3
great playing yesterday and all of a sudden i get dced and i have tryed everything and i just cant get it to work...... WTF!!!
yep i have tried everything possible and still not working :(

Join the Conversation

Return to Forum