XI 7.0 Visual Admin issue

Hello,
I am trying to install XI 7.0 (NW 2004s). The installation was error-free. However, while doing post installation steps, Visual Admin threw a 'Session expired' error. Since then, I am unable to login to Visual Admin using J2EE_ADMIN (throws "Authentication did not succeed" error). I have activated SAP* user using configtool, and unlocked J2EE_ADMIN. I have also changed J2EE_ADMIN password several times using SAP GUI.
But still, the error persists.
Please let me know if anyone has a solution.
Thanks in advance
Partha

Hi Partha,
Try opening Visual Admin if your not able to login with username(administrator) and password. Problem with NWD2004s do the following steps.
C:\usr\sap\J2E\JC01\j2ee\configtool->configtool.bat->open it
1. Click on Secure store
2. Right you will find :
admin/password/J2E->retype your admin passowrd which you gave during installation=>SAVE properly
Restart the server and try login visual admin
Now ur able to login visual admin right follow the steps:
Try here If ur not able to login http://<server name>/irj/portal :home page using (username)administrator and password
do the following steps(user locked).
(**Administrator locked so we have enable superadmin and unlock the administrator and again diasble the super admin
then only can able to login using administrator**)
=>Activating emergency(super admin) user:-
1. Start configtool
2. set the following properties: [Instance_ID<ID> -> Server_ID<ID> -> services -> com.sap.security.core.ume.service]
a. ume.superadmin.activated - true
=>i doubht here did u saved properly
b. ume.superadmin.password - <password> [set the password->click set button->
it will again ask by open popup window type the same and it will say restart to reflects]
3. Restart Java Application server
Unlocking administrator:
Login to Portal Page => http://<severname>/irj/portal
Give username:SAP* and password which u typed
=>under user management tab ->click on search user left pane -> search label followed by input field will be there ->give * in inputfield and click search button->
you can we view ALL users and roles etc.
select user administration by clicking on check box ->modify->reset the password->save properly
Again diable super admin go to
1. Start configtool
2. set the following properties: [Instance_ID<ID> -> Server_ID<ID> -> services -> com.sap.security.core.ume.service]
a. ume.superadmin.activated - false->save it will ask u restart is must for reflect the settings
3. Restart Java Application server
Go to http://<severname>/irj/portal
Give username:aministrator and password which u typed
hopefully i should solve ur problem
Regards, Suresh KB

Similar Messages

  • Visual Admin Issue

    Experts ,
    I want to know about Visual Admin and ConFig Tool and in How many ways they  are used
    list out all briefly ,
    Thanks in  Advance,
    Phani

    Hi Phani,
    The J2EE Engine Visual Administrator is a graphical user interface (GUI) that enables administration of the whole cluster, all cluster elements, and all modules running on them. It provides remote monitoring and management of managers, services, libraries, and interfaces working on each element in a single GUI
    Visual Administrator includes functions for:
    a) Obtaining general information about a service, manager, interface, or library (for example, its name, group,    and so on).
    b) Logging on to the J2EE Engine via the Visual Administrator tool
    c) Administrating and changing the properties either specific or common for each service or manager
    d) Configuring the global properties
    e) Runtime administration and control.
    Read out more about its features on [VISUAL ADMINISTRATOR|http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm]
    CONFIG TOOL :-
    The Config Tool enables offline configuration of the J2EE Engine cluster elements. It is XML-based and allows exporting the system configuration for later use.
    When you run the J2EE Engine Config Tool via a GUI or text-only interface, it connects to the database and scans the server configuration. The information provided is passed to the corresponding interface that is used for configuration.
    Each change you can perform corresponds to a particular task in the Batch Config tool.
    All modifications made using the J2EE Engine Config Tool can be exported to an XML file for later use.
    two types:-
    a) GUI Config tool :- The J2EE Engine GUI Config Tool enables offline configuration of J2EE Engine cluster elements concerning serviceu2019s and manageru2019s properties, adding new server processes, changing Java parameters, exporting the system configuration to an XML file, and so on.
    After installing the SAP Web AS Java, a configtool directory is created, containing a configtool script file. Double clicking on this file starts the Config Tool.
    b) Text Only Config tool:- The text-only Config Tool enables you configuration of J2EE Engine cluster elements using a text-only based interface. It enables you to change the cluster element properties, JVM settings, add new elements, export the system configuration to an XML file, and so on.
    After installing SAP Web AS Java, a configtool directory is created under <SAP_install_dir>/<system_name>/<instance_name>/j2ee, containing a consoleconfig script file. Double clicking on this file starts the text-only Config Tool.
    Read more about config tool on  [CONFIG TOOL|http://help.sap.com/saphelp_nw04/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htm]
    Hope this helps,
    Regards,
    Shailesh

  • NW2004s(SP19) Visual Admin issue

    Hi,
    I could not login to the VA due to the following issue;
    Error while connecting
    com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext.
    The log of visual_administration.0.trc show as:
    #1.5 #C0000A1F12130000000000000161F39E0004853110463D48#1272345664070#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#######Thread[Thread-10,5,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.Parser newRequest MSG:The possible problem is that there is no correctly working server node available. Check your working servers#
    #1.5 #C0000A1F12130001000000010161F39E000485311051E990#1272345680538#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-2,5,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Java###Error while trying to login to ord-sapprtdev.serena.com: Cannot create new RemoteLoginContext.
    [EXCEPTION]
    #1#com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext.
         at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:71)
         at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectAction(LoginTask.java:98)
         at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run(LoginTask.java:81)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:709)
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:697)
         at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
         ... 1 more
    Any help in this regard would highly appreciated.
    Kind regards,
    Vijay

    Hi
    Please check the  Java VM settings for J2EE 6.40/7.0 as per note 723909  as wrong setting can be a cause of this issue
    Regards
    Priyanka

  • MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin

    Hi,
    I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
    The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
    This is the setup I used:
    JDBC Version "2.0 (with XA support)
    JDBC 2.0 Compliant:
      object factory:  com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
      datasource type: XADataSource
      xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
    On the additional tab:
    databaseName=fldev_jj
    portNumber=1433
    serverName=dbsrv61
    user=fldev_jj
    password=******
    Even added the url, but that made no difference. Chose Vendor SQL,
    and have initial connections set to 1. This url worked when used
    with a version 1.x datasource.
    What can I try to do to resolve this?
    Full exception:
    java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         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:320)
         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)
         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)
    Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         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:320)
         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)
         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)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
         ... 42 more
    Caused by: java.sql.SQLException: Invalid DataSource reference.
         at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
         ... 43 more
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         ... 31 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         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:320)
         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)
         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)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
         ... 42 more
    Caused by: java.sql.SQLException: Invalid DataSource reference.
         at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
         ... 43 more
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         ... 33 more
         at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
         at javax.management.MBeanException.writeObject(MBeanException.java:126)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
         at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
         at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
         at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
         at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
         at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         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)
         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)

    Leaving the object factory empty is absolutely part of the solution.
    I can now start the data source and it can get a connection.
    The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
    The problem with that is that I'm no longer sure it uses XA transactions...
    Will do more testing...
    Very helpful reply Yuri!
    Thanks

  • Visual Admin - Dispatcher - Monitoring Node issue

    Hi all,
    On a PI 7.0 SP13,
    In visual admin, the monitoring node of the dispatcher section doesn't start fully :
    Only both tabs "Properties" and "Additional Infos" are available.
    When we try to start the Monitoring service manually, we got the following error message :
    Start service Monitoring
    java.rmi.RemoteException: Could not start service monitor on cluster ID 4226000; nested exception is:
         com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Service monitor error. Nested exception is: java.lang.NoClassDefFoundError: com/sap/mona/api/MonitoringNode
         at com.sap.engine.services.monitor.common.MonitorServiceRuntime.installCcmsConnector(MonitorServiceRuntime.java:662)
         at com.sap.engine.services.monitor.dispatcher.MonitorDispatcherFrame.start(MonitorDispatcherFrame.java:53)
         at com.sap.engine.frame.CommunicationFrameAdaptor.start(CommunicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
         at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
    ', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Service monitor error. Nested exception is: java.lang.NoClassDefFoundError: com/sap/mona/api/MonitoringNode
         at com.sap.engine.services.monitor.common.MonitorServiceRuntime.installCcmsConnector(MonitorServiceRuntime.java:662)
         at com.sap.engine.services.monitor.dispatcher.MonitorDispatcherFrame.start(MonitorDispatcherFrame.java:53)
         at com.sap.engine.frame.CommunicationFrameAdaptor.start(CommunicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:228)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:158)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)
         at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)
    Do you have an idea to solve this issue.
    Thanks a lot in advance
    Edited by: Jean-Charles on Feb 14, 2008 5:02 PM

    It is correct one
    sorry
    The monitoring service is red cross marked as it is not started. when we do rigth click and start we have the message quoted above...

  • Visual admin : logon issue

    Hello sdn,
    while I navigate to j2ee folder ,I dont see admin folder.
    I am logging on as SIDADM
    I want to open visual administrator. I am using PI 7.1.
    Can you suggest how to open visual admin?
    Thanks

    Hi,
    /people/suneet.agera/blog/2008/02/18/sap-landscape-administration-and-java-system-administration-an-overview
    Thanks
    Anil

  • Error in creating MSSQL 2005 server Datasource in visual admin

    I need to create a datasource in Visual Admin for SQL Server 2005. I have already downloaded the JDBC Driver for SQL server 2005 and while creating the driver in visual admin I specified sqljdbc.jar from the downloaded directory.
    Then created the datasource, filling out the following properties:
    o Main tab > DataSource Name: fx “MyDatasource”
    o Main tab > Add Alias: fx “MyAlias”
    o Main tab > Driver Name: SQL Server
    o Main tab > JDBC version: 2.0 (with XA support)
    o Main tab > Object factory: com.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory
    o Main tab > DataSource Type: ConnectionPoolDataSource
    o Main tab > CPDS classname: com.microsoft.jdbcx.sqlserver.SQLServerDataSource
    o Additional tab > add property “serverName = <myserver>,
    o Additional tab > add property “databaseName = <mydb>,
    o Additional tab > add property “portNumber = <port>, fx 1433”
    o Additional tab > add property “user = <sql database user>, fx sa”
    o Additional tab > add property “password = <password>”
    Then I set the initial connections to 1. On saving, I was shown an error saying:
    Causedby: java.lang.ClassNotFoundException:com.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory
    Then I tried with SAP’s Driver for MSSQL, giving the parameters as:
    Driver Name: SYSTEM_DRIVER
    JDBC Version: 1.x
    Driver Class: com.sap.portals.jdbc.sqlserver.SQLServerDriver.class
    Database URL: jdbc:sap:sqlserver://<myserver>:1433;DatabaseName=<mydb>
    On saving an error was generated saying:
    Causedby:java.lang.ClassNotFoundException:com.sap.portals.jdbc.sqlserver.SQLServerDriver.class
    Where have I gone wrong? Pls help.
    Regards
    Shyam.
    <b></b><b></b>

    hi all,
    i have solved the issue.
    it was due to the changes in formats of the driverclass name&URl for accessing SQLServer2005.
    Details:
    in SQLServer2000:
    the driverclass name format is like:
    com.sqlserver.microsoft.jdbc.SQLServerDriver
    but in SQLServer2005 it is:
    com.microsoft.sqlserver.jdbc.SQLServerDriver
    and
    the URL in SQLServer2005 should be of the format:
    jdbc:sqlserver://<server>:1433;DatabaseName=<db>
    instead of SQLServer2000's
    jdbc:microsoft:sqlserver://<server>:1433;DatabaseName=<db>.the prefix has
    changed.
    i selected JDBC version as 1.x.
    now its working fine and i cud fetch data from the db in my Web dynpro appln.
    Thanks a lot.
    regards
    shyam.

  • Virsa application components not found in Visual Admin tool (GRC AC 5.3)

    Hi experts,
    I have this weird issue. I was trying to run the background job to synch the backend roles, users and profiles in CC. But when I checked the background job deamon through this link
    http://209.207.245.71:50000/sap/CCADStatus.jsp  , the screen was blink.
    I searched and found this note #999785.
    When I looked for the " virsa/ccxsysbgear application" through the Visual Administrator, I could not find any of the Virsa components application in our GRC server under this path:
    Visual Admin --> cluster tab --> deploy folder --> virsa/*  (all components)
    We have AE, FF configured and running in our development server. Now I am configuring the CC and found all the virsa application services are missing.
    We are implemented GRC Access control 5.3 . Any ideas how to get these components deployed and running in the Visual Admin tool??
    Some of the sample deployed components are
    1. virsa/ccxsysbgear application '
    2. virsa/ccume
    3. virsa/AEume
    4. virsa/ccxsysbher etc
    Greatly appreciate your help!
    Thanks
    Siri

    I found these files with the new name.. There is no virsa tag for these files.

  • Visual admin stoping at 99%

    Hi
    we have Nw04sp17 portal installation and except visual admin tool every thing workingfine.
    when we logon to VA with aministrator and pwd its stoping at 99% and throwing following error at console
    <b>java.lang.NullPointerException
         at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.connectAction(LoginTask.java:191)
         at com.sap.engine.services.adminadapter.gui.tasks.LoginTask.run(LoginTask.java:79)
         at java.lang.Thread.run(Thread.java:534)</b>
    We found some notes on sdn about this and upgrade the WAS to sp18 even though its showing same error.any body has suggestions to
    resolve these issue.
    Thanks in advance
    Gopal

    Hi Gopal,
    another option is to check if maybe the filesystem /usr/sap/<SID> is full (that the Visual Admin cannot write any logs).
    Which operating system and which database do you use?
    Try the login with another user than Administrator which is also in the group "Administrator" and see if that brings the same error.
    You can also try to download the Visual Admin from another system and log in from your local PC (copy the directory /usr/sap/<SID>/j2ee/<b>admin</b> to your PC, make sure you have Java Version 1.4. installed, open go.bat with Notepad or something similar and make sure that "set JAVA_CMD=" points to the java version 1.4 - then start go.bat and try to login)
    Sorry, I start running out of more ideas ....
    Regards,
    Cornelia

  • Visual admin /config tool opens in a small window

    Hi All,
    Can any one let me know, how to enlarge my visual admin and config tool. when, I login to any of the windows server to configure on Visual admin tool, they appear very small and I cannot enlarge them. does any one faced this problem before.
    Please advice.
    Regards,
    Satish Narayana.

    Hi Satya,
    there will  be one tab which is on right top corner..Keep the cursor on the tab and drag to enlarge it..
    I have faced the same issue and am able to do this.If ur not clear send me ur email i will send u the screenshots.
    Regards,
    Siva Kumar

  • Locked out of J2EE Visual Admin and other  problems

    I recently tried to install some Java PDK components using the SDM tool. However it failed when trying to deploy the javadoc component. Since then the following has occurred:
    1. My enterprise portal website is unavailable (ERROR: 'Details: Web container not available!').
    2. I can't login into the J2EE admin tool (ERROR: 'the object does not exist') using either the initially reset Admin password (as part of the original install) or 'admin'.
    3. In the SAP MMC, the Server 0 instance displays yellow, with the jcontrol.exe status (under Process List) as 'some processes running' and server0 (under Process Table) status as 'starting applications'.
    4. The log file on the J2EE database is 100% (not sure if this is relevant or not).
    I've tried to undeploy the java components in case they are the cause of the above issues but get the following error in SDM:
    Info: ***** Begin of SAP J2EE Engine Online Undeployment (J2EE) *****
    No information about the J2EE engine cluster is available. The online undeployment process is continuing.
    Info: ***** End of SAP J2EE Engine Online Undeployment (J2EE) *****
    Error: Undeployment of SDA executed with errors.
    Error:  See below for details:
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running. com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [server] with user name: [Administrator]
    Check your login information.
    Exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineAppOnlineUndeployerImpl.checkLoginCredentials.DMEXC)
    Error: Result: error
    In summary, assuming the new java components broke the EP and J2EE I can't undeploy them (because J2EE is broken) in order to fix J2EE. Damned if I do and damned if I don't.
    Does anyone know why I can't login to J2EE VA, why the J2EE server only partials starts up, why the EP is not working, or how I can truncate the database log file?
    I'm running EP 6.4 SP9 on W2K3.
    Mike D.

    Hi Mike,
    May be the following link will help you.
    J2EE Engine start error: Database initialization failed!
    Moreover, make sure that your port no to which connecting through visual admin is around 50000.
    Regards,
    Bharath

  • Error while Loggin inot VISUAL ADMIN-No login module succeeded.

    Hi,
    I am trying to login to the Visual Admin for the first time for my new Portal System (Quality).
    But I am getting error while loggin in with Administrator user:-
    com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
    The visual_administration.0.trc file shows the following:-
    1.5 #C000AC117C1900010000000159CB59CB000455D3152A8478#1220264988408#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-15,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Java###Error while trying to login to SBQEP: No login module succeeded.
    [EXCEPTION]
    #1#com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:188)
         at java.security.AccessController.doPrivileged(AccessController.java:231)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
         at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
         at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_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:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    predecessor system -
    com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:188)
         at java.security.AccessController.doPrivileged(AccessController.java:231)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
         at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
         at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_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:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Have reffered SAP Note 957355 and performed the steps given in the note,but still the same error.
    I am able to login to the PORTAL with the same Administrator user and password.
    Pls suggest where could be the issue and how to process.
    Regards,
    Abhijeet

    Problem solved. ... No, I have also an answer , perhaps it can help some other peoples.
    As I said there is a note 957355. I create the entrys in offlineconfigtool, but nothing happens. So I checked the other entrys in the "configuration" node in "security" (the note 957355 treated the authentication entry)    , like "UME User Store"  "ticket" and so on. I've taking another system and ckecked this entrys and compare it with my system. So I could restore the default entrys in all security nodes (for authentication). After an restart - voila, it workes.
    greetings
    ps.: hm, can I give some points for me?

  • Installing SAP Java License without Visual Admin

    Hi All,
    I installed a stand alone SAP Java instance a couple of months ago and the temp license key has expired.
    I have applied for a perm license key, which I now have.
    Here is my main issue:
    1. The JControl service will not start because it "failed license check"
    2. The Java VM won't start because of issue "1".
    3. I can't start the Visual Admin tool because of issue "2".
    Hope that all makes sense :-s
    Main Question:
    Does anyone know how to install my new license WITHOUT using the Visual Admin tool?
    Thanks to anyone who responds.
    PS: I do credit responses if they are helpful
    Edited by: Paul Baverey on Jan 23, 2009 12:44 PM

    Hi Tobias,
    Incase if we miss that 30 mins to update the license, how can we install the new license. Is there any possible way to update from configtool?
    Thank you,
    Kasi

  • Visual admin tool not working

    hii guys,
    in my netweaver system visula admin tool not working .when ever im trying to connect with user id and password its showing like this.how can i solve this issue.plz help me

    Hi,
    Try to login to system info page with administrator or j2ee_admin for java and dual stack respectively to check if the password is correct.
    If the password is incorrect, then check if you have any alternate admin ID. Change the administrator or j2ee_admin password, then try to login with the new password. Change the password of SDM and securestore to the new one.
    If this is not the case, then check the log files in visual admin directory. Please post the same.
    Cheers...,
    Raghu

  • 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

Maybe you are looking for

  • License server refimpl install

    Hello everybody! We got trial Flash access license server. We decided to enroll reference implementations first to test FA potentialities. For this purposes we have debian linux 2.6.26-2-xen-amd64 x86_64 with FA_2 distrib copied to it. jdk1.6_20, MyS

  • Safari not playing embedded midi music clips

    I recently noticed that embedded midi music clips in Apple Mail and in Safari do not play. Basically, I am referring to background music one often hears while going to some web sites. Particularly those individual web sites folks have created. Of cou

  • Steps on Installing iPod Shuffle on Comp that has iPod Mini Installed

    I will be getting an iPod Shuffle soon and will be installing it on the same computer that already has my iPod Mini (2nd gen) installed. It's a PC and I'm running XP Home with iTunes version 6.0.1.3. I was just wondering if prior to getting the Shuff

  • Ipod touch will not stay connected to network after trying to use scrabble

    I had a new ipod touch and purchased the scrabble app from EA games. I could not log into facebook to load my games onto the app on my touch. The ipod would send me to my home page and disconnect me from the internet. Eventually my ipod would not con

  • What is green icon in Safari?

    When I open a page in Safari (e.g, Amazon, Google, DuckDuckGo), a green circular icon appears on the top left side of the page.  See example below.  The icon remains for a few seconds, then disappears.  It reappears when I open the next webpage.  Doe