{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/15/2020 3:58:43 PM
7
Watercress a “Pointer problem?”
Here are the things I did, and none of them worked:
After trying the following: Deleting characters that I never use; uninstalling D2, reinstalling D2
I got in touch with a tech at Microsoft. I did the following at her suggestion: uninstalling D2; removing my profile then restarting the Xbox one; adding my profile again; installing Mega Man 11 demo (I used it to check that my profile was working); installing D2 again; log into D2.
NONE OF THAT WORKED; I still ended up with the watercress failure.
My son, Patrick, a computer programmer, thinks it’s a “pointer” problem.
He also thinks that if it’s a pointer problem, a “rollback’” to an earlier time won’t fix the Watercress issue.
He says the following:
If you get a tech, ask them if they can use administrative tools to access the character attributes in the database.¿¿If the data is accessible, then the pointer to the data (your Mithgar01 -> D2 connection) is what needs to be repaired. I highly suspect this to be the case.
So, unless and until I can get in touch with a tech ...
Dennis L. McKiernan
Mithgar01
English
#destiny2
-
2 RepliesOh, here’s another couple of things I tried: I have two Xbox Ones: “mine,” and an Xbox One that one of my adult sons plays on when he visits. “My” Xbox One with “my” Hunter gets the Watercress error. D2 doesn’t play. “His” Xbox One with “his” Hunter plays perfectly. D2 plays correctly. So . . . I loaded his profile on “my” Xbox One, and logged him in, and activated his Hunter, and D2 plays perfectly on “my” Xbox One. Then . . . I loaded ‘’my” profile on “his” Xbox One and D2 doesn’t play and I get the Watercress error. So, It is not a network problem, not a wireless problem, but it is probably a pointer problem. For some reason the Bungie servers do not recognize my profile. And as noted in my previous message, I deleted my profile, restarted my Xbox One, then reestablished my profile. Lastly, let me say that the Ishtar app and the Destiny app ore behaving normally, so, those two apps recognized my deleted profile and recognize my reestablished profile. So . . . In my opinion, the problem is at the Bungie end.
-
I know a lot about programming and IT but I’ve never heard of a “pointer problem”
-
Mate it’s horrible. They said we should cross-play but I’m not going to play destiny 2 on another console without my mates!? Stupid they won’t fix the issue.
-
I managed 15k on my cross trainer today. Feeling good 👍
-
one of the bungie help accounts told someone that the problem had to do with some xboxs not clearing player sessions once they ended so some people have multiple play sessions going on at once which causes the error.
-
What xbox one are you on? Ive been reading some of bungies replies about the issue and im thinking the console you own might determine if you have the issue If you didnt know already they claim its an issue with having too many session open
-
2 RepliesDunno if it helps but: https://www.bungie.net/en/Help/Article/46392 Possibe WiFi issue?
