Bungie names this code but does not publish the wording it prints on screen, so we quote only the code itself: HONEYDEW. Any site showing you an exact message for it has written one.
When you see this one, the problem is most often on the operator's side and there is nothing on your machine to fix. Check the live status first.
Bungie has every core Destiny 2 service switched on
Bungie's description is unusually specific: “You may have encountered this Error Code if public access to an Activity has been manually overridden by Bungie. This may occur if an issue has been found, or if an activity have been taken offline prior to a Destiny Update.”
So this is not a fault at all. It is a deliberate action — a raid, dungeon or playlist taken out of rotation because something is wrong with it, or because an update is imminent.
The giveaway is that everything else works. If you can load into the game, move around and enter other activities, but one specific activity refuses you, that activity has been disabled rather than broken.
Operator documentation: help.bungie.net. Bungie documents its error codes in a public directory of over 300 articles. Those articles describe causes and fixes and never quote the in-game dialog, so neither do we. Bungie's wording also makes HONEYDEW a useful early warning: activities get pulled before an update lands.
Bungie's description is unusually specific: “You may have encountered this Error Code if public access to an Activity has been manually overridden by Bungie. This may occur if an issue has been found, or if an activity have been taken offline prior to a Destiny Update.”
When you see this one, the problem is most often on the operator's side and there is nothing on your machine to fix. Check the live status first.
Start with: There is no fix. Bungie disabled it on purpose. Nothing on your end changes that.