Scan and Repair fails

Support Technical Support
1

I’m having the disconnect-at-login issue many others are experiencing, so I tried to do a scan and repair, but every time it completes, I get an error message that says “Oops! Looks like something broke” and a prompt to retry. I’ve gone through it several times. Also, when it’s done or I stop it, the “Play” button says “Update,” but when I click it, it goes into scan and repair again, and fails.

5 Likes
2

Same issue and symptoms here. ISP is Ting and I’m located in NC. I suspect the issues with updating and disconnect at login are related

1 Like
3

i get put into a que for my server and i instantly get logged out for some reason

1 Like
4

I’m in Missouri. This seems to be a nationwide issue, from the comments I’ve seen.

5

Same here. How do we fix?

6

I’m also having this issue from Missouri. What server are you trying to connect through? Are you using Spectrum as well?

7

I use Socket. Ravenholdt is my server.

8

same story here in texas, got disconnected from servers when i tried to log, then scan repair for all eternity. I dont understand whats wrong my roommate is literally right across the hall wrecking shop in SL right now with no issues when he updated

1 Like
9

same here!

1 Like
11

Everything on my end works fine. It is Blizzard that is the problem. They messed up again with their coding. I log in and instantly at the character select screen get disconnected. It is the WOW51900319 code again. I did get logged in and almost got in, but it would just stay on the loading screen.

2 Likes
12

I’m also in Texas…so, I have all these same issues with perpetual scan/repair/oops I broke it cycle and my husband is sitting right next to me playing. lol

13

got same problem here in Indonesia. hope theres solution for this problem.

14

I also tried the tricks in the other thread. I “deleted” my cache and restarted the game. I uninstalled bnet launcher and reinstalled. I tried using my husbands cache folder, but unsuccessful.

15

Can those of you who can’t connect post the results of this command from the command prompt -

nslookup us.depot.battle.net

16

Server: UnKnown
Address: 192.168.1.1

Non-authoritative answer:
Name: blizzard-dl.vo.llnwd.ne[t]
Addresses: 69.28.131.80
69.28.131.81
Aliases: US.depot.battle.ne[t]

C:\WINDOWS\system32>
C:\WINDOWS\system32>
C:\WINDOWS\system32>

Note: I put the “t” at the end of “net” in brackets because this site doesn’t let us post links and if I’d left it as it was, it showed up as a link.

17

That’s different from what I get and I can get on just fine. I get addresses in the 117.121.253.xxx range.

This might be an explanation of why some people can connect but others can’t - there’s some cache server nodes out there with bad data (possibly)

My guess to fix it would be to try changing your DNS server to a public one like Open DNS , Google DNS to see if that fixes it. If it does then I would be interested in finding out if that changes what us.depot.battle.net resolves to.

There’s also grabbing a known good Cache folder and replacing your Cache folder with a known good one. Should be able to crib off a mate for that one (or use the zip links in the thread with the blue responses in it)

18

Thanks for the info. I’ve never actually changed my DNS server before, so I’ll have to do some research.

I tried using the cache someone posted a link to in another thread, but I can’t get past the scan and repair loop in the Battle.net launcher. Is there a way to bypass that and just launch the game itself?

19

i tried delete some local data, app data, temp, program data. removing idx data from wow folder. using someone else cache, delete the cache. still no good. wtf is happening here!!

20

Here’s mine

➜  nslookup us.depot.battle.net
Server:         4.2.2.2
Address:        4.2.2.2#53

Non-authoritative answer:
us.depot.battle.net     canonical name = blizzard-dl.vo.llnwd.net.
Name:   blizzard-dl.vo.llnwd.net
Address: 208.111.161.206
Name:   blizzard-dl.vo.llnwd.net
Address: 208.111.161.148

I’ve reinstalled battle.net client, deleted cache folder and a Scan & Repair fails.

I finally got everything working by doing a full uninstall of Battle.Net and World of Warcraft. I then installed Battle.net, reinstalled WoW to a different folder than I had it in originally. This worked for the Scan & Repair, but I still get disconnected when trying to log in. Finally, I replaced the cache folder with the one from the Disconnect thread and things are working.

21

Same. It’s clearly linked to the screw-up Blizzard is currently making with the log-in servers. The update servers seem just as broken.