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.
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?
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.
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.
That's the same error but rather than a console error it was a soap ui api call error. It turned out to be a simple pw issue, this wasn't spotted right away as we were focusing on the upgrade.
We have actually seen the console version of this error but not recently. When it occurred it was for random users with no identifiable pattern. We were able to work around the issue be changing the call to the client to admin mode. Hope this helps.
