Visual admin authentication failed

Hi Gurus,
I just installed XI server and I have a problem with logging in into the visual admin.Whenever I give the password its says the user authentication failed.I checked it several times, the password and user name are correct.I am also facing a problem in the rep/start/index.jsp .when I try to open this it gives me a ' 500   Internal Server Error ' .Please help me out.

The  error description for the internal server error is :
Message
java.lang.NoClassDefFoundError
Stacktrace
Thrown:
java.lang.NoClassDefFoundError: null
     at com.sap.aii.ibrep.server.transport.api.RepTransportServiceStartup.startupIbrepTransportServices(RepTransportServiceStartup.java:22)
     at com.sap.aii.ibrep.server.applcomp.StartupCodeEntry.startup(StartupCodeEntry.java:442)
     at com.sap.aii.ib.core.applcomp.IStartupCodeEntry.startupIfNotAlreadyDone(IStartupCodeEntry.java:33)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:116)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:383)
     at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:209)
     at jsp_Main1218522199250._jspService(jsp_Main1218522199250.java:21)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Similar Messages

  • Essbase Error 1051440 - Authentication fails for user admin

    We are facing a very unique problem...
    The application is up & running.. even I can login into the application, can perform member addition, editing & mamage database from planning.... but I get this error while retreiving from excel addin or running scripts.
    What I analysed is that this problem is Actually coming when a particular set of members are called anywhere either in scripts or during retreival thru Addin.
    Recently we had added one dimension in one of the database of our application. After that that this problem started.
    There were fewer Xref functions used to pull data from other cubes.... The problem is cominng with only those set of members where this Xref function has been used.
    Even I had changed the formulas & incorporated member of new dimension in the formulas to point to target members....
    Can you guys ever had faced such kind of issue....
    Please help in resolving....
    Complete Error is: msg fromremote site[date n time] Local////Error(1051440) Essbase user[admin] Authentication fails against shared services serverwith Error[30:1005:Authentication failed for user admin. Enter valid credentials.]]

    Hi,
    are you sure that user "admin" has all necessary rights to run your scripts? I have to ask because we sometimes had problems with our admin user... There is an "native essbase server admin" and the admin user in shared services.
    We dont had any idea how this could happen but sometimes our admin user changed to the mentioned "native essbase server admin" - you can see it if you are connected as "admin (internal)".
    If you are logged in as "admin (internal)" you have to "externalize" this user.
    Hope this helps and my bad english is not so much confusing... :-)
    Kind regards
    André

  • User Authentication Failed via http BUT not with Visual Administrator !!?

    OS : Win 2k3 Server UK * DB : SQL Server 2005
    SAP Netweaver 2004s Application Java
    Hi All,
    Since a couple of days, I have a problem concerning authentication to the java apllication on a SAP Netweaver 2004s.
    Using the user ‘Administrator’, I CAN logon the Visual Administrator tool, with the same user I tried to logon via http://host:port/nwa without success.
    At the beginning, I was thinking about a problem of password then I enabled the emergency user SAP*, the problem was the same. Ok with Visual Administrator but not via http.
    Here is two logs found in folder : D:\usr\sap\SID\JC02\j2ee\cluster\server0\log\system\
         security.3.log
         <i>#1.5#001871E5EA3A00550000006D0000172800043B836D838427#1191335570983#/System/Security/Audit#sap.com/com.sap.security.core.admin#com.sap.security.core.util.SecurityAudit#Guest#0####5aac137070f411dcc513001871e5ea3a#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest     | LOGIN.ERROR     | null     |      | Login Method=[default], UserID=[Administrator], IP Address=[192.168.10.125], Reason=[Authentication did not succeed.]#</i>
         server.0.log
         <i>#1.5#001871E5EA3A0052000000130000172800043B835E3661D1#1191335314249#/System/Server/SLDService##com.sap.sldserv.SldServerFrame######c1a349a070f311dcaa68001871e5ea3a#SAPEngine_System_Thread[impl:5]_71##0#0#Warning#1#com.sap.sldserv.SldServerFrame#Plain###Failed to collect SLD data. Failed to send HTTP data: 401 : Unauthorized. Please check if the target SLD system is available and the SLD bridge is started there.#</i>
    &#61664; I tried to connect http://host:port/sld same problem User Authentication Failed
    <b>Do you have an idea for me? Why a user can connect via Visual Administrator and not via the http interface?</b>
    Thanks in advance
    Yves

    Hi,
    I found the solution this last week-end.
    This behavior let's thinking to a problem of authentication.
    But the problem was in SQL, an index was missing in table J2EE_CONFIG, called J2EE_CONFIG_I3
    Cheers
    Yves

  • Authentication did not succeed in Visual Admin On solution manager?

    Hello friends,
       We are unable to log in in visual admin with j2ee_admin default connection. while log in we receiving authentication did not succeed error.
    Please help me to solve this issue.
    Regards,
    Farkath C

    Hello Friends,
       Still we are unable to login to visual admin using J2ee_admin user,
    Please find the Security log,
    If you find any idea to resolve this issue, Please help me.
    #1.5 #001EC94523270053000001170000199000050333FB9C3FF5#1410896683295#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#895##E7B8C5FD3DD911E4AF340000002B7B0E#e7b8c5fd3dd911e4af340000002b7b0e-0#e7b8c5fd3dd911e4af340000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SLDDSUSER
    Authentication Stack: sap.com/com.sap.lcr*sld
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                                true                  #
    #1.5 #001EC9452327004C0000011F0000199000050333FB9E05C9#1410896683405#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#896##E7C9690F3DD911E481880000002B7B0E#e7c9690f3dd911e481880000002b7b0e-0#e7c9690f3dd911e481880000002b7b0e#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SLDDSUSER
    Authentication Stack: sap.com/com.sap.lcr*sld
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                                true                  #
    #1.5 #001EC9452327004B000000EE000019900005033406875E27#1410896866503#/System/Security/Usermanagement##com.sap.security.core.persistence#J2EE_GUEST#0##54E022B53DDA11E48F670000002B7B0E#54e022b53dda11e48f670000002b7b0e-0#54e022b53dda11e48f670000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.security.core.persistence#Java#User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.##User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.#2#J2EE_ADMIN#SLMCLNT100#
    #1.5 #001EC9452327004B000000EF00001990000503340687960E#1410896866518#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##54E022B53DDA11E48F670000002B7B0E#54e022b53dda11e48f670000002b7b0e-0#54e022b53dda11e48f670000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
    User: N/A
    Authentication Stack: SAP-J2EE-Engine
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   SUFFICIENT  ok          exception             true       Authentication did not succeed.#
    #1.5 #001EC9452327004B000000F4000019900005033412BB19D3#1410897071292#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SOLMAN_ADMIN#910##CEF7CEF83DDA11E498040000002B7B0E#cef7cef83dda11e498040000002b7b0e-0#cef7cef83dda11e498040000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SOLMAN_ADMIN
    Authentication Stack: sap.com/com.sap.lcr*sld
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                                true                  #
    #1.5 #001EC9452327005700000144000019900005033412BBC3C3#1410897071339#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SOLMAN_ADMIN#911##CF03B6AC3DDA11E4A9C90000002B7B0E#cf03b6ac3dda11e4a9c90000002b7b0e-0#cf03b6ac3dda11e4a9c90000002b7b0e#SAPEngine_Application_Thread[impl:3]_34##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SOLMAN_ADMIN
    Authentication Stack: sap.com/com.sap.lcr*sld
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                                true                  #
    #1.5 #001EC9452327008900000005000019900005033417E870E1#1410897158131#/System/Security##com.sap.engine.services.keystore####4EF963E63DAE11E4A2050000002B7B0E#4ef963e63dae11e4a2050000002b7b0e-0#4ef963e63dae11e4a2050000002b7b0e#Thread[ExRun:SMD_MGR_26,10,SMD_MGR:ExecTG]##0#0#Error#1#com.sap.engine.services.keystore#Java###Source: com.sap.engine.frame.core.configuration.NameNotFoundException: A file entry with the name "SMDAgent-cert" cannot be found in the configuration "keystore/TrustedCAs/entries".; Description: EntriesStorage - readEntry(SMDAgent-cert) in configuration [keystore/TrustedCAs/entries] failed with unexpected exception; Consequences: ; Countermeasures:check log for details##
    #1.5 #001EC945232700500000012800001990000503341E810CD6#1410897268826#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SM_INTERN_WS#918##001EC94523271EE48CE20FF9FB774D30#AC14008B0CDC54189574001F00000000-0#43DB3DE44884F13EB530001EC9452327#SAPEngine_Application_Thread[impl:3]_28##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SM_INTERN_WS
    Authentication Stack: sap.com/tc~smd~ws~agent~monitoring*SMDAgentMonitoring_DataProvider
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT  ok          exception  false                 Received no SAP Authentication Assertion Ticket.
    3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   OPTIONAL    ok          true       true                 
    4. com.sap.security.core.server.jaas.CreateTicketLoginModule               SUFFICIENT  ok          true       true                 
    Central Checks                                                                                                true                  #
    #1.5 #001EC9452327007E0000011100001990000503341E81D7E9#1410897268873#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SM_INTERN_WS#919##001EC94523271EE48CE20FF9FB774D30#AC14008B0CDC54189574002000000000-0#43DB3DE44884F13EB530001EC9452327#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SM_INTERN_WS
    Authentication Stack: sap.com/tc~smd~ws~agent~monitoring*SMDAgentMonitoring_DataProvider
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT  ok          exception  false                 Received no SAP Authentication Assertion Ticket.
    3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   OPTIONAL    ok          true       true                 
    4. com.sap.security.core.server.jaas.CreateTicketLoginModule               SUFFICIENT  ok          true       true                 
    Central Checks                                                                                                true                  #
    #1.5 #001EC94523270053000001280000199000050334253E502B#1410897381878#/System/Security/Usermanagement##com.sap.security.core.persistence#J2EE_GUEST#0##DC2A72A83DDA11E4CB770000002B7B0E#dc2a72a83dda11e4cb770000002b7b0e-0#dc2a72a83dda11e4cb770000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.security.core.persistence#Java#User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.##User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.#2#J2EE_ADMIN#SLMCLNT100#
    #1.5 #001EC94523270053000001290000199000050334253E5151#1410897381878#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##DC2A72A83DDA11E4CB770000002B7B0E#dc2a72a83dda11e4cb770000002b7b0e-0#dc2a72a83dda11e4cb770000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
    User: N/A
    Authentication Stack: SAP-J2EE-Engine
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   SUFFICIENT  ok          exception             true       Authentication did not succeed.#
    #1.5 #001EC9452327008A00000102000019900005033431310D8E#1410897582354#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#931##FF9A34B63DDB11E4BB010000002B7B0E#ff9a34b63ddb11e4bb010000002b7b0e-0#ff9a34b63ddb11e4bb010000002b7b0e#SAPEngine_Application_Thread[impl:3]_3##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SLDDSUSER
    Authentication Stack: sap.com/com.sap.lcr*sld
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                                true                  #
    #1.5 #001EC94523270084000000FF000019900005033431329358#1410897582463#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#932##FFAADBF23DDB11E4B6910000002B7B0E#ffaadbf23ddb11e4b6910000002b7b0e-0#ffaadbf23ddb11e4b6910000002b7b0e#SAPEngine_Application_Thread[impl:3]_6##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
    User: SLDDSUSER
    Authentication Stack: sap.com/com.sap.lcr*sld
    Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
    1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
    2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
    3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
    Central Checks                                                                                                true                  #
    Regards,
    Farkath C

  • User Authentication Fails,Unless Admin resets the pwd,user cannot logon.

    Hi
    I have a EP7 SP18 Portal .
    The portal UME is Readonly Microsoft LDAP + UME Database.
    I have a user named testuser which exists in Both the UME's.
    the testuser of LDAP is locked through Portal User admin.
    Now whenever the testuser tries to logon to portal,he gets User Authentication Failed message.
    The failed logon  attempt info is not reflcted  in User Account details.when viewd through portal user admin.
    if Administrator resets the Password of testuser in portal,then user is able to logon to the portal using this password.
    Next day,again same thing happens.
    what can be the reason behind this ?
    Regards
    Rajendra

    invalid now.

  • "User authentication failed" when connecting with Visual Administrator

    Hello,
    I am having trouble making a connection to my local J2EE Engine using the Visual Administrator (VA).
    I open the VA interface and create a new connection. The default User Name is "Administrator". I put in "localhost" for host, "50004" for port and leave the Transport Layer selection to "Default".
    When I try to connect this way I get the following message:
    User authentication failed
    Next I went into Start|Settings|Control Panel|Users and Passwords  and saw that there were several ids created by the Developer Workplace (DW) installation. The ids that I see are: j2eadm,sapadmin,sapinstall and SAPServiceJ2E
    I checked all of them to see what groups they're members of and they're all at least members of "Administrators" group.
    There are also 3 new groups that must have been created by the DW installation: SAP_J2E_GlobalAdmin, SAP_J2E_LocalAdmin and SAP_LocalAdmin.
    The j2eadm id belonged to all 3 new sap groups so I changed its password to something I'd remember and then changed the connection to use that login.
    When I tried to connect thru VA using this id and the new password I still get the "User authentication failed" error message.
    Can anyone please tell me what I'm doing wrong?
    Thanks in advance for any help.
    David.

    Hi,
    During the installation the SAPINST asks for a Administrator  Password.. This password is very important.
    We had kept same passwords for all userids to start with.
    This helped reduce lot of confusion.
    Warning: if you enter the wrong password 5 times, the userid 'Administrator' gets locked.
    However there is an Emergency password recovery procedures.
    Try this link
    http://help.sap.com/saphelp_erp2004/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm
    Hope that helps
    Regards,
    Siddhesh

  • Admin Console Authentication Fails

    When the credentials for a Groupwise System Administrator contains a colon, the authentication fails for the Administration Console...
    Recently had same bug fixed in Sentinel's web interface SAML token... Bug 817681

    Never mind, found that it was admin user that caused the issue. Bug will be written
    --Morris
    >>> Morris Blackham<[email protected]> 5/19/2014 9:04 AM >>>
    when you say credentials, are you referring to the admin name or the password, or both?
    Inquiring minds need to know to write a proper defect...
    --Morris
    >>> ScorpionSting<[email protected]> 5/16/2014 8:36 PM >>>
    When the credentials for a Groupwise System Administrator contains a
    colon, the authentication fails for the Administration Console...
    Recently had same bug fixed in Sentinel's web interface SAML token...
    Bug 817681
    *Deja Moo:* The feeling you've heard this bull before.
    ScorpionSting's Profile: https://forums.novell.com/member.php?userid=1663
    View this thread: https://forums.novell.com/showthread.php?t=477090

  • User authentication failed when user is locked by system admin

    Hello!
    We have EP 6.0 (SP 18) and ABAP Backed 6.40 (SP21).  UME is connected to the backend system for user managment.
    When we try to log on to EP with a user that is locked by the system admin in the backend, the message shown is "User authentication failed".
    Should it be possible to show a message as "User locked by system admin", for the user to know the reason?
    Thanks in advance and regards!

    Hi,
    We are using SAP EP7 and BW7 SP15. We are getting proper messages in portal when account is locked at BW System.
    Regards
    Baby

  • Nw 7.3 user admin lock : Authentication failed. Password locked

    Hi expert.
    please help me
    i have a portal nw 7.3, but idont acceces ,  the administrator user  is lock.
    how i can this user?

    Please avoid double postings.
    The original question (where answers should be put, too) is here: Nw 7.3 user admin lock : Authentication failed. Password locked

  • Authentication Failed :  BPEL Console and BPEL Admin

    Hi ,
    I am trying to log in to BPEL Console repeatedly. I am using the user oc4jadmin. I have logged in successfully previously using oc4jadmin.
    I read somewhere that a workaround is
    "Workaround is you take login_error.jsp off from URL http://<host>:<port>/BPELConsole/login_error.jsp, So your URL would look like http://<host>:<port>/BPELConsole/. This will automatically log you in. Since the problem was with redirection and not with your credentials"
    This is also not working for me.
    Could it be possible that I have locked this account ? Is so, how can I unlock it .
    Any suggestions on why I get repeatedly Authentication Failed ?

    Hi ,
    Thanks for the response .
    This the log from opmn/logs/default_group~oc4j_soa~default_group~1.log
    09/08/17 14:14:33 ############# statusFilter = ASSIGNED###########
    09/08/17 14:14:33 ############# session = oracle.portal.provider.v2.http.ServletProviderSession@1ee1212###########
    09/08/17 14:14:33 ############# wlCtxKey = _piref985378135.worklistContext###########
    09/08/17 14:14:33 ############# ctx = null###########
    09/08/17 14:14:33 ############# wlRmtUserKey = _piref985378135.remoteUser###########
    09/08/17 14:14:33 ############# sessionRemoteUser = null###########
    09/08/17 14:14:33 ############# currentRemoteUser = null###########
    09/08/17 14:14:33 ############# filterPredicate = ( wfn.State IN (?,?))############
    09/08/18 13:07:52 BI Beans Graph version [3.2.2.0.24]
    09/08/18 13:07:55 Tue Aug 18 13:07:55 CEST 2009 PROBLEM: In oracle.dss.thin.beans.graph.ThinGraph::setTabularData: all relational rows are null
    09/08/18 13:07:55 BI Beans Graph version [3.2.2.0.24]
    09/08/18 13:07:55 BI Beans Graph version [3.2.2.0.24]
    09/08/18 13:07:55 Tue Aug 18 13:07:55 CEST 2009 PROBLEM: In oracle.dss.thin.beans.graph.ThinGraph::setTabularData: all relational rows are null
    09/08/18 13:07:55 BI Beans Graph version [3.2.2.0.24]
    09/08/18 13:07:55 Tue Aug 18 13:07:55 CEST 2009 PROBLEM: In oracle.dss.thin.beans.graph.ThinGraph::setTabularData: all relational rows are null
    09/08/18 13:07:55 Tue Aug 18 13:07:55 CEST 2009 PROBLEM: In oracle.dss.thin.beans.graph.ThinGraph::setTabularData: all relational rows are null
    09/08/18 13:09:09
    ConnectionPoolManager uiauthpool intialized with url=jdbc:oracle:thin:@//SHK-ORADEVAPP02.HK.INDISKA.SE:1521/orcl.hk.indiska.se driver=oracle.jdbc.driver.OracleDriver user=ORAWSM maxConn=5
    [oraias@SHK-ORADEVAPP02 logs]$

  • "Authentication failed. User is already authenticated as a different user."

    Hello,
    Initially I was not able to log into the Visual Admin. When I logged into the Visual Admin, I got authenication failed. I reset the password of Administrator in the User Administration on the portal. Now I can log into the Visual Admin using the password I just changed on the portal .
    I am not able to logon to the portal using "Administrator". I get this message: "Authentication failed. User is already authenticated as a different user."
    The URL is somewhat different as this is a production portal: "http://host.com/sld" (/irj/portal)
    Does any one have a clue.
    Thanks
    Srinivas

    There were no relevant roles assigned.

  • Visual Admin Login

    Hello,
    We have Netweaver 7.0 ABAP+Java.
    I copied used J2EE_ADMIN to J2EE_ADMIN1 in the UME data source client - 400.
    User type - Service User
    I created a new connection in Visual Admin using Message Server
    Entries -
    User name : J2EE_ADMIN1
    Host: ASMVTOL14 (hostname of server)
    HTTP Port: 8101 (message server is on instance 01)
    Load Balancing Method: Random
    Transport Layer: Default
    But when I try to connect using the new connection and user J2E_ADMIN1. It gives me error - User Authentication failed.
    However, the password is correct. I am able to log into Client 400 of ABAP using the same credentials.
    I checked the Logs(defaulttrace) and there is no error in that.
    kindly help.

    Hi Gautam,
    If the UME database is ABAP System, you cannot modify in the portal as if some restrictions are placed for the same.
    You can modify the J2EE_ADMIN1 in the backend system SU01...
    As per details for connecting visual admin
    User name : J2EE_ADMIN1
    Host: ASMVTOL14 (hostname of server)
    HTTP Port: 8101 (message server is on instance 01)
    Load Balancing Method: Random
    Transport Layer: Default
    Please re-check the message server port. and try again
    Hope it helps
    Regards
    Arun

  • Portal administrator authentication failed

    Hi all
    i instald a new netwaever 2004s portal wite xi and sld abap +Java .
    in the installion i used the same password fur all users option,
    the installation finish successfully.
    when i am traing to logon the portal useng administrator and the password i enter in the installion i get authentication failed,
    i dont think i mead a mistake in the password ,
    the password is fine in the visual admin and in the sql plus .
    Could any one please help on this one.
    Thanks and Regards

    Hi,
    if you are able to login to server through SAP LOGON , then you need to check for the authorizations....
    from sap easy access you go to SU01 and check for the roles.....and on the Integration Builder screen click on administration and check for the roles in Java Stack....
    hopefully you can solve your problem...
    Thanks,
    Madhu

  • Error while creating RFC Jco provider in visual Admin

    Hi,
    I have crated a rfc jco provider in visual admin , I have given all the ECC related details both in registered server AND Spcific application server. In both of these I have given R/3 related details like host of ecc and all.
    All i have given correct used ID and passowrd also (I am using my own user id and password in this jco rfc provider). that user id is there in ecc with sap all in profile and in roles also i have given 2 roles for that used id, namely sap_bc_jsf_communication AND sap_bc_usr_cua_client_rfc
    Still when i try to  start it its giving me error:  Error starting bundle
    please help

    This I am getting:
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=sapecdsrv SYSNR=00 GWHOST=sapecdsrv GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       hostname 'sapecdsrv' unknown
    TIME        Wed May 26 14:26:21 2010
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -2
    MODULE      nixxhsl.cpp
    LINE        223
    DETAIL      NiHsLGetNodeAddr: hostname cached as unknown
    COUNTER     2
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
    at com.sap.mw.jco.JCO$Pool.initPool(JCO.java:4725)
    at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6180)
    at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6135)
    at com.sap.mw.jco.JCO.getClient(JCO.java:8803)
    at com.sap.engine.services.rfcengine.Bundle.startAll(Bundle.java:248)
    at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(RFCRuntimeInterfaceImpl.java:350)
    at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.changeBundleConfiguration(RFCRuntimeInterfaceImpl.java:654)
    at sun.reflect.GeneratedMethodAccessor401.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
    at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
    at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
    at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
    at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
    at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
    at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
    at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
    at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
    at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
    at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
    at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
    at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
    at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
    at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
    at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(AccessController.java:219)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172

  • ERROR: Ldap Authentication failed for dap during installation of iAS 6.0 SP3

    I am attempting to install ias Enterprise Edition (6.0 SP3) on solaris 2.8 using typical in basesetup. I am trying to install new Directory server as I don't have an existing one.
    During the installation I got the following error.
    ERROR: Ldap Authentication failed for url ldap://hostname:389/o=NetScape Root user id admin (151: Unknown Error)
    Fatal Slapd did not add Directory server information to config Server.
    Warning slapd could'nt populate with ldif file Yes error code 151.
    ERROR:Failure installing iPlanet Directory Server.
    Do you want to continue: ( I entered yes )
    Configuring Administration Server Segmentation fault core dumped.
    Error: Failure installing Netscape Administration Server.
    Do you want to continue:( I responded with yes).
    And during the Extraction I got the following
    ERROR:mple_bind: Can't connect to the LDAP server - No route to host
    ERROR: Unable to connect to LDAP Directory Server
    Hostname: hostname
    Port: 389
    User: cn=Directory Manager
    Password: <password-for-cn=Directory Manager
    Please make sure this Directory Server is currently running.
    You might need to run 'stop-slapd' and then
    'start-slapd' in the Directory Server home directory, in order to restart
    LDAP. When finished, press ENTER to continue, or S to skip this step:
    Start registering Bootstrap EJB...
    javax.naming.NameNotFoundException
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled > Code)
    at javax.naming.NamingException.<init>(NamingException.java:114)
    at javax.naming.NameNotFoundException.<init>(NameNotFoundException.java: 48)
    at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
    "ldaperror" 76 lines, 2944 characters
    at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
    at com.netscape.server.jndi.RootContext.bind(Unknown Source)
    at com.netscape.server.jndi.RootContext.bind(Unknown Source)
    at javax.naming.InitialContext.bind(InitialContext.java:371)
    at com.netscape.server.deployment.EjbReg.deployToNaming(Unknown Source)
    at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled Code)
    at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled Code)
    at com.netscape.server.deployment.EjbReg.run(Compiled Code)
    at com.netscape.server.deployment.EjbReg.main(Unknown Source)
    Start registering iAS 60 Fortune Application...
    Start iPlanet Application Server
    Start iPlanet Application Server
    Start Web Server iPlanet-WebServer-Enterprise/6.0SP1 B08/20/200100:58
    warning: daemon is running as super-user
    [LS ls1] http://gedemo1.plateau.com, port 80 ready
    to accept requests
    startup: server started successfully.
    After completion of installation, I tried to start the console. But I got the following error;
    "Cant connect ot the admin server. The url is not correct or the server is not running.
    Finally,when I started the admintool(iASTT),it shows the iAS1
    was registered( marked with a red cross mark) and says "cant login. make sure the user
    name & passwdord are correct" when i click on it.
    Thanks in advance for any help
    Madhavi

    Hi,
    Make sure that the directory server is installed first. If it is running
    ok, then you can try adding an admin user, please check the following
    technote.
    http://knowledgebase.iplanet.com/ikb/kb/articles/4106.html
    regards
    Swami
    madhavi korupolu wrote:
    I am attempting to install ias Enterprise Edition (6.0 SP3) on
    solaris 2.8 using typical in basesetup. I am trying to install new
    Directory server as I don't have an existing one.
    During the installation I got the following error.
    ERROR: Ldap Authentication failed for url
    ldap://hostname:389/o=NetScape Root user id admin (151: Unknown
    Error)
    Fatal Slapd did not add Directory server information to config
    Server.
    Warning slapd could'nt populate with ldif file Yes error code 151.
    ERROR:Failure installing iPlanet Directory Server.
    Do you want to continue: ( I entered yes )
    Configuring Administration Server Segmentation fault core dumped.
    Error: Failure installing Netscape Administration Server.
    Do you want to continue:( I responded with yes).
    And during the Extraction I got the following
    ERROR:mple_bind: Can't connect to the LDAP server - No route to host
    ERROR: Unable to connect to LDAP Directory Server
    Hostname: hostname
    Port: 389
    User: cn=Directory Manager
    Password: <password-for-cn=Directory Manager
    Please make sure this Directory Server is currently running.
    You might need to run 'stop-slapd' and then
    'start-slapd' in the Directory Server home directory, in order to
    restart
    LDAP. When finished, press ENTER to continue, or S to skip this
    step:
    Start registering Bootstrap EJB...
    javax.naming.NameNotFoundException
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled > Code)
    at javax.naming.NamingException.<init>(NamingException.java:114)
    at
    javax.naming.NameNotFoundException.<init>(NameNotFoundException.java:
    48)
    at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
    "ldaperror" 76 lines, 2944 characters
    at com.netscape.server.jndi.RootContext.resolveCtx(Unknown Source)
    at com.netscape.server.jndi.RootContext.bind(Unknown Source)
    at com.netscape.server.jndi.RootContext.bind(Unknown Source)
    at javax.naming.InitialContext.bind(InitialContext.java:371)
    at com.netscape.server.deployment.EjbReg.deployToNaming(Unknown
    Source)
    at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled
    Code)
    at com.netscape.server.deployment.EjbReg.registerEjbJar(Compiled
    Code)
    at com.netscape.server.deployment.EjbReg.run(Compiled Code)
    at com.netscape.server.deployment.EjbReg.main(Unknown Source)
    Start registering iAS 60 Fortune Application...
    Start iPlanet Application Server
    Start iPlanet Application Server
    Start Web Server iPlanet-WebServer-Enterprise/6.0SP1 B08/20/200100:58
    warning: daemon is running as super-user
    [LS ls1] http://gedemo1.plateau.com, port 80 ready
    to accept requests
    startup: server started successfully.
    After completion of installation, I tried to start the console. But I
    got the following error;
    "Cant connect ot the admin server. The url is not correct or the
    server is not running.
    Finally,when I started the admintool(iASTT),it shows the iAS1
    was registered( marked with a red cross mark) and says "cant login.
    make sure the user
    name & passwdord are correct" when i click on it.
    Thanks in advance for any help
    Madhavi
    Try our New Web Based Forum at http://softwareforum.sun.com
    Includes Access to our Product Knowledge Base!

Maybe you are looking for

  • Macbook Pro does not turn on, service battery

    Heres the backstory. One day, my mac simply wouldnt turn on. No video, no chime. Just one indicator light turns on, then turns off a few seconds later. then turns back on. After that happened, I brought my laptop to school the next day and plugged my

  • Mail attachments come through as winmail.dat

    When I send out mail from MS Outlook enterprise account in the office to my Mac at home they are received as "winmail.dat" files.  Even if I perform a "save as" to the correct file name the file format is still not recognized.  Why is this happening!

  • How can I change desktop size of remote slave mac?

    Hi I use a setup of one mac controlling 2 other macs for audio purpose. This means that I have one mac with a Cinema display connected and the 2 other macs without any monitor connected. Have can I decide the desktop size of the 2 connected macs with

  • PDF Viewer Not Working Some Scanned PDF Files.

    I Have Firefox Latest Version. I Want To View PDF files in Firefox without downloading them. But Firefox PDF Viewer Not Working Scanned PDF. Other Browsers Can View It. http://t.co/teYs9LOtyq This Is A Serious Problem & Please Fix This Issue. Thank Y

  • Help for 'SO_NEW_DOCUMENT_ATT_SEND_API1'

    I am using this function module: CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'       EXPORTING     DOCUMENT_DATA                    = wa_doc_chng   PUT_IN_OUTBOX                    = ' '   COMMIT_WORK                      = ' '     IMPORTING   SENT_T