Menu
Reply
  • 10
  • 0
  • 0
cutfrom
Tuning in
1,339 Views
Message 1 of 18
Flag for a moderator

Destiny 2; Error Code "Bee"

I have resumed (a hiatus since Spring 2018) playing Destiny 2. I am frequently unable to play due to encountering an error code the developers (Bungie) call “Bee”. A bit of research suggests this is to do with errors arising from some aspect of the internet connection. I have read various suggestions about “packet loss” or interference from other devices. I run my PC from via a wired connection to the router. I have tried testing these. An online test detected no packet loss. I tried using the Hub 3 in modem mode (to rule out other devices) – this made no difference. The error is not uniform across game modes. I have not experienced it at all in Crucible, or other PvP modes; only in the adventures and other one-player components. I am trying to seek help from the game developers; but they have not helped; and their guidance placed this error code at the feet of the ISP. Is this a problem your customers have encountered before? Can you propose any improvements or fixes? Thanks in frustration, Brian
0 Kudos
Reply
  • 10
  • 0
  • 0
cutfrom
Tuning in
1,274 Views
Message 2 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

Can anyone from Virgin voice an opinion on this - or knows anything about it?

 

Is the lack of IPv6 relevant?

 

I have tried all the self-help stuff in the BEE article by Bungie; checked all my settings. I'm playing on PC with a wired connection. I've tried putting the router (Virgin Hub 3.0) into modem mode to remove other devices/wi-fi from the equation; no change.

I'm monitoring (link below) the quality of the connection. It's almost always latency 20-40 ms, with no packet loss.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/76a8b31de686b938521bef5fd917baf9d1...

A different line quality test shows no issues:

Packet Loss: None
Mean Latency: 19.16ms
Jitter: 2ms

I have seen some other users on Bungie's forums also encountering this. Is there anything Virgin can do with the connection to rectify this?

 

 

0 Kudos
Reply
  • 979
  • 46
  • 87
Forum Team (Retired) Tom_S
Forum Team (Retired)
1,244 Views
Message 3 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

Hi cutfrom,

 

I am sorry to hear that you've been experiencing issues with this, the lack if IPv6 shouldn't make a difference to your connection.

So I can better understand the situation would you be able to answer the following for me please;

Is it just Destiny 2 where you are noticing connectivity issues or do you experience the same issues in other games?

Have you been able to ensure any ports used by the service are correctly forwarded?

 

Thanks,

Tom_S

  • 10
  • 0
  • 0
cutfrom
Tuning in
1,230 Views
Message 4 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

Thanks for getting back to me.

 

Yes - it's only Destiny 2.

I have followed the developer's troubleshooting; and have forwarded all applicable ports as they advise. 

I've also tried every other fix I can think of (as well as everything in Bungie's guidance); trying without UPnP, without firewalls - every variable the router will let me control.

 

For reference:

 

Bungie's guidance re error code "Bee" : https://www.bungie.net/en/Support/Troubleshoot?oid=12915

 

My thread on Bungie's forums documenting the issues and my efforts: https://www.bungie.net/en/Forums/Post/252381826?sort=0&page=0

0 Kudos
Reply
  • 979
  • 46
  • 87
Forum Team (Retired) Tom_S
Forum Team (Retired)
1,226 Views
Message 5 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

In that case it sounds like it might be a routing issue from your location and the Destiny 2 servers.

Have you tried a trace route test to see where your communication with their servers fails?  Windows TRACERT Test

 

Thanks,

Tom_S

0 Kudos
Reply
  • 10
  • 0
  • 0
cutfrom
Tuning in
1,220 Views
Message 6 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

Traceroute Results pasted below - does this clarify anything?

 

Besides this is it worth me using the ping command? Toward Bungie servers it is reporting 100% packet loss. However, pinging Google.com (216.58.198.164) reports 0% loss.

 

Any other servers I could ping to test?

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\cutfrom>tracert 199.189.118.227

Tracing route to bungie.net [199.189.118.227]
over a maximum of 30 hops:

1 3 ms 3 ms 2 ms 192.168.0.1
2 13 ms 11 ms 10 ms 10.117.128.1
3 9 ms 17 ms 8 ms bmly-core-2b-xe-132-0.network.virginmedia.net [8
0.1.226.125]
4 * * * Request timed out.
5 13 ms 16 ms 12 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174
]
6 11 ms 14 ms 24 ms 213.46.175.26
7 172 ms 170 ms 170 ms et-4-1-0.cr0-las1.ip4.gtt.net [213.200.112.78]
8 170 ms 177 ms 171 ms ip4.gtt.net [173.205.40.138]
9 136 ms 137 ms 138 ms be775.las-score7-3.sinap-tix.com [199.189.116.20
5]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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.

Trace complete.

 

0 Kudos
Reply
  • 979
  • 46
  • 87
Forum Team (Retired) Tom_S
Forum Team (Retired)
1,217 Views
Message 7 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

You can also try pinging other game servers you are aware of to see if you experience further timeouts.

However from what I can see the connection is indeed failing at some point on the route between our servers and the Bungie ones.

 

Thanks,

Tom_S

  • 10
  • 0
  • 0
cutfrom
Tuning in
1,208 Views
Message 8 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

Thanks Tom,

Really encouraging that the problem is now on Virgin's radar.

 

Here's hoping you can figure out some solution. Also interested now in what's causing the problem itself!

 

Ta

0 Kudos
Reply
  • 10
  • 0
  • 0
cutfrom
Tuning in
1,210 Views
Message 9 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

Any progress?

0 Kudos
Reply
  • 10
  • 0
  • 0
cutfrom
Tuning in
1,195 Views
Message 10 of 18
Flag for a moderator

Re: Destiny 2; Error Code "Bee"

Could there be any benefit from something as simple as Virgin cycling our external IP?

0 Kudos
Reply