Client side login failures

You received the following error: Failed to authenticate current user against selected Domain Could not connect to server [rmanikon-2] on port [9080]

Stack Trace

The error indicates that your client cannot connect to the Information Server Services Tier (domain) server. There are many reasons that can cause this problem to occur. It can be as simple as an invalid server name or port number. Click the “More” button to get a stack trace for the error.

javax.security.auth.login.LoginException:  Could not connect to server [RMANIKON-2] on port [9081].  
 at com.ascential.acs.security.auth.client.AuthenticationService.getLoginException(AuthenticationService.java:991) 
 at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:370)
Caused by: com.ascential.acs.registration.client.RegistrationContextManagerException: Caught an unexpected exception.
 at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:76)
 at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:364) 
Caused by: com.ascential.acs.registration.client.RegistrationHelperException: Caught an unexpected exception. 
  at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:672)  
 at com.ascential.acs.registration.client.RegistrationHelper.getBindingConfigProperties(RegistrationHelper.java:566)
 at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:173)
 at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:73) 
  ... 1 more 
 Caused by: java.net.ConnectException: Connection refused: connect 
  at java.net.PlainSocketImpl.socketConnect(Native Method)  
  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:391) 
  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:252) 
  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:239)

There are four important things to note in the stack trace. There is no text that states “Trace from Server”, so this means that it is a client side issue. Look at the first highlighted message in the stack trace example. It is giving the host name and port number. The second highlighted message indicates that the error happens during the RegistrationHelper call. The last thing to note is the last highlighted message indicates the root cause is a socket connection error.

Invalid server name or port

Verify server name in DataStage login screen ping <DataStage Server>
Verify that the port number is correct
- View the registered-servers.xml file in the following location: InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client_configuration_<is_ver sion>/ registered-servers.xml
- Find “<asb-server” <asb-server name="RMANIKON-2” host-name="RMANIKON-2“ port="9080“ is-primary-server="true" />
- Client has invalid entry in hosts file for DataStage server
Check Windows\System32\drivers\etc\hosts ds_ip_address host_short_name host_long_name

There are several scenarios that can cause an error “could not connect to the server”. The first issue can be an invalid server name or port. Verify that the server name is entered correctly in the DataStage login screen. Ping the DataStage server name from the client system to be sure that it is a valid host name.

Next, be sure that the Information Server port number you are using in the DataStage login screen is correct. To check this, open the registered-servers.xml file. Look for the string <asb-server> and check the port number in the asb-server tag.

Another issue could be that the client has an incorrect entry in the client hosts file. For example, the ip_address for the DataStage server in the host file might be wrong or the client does not have a valid entry for the server. If so, correct the entry in the hosts file for the DataStage server.

Causes and resolution

Server listening port might be blocked by firewall
- telnet <DataStage server> <port number>
- Linux® nc –v –z <host> <port>
- Check with network administrator to see if port 9080 is blocked
Information Server not running
- Windows: Check IBM WebSphere® Application Server status => Started
- UNIX® or Linux: ps-ef | grep java root 25468 1 0 May 02 ? 33:33 /u1/IBM/WebSphere/AppServer/java/bin/java …

Another issue might be that the port is blocked by a firewall. You can do a quick test by trying to telnet to the host and port number. Use the command “telnet <DataStage host> <port number>”.

If the telnet fails, then the port is most likely blocked. If you are on Linux, you might also use the nc command to see if the port is open. If the port is blocked, your administrator must open the port.

The last issue might be that WebSphere Application Server is not running. For Windows, go to Services in the control panel and see if the service IBM WebSphere Application Server is started. For UNIX and Linux use the command ps –ef | grep javaand check to be sure that the WebSphere process is running.