Question Frequent disconnections and DCOM error code 10016 ?

[zewoo]

Hi, I'm looking for someone with tech knowledge to help me sort something out. It really bothers me, so I will give as much detail as possible.

When I play Diablo 3 on battle net, I randomly get these network disconnections, lately many of them.
But in other games, launchers everything is good and nothing happens with network disconnections. It only happens in Diablo 3 game. Always it's overtaken by Windows distributed com error 10016, while in diablo 3 it's one zero less, error code 1016.

I know some may say it's not related, but I'm sure it is. Network disconnections last for 5minutes and then everything is back to normal. I need someone to help me fix this. I tried all Diablo 3 disconnection steps and DCOM error codes fixes, even the advanced ones. I asked a lot of people in Diablo 3, they all said it's just my problem.

I don't know what to do, App ID is unavailable and CLSID isn't written. Please someone help, I've been dealing with this for 2 years. I reinstalled Windows, even deleted Diablo 3 accounts so got new ones (but that's because of sms bypassers that got to my PC and make it die, literally).

 

[gggplaya]

Appears to be a permissions issue. Try running Diablo 3 and Battle.net both in Admin mode.

Reference: https://learn.microsoft.com/en-us/t...gement/event-10016-logged-when-accessing-dcom

Also, don't let windows auto find your drivers. Make sure you're using the ethernet and wifi drivers found on your motherboard's website, as well as the chipset driver.

 

[evermorex76]

Or go further and get the drivers directly from the manufacturer of the component (network chip, motherboard chipset/CPU, etc.), which are generally far more up to date.

Appears to be a permissions issue.

Its not an issue with permissions that needs to be fixed. They only say that you can change permissions to stop the events from being logged if they bother you, and otherwise that you can just ignore them. They explicitly say that the events aren't an indication that any functionality is effected. It just indicates that the first, preferred method of accessing the DCOM components failed, so the software fell back to using a different set of parameters to do it. There is only an issue if you see other events that indicate there was an actual failure. Having them logged is basically just so that if someone was debugging software and trying to optimize it, they'd know they should look at this and change their methods. Event Viewer has a LOT of entries that are irrelevant to anyone trying to do normal troubleshooting.

So Diablo 3 is trying to access DCOM components and it has to fall back to alternate parameters, but it otherwise succeeds. This may simply be that the game activates some feature to try to test and restore the connection, which happens to result in the DCOM events, but it doesn't mean the feature is failing to work. The DCOM events in themselves do not indicate a failure OR that what causes them is the cause of the disconnect. The fact that the numbers are similar is just coincidence. Event 10016 occurs constantly on my system and it's just a warning, not an error. (In fact it happens whenever there is a DNS lookup failure due to a timeout, in my BitTorrent client, so it's Windows's own services that are not using the "preferred" methods.)

Blizzard specifies that the code 1016 is usually caused by a connection issue. It's a generic disconnect error. The game lost connectivity to the servers. Aside from the DCOM errors, are there any other warnings or errors or even informational events that occur at the precise time that it happens? Especially anything network related but it could also be something that doesn't at first seem to mean anything.
What "3 disconnection steps" did you actually try? Are you using wired or Wi-Fi on your computer? What kind of Internet service do you have?

As shown here, you could use WinMTR running while you play to see whether there are any problems. (As one pointed out, if a single hop loses packets but the ones after it don't, then the packet loss at that hop isn't necessarily a problem, but other issues may be seen.)
https://us.forums.blizzard.com/en/d3/t/constant-there-was-an-error-code-1016/4555/4

It's entirely possible that this has nothing to do with YOUR machine or even your ISP, but is instead an issue somewhere in the middle, at one of the providers through which the traffic passes on the way to/from the remote server. You may get resolution simply by using a different server.