login failed to connect to datastage server through client

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
prasson_ibm
Premium Member
Premium Member
Posts: 536
Joined: Thu Oct 11, 2007 1:48 am
Location: Bangalore

login failed to connect to datastage server through client

Post by prasson_ibm »

Hi,
I am unable to connect to datastage server when i login to client i get below error:-

:- Failed to authenticate the current user against the selected Domain:
Session id for principal [username] is null. Either the client is not using the ASB authentication service, or your server JAAS configuration is missing the proper ASB custom JAAS login modules.

Code: Select all

Failed to authenticate the current user against the selected Services Tier

Session id for principal [W2388] is null. Either the client is not using the ASB authentication service, or your server JAAS configuration is missing the proper ASB custom JAAS login  modules.

This error occurred on 05/08/2013 at 11:37:09 (Standard format: 2013/08/05 11:37:09)

Product Version: 8.7.0.0
Client tag: ccdefd8a-578c-4401-8009-f01fe1ed0218
Application: director.exe (PID 5104)
Operating System: Windows 7 6.1 Service Pack 1
.NET Framework version: 4.0.30319.1008
Machine Name: W41010463
User Name: W7072388
Language: English (South Africa)
Time Zone: South Africa Daylight Time

Error message:
Failed to authenticate the current user against the selected Services Tier



Session id for principal [W2388] is null. Either the client is not using the ASB authentication service, or your server JAAS configuration is missing the proper ASB custom JAAS login  modules.

Exception type: javax/security/auth/login/FailedLoginException
Exception message: Session id for principal [W2388] is null. Either the client is not using the ASB authentication service, or your server JAAS configuration is missing the proper ASB custom JAAS login  modules.
Exception stack trace:
javax.security.auth.login.FailedLoginException: Session id for principal [W2388] is null. Either the client is not using the ASB authentication service, or your server JAAS configuration is missing the proper ASB custom JAAS login  modules.
	at java.lang.Throwable.<init>(Throwable.java:67)
	at com.ascential.acs.security.auth.server.impl.AuthenticationServiceBean.loginImpl(AuthenticationServiceBean.java:347)
	at com.ascential.acs.security.auth.server.impl.AuthenticationServiceBean.login(AuthenticationServiceBean.java:166)
	at com.ascential.acs.security.auth.server.EJSRemoteStatelessAuthenticationService_e0d03809.login(Unknown Source)
	at com.ascential.acs.security.auth.server._EJSRemoteStatelessAuthenticationService_e0d03809_Tie.login(_EJSRemoteStatelessAuthenticationService_e0d03809_Tie.java:149)
	at com.ascential.acs.security.auth.server._EJSRemoteStatelessAuthenticationService_e0d03809_Tie._invoke(_EJSRemoteStatelessAuthenticationService_e0d03809_Tie.java:92)
	at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:623)
	at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:476)
	at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
	at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
	at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2845)
	at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2718)
	at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
	at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)

Loaded modules:
C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll     6.1.7601.18120
C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL     6.10.7601.17514
C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\comctl32.dll     5.82.7601.17514
C:\Windows\system32\WSOCK32.DLL     6.1.7600.16385
C:\Windows\System32\wshtcpip.dll     6.1.7600.16385
C:\Windows\System32\wship6.dll     6.1.7600.16385
C:\Windows\system32\WS2_32.dll     6.1.7601.17514
C:\Windows\system32\wkscli.dll     6.1.7601.17514
C:\Windows\System32\winrnr.dll     6.1.7600.16385
C:\Windows\system32\WINNSI.DLL     6.1.7600.16385
C:\Windows\system32\WindowsCodecs.dll     6.2.9200.16583
C:\Windows\system32\VERSION.dll     6.1.7600.16385
C:\Windows\system32\uxtheme.dll     6.1.7600.16385
C:\Windows\system32\USP10.dll     1.626.7601.18009
C:\Windows\system32\userenv.dll     6.1.7601.17514
C:\Windows\system32\USER32.dll     6.1.7601.17514
C:\Windows\system32\SXS.DLL     6.1.7601.17514
C:\Windows\system32\SspiCli.dll     6.1.7601.17725
C:\Windows\system32\srvcli.dll     6.1.7601.17514
C:\Windows\system32\SHLWAPI.dll     6.1.7601.17514
C:\Windows\system32\shfolder.dll     6.1.7600.16385
C:\Windows\system32\SHELL32.dll     6.1.7601.18103
C:\Windows\SYSTEM32\sechost.dll     6.1.7600.16385
C:\Windows\system32\scrrun.dll     5.8.7600.16385
C:\Windows\system32\rsaenh.dll     6.1.7600.16385
C:\Windows\system32\RpcRtRemote.dll     6.1.7601.17514
C:\Windows\system32\RPCRT4.dll     6.1.7601.17514
C:\Windows\system32\rasadhlp.dll     6.1.7600.16385
C:\Windows\system32\PSAPI.DLL     6.1.7600.16385
C:\Windows\system32\profapi.dll     6.1.7600.16385
C:\Windows\system32\pnrpnsp.dll     6.1.7600.16385
C:\Windows\system32\OLEAUT32.dll     6.1.7601.17676
C:\Windows\system32\ole32.dll     6.1.7601.17514
C:\Windows\SYSTEM32\ntdll.dll     6.1.7601.17725
C:\Windows\system32\NSI.dll     6.1.7600.16385
C:\Windows\system32\NLAapi.dll     6.1.7601.17964
C:\Windows\system32\netutils.dll     6.1.7601.17514
C:\Windows\system32\NETAPI32.dll     6.1.7601.17887
C:\Windows\system32\napinsp.dll     6.1.7600.16385
C:\Windows\system32\MSWSOCK.DLL     6.1.7601.17514
C:\Windows\system32\msvcrt.dll     7.0.7601.17744
C:\Windows\system32\MSVCR100_CLR0400.dll     10.0.30319.1
C:\Windows\system32\MSVBVM60.DLL     6.0.98.15
C:\Windows\system32\MSCTF.dll     6.1.7600.16385
C:\Windows\system32\mscoree.dll     4.0.40305.0
C:\Windows\system32\LPK.dll     6.1.7600.16385
C:\Windows\system32\KERNELBASE.dll     6.1.7601.18015
C:\Windows\system32\kernel32.dll     6.1.7601.18015
C:\Windows\system32\IPHLPAPI.DLL     6.1.7601.17514
C:\Windows\system32\IMM32.DLL     6.1.7601.17514
C:\Windows\system32\GDI32.dll     6.1.7601.17514
C:\Windows\System32\fwpuclnt.dll     6.1.7601.17514
C:\Windows\system32\dwmapi.dll     6.1.7600.16385
C:\Windows\system32\DNSAPI.dll     6.1.7601.17570
C:\Windows\system32\CRYPTSP.dll     6.1.7600.16385
C:\Windows\system32\CRYPTBASE.dll     6.1.7600.16385
C:\Windows\system32\CLBCatQ.DLL     2001.12.8530.16385
C:\Windows\system32\apphelp.dll     6.1.7601.17514
C:\Windows\system32\ADVAPI32.dll     6.1.7601.17514
C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll     4.0.30319.1008
C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll     4.0.30319.237
C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll     10.0.30319.1
C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll     4.0.30319.1001
C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll     4.0.30319.1008
C:\Windows\assembly\NativeImages_v4.0.30319_32\System\1c0a3dbd8b8c2033b811036ff7043ef3\System.ni.dll     4.0.30319.1001
C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\6af6587a49ca918291917ca318dabbbc\System.Xml.ni.dll     4.0.30319.1009
C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\88b9d1c2090f7f3e0e61833ec101923c\System.Windows.Forms.ni.dll     4.0.30319.1002
C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\203d9fcb7dfa54b7923d01ca8bfea8d0\System.Drawing.ni.dll     4.0.30319.1001
C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\af542b07d5ab8851604628f895888336\System.Configuration.ni.dll     4.0.30319.1009
C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\c799474a067f07ef3a167d75029fa012\mscorlib.ni.dll     4.0.30319.1008
C:\ProgramData\Sophos Web Intelligence\swi_lsp.dll     1.0.6.0
C:\PROGRA~1\Sophos\SOPHOS~1\SOPHOS~1.DLL     9.5.7.9577
C:\IBM\InformationServer\Clients\Classic\vmdsrpsENU.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsrpos.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdspass.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsparENU.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsosvENU.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsobj.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsexpr.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsesvENU.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsedit.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsdirENU.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\dssingleton.dll     8.7.0.0
C:\IBM\InformationServer\Clients\Classic\director.exe     8.7.0.0
C:\IBM\InformationServer\ASBNode\apps\proxy\dotnet\xmogrt.DLL     3.1.6.1
C:\IBM\InformationServer\ASBNode\apps\proxy\dotnet\MSVCR71.dll     7.10.3052.4
C:\IBM\InformationServer\ASBNode\apps\proxy\dotnet\MSVCP71.dll     7.10.3077.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\zip.dll     6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\vmi.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\nio.dll     6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\net.dll     6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\jsig.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\jclscar_24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\java.dll     6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9zlib24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9vrb24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9vm24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9vm\jvm.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9ute24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9trc24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\J9THR24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\J9PRT24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9jvmti24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9jit24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\J9HOOKABLE24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9gc24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9dyn24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9dmp24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9bcv24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\iverel24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\HYTHR.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\hyprtshim24.dll     2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\dbgwrapper.dll     6.0.0.0
C:\IBM\INFORM~1\Clients\Classic\DSRPC32.dll     8.7.0.1
C:\IBM\INFORM~1\Clients\Classic\DSOBJE~1.DLL     1.0.0.1
C:\IBM\INFORM~1\Clients\Classic\DSCLNT32.dll     1.0.0.1
When i tried to login to Web console i got below error:-

The server encountered an unexpected condition which prevented it from fulfilling the request. Click here to go back to the previous page.

Can anyone help me to resolve this issue.
Top
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Contact ray.wurlod

Post by ray.wurlod »

Check whether the password to the XMETA database has expired, and whether the WebSphere Application Server instance (server1) is running.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Top
prasson_ibm
Premium Member
Premium Member
Posts: 536
Joined: Thu Oct 11, 2007 1:48 am
Location: Bangalore

Post by prasson_ibm »

I am able to login to server using xmeta userid and password and was is also running.

Code: Select all

dsadm@ait-etl01dev:/home/dsadm $ netstat -a|grep 9043
tcp        0      0  *.9043                 *.*                    LISTEN
Top
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

Is it a new installation? were you able to connect to the server before this issue popped up? Did you do any authentication type changes in the server such as OS authentication or LDAP?

Are you able to login to WAS admin console (not the IS console)?

Hopefully you have to login to WAS admin console and there is a check box on the screen where you select the type of authentication, I do not remember that property but it is on the same screen. Do not change anything just let us know what you see on that screen.

Also 9043 is not the only port you should check for. You should check the services related to DB2 as well as WAS and ASB.

Another question, Are you able to connect to server from another client machine??
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
Top
prasson_ibm
Premium Member
Premium Member
Posts: 536
Joined: Thu Oct 11, 2007 1:48 am
Location: Bangalore

Post by prasson_ibm »

Hi priyadarshikunal
I am not able to connect to server from any client machine.

Is it a new installation? No i am working on this server since last oct.

Were you able to connect to the server before this issue popped up? Yes

Did you do any authentication type changes in the server such as OS authentication or LDAP? I didnt do any authentication changes.I will reconfirm with my team here as well.

Are you able to login to WAS admin console (not the IS console)? How to login to was admin console.I am loggin to
http://etl-dev:9080/ibm/iis/console.

I have checked other services on server(like db2,was,engine,ASB Node) all are up and running.

Are you able to connect to server from another client machine?? No
Top
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Contact ray.wurlod

Post by ray.wurlod »

Basically you have to be a detective, and work out what's changed.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Top
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Re: login failed to connect to datastage server through clie

Post by SURA »

It seems some one might changed the ASB server password.

The server or services might be restarted now only, even the ASB Server password changed long time back!!

Please confirm?
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Top
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

you have to connect to below link considering that the port is default (9043) else the corresponding port should be used. For http, the default port is 9060.

https://etl-dev:9043/ibm/console
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
Top
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

login to WAS admin console using wasadmin (or if the name was different for the WAS administrator the use that) user and then go to security -> global security. on that page check if administrative security and application security options are enabled (they should be, by default).
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
Top
Post Reply

Return to “General”