Failure to connect failure-to-connect

Checks

Resolution

Do you have Internet access from your computer?

Check that you can connect to websites on the Internet (for example). If you cannot connect, the problem is on your machine. Contact your system administrator.

Can you connect to the server hosting Adobe Campaign via another service?

Connect to the server via SSH or any other means. If this is not possible, your host company has a problem. Contact their system administrator.

Does the Web server respond?

Connect to the Adobe Campaign server access URL using a Web browser: http(s):// <urlserver>. If it does not respond, the web server is stopped on the machine. Contact the system administrator of your host company in order to restart the service.

Has Adobe Campaign been correctly integrated?

Log on to the: http(s)://<urlserver>/r/test URL. The server should return the following type of message: <redir status='OK' date='YYYY/MM/DD HHSS' build='XXXX' host='<hostname>' localHost='<server>'/> If you do not obtain this result, check in your Web server configuration that integration is taken into account.

Connect to the following URL: http(s)://<URLSERVER>/nl/jsp/logon.jsp

If you obtain a Tomcat Java error, check if the JAVA integration is correctly performed. It is integrated in the file [path of application]/nl6/customer.sh

Connect to the following URL: http(s)://<URLSERVER>/nl/jsp/logon.jsp

If you obtain a blank page, check if the Adobe Campaign Web module is started. The command nlserver pdump should return Application server for Adobe Campaign Classic (7.X YY.R build XXX@SHA1) of DD/MM/YYYY. If not, restart the module with the command nlserver start web

Check the general configuration of the security zones.

For more on configuring security zones, refer to this section.

The command nlserver pdump returns No tasks

You must restart the entire Adobe Campaign application. To do this, use the following command: nlserver watchdog -svc -noconsole