Skip to main content
Poonam_Dogra
Level 4
Oct 13, 2022 5:03 AM UTC
Solved

Error- Document is empty- while created via WSDL- adobe campaign classic

While Calling a schema wsdl [xtk:session] for adobe campaign classic I am getting below error after entering creds. Am I missing a small step?

 

May I know where to check this and how to fix this error.

 

Thanks in advance!

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Shubham_Goyal__
Shubham_Goyal__Accepted solution
Level 6
Oct 27, 2022 4:58 AM UTC

Hi @poonam_dogra,

 

Logon SOAP function is a very simple function and it should be working if everything I said have had been followed.

We can connect and discuss this issue further if you like: 

https://www.linkedin.com/in/shubham-goyal-205037128/

 

Br,

Shubham


Hi @poonam_dogra,

 

To document the correct answer for any future reference:

In our further discussion, the issue was found with the endpoint Url of the campaign server which was missing 's' in http:// ,  post correcting which the Logon call was successful.

 

Br,

Shubham 

~Thanks - Shubham Goyal (Enterprise Architect)
View in thread

11 replies

DavidKangni
Adobe Champion and Community Advisor
DavidKangniAdobe Champion and Community Advisor
Adobe Champion and Community Advisor
Oct 13, 2022 3:59 PM UTC

Hi @poonam_dogra,

 

You may need to save the WSDL correctly

To save the WSDL file:

  • Right click on the page
  • Select view source
  • Copy and paste the text into a text editor
  • Save the file with the extension .wsdl

Thanks,

David

Translate
David Kangni
    Poonam_DograAuthor
    Level 4
    Oct 13, 2022 4:27 PM UTC

    HI @davidkangni ,

    Thank you for responding, I am able to load the sessions now but when I am hitting it with user id password to get the session token, its throwing connection time out error. It will be helpful if you could please guide me how can I get the session token.

     

    Translate
    Shubham_Goyal__
    Shubham_Goyal__
    Level 6
    Oct 14, 2022 4:33 AM UTC

    Hi @poonam_dogra,

    It seems like a connection timed-out error.

    For this, you can first check if your IP address (public) from where you hit this Soap call is whitelisted (added to the security zone in the serverConf.xml file) on the Campaign server that you are trying to reach. doc 

    Also, you can check the web logs of the campaign server to see if it points to some other error when getting soap connection requests via Home>Monitoring>Overview>web logs.

    Br,

    Shubham

    Translate
    ~Thanks - Shubham Goyal (Enterprise Architect)
    Terms & ConditionsAccessibility statement

    Loading footer...