error 1016???

#1 - March 23, 2017, 2:13 a.m.
Blizzard Post
I got DCed during a bounty, yet again. But this time, I got this error code and when I went to close the pop up, was completely sigend out.
WTH???
Forum Avatar
Support Forum Agent
#75 - March 28, 2017, 10:08 p.m.
Blizzard Post
Hey all,

The error 1016 can be caused by several things. It is a bit of generic connection error message. If you have not yet please to try the steps SilverFox posted here: https://us.battle.net/forums/en/d3/topic/20753637526?page=3#post-60

If you are still seeing the error after trying the steps please do post a WinMTR. This will help us get a in-depth look at the connection.

WinMTR
    1) Download WinMTR - http://winmtr.net/download-winmtr/
    2) Unzip the WinMTR.zip file to the Desktop.
    3) Open the WinMTR folder and select the one corresponds to your version of Windows (32 or 64 bit version).
    4) Run the WinMTR.exe
    5) Type the IP address you would use to run a trace route in the "Host" - https://battle.net/support/article/496
    6) Click on "Start" while playing
    & Run for at least 10 minutes then click on "Stop" in WinMTR
    7) Click on "Export text" and save to a text file.
    8) Copy and paste the contents of whole file here.
    9) Click on "Start"
    10) Run for 10 minutes then click on "Stop" in WinMTR
    11) Click on "Export text" and save to a text file.
    12) Copy and paste the contents of whole file here.
Forum Avatar
Support Forum Agent
#90 - March 30, 2017, 9:59 p.m.
Blizzard Post
ZEUS01, Thank you for letting us know what stopped the disconnections for your you.
Forum Avatar
Support Forum Agent
#91 - March 30, 2017, 10 p.m.
Blizzard Post
Hey all,

ZEUS01 mentioned that they were seeing the disconnections stop when the Anti-virus was turned off. I would like to see if there is a correlation with the security programs and the disconnections everyone else is seeing. First instead of turning off the security program add Diablo III and the Blizzard App to the security programs exception/exclusion list. The launch Diablo III and see if the disconnections still happen.

If that does not make a difference, see if temporarily disabling the security program makes a difference.

If adding Diablo III to the security programs exclusion/exception list or temporarily disabling the security program makes a difference, please post which security programs you are using.
#276 - April 9, 2017, 11:20 a.m.
Blizzard Post
Hey all,

I'm really sorry for the lack of a reply here. Let me explain a little on what this error is since it did appear sort of out of nowhere with patch 2.5.

The error is basically a generic "You have been disconnected." Much like for those that have played WoW and get the BLZ51900319 error. All that it means is that the game client lost connection with the game server. Which leaves a wide array of possible causes I know.

Normally I would prefer to troubleshoot these issues for each of you in your own thread. However I will do what I can in here to help troubleshoot with all of you at once. So to start I would say go through every -possible- step that is listed on the common connection troubleshooting page. Since again this can be a connection issue for any reason.

Past that, I would say you're welcome to start your own thread or reply here. We will do out best to try and get to everyone that we can. However if you need direct assistance I would suggest opening a contact with the support staff.
#289 - April 10, 2017, 8:56 a.m.
Blizzard Post
Thanks for the wealth of information here. I know you're likely going to flood the thread with results, so I'll do my best here to keep up but can you each post your WinMTR information while having the issue please:

IP Chart:
North America 24.105.30.129
Brazil (Americas) 54.94.196.47
Europe 185.60.112.157
185.60.112.158
Australia 103.4.115.248

  • First, download the WInMTR program
  • To run this you’ll want to right click on the .exe and select run as admin or you’ll likely get an error.
  • In the “Host” field you want to put in the server IP. For this see the chart above
  • Click Start and now we want to run this while you’re playing the game. So go ahead and log in.
  • Let this run for roughly 10-20 minute intervals while you play until you start to lag or DC. By this I basically mean play for 10-20 minutes if you don’t DC stop it and start the WinMTR again. That way we can have about 10-20 minutes worth of connection information while the game is having latency or DC.
  • Once you’re sure that you have the ~10-20 minutes of latency/DCs recorded. Press the stop button and just select the option for “Export TEXT”.
  • Save the file as something easy to remember on the desktop and post here.
  • #303 - April 10, 2017, 11:32 a.m.
    Blizzard Post
    Okay here's what I'm seeing for each of these so far. As you can see the possible issues are quite varied based off just these few replies. So we may end up needing to break this thread into individual thread :

    @KiLL3RSiX -
    04/09/2017 07:24 PMPosted by KiLL3RSiX
    Here you go 10mins+ of constant relogs and internet drop after closing D3. cheers...

    If you're unable to connect at all, that's definitely a different issue. As for the WinMTR you submitted, all and all it looks pretty good. Can you try the other EU IP as well for me please, then post the results plus a recap of the issue you're having in a new thread so we can work with you on it please.

    @Dixavado -
    | 192.168.0.1 - 78 | 6938 | 1568 | 0 | 2 | 66 | 1 |
    | 10.46.128.1 - 79 | 7401 | 1568 | 6 | 12 | 101 | 8 |

    What's interesting here is the high level of data loss, normally I would think that's shaping by an ISP, however in this case it's starting at the router/modem device. Is this a separate modem and router? If so, try bypassing the router and connect directly to the modem.

    @ALeetPlayer -
    | 10.178.206.24 - 3 | 254 | 247 | 0 | 15 | 26 | 22 |

    Overall the connection looks pretty good until this point. What's odd here is the first 4 hops are all private network IPs. Are you using a school connection or something similar?

    @Lazerus -
    | 10.0.0.1 - 3 | 802 | 782 | 1 | 10 | 212 | 3 |
    | 96.120.29.109 - 3 | 806 | 787 | 11 | 27 | 274 | 11 |

    The latency here isn't terrible, I'm guessing it's a wireless connection since it's up at 10ms average to the modem. We're also seeing 3% data loss here, so if this is a modem can you give a wired connection a shot to test please.

    @Brickroad -
    | 192.168.0.1 - 99 | 153675 | 2604 | 0 | 0 | 34 | 0 |
    | 10.206.208.1 - 99 | 169010 | 2589 | 4 | 8 | 56 | 10 |

    Something happened here to cause an issue with the sent data via the WinMTR program. Because that would be ~40 hours of WinMTR recording. >.< Can you try reinstalling the program and running it again please.
    #345 - April 12, 2017, 11 a.m.
    Blizzard Post
    Hey again everyone,

    After going through the prior WinMTR's and these new ones, the best option so we can help as many of you as possible is going to be to lock this thread and have you each make a thread OR contact our support team so we can work with you individually. Since we're seeing lots of different connection issues with the connection data being supplied and it's not a singular issue causing the disconnects for everyone.

    I did also see a few mentions of why did this start on this patch. The simple answer is that error code didn't exist prior to this patch. It was created to replace the generic "Lost connection to server" message that you would see. So at it's core, this is also just a generic error code stating that the game client lost connection to the server. As for why some customers are getting disconnected, in the prior connection reports there are a multitude of possible issues with no commonalities thus far. We can help troubleshoot, but it'll be best for everyone to create a new topic or ticket so we can work with each person individually.