Failed to authenticate the current user against the selected

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
altruist
Participant
Posts: 73
Joined: Thu May 11, 2006 6:50 am

Failed to authenticate the current user against the selected

Post by altruist »

Hi All,

I have tried to restart datastage server.

Is it obligatory to restart WAS and ASBnode.

I am able to login to unix box using "dsadm" and able to use orchadmin commands.

Thanks
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It is not obligatory to restart WAS or the agents.

It is also not correct to use orchadmin command to stop and start DataStage.

Study the administration manual and document the correct methods for your site.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
altruist
Participant
Posts: 73
Joined: Thu May 11, 2006 6:50 am

Post by altruist »

Hi Ray,

Sorry I meant... I was able to use orchadmin commands to access datasets after restarting datastage server.

The root user has restarted WAS/ASBnode, but the users (even dsadm) is still not able to login to datastage via client.

Thanks
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Then please post the complete error message. There's a limit on the number of characters in a subject line.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
altruist
Participant
Posts: 73
Joined: Thu May 11, 2006 6:50 am

Post by altruist »

Below is the entire message.

Code: Select all

javax.security.auth.login.LoginException: Could not connect to server [170.226.199.130] on port [9080].
	at com.ascential.acs.security.auth.client.AuthenticationService.getLoginException(AuthenticationService.java:965)
	at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:358)
Caused by: com.ascential.acs.registration.client.RegistrationContextManagerException: Caught an unexpected exception.
	at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:67)
	at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:352)
Caused by: com.ascential.acs.registration.client.RegistrationHelperException: Caught an unexpected exception.
	at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:567)
	at com.ascential.acs.registration.client.RegistrationHelper.getBindingConfigProperties(RegistrationHelper.java:534)
	at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:167)
	at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:65)
	... 1 more
Caused by: java.net.ConnectException: Connection refused: connect
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:201)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188)
	at java.net.Socket.connect(Socket.java:478)
	at java.net.Socket.connect(Socket.java:428)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:435)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:649)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:339)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:300)
	at sun.net.www.http.HttpClient.New(HttpClient.java:372)
	at sun.net.www.http.HttpClient.New(HttpClient.java:353)
	at sun.net.www.http.HttpClient.New(HttpClient.java:348)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:562)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:539)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:667)
	at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:559)
	... 4 more
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

OK, the exception is "connection refused". This could be incorrect user name and password, it could be that the user name you are using is not actually registered within Information Server with at least Suite User role, or one of a number of other possibilities. Please check the correctness of the user name and password that you are using.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
altruist
Participant
Posts: 73
Joined: Thu May 11, 2006 6:50 am

Post by altruist »

All the users are not able to login to datastage, including "dsadm". We have verified the credentials.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Can you log in to Web Console for Information Server?

Have you confirmed that the services tier, the agents and DataStage were successfully started?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply