Destiny 2: New Light, the game’s latest expansion Shadowkeep, and the integration over to Steam is all happening today. That’s right, Bungie has its hands full attempting to balance these new launches. Plenty is going on, and because the game is moving from Blizzard’s Battle.net launcher to Steam, you can imagine there are plenty of problems going on right now. We’re gathering up what we can. This guide is going to cover the Olive error code.
Destiny 2 Olive Error – What Does it Mean?
If you see this error pop up on your screen, you’re going to have the natural reaction of annoyance and panic, wondering what you need to do. Don’t worry. Bungie has you covered. They have an error code page already prepared for this, should any players encounter it. Here’s what the Bungie help forums website says about Olive:
Please retry that activity again and resume what you were doing before the error occurred. If you encounter this error again, please exit Destiny then relaunch. If you continue to see this error, it’s likely due to testing we are doing on our end, please pardon our dust! Watch help.bungie.net and follow @BungieHelp for updates.
Overall, it looks like there are some hiccups in their system when this error pops up. When you get it, close down the game and do a full restart of the game and start over from the top. If you get it again, exit the game and then restart your machine. You want to properly turn it off and then on again to make sure your system does a clean sweep. Following those attempts, if you’re still experiencing this error, it’s like Bungie is testing something on its end.
It doesn’t look like you’re going to get much done if Bungie is testing something on its side of things. Unfortunately, you’re going to have to wait for this one out or continue to fully power cycle the game by restarting it over and over again. If you’re willing to endure it, then good luck. Regardless, it may take some time and starting Destiny 2 on day one means things are going to remain hectic.