Hi
I am facing this queer issue where when I try to login to any project, the DS clients hang. This measn I am not able to login either through Administrator or the Designer.
Even the IBM information server console hangs on that particular AIX server box.
Recently the particular server had space issues which was "taken care" by the network people. (I do not know what they did) but now the machine is up.
I am using DS 8.1
I bounced the Datastage server aslo but to no avail. Is there any way to figure out what is wrong!!!
Cannot login to project
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 86
- Joined: Wed Apr 02, 2008 2:32 am
- Location: Bangalore
-
- Participant
- Posts: 86
- Joined: Wed Apr 02, 2008 2:32 am
- Location: Bangalore
Bounced the server
After bouncing the server, i am at least able to get some error message...the message says:
The additional message that i get is:
The problem is that i am not even able to login to the information server console to check on the domain managemnet, if that is applicable on V8.1
Any help please!!
Code: Select all
com.ibm.websphere.security.auth.WSLoginFailedException: Unable to begin a transaction: [Can't lookup a connection]
at com.ibm.ws.security.server.SecurityServerImpl.simple_authenticate(SecurityServerImpl.java:175)
at com.ibm.ws.security.server._SecurityServerImpl_Tie.simple_authenticate(_SecurityServerImpl_Tie.java:116)
at com.ibm.ws.security.server._SecurityServerImpl_Tie._invoke(_SecurityServerImpl_Tie.java:93)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java)
at com.ibm.rmi.iiop.ORB.process(ORB.java)
at com.ibm.CORBA.iiop.ORB.process(ORB.java)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java)
Code: Select all
failed to authenticate current user against selected domain
unable to begin a transaction(can't lookup a connection)
Any help please!!
-
- Participant
- Posts: 86
- Joined: Wed Apr 02, 2008 2:32 am
- Location: Bangalore
Thanks Chulett, while I get some words from network admin people, I did some google.
I found this link to be useful:
http://www-01.ibm.com/support/docview.w ... wg21317812
Though this did not solve my issue as I was able to ping the hostname of the server from the client machine...they(IBM) did not provide the other version...umm
Still if any more ideas....
I found this link to be useful:
http://www-01.ibm.com/support/docview.w ... wg21317812
Though this did not solve my issue as I was able to ping the hostname of the server from the client machine...they(IBM) did not provide the other version...umm
Still if any more ideas....
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 86
- Joined: Wed Apr 02, 2008 2:32 am
- Location: Bangalore
Thanks Ray, we are doing that....
while on DSX i still found this useful link
viewtopic.php?t=115730&highlight=Unable ... connection
It may help others ...
meanwhile i am also trying to rectify the problem based on the resolution for that particular problem
wish me luck!!
while on DSX i still found this useful link
viewtopic.php?t=115730&highlight=Unable ... connection
It may help others ...
meanwhile i am also trying to rectify the problem based on the resolution for that particular problem
wish me luck!!
-
- Participant
- Posts: 86
- Joined: Wed Apr 02, 2008 2:32 am
- Location: Bangalore
WAS restarted
Hi
I am closing this thread as the issue has resolved.
I have only deduced that the actual problem was with the WAS server...several attempts to bounce it were not successful.
Finally the WAS team did something to bring up the WAS server. Once it was up, we only bounced the DS servers and we are able to login to DS
I will try to get some words from the WAS team as to what actually went wrong that forced DS to behave irrationally. I will post it here, then!!
I am closing this thread as the issue has resolved.
I have only deduced that the actual problem was with the WAS server...several attempts to bounce it were not successful.
Finally the WAS team did something to bring up the WAS server. Once it was up, we only bounced the DS servers and we are able to login to DS
I will try to get some words from the WAS team as to what actually went wrong that forced DS to behave irrationally. I will post it here, then!!