{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/13/2016 9:22:51 PM
11
Hey Ecto. Is it [i]always[/i] the Elderberry error code that you experience, and does it only occur when trying to transition to social spaces?
I see that you have already attempted clearing your cache, have you attempted any other troubleshooting steps?
English
-
Ya its elderberry, I have tried checking the Internet and resetting routers, I have done power offs (complete not just quickstarts) I have tried making a new character and the new character could get to the tower but not my prior characters, that's about it
-
Edited by Lime Lyfe: 5/13/2016 9:55:25 PMAlright, if you are still experiencing this error consistently you should attempt a full re-installation of Destiny. 1) Remove all the Destiny related content from your HDD, including DLC and the base game. 2) Clear your cache, this is an important step during re-installation as it removes any cached files in temporary memory from being used in the re-installation process. [url=https://www.bungie.net/en/Help/Article/12539]You can find information on how to properly clear the cache on different consoles here.[/url] 3) Re-download all content, during this step try to maintain a wired and stable connection. Once re-downloaded load up Destiny and re-attempt joining a social space. Please note that deleting Destiny content on your console will not affect your progress, characters or items. These are all stored on Bungie's servers, and remain unaffected by actions performed on your console. [url=https://www.bungie.net/en/Help/Article/12288]In addition to the above steps you can find a guide on re-installation here.[/url] Please get back to me if the Elderberry issue is still present after you have performed the above steps.
-
Will let you know
-
Please do, working or not :)
-
Could you please lend your opinion if you have the time to spare on my post? [url]https://www.bungie.net/en/Forums/Post/204743757?sort=0&page=0[/url]
-
Total install clear cache and reinstall did the trick thanks for your help and your time
-
Hey Ecto, thanks for the feedback, great to see that it did the trick. If anything changes please let me know.
-
Heh, well got to play for a about an hour maybe a lil more and now i am stuck with newt codes cant go anywhere
-
Hey Ecto, apologies for the late reply. Is the issue still occurring? If it is can I get you to once again [url=https://www.bungie.net/en/Help/Article/12539]clear the cache,[/url] and perform a power cycle on your router. A few questions again as well: [b]Is Newt the only error you are receiving and is it happening consistently? If so what activities are affected, can you log in at all?[/b]
-
Just Newt,cache has been cleared and Power cycled I got to play for about an hour last night before it started doing it again
-
Hey again Ecto, the error codes you are experiencing both Newt and Elderberry, [i]can be[/i] indicative of a NAT issue. It is worth checking your home networks NAT configuration in an attempt to remedy the issue. If you have manual port mapping settings configured, disable them and enable uPnP by itself. If uPnP is enabled in tandem with port mapping settings configured by the user this can cause issues when sending and receiving data.[url=https://www.bungie.net/en/Help/Troubleshoot?oid=13611] Check this guide for information on configuring uPnP[/url], this differs router to router so you may need to contact your router manufacturer or ISP. Additionally if your router offers settings for uPnP security you can try enabling and disabling these settings to see if there is any change in connectivity, you should again check with your router manufacturer/ ISP for potential implications. If uPnP is still causing issues when attempting to load into instances within Destiny, you can disable uPnP and go the route of enabling manual portmapping. [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13610]You can find which ports need forwarding and opening within the Network Troubleshooting Guide.[/url] When configuring these settings make sure you review your firewall settings, possibly setting up specific rules to allow traffic on specific ports. More advanced than both of these would be using enabling DMZ settings for the device (in this case your console) on your router. This puts your console past the router firewall. I would only recommend doing this to test if either port mapping settings or firewall rules are blocking connectivity. If you are not familiar with using the DMZ or aren't familiar with security implications, please contact your ISP before changing these settings. Finally there are other networking hardware issues that could be triggering these issues. [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13602]You can review them all in this article here.[/url]
