Netweaver CE7.1 Visual Admin problem

Hello every one!
I am failed to start Visual Admin for Netweaver CE 7.1. Connection process hang on when reach 99%.
How this can be solved?
Appreciate any help!
Kirill.
Edited by: Kirill Trunov on Aug 15, 2008 5:20 PM

Hello,
Actually I able to work through Web admin (http://<host>:<port>/nwa).
But cannot perform this steps:
1.   Start the Visual Administrator and select the node Server <x> / Services / Web Services Security from the Cluster tab.
  2.  Within the tab Web Services in the right frame select Security Configuration / Web Service Clients / sap.com / tcwdpdfobject / com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.
Please help!
Kirill

Similar Messages

  • WAS visual Admin. problem.

    Hi,
    The problem occured after the following setting was changed.
    Recent change done in WAS:
    In Visual Admin>> Services >> Security Provider >> Policy Configuration >> J2EE-Engine, the authentication was set to "no". Most probably this has been changed to "ticket" authentication template and the ticket template contains only "EvaluateTicketLoginModule" login module.
    Thank you,
    Laxmikant

    The problem been?...
    Not enough information
    Read the "Rules of Engagement"
    Regards
    Juan

  • 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

  • Visual Admin problem

    Hi All,
      We have an issue where a series of Windows security patches were applied to a WIN2K3 server and Visual Administrator (among other services) will no longer function.
      Could  you please help me what could be the problem?
    Thanks in Advance
    Kiran

    What are the errors?  You have to give us something to help you with.

  • Visual admin login problem

    Hi,
        My visual admin is not starting.can you tell me what is the problem.it s showing warning "cannot open connection on host and port"

    Hi Venkat,
    I guess these links can help you know more about visual administrator and will also help you solve you problem:
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
    Regards,
    Abhy

  • Problem facing while creating DataSource through visual admin utility

    Hi,
    I have created my database on shw6ur-3\tdemand_1 machine where shw6ur-3 is machine name and tdemand_1 is database instance. Still now we used to create database on the sqlserver machine without databaseinstance . This is first time we have installed separate database instance tdemand_1 on the machine. I am entering parameter through visual admin->serverices-> JDBC connector to create database parameter are server name: shw6ur-3\tdemand_1 and database:ABC.
    But it is not allowing me to create the DataSource.
    I am having the doubt on server name.
    Does anybody know how to create DataSource to connect to particular database on particular database instance.
    regards,
    Chandan

    If you connect as sys you have to specify that you want to connect in the role of sysdba or sysoper.
    In the connection dialog you'll find a drop down box where you select sysdba instead of normal.
    Timo

  • Problem visual admin java parameters

    Hi guys,
    I just wanna know in the visual admin, how to put a new java parameters ?
    I can't press enter and had a new line ... Can someone had a parameter ? Not a change but a new one ?
    Thanks.

    yes it is ! had a parameter in the config tool !
    -Xbootclasspath
    -Dcom.wily.introscope-agentProfile
    -Dcom.wily.introscope
    By the documentation Introscop Version 8 Installation Guide For sap June 2009 page 27
    I can modify the parameters, but not had a new line, so not had a newx parameter

  • 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

  • Problem starting visual admin tool

    HI
    I have recently installed SAP ENTERPRISE PORTAL
    Now,I need to do some changes in the visual admin tool
    I browsed to following loaction in my personal computer where I have installed SAP EP
    c:\usr\sap\CE1\J00\j2ee\JSPM
    There I See the file go.bat Once I click on  that I see blank command prompt window being get displayed.
    What are the settings I need to perform inorder to open the VISUAL ADMIN TOOL
    Thanks in advance

    HI
    Once I browse to the following path
    c:\usr\sap\CE1\J00\j2ee  I do not see admin folder being displayed I see the following folders
    cluster,configtool,console,deployement,jpa,jspm,j2eeclient,migration,objectprofilertool,temp,rmic,os_libs,rdbg.proxy
    thanks in advance

  • 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

  • How to start/ restart the service in visual admin of SAP WAS 6.4?

    I have installed the sneak preview version of SAP NetWeaver WAS 6.4 for default Database MaxDB. While developing a simple application to manage simple database table citymaster with 2 columns in jsp I am getting error as
    Exception e com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at : java.comp.
    Looking at visual admin tool for WAS 6.4 all the entries are in color blue but the last entry for 'DATASOURCE' is in RED color where 'java.comp/env/JDBC/DATASOURCE' is the jndi reference created for default DataSource.
    Can any one help me that why the last entry is in RED and it that say that some error has occured or that entry is not started then how to start that?
    Please help....

    Dear Daniel,
    I have checked the Visual Administrator's  JNDI Registry service entry in the ejbContexts node but there is no entry for the project which I have created.
    It get deployed while I right click on the project's ear file and click on "Deploy on J2EE Engine". But same as before while checking in Browserthe site gives the same error...
    503   Service Unavailable
    Application cannot be started!
    Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application bcone.com/EntityCMPAppln cannot be started, because it has hard reference to resource CONFIG_DB with type javax.sql.DataSource, but it is not active on the server.
         at com.sap.engine.services.deploy.server.ReferenceResolver.processUsageOfComponent(ReferenceResolver.java:508)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:149)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:285)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:355)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:120)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:224)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4170)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2390)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2267)
         at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:41)
         at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:101)
         at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
         at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:80)
         at com.sap.engine.core.thread.impl4.SingleThread.execute(SingleThread.java:70)
         at com.sap.engine.core.thread.impl4.SingleThread.run(SingleThread.java:111)
    Please help me, how to recover this error.
    Rgds,
    Vivek

  • How to log on to visual admin and create destination service

    Hi all,
    I see this statement everywhere while trying to configure adobe forms.
    *it was only the HTTP destination FPICF_DATA_<SID> that was not created in the Visual Admin under Cluster -> Services -> Destinations*_
    I got 2 questions here:-
    1. the programs "FP_CHECK_DESTINATION_SERVICE" runs fine w/o destination check box. andwith the check box it gives the error "ADS: Request start time: Thu Nov 26 12:07:42 ........". SO how to resolve this. I have checked the blogs before and I did everything so far and stuck at the statement given above in bold.
    2. What  is this destination fp_icf_data_sid........... where to look for, I understand u need to log on to visual adm. But how is there a sap transaction "AL11" or from the web url.   if it is web url  ...   "http://server_name:port/ ....." then I am lost after this I dont see anything called cluster and services anywhere....
    And if am looking for visual admin at wrong places please provide step by step guide. I have seen steps to log on to visual admin on wesites but i dont know what am i doing, thats not clear. If someone can help from here.
    Thanks,
    Anu.

    The Visual Administrator is a Java tool installed during the installation of a Java AS. It is a separate tool that can be copied and used remotely if desired. On a system running Java AS it can be found under /usr/sap/<SID>/JC00/j2ee/admin - just run 'go' under Linux/Unix or 'go.bat' under Windows. You must have Java installed on your remote system.
    Once you have logged into your Java AS system using the Visual Administrator you can then setup your "Destinations", located under Server -> Services.
    Check Note 944221 - Troubleshooting if problems occur in forms processing ...which will make clear the errors you are experiencing and help you solve them.
    Nelis

  • 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

  • LCRSAPRFC is missing in Visual Admin (JCo RFC Provider)

    H y,
    I'm facing a problem while connecting our SolMan via RFC to SLD.
    Found documents explainig how to set up connection to SLD.
    SAPSLDAPI (was present in Abap and Java - wrong credentials - repaired)
    LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
    How can be the LCRSAPRFC added to JCo RFC Providers?
    Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
    Thanks in advance
    Tom

    Hi,
    Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
    Not Required.
       LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
    Usual Process
    Maintaining the RFC Connections (Transaction SM59)
    1. Log on to your SAP Exchange Infrastructure central instance host.
    2. Call transaction SM59.
    3. Choose Create.
    4. Enter at least the following:
    RFC destination:LCRSAPRFC
    Connection type: T
    Description: <your description>
    5. Choose ENTER
    6. Choose the tab Technical settings and do the following:
    a. Select Registered Server Program
    b. In the Program ID field, enter: LCRSAPRFC_<SID>
    where <SID> is the SAP system ID of your Integration Server host.
    Use uppercase letters only.
    c. Enter Gateway host and Gateway service of your Integration Server host.
    To find out the required parameters:
    a. On the Integration Server host, call transaction SMGW
    b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and
    gateway service)
    7. Choose tab Special Options and select the flag Unicode in the box Character Width in
    Target System.
    8. Save your settings.
    Java Stack
    SAP J2EE Configuration for the Destinations (Visual Administrator)
    1. On your SAP Exchange Infrastructure central instance host, start the SAP J2EE
    Engine administration tool.
    If you do not know how to start, see section How to start the SAP J2EE Administration Tool .
    2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
    3. In the section RFC destination, enter exactly the same program ID and gateway options for LCRSAPRFC that you used in the step Maintaining the RFC connection above.
    Additionally, set the number of processes to 3.
    4. In the section Repository, do the following:
    a. Enter the parameter for the SAP XI host: Application Server, System Number, Client
    and Language.
    b. For User and Password maintain the login parameters for the user SAPJSF.
    c. Select the flag Unicode.
    6. Choose Set.
    Testing
    After you have maintained an RFC destination in both the ABAP and Java environment,
    you can check it as follows:
    1. Call transaction SM59 again.
    2. Open your RFC destination.
    3. Choose Test Connection.
    No error should be displayed.
    Regards,
    Rao.Mallikarjuna
    Edited by: Rao Mallikarjuna on May 31, 2008 11:40 AM

  • Visual admin

    Hi all,
    I have to check JNDI Service in visual admin.
    how to check the JNDI Service which shows the node localejbs/SAP XI JMS Adapter/ConvertMessageToBinary in the JNDI lookup tree.
    My JMS adapter having problem in connecting to MQ system.
    Can anyone give me suggestions.
    Thanks,
    kalyan

    Hi,
    you log on in VisuaAdmin from here \usr\sap\J2E\JC01\j2ee\admin\go.bat .
    Find the JNDI service node on the left side of the VA.
    When you select the JNDI tree will apear and you can check if there is somehting binded in JNDI for "localejbs/SAP XI JMS Adapter/ConvertMessageToBinary".
    greetings Georgi

Maybe you are looking for