2

We are trying to connect the content porter giving domain name in username as well as without domain name. But its not able to connect. We tried to login with public ip address as well as with internal ip address on AWS server. we are using Tridion 2013 SP1

enter image description here

3
  • Some additional Info : we are using Tridion 2013 SP1
    – user918
    Apr 23, 2014 at 7:38
  • also, choose correct protocol from dropdown (HTTP, HTTPS), while connecting CMS from CP. because of this the error could occur as well. Apr 23, 2014 at 7:42
  • The error message is indicating that the login failed I believe, since your CMS server appears online via the given address (you might want to modify that picture and blank out the public IP address). So I would validate that you can login with the given credentials from the same location that you try Content Porter from, if that does work, check out the IIS log for authentication failures. Apr 23, 2014 at 7:50

1 Answer 1

1

You can get more insight by looking at Content Porter log file, Event log on Tridion machine, IIS log, as suggested by Bart and by using HTTP debugger, like Fiddler. I would start with Fiddler, this way you can see if you have 401 error straightaway.

1
  • He is right! This is generic error, when something unexpected on connection to server is happened. Source error you can find in the "ContentPorter.log" (path to log directory, e.g. place where this file will be created can be set in Settings->Logging tab-> Log files location)
    – Syav4eg
    Apr 23, 2014 at 9:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.