Visual Admin connection problems (MBean related?)

Has anyone experienced problems starting the Visual Administrator with the preview?
I can authenticate correctly but then receive an exception during the post-authentication connection process.
The Visual Administrator continues to count toward 100% but stops at 99%!

Hi Peter,
Just try after restarting the server.
Regards,
Nagarajan.

Similar Messages

  • 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

  • Visual adminstrator connecting problem

    Hi experts,
    I installed xi in my system to do some configuration part I want to login to the visual administrtor by going to the file go.bat but it is showing the error that
    error while connecting I am facing this very regularly plz give me some solution
    i will be thankful.
    Regards,
    Srinivas.D

    Hi Srinivas,
    You are not telling what kind of error you are facing?
    If you are facing any logon issues, just follow below steps:
    For openting Visual Admin, just follow below steps:
    1. Go to <Driver>:\usr\sap\<SID>\<Instance num>\j2ee\admin --> click on go.bat
    ex: C:\usr\sap\X67\JC01\j2ee\admin --> go.bat
    2. you will get logon dialog box; Click on "New" button.
    3. Enter "Display Name" and Choose "Direct Connection to Dispatcher Node" then sya "Next".
    4. Give UserName, Host and Port number.
    5. Save
    6. Click on "Connect" button then enter Password of User.
    Note:
    How to find the Port number.
    You can find you engin Port number in folder structure.
    <driver>:\usr\sap\<Instance ID>\ JC<Instance Num>\
    Please find below information
    ex: C:\usr\sap\X67\JC01\j2ee\cluster
    As per above example C:\usr\sap\X67\JC01 -->( <driver>:\usr\sap\<Instance ID>\ JC<Instance Num>\ )
    Instance number is : 01
    Port number = 50000 + 100 * Instance number + Port Index
    Port Num = 50000 + 100 * 01 + 04 = 50104
    Now you can find you port number according to above steps:
    In Visual Admin we are using P4 Port. this port index is 04;
    Plz check URL. http://help.sap.com/saphelp_nw70/helpdata/en/a2/f9d7fed2adc340ab462ae159d19509/frameset.htm
    Please give points; if it is realy helpfull.
    Thanks,
    Nagaraju

  • Error in connecting Visual Admin.

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

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

  • 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

  • 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

  • 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

  • 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

  • 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

  • Visual Admin often lost connection

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

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

  • 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

  • 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

  • Error while creating RFC Jco provider in visual Admin

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

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

  • 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

  • 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

Maybe you are looking for