Visual Admin: Unable to loockup connection default

After HSC JAVA STack I am not able to log on Visual Administrator. I got the erro:
Unable to loockup connection default  
How can I solve this?

You shoul first Check ConfigTool that it is working or not and Secndly how did you clone a System through Export/Import or Restore ?
Regards,
Subhash

Similar Messages

  • Dispatcher service is yellow and unable to start visual admin.

    Hello all:
    Here is my new problem.
    Everything was going fine untill I finished the post installation activites on PI7.0. I am not sure if I missed any step or not.
    After the changes I stopped the instance and restarted it and the "Disp+word.exe" is yellow with the message <b>"Running, Message Server connection ok, Dialog Queue time: J2EE:Some Processes running".</b>
    I can't connect to Visual admin. Getting an error when hit connect "<b>unable to loockup connection default, http:
    sapinst001:8010/msgserver/text/logon returned empty list of conneciton parameters"</b>
    Check the log files and here are some info from them:
    Dev_Server0:
    Thr 1644] *** WARNING => INFO: Unknown property [instance.box.number=PI7DVEBMGS00sapinst001] [jstartxx.c   841]
    [Thr 1644] *** WARNING => INFO: Unknown property [instance.en.host=sapinst001] [jstartxx.c   841]
    [Thr 1644] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 1644] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    Can you please help me with this? I need to finish this install by Monday.
    Regards,
    N.S

    It's important to understand if the dispatcher is not running or just the server is not running: try to look to the log files
    /usr/sap/<SID>/DVEBMGS<nr>/work/dispatcher
    /usr/sap/<SID>/DVEBMGS<nr>/work/server0
    and
    /usr/sap/<SID>/DVEBMGS<nr>/j2ee/cluster/server0/log/defaultTrace.trc
    You should find the error that prevent the java application to start.
    The more common reason are the inability to detect the path of JRE or some parameter wrong in the configtool
    Regards
    Sandro

  • Error access J2EE Visual Admin

    I've just completed installing the SAP NetWeaver 04 Sneak Preview. Unfortunately, TREX is not running (or maybe even installed). I've tried to login to the J2EE admin tool to specify the TREX server but I get the following message:
    Unable to lookup connection default
    http://server:50004/msgserver/test/logon returned empty list of connection parameters.
    Port 50004 is the P4 port for the Java install. I've tried port 50000 but get the same message. Does anyone have any idea?

    Hi Robert,
    Just so there is no confusion - there is no TREX included with the Sneak Preview packages currently available on SDN.
    Regards,
    Kathy Meyers
    SDN

  • Visual admin problem(urgent)

    Hi Gurus,
    its very urgent please help me
    i am getting the below error when i am loging into visual admin
    <b>Error while connecting
    Error in SPNegoLoginModule.</b>
    thanks and Regards,
    Kishore

    Hi,
    Plz check below link
    http://help.sap.com/saphelp_nw04s/helpdata/en/71/540c404a435509e10000000a1550b0/content.htm
    thanks,
    Venkat

  • Error in connecting Visual Admin.

    Hi all , postong a new therad.
    after appying some of the patches we are unable to connect into Visual administrator.The Pop up says:
    com.sap.engine.services.security.except
    ions.BaseLoginException: Can not
    create new Remote LoginCOntext.
    Any clue on this :
    Thanks.

    Hi,
    If you no longer connect to the Visual admin it is better change the password of the user j2ee_admin as mentioned bellow
    You have to change the J2EE Engine administrator password in the secure store as follows:
    1. Start the Config Tool by executing the /usr/sap/<SID>/<Instance name>/j2ee/configtool/configtool script file.
    2. Select secure store.
    3. Select the admin/password/<SID> entry.
    4. Enter the J2EE Engine administrator user new password in the Value field and choose Add.
    5. Choose File -> Apply to save the data.
    6. Restart the J2EE Engine
    Also check this PAG for java Problems.
    [http://help.sap.com/saphelp_nw04s/helpdata/en/6C/7FFB3F6C78EE28E10000000A1550B0/frameset.htm]
    Regards,
    Dhruv Shah

  • Unable to Enter Visual Admin for change of licence key

    Hi all,
    I have installed webdynpro on a stand alone system. As my linence expiry 15 days. I need to update it . But i am unable to entry the visual admin of webdynpro to enter the new license , as it stops at 99%. then in the back ground DOS prompt  throwing exceptions like
    Exception in Thread "Thread-3" java.lang.NullPointerException at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectionAction< LoginTask.java:191>
    com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run<LoginTask.java:191>
    at java.Lang.Thread.run<Unknown Source>
    Regards,
    karthik

    Hi karthik,
    Activate SAP* super user, apply license, deactivate SAP* user.
    http://help.sap.com/saphelp_nw04s/helpdata/en/3a/4a0640d7b28f5ce10000000a155106/frameset.htm
    Best regards, Maksim Rashchynski.

  • Cannot connect to J2EE server through Visual Admin

    Our WAS640 based EP7.0 trial license got expired after 30 days. Then we applied permanent license on the WAS. .
    However J2EE server is not starting. When we try to connect to Visual Administrator getting the following error:
    Unable to lookup connection EPJ
    http://hostname:8102/msgserver/text/logon returned
    version 1.0
    J2EE37079800
    P4     XXXX     50304     LB=1
    JC_XXXX_EPJ_03
    SDM     XXXX     50318     
    Tried to take direct connection through Visual Administrator with Port 50304 but in vain because J2EE server itself is not running.
    Our J2ee server instance no is 03
    I have seen many people posted this question on SDN, but no one updated with the resolution found. Can anyone suggest debug/resolution??
    Thanks

    Multiple causes can generate this error. Some possibilities:
    a) the ciphers between your client and server don't match; validate the Ciphers line /etc/ssh/sshd_config:
    grep Ciphers /etc/ssh/sshd_configb) your sshd is running without host keys (p.e. manually adding sshd to your system after install); generate the host keys:
    /lib/svc/method/sshd -c
    svcadm restart ssh

  • Visual Admin often lost connection

    Hi experts,
    I login to Visual Admin , the connection was lost about 5 seconds.
    If I login again, the connection will lost again.
    It pop-up a message "Ping time out. Conection server  is lost!" .
    But the J2EE is running well, all stutas in MMC is green.
    The userful information in log files as follow :
    Caused by: java.io.EOFException: End of stream is reached unexpectedly during
    input from Socket[addr=/192.168.0.27,port=50704,localport=3748]
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
    com/sap/sldserv/vaclient/ClientManagementGui$WaitForServiceIf
    Caused by: com.sap.engine.services.rmi_p4.NoSuchObjectException: ID:011781:
    Object:<security>
         at
    com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getInitialObject
    (P4ObjectBrokerServerImpl.java:959)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
    (DispatchImpl.java:396)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
    (P4SessionProcessor.java:129)
    exceptions.BaseLoginException: Cannot create new RemoteLoginContext.
    Please give me some advice !
    Thanks.
    BR,
    Jianguo Chen

    Hi
    Check the following link
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/4a/f434417f222004e10000000a155106/content.htm">Ping Timeout – Connection to Server Is Lost</a>
    Hope it helps you..
    Regards
    ambicasony
    null

  • Unable to find the Visual Admin Tool Nw 7.3 Ehp1

    Hi Experts,
    We have Installed the Portal System (NW 7.3 Ehp 1) in that we are unable to find the visual admin Tool in the path drive:\usr\sap\\J00\j2ee. Can you please suggest me how to rectify the error..
    Thanks in Advance...
    Regards,
    Krishna.M

    Dear Krishna,
    Visual admin is no longer supported in NW 7.3. Please find the below link to see all the changes in NW 7.3:
    Nice Blog For All the changes in NW 7.3
    Hope its helpful.
    Regards,
    Deeraj Shetty

  • Server Admin unable to connect to local server

    Hey all. I've been using SLS to serve a Promise RAID via NFS for a few weeks now, and it's been stable and smooth. I've had Server Admin open all that time so I could watch the network usage graph via ARD. Today, Server Admin can no longer connect to the local server. I've tried stopping and starting com.apple.servermgrd but it still cannot connect. Is my only option at this point a reboot?
    Has anyone else experienced this on SLS? I've always had stability issues with Server Admin in the past, but I'd been told the issues had been addressed in SLS. Could someone verify this? Thanks

    I should have been more clear. This is on an 8-core Intel XServe.
    I was able to use Server Admin locally on the machine for weeks. Now I can't. Nothing has changed or been altered on the machine during that period.
    I can not connect to the server via Server Admin remotely or locally. I can connect via SSH, ARD, etc. and the system is still serving NFS just fine, so it's just the process that handles communication with Server Admin that is non responsive.
    Something interesting from the syslog:
    qt1 servermgrd[44258]: servermgr_accounts: noteDirectorySearchPolicyChanged (reopening nodes)
    qt1 servermgrd[44258]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) openLocalLDAPNodeIfNeeded]: dsLocalLDAP = (null) , error = Error Domain=com.apple.OpenDirectory Code=2000 UserInfo=0x1066a16c0 "Unable to open Directory node with name /LDAPv3/127.0.0.1."
    qt1 DirectoryService[31]: DirectoryService has 42000 internal references open (due to clients), warning limit is 2000.
    These lines repeated apprx. every 30 secs until I bounced the servermgrd. Now, I see that entry whenever I try to connect to the local server via Server Admin.
    Now, this system is not a LDAP server, but I understand OSXS still uses LDAP for local directory info... I've tried restarting the related directory services as well, but still no joy.
    It looks like my only recourse is a reboot, which is really not a great option for a dedicated file server. Am I the only one who has ever encountered this issue of Server Admin eventually losing contact with a server?

  • Unable to open the Virus Scan Provider in Visual Admin

    Hello, dear experts!
    [SAP WebAS 6.40 SP13 Windows]
    We have downloaded and installed the latest Anti-Vir dll as a virus scan provider (they are officially certified provider).
    After I tried to activate it gave me error message that the version of anti-virus software is incorrect.
    I restarted the SAP WebAS and since then I can't even get to open the Virus Scan Provider service in Visual Admin anymore.
    The Visual Admin complains on the status line:
    java.lang.ClassNotFoundException: com.sap.security.core.server.vsi.gui.VSIRuntimeControl.
    So I can't even change it back now.
    Please help!

    The problem went away once I rebooted the machine.

  • 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

  • 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

  • Unable to view latest default trace in log viewer

    Hello all,
    We have NW 7.0 J2EE production server. We have a CI and two application servers.
    Our SP level is SP18.
    The DB is oracle and the operating system in RHEL 4.
    I have a problem in viewing the default trace files in log viewer using the visual administrator.
    I am able to view the old default trace but unable to view the latest trace data generated.
    I am facing this problem when i try to view the logs of a particular application server.
    Able to view the latest default trace properly for CI and the other application server. Problem lies only with a single application server.
    I have also check the permissions in OS level for the trace files. Everything looks fine.
    Could some one give me a clue on how to solve this issue.
    Regards,
    Chandru

    Hello Joey,
    The trace file isnt too big....
    We have set the file size as 10 MB.
    We have some 15 to 16 default trace files for each of the server process and we have 3 server process in that application server.
    The ForceSingleTraceFile parameter is set as YES in visual admin.
    So the logs will be displayed in visual admin as a single default trace file.
    Hope I had provided the inputs you have asked...
    Regards,
    Chandru

  • Visual Admin not Starting

    Hello,,
    I am unable to log into my Visual admin. It says "Cannot open connection on host: 64.13.232.162 & port:51004" .
    I dont know which host it is referring to??? That IP is not our servers IP.
    I referred many forums andI checked Port Number on Config Tool. Its correct & i tried with different Transport Layer options but nothing is working??
    Any help on this???

    Hi
    First check the Java stack is up or not.
    If java is up do the following
      open the visual admin
      In the connect to sap j2ee Engine screen
    Select new
    select the lookup method Via message Server
    Display name as Test click Next
    username  :  provide J2ee_admin
      host    : localhost
    HTTP Port : 81(scs instance number) which is java instance number
    click save
    select test and click on connect .
    It will direct to the correct Port
    Give the password and u will login to visual admin

Maybe you are looking for

  • Hallo ich hätte eine Frage zur Adobe Creative Cloud ?!

    Ich bin Schüler .... Wen ich mir ein Jahres Abo der Creative Cloud hole habe ich dann zugriff auf alle Produkte oder wie genau Funktioniert das .... Habe das nicht ganz verstanden ! Möchte After Effects Hauptsächlich .

  • Print driver for hp officejet 6500 unavailable with Windows 8.1

    I have an Asus laptop running Windows 8.1.  Every few days I can not print on our Officejet 6500 e709n.  The message says the print driver is unavailable.  I must then uninstall and reinstall the print driver.  We have a Dell laptop running Windows 7

  • Bulk Upoad of Excel file in oracle data-base

    Hi In my jsp application, I needed a utility which allows the user to locate the Excel-file on his/her machine and upload that data after proper validation in the database. How will I achieve this? Regards sachin

  • ANN: A New Web Widget from PVII

    Similar in concept to jQuery Carousel, Horizontal Glider Magic sets the benchmark for quality, flexibility, features, automation, and accessibility. Horizontal Glider Magic is a panel widget. Hidden content panels are made to glide horizontally throu

  • Apple TV photostream "unable to sign in"??

    Just purchased and installed Apple TV today but when I try to launch Photostream, I keep getting the same error message " Unable to sign in  The icloud Terms of Service have changed.  For more information, go to http://www.apple.com/support/icloud/."