Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Ken_Qrious
Ken_QriousAccepted solution
Level 4
Mar 31, 2021 7:29 PM UTC
Hell Craig, I did have a look at the links but didn't find what I needed. In the end the answer was actually a simple one. The pw for the user had changed without my knowledge. Once I updated that everything was back to normal. Thanks for looking into this though, it was most perplexing.

7 replies

Jonathon_wodnicki
Community Advisor
Community Advisor
Mar 25, 2021 4:01 AM UTC

Hi,

 

I didn't see anything in the release notes:

 

Are you using password auth without enabling password auth?

 

Thanks,

-Jon

Translate
Ken_Qrious
Level 4
Mar 25, 2021 8:38 PM UTC
I checked serverConf.xml for the security settings. These didn't change during the upgrade and they align with the defaults except for allowUserPassword being set to true for the vpn setting. The soap request includes a sessiontoken value and again this hasn't changed. Is there something else I should check?
Translate
Craig_Thonis
Adobe Employee
Adobe Employee
Mar 31, 2021 4:39 PM UTC

Hi Ken,

Have you checked any of the related topics listed to the right of this post?  This type of error can occur for multiple reasons, including IP addresses not being whitelisted. I'd suggest double-checking the usual suspects in the related topics and escalating to Campaign Support if the issue persists.

 

Regards,

Craig

Translate
Ken_Qrious
Ken_QriousAuthorAccepted solution
Level 4
Mar 31, 2021 7:29 PM UTC
Hell Craig, I did have a look at the links but didn't find what I needed. In the end the answer was actually a simple one. The pw for the user had changed without my knowledge. Once I updated that everything was back to normal. Thanks for looking into this though, it was most perplexing.
Translate
Feb 15, 2024 11:58 AM UTC

We see this error in our envrionment was that same for your inviroment

 

 

Translate