JavaScript is required to use Bungie.net

Help

Help us help you.
1/3/2023 9:35:53 AM
2

XBOX: NETWORK - Player encountering 3 contacting Destiny 2 server notifications before disconnecting to error code Weasel

TITLE: XBOX: NETWORK - Player encountering 3 contacting Destiny 2 server notifications before disconnecting to error code Weasel DESCRIPTION: During gameplay/in orbit, User intermittently encounters 2 successive 'Contacting Destiny 2 servers' prompts, then a 3rd before disconnecting from the session. User is prompted with 'Error code: Weasel' before being returned to the title screen. User is not being affected by packet loss/other network issues when disconnecting. Occasionally, User also encounters a crash after attempting to re-enter the title from title screen IMPACT: players encountering multiple daily disconnects/crashes become frustrated at loss of progress during solo activities and penalizations for involuntarily disconnecting during PvP/Ritual activities. This causes the title to look and feel unpolished. NOTES: Issue was encountered on Xbox Series X and Xbox One Issue occurs within all activities Issue occurs on version: 0.1.45680 Issue has occurred since season of the splicer. User plays using a wired ethernet cable/Netgear Nighthawk R7000 router User has no other Consoles/Accounts linked to Destiny 2 account REPRODUCTION: 1. Launch Destiny 2 version: 0 1.45680 on Xbox series X 2. Bypass ISS screen > Select character 3. Load into any location/activity 4. Progress through activities until 'Contacting Destiny 2 servers' notification appears prompts twice in succession, then a third time. ACTUAL RESULTS: User is disconnected from the session via 'Error Code:Weasel' EXPECTED RESULTS: Title is free of disconnects/crashes and user is able to remain in-game for prolonged periods of time without issue
English
#Help #Networking

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
You are not allowed to view this content.
;
preload icon
preload icon
preload icon