XSV-350012 Invalid login or password. Connection denied for soap calls | Community
Skip to main content
Ken_Qrious
Ken_Qrious
New Participant
March 24, 2021
Solved

XSV-350012 Invalid login or password. Connection denied for soap calls

  • March 24, 2021
  • 2 replies
  • 5732 views

Recently we upgraded from 9032 to 9187.  Before the upgrade we could successfully make a soapUI call to

https://xxxxxxxxxxxxxxxxxxxxxxxxx/nl/jsp/soaprouter.jsp but after the upgrade we get XSV-350012 Invalid login or password. Connection denied.  

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ken_Qrious
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.

2 replies

Craig_Thonis
Craig_Thonis
Employee
March 31, 2021

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

Ken_Qrious
Ken_QriousAuthorAccepted solution
New Participant
March 31, 2021
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.
A
Arun_2024
New Participant
February 15, 2024

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

 

 

Jonathon_wodnicki
Jonathon_wodnicki
New Participant
March 25, 2021

Hi,

 

I didn't see anything in the release notes:

 

Are you using password auth without enabling password auth?

 

Thanks,

-Jon

    Ken_Qrious
    Ken_QriousAuthor
    New Participant
    March 25, 2021
    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?
    Terms & ConditionsAccessibility statement

    Loading footer...