Re-create current datasource -- SIA port

running Windows clustered BOE XI3.1.. have re-created current datasource option in CCM of SIA agent.. This is in QA environment.. recreated ok and was able change default cms port to 6401 but SIA port was set at 6410 and it appears I do not have rights to change ???
Bryan

Denis, I am running windows BOE XI3.1
Server A. I stopped SIA. went into config tab and re-created current datasource. all is ok at this point
I then went and started SIA and updated objects.. again no problem.. i did have option of selecting default cms port that I changed to 6401..
now when the SIA is running or stopped when I go into config tab SAI port is defaulted to 6410 and I can not change it..
any ideas would be appriciated
Bryan

Similar Messages

  • OSR - Oracle Service Registry won't create database datasource

    Current configuration:
    Oracle 10g database
    Oracle Service Registry 10gR3
    Oracle Weblogic application server 10.1.3
    I have tried many ways to install the registry (GUI, command prompt, config file) but my datasouce is not getting created. In the /log/install.log the flag to create the datasource is set to "yes" and the name is also set. I don't see any kind of msg/error in the install.log or in the weblogic log. One other thing the registry deploys just fine during installation so all the information seems to be ok. Since the datasource is not created, i get the following exception which is expected since there's no connection to the database:
    ERROR: account.com.systinet.uddi.account.database.DBAccountApiImpl - DatabaseCoreException: (12021) Cannot obtain new connection.
    ERROR: account.com.systinet.uddi.account.AccountCoreApiImpl - Initialization of accounts has failed in the database. Database is not running.
    ERROR: group.com.systinet.uddi.group.database.DBGroupApiImpl - DatabaseCoreException: (12021) Cannot obtain new connection.
    ERROR: group_core.com.systinet.uddi.group.GroupCoreApiImpl - Initialization of groups has failed in the database. The database is not running.
    The only way to make it work is to create the datasouce manually. In the environment that I'm running the less steps the better.
    So thank you for any ideas/help that you can give me!

    Oracle Service Registry Installation to Weblogic
    1. Run installation
    java -jar oracle-service-regisry-10.3.jar
    2. In the Oracle Service Registry installer proceed through the following screens
    * Installation Type screen: select 'Standalone' or other type of installation
    * Installation Directory screen: enter folder where OSR will be installed i.e:-
    /home/oracle/OSR/osrregistry_10_1_3
    * SMTP Configuration screen: (optional) accept defaults
    * Administrator Account Configuration screen: admin user account details
    * Database Setup screen: create new New Schema / Database or connect to existing schema
    * Database Selection screen: select Oracle or other database you may be using
    * Oracle screen: enter database details and schema information.
    3. Data Source screen: IGNORE this for Weblogic servers. Only affects Oracle Application Servers.
    4. JDBC Driver Selection screen: search and select JDBC driver i.e. JDBC 1.6 for Weblogic:-
    $WEBLOGIC_HOME/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6.jar
    5. Account Provide Selection screen: select 'Database'.
    6. Application Server Selection screen: MUST SELECT 'Oracle Weblogic 9.2 or 10.3'
    7. Deployment to Oracle Weblogic Application Server screen: enter correct Weblogic details such as:-
    * Weblogic HTTP Port: AdminServer port i.e. 7001 or a managed server port i.e. 7003
    * SSL Ports (optional): i.e. 7002
    * Hostname where WLS resides.
    * Application Server Context (name of application).
    8. Also on this screen there is the option "Deploy at the end of the installation" which will either deploy the OSR application to Weblogic after it is installed (selected option) or just deploy a WAR file to the command line and get deployed to Weblogic at a later stage (de-select option).
    9. Deployment Details screen: If selected Deploy at the end of the installation in the above screen, then the following screen will be displayed which allows you to enter details of where to deploy the application in Weblogic. Enter all relevant details:
    * Weblogic home: enter the folder where Weblogic resides (WebLogic server installation directory) i.e.
    $WEBLOGIC_HOME/wls_servber1013
    $WEBLOGIC_HOME/weblogic92
    * Java Home: enter the path of the JDK i.e.
    $WEBLOGIC_HOME/jdk160_05
    * Hostname: host of where to deploy application.
    * Admin Username | Password: admin details for weblogic server.
    10. The summary screen is shown regardless of if deployed to Weblogic or not. Press [Next] to install OSR.
    11. After successfully installing OSR a screen will detail that the installation has been successfully installed and with what tasks that need to be completed.
    Deploy OSR to Weblogic
    1. If in the installer the Deploy at the end of the installation option was not selected, then the OSR application needs to be deployed via the Weblogic console. So log into the Weblogic console, press Deployments and then Install.
    2. Install Application Assistant screen:
    * Enter the path where the OSR deployment WAR file (registry.war) resides. It is found in the following path:
    $OSR_HOME/conf/porting/weblogic/build
    * Select file file registry.war.
    3. Complete the rest of the installation/deployment whilst selecting a target server.
    POST INSTALLATION
    The following MUST be done to be able to log into the Oracle Service Registry consoles.
    1. Edit the following Weblogic file:-
    Linux
    $WEBLOGIC_HOME/user_projects/domains/<domain_name>/bin/startWebLogic.sh
    Windows
    %WEBLOGIC_HOME%/user_projects/domains/<domain_name>/bin/startWebLogic.cmd
    2. Modify the following line
    JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}"
    to
    Linux
    JAVA_OPTIONS="${SAVE_JAVA_OPTIONS} -Djava.security.auth.login.config=$OSR_HOME/conf/jaas.config"
    Windows
    set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% -Djava.security.auth.login.config=%OSR_HOME%\conf\jaas.config
    OSR Console
    1. Go to the Oracle Service Registry on Weblogic
    Service Registry
    http://<host>:<port>/registry/uddi/web
    Business Service Registy
    http://<host>:<port>/registry/uddi/web
    2. Press Login and enter login credentials and should be able to successfully login.

  • Error while trying to use Ant and creating Jdbc Datasource

    I was following the documentation to auto-create my datasource in my weblogic server. I get an error while it is trying to link the datasource to the server. Does anybody have any ideas,it is almost like the query to get the server isn't working.
    Here is my ant task:
    <target name="setupJdbcDatasource">
         <wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic">
         <query domain="MyDomain" type="Server" name="AdminServer" property="adminserver"/>
         <create type="JDBCConnectionPool" name="TestDatasource" property="DatasourceTest">
              <set attribute="CapacityIncrement" value="1"/>
              <set attribute="DriverName" value="weblogic.jdbcx.oracle.OracleDataSource"/>
              <set attribute="InitialCapacity" value="1"/>
              <set attribute="MaxCapacity" value="10"/>
              <set attribute="Password" value="cmuser"/>
              <set attribute="Properties" value="user=cmuser SID=ORCH serverName=10.13.5.144 portNumber=1521"/>
              <set attribute="RefreshMinutes" value="0"/>
              <set attribute="ShrinkPeriodMinutes" value="15"/>
              <set attribute="ShrinkingEnabled" value="true"/>
              <set attribute="TestConnectionsOnRelease" value="false"/>
              <set attribute="TestConnectionsOnReserve" value="false"/>
              <set attribute="URL" value="jdbc:bea:oracle://10.13.5.144:1521"/>
              <set attribute="Targets" value="${adminserver}"/>
         </create>
         </wlconfig>
    </target>
    My Domain is MyDomain, and server is AdminServer. The error I get is:
    [wlconfig] weblogic.management.DistributedManagementException : Distributed Management [1 exceptions]
    BUILD FAILED
    X:\ibutt_PCView\src\CM\build.xml:285: Error invoking MBean
    command: javax.management.MBeanException
    And in my server log:
    jdbcDataSourceBean=[MBeanServerInvocationHandler]com.bea:Name=CP-ConfigManagemen
    tTest,Type=weblogic.j2ee.descriptor.wl.JDBCDataSourceBean,Parent=[MyDomain]/JDBC
    SystemResources[CP-ConfigManagementTest],Path=JDBCResource
    <May 21, 2006 3:50:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception
    while creating connection for pool "ConfigManagementTest": [BEA][Oracle JDBC Dri
    ver]Missing connection information: no serverName specified.>
    <May 21, 2006 3:50:58 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occured i
    n the execution of deployment request with ID '1148241051441' for task 'weblogic
    .deploy.configChangeTask.2'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:

    Hi. This seems like an XML parsing problem.
    Could you please try changing the driver
    properties from:
    <set attribute="Properties" value="user=cmuser SID=ORCH serverName=10.13.5.144 portNumber=1521"/>
    to:
    <set attribute="Properties" value="user=cmuser SID=ORCH"/>
    The server and port are already in the URL
    thanks,
    Joe

  • Create a datasource at deploy time

    Hello. I'm new to EJB3.
    I've developed an application with a datasource (JAVADB) running on netbeans 5.5.1 and sun application server 9. It works well.
    Next y try to deploy the .ear file into another application server and get the error "can't find jndi datasource". That's Ok, because this datasource doesn't exist on the second application server. How can i create a new database and datasource while deploy the .ear file?
    Thanks.

    Hi, thanks for your help!
    I'll try to explain my problem again.
    I have netbeans 5.5.1 and i've already configured a datasource so my application can use it.
    The problem comes when i try to deploy the ear file into another app server that have not already configured the datasource that my application use. And i cant create it manually because it is on in my client's pc.
    At this point, what i really need is create a datasource while my .ear file is deployed. The current solution that i've found is to use ant. Is there another?
    Thanks a lot!

  • Creating export datasource

    Hi UmaMaheswar Plz
    Let me know about the  creating export datasource, infosource,infocube,update rules and info package. The APO version is 4.1
    Thanx a lot for ur help

    http://help.sap.com/saphelp_scm40/helpdata/EN/8f/9d6937089c2556e10000009b38f889/frameset.htm
    Extracting Data from a Planning Area
    Use
    There are two purposes for which you might follow this procedure:
    ·        Ad hoc reporting on a planning area
    ·        To save planning data persistently to the database
    Procedure
           1.      Generate an export DataSource for the planning area.
                                a.      From the SAP Easy Access menu, choose Demand Planning ® Environment ®  Current Settings ®Administration of Demand Planning and Supply Network Planning.
                                b.      Select the planning area and in the context menu choose Change/Display. 
                                c.      In Planning Book maintenance, choose Extras ® Generate Data Source
                                d.      A dialog box appears in which you enter a name for the data source. Choose Execute. A screen appears with details of the data source.
                                e.      Specify which fields you wish to be selectable later for reporting purposes. This step enables you to limit a query to specific objects or ranges of objects. What you select here does not affect which fields are included in the export structure. Select the Suppress field indicator for the fields (InfoObjects) that you do not want to transfer
    The number of fields you transfer directly affects performance. Therefore you should only transfer those fields that you require for reporting purposes in the InfoCube.
    The field for the planning version is selected per default; you cannot deselect it. This means that you must enter a planning version in the infoPackage later.
                                  f.      Make a note of the DataSource name.
                                g.      Choose Save.
           2.      Replicate the data source. To do so, right mouse click the source system and choose Replicate DataSources in the Administrator Workbench. The source system is in this case the system in which you are doing Demand Planning. For example, if you are planning in system APO client 002, the technical name of the source system is APOCLNT002.
    When the system messages at the bottom of your screen cease, a background job is triggered. Check in the job overview that this job has finished before proceeding to the next step.
           3.      Still in the source systems view of the Administrator Workbench in the context menu for the source system choose DataSource Overview.
           4.      Assign an InfoSource to the DataSource:
                                a.      In the DataSource overview under Data Marts, select the DataSource and choose Assign InfoSource from the context menu.
                                b.      In the dialog box click the Create icon.
                                c.      In the next dialog box, enter a name and a short description for the InfoSource.
                                d.      When the InfoSource has been created, choose Enter.
                                e.      Answer the prompt with Yes.
    This saves the InfoSource/DataSource assignment.
    If the above procedure is unsuccessful, use the following alternative:
    ·         Switch to the InfoSource view.
    ·         Create an InfoSource (right mouse click a suitable InfoArea and choose Create InfoSource).
    ·         Select the InfoSource and choose Assign DataSource from the context menu.
    A dialog box appears with an overview of all DataSources in the Data Mart, including the export data sources you have generated yourself.
    ·         Select the DataSource you created in step 1.
           5.      In the Administrator Workbench switch to the InfoSource view.
           6.      Right mouse click the InfoSource you have just created and choose Change.
    The definition screen for the assignment of the communication structure to the transfer structure appears. You see the communication structure in the upper half of the screen and the transfer structure in the lower half. Some of the assignment information is proposed by the system. You must fill in the missing information.
    This is another opportunity to remove superfluous InfoObjects from the communication structure. See also step 1.
           7.      Define the assignment of the communication structure to the transfer structure.
                                a.      In the lower half of the screen, enter the source system and the DataSource for the transfer structure.
                                b.      On the Transfer structure tab page, copy the objects from the DataSource to the transfer structure (from right to left).
                                c.      Click on the Transfer rule tab page.
                                d.      Check where the assignment of transfer structure fields to communication structure InfoObjects is not proposed by the system.
                                e.      Where the assignment has not been proposed:
                                                      i.       Include new InfoObjects in the communication structure in the upper half of the screen.
                                                    ii.       In the lower half of the screen, select the new InfoObjects in the communication structure on the left and copy them to the appropriate fields in the transfer structure on the right.
                                  f.      Choose Activate.
           8.      If you need an InfoCube to carry out reporting with a BW front end, create an SAP Remote InfoCube, specifying as the InfoSource the one you created in step 4.
    Otherwise, see the note below.
           9.      Activate the SAP Remote InfoCube.
    Result
    In the SAP Business Explorer Browser, you can now build queries based on this Remote InfoCube. See also Reporting on Data in a Planning Area.
    If you want to copy planning area data to an InfoCube for backup purposes or to save old planning data, create a basic InfoCube at step 8 (for example, by running program  /SAPAPO/TS_PAREA_TO_ICUBE) and proceed as you would to upload data from R/3 or a flat file.

  • Error while creating a datasource for XMLfile in DataFederator

    Hi,
    I am trying to create a datasource in Data federator for XML file, when I tried to click on Generate Elements and Attributes button
    Data Federator gives me error "Java.lang.reflect.InnovationTargetException".
    Thanx In Advance.
    Yogesh
    Edited by: mahayog74 on Dec 2, 2011 11:09 AM

    It looks like more of an issue with connecting to essbase, usually "java.lang.UnsatisfiedLinkError: no HspEssbaseEnv in java.library.path" means planning has not been installed or deployed correctly, what OS is it running on?
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Creating a datasource that sits on a table

    Hello All,
    I have to create a datasource that sits on a table and reads certain fields. I have found the relevant table via the data browser "RSPCLOGCHAIN". I am now in transaction sbiw - please advise further.
    Thank you and kind regards,
    Keith

    Hi Keith,
    The steps would be as follows:
    1. Goto to RSO2.
    2. Create a datasource with a technical name and assign it to a Application Component.
    3. Choose the Extraction from view section and enter you table name.
    4. Save it.
    5. It would list all the fields of that table. You can hide the ones that you do not want. Save again.
    Bye
    Dinesh

  • Create current date variable at universe level

       Hi Everyone
    I have created report regarding to daily car sales. However there is records registered for further months, 2015 December for instance.
    Actually they are error records, but I can't delete them since data transfer is realizing automatically and updates hourly.
    That is why I have decided to use prompt for report: date is less or equal to current date. But couldn't find way how to create current date variable.
    Please help with this.
    Regards...

    Yes.
    Create an object called Today as:
    cast(convert(char(10),getdate(),23) as datetime)
    Note that it will not parse because it does not reference a table. Don't associate it with a table just to get it parsing as you will then have that table in every query that uses the Today object, whether you want it or not!
    It will work fine when you use it in your query. In your example, create a condition of Ship Date Less Than Or Equal To Today where Ship Date and Today are the names of the two objects. This will then translate into SQL as:
    WHERE orders.ship_date <= cast(convert(char(10),getdate(),23) as datetime)
    This will parse because the table orders is in the statement.
    I hope that is clear.
    Regards,
    Mark

  • Getting Error while creating Genric Datasource

    Hi,
    I was try to create genric extracter where i was getting error
    While creating view genric extracter where i am getting error "Entry A ZV_ZFRT  does not exist in DD02L - check your entry".
    My requirement is need to create extracter which is getting populated from three modules like SD,MM,FI/CO.From these three module i am using several tables and some of the tables don't have relation btween these tables as like foreign key and refrence key.
    Which extracter i need to create as given scenario?
    Does view will fullfill with my requirement or any other extracter.
    Please some one can help me in this scenario.
    Answer would be great appreciate.

    Hi,
    Rather than writing a program write a function module. Create a structure and include all the necessary fields in the structure. Then in the function module write the logic to extract the values for those fields. While creating the datasource specify the function module and structure name.
    Refer this link:
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    Hope this helps.
    PB

  • Invalid Extract Structure error while creating "Generic DataSource" on a view...

    Dear All,
    I have created a view on following tables MARA, AFKO and MSEG. The Table/Join condition is as follow:
    AFKO--AUFNR  = MSEG--AUFNR
    AFKO--PLNBEZ = MARA--MATNR
    I have included all the fields from MSEG and other all fields from MARA and AFKO. The view is created successfully and contents/records are also being fetched/displayed from this view.
    See screen shot as well:
    But when I go to RSO2 to create a "Generic DataSource" on this view. I get a series of warning messages and then error message "Invalid Extract Structure" and therefore I'm unable to create my DataSource on this view. See below screen shots of warning and error messages.
    Other warning messages are as follow:
    Field GAMNG with reference field MEINS: Reference table MARA is replaced by ZOXPRD0150
    Field PLSVB with reference field PLNME: Reference table PLKO is replaced by ZOXPRD0150
    Field PLSVN with reference field PLNME: Reference table PLKO is replaced by ZOXPRD0150
    Field LODIV with reference field MEINS: Reference table MARA is replaced by ZOXPRD0150
    Following is the screen shot of error message:
    1. How can I get rid of this error message and be able to create my "Generic DataSource" on top of this "View"?
    2. What should I do to resolve the above warning and error messages?
    I will appreciate your reply.
    Many thanks!
    Tariq Ashraf

    Hi Vipul,
    as you can find in CKIS table, the reference feild for value feild "WERTN" is missing.
    As per the table the reference feild is HWAER. This should have been used in place of FWAER.
    Try mentioning this in your view and this should work.
    Also I am a little enthusiastic to know, what are you trying to get from the datasource.
    If you are trying to get the cost estimate of multi level BOM, not (just one child level), then this approach may not work.
    There is a BAPI that gives such itemization split. Just FYI, in case you are looking for multi level explosion.
    "BAPI_COSTESTIMATE_ITEMIZATION".
    Hope this helps.
    Naveen.A

  • Error while creating Generic Datasource

    Hi,
    I try to create generic datasource using function module in RSO2, it is giving the following errors and the datasource is not creating.
    "Units field WAERK for field TOT_REV of DataSource ZIPO_TRANSCATION is hidden Message no. R8147"
    "Units field WAERK for field EXP_REV of DataSource ZIPO_TRANSCATION is hidden Message no. R8147"
    TOT_REV and EXP_REV fileds datatype is CURR.
    Fuction Module is working fine. Please give me any inputs, it is very urgent.
    Best Regards,
    SGK.

    hi,
    let WAERS field be present in your structure defn
    In the Currency/Quantity fields tab of your extract structure give the refernce of the same structure and same field
    Regards,
    Sampat

  • Error in creating a DataSource inVisual Administrator

    Hi Friends,
    My requirement is to connect to an external oracle database, for which I am trying to create a DATA SOURCE in Visual Administrator.
    the approach I followed is as given in many threads,
    In JDBC Connector service in Visual Admin:
    1. Created a driver using ojdbc.jar
    2. Created a datasource using the above driver,
    but after filling all the values, when I save it, I get following error(some part is displayed here):
    java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/DS_ConnectOracle". [id = StartupError]
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    Also this application name comes from where?
    why it is not able to start the application?
    Just to inform I am successfully able to connect to database using webdynpro application where I have coded the lines to connect to Oracle database.
    But DataSource thng is not working.
    Regards
    Deepak

    just to inform the issue is resolved, I got to know the cause.
    actually I was giving the DataSource Name & DataSource Alias Name as same,
    while they must be different.

  • Different Options while creating a Datasource in Weblogic

    Hi
    I am using Weblogic 11 as Application Server .
    While in the process of creating a DataSource in Weblogic , i came across different options such as for Instance Connections , for Service Connections.
    Please tell me whats the difference in these two ??
    Whats the difference in Oracle Drivers (Thin) for Instance Connections versions 9 , 10 , 11
    Whats the difference in Oracle Drivers (Thin) for Service Connections 9 , 10 , 11
    Thanks in advance .

    Hi,
    Your query is replied by Joe Weistine (JDBC Expert) Please find the answer:
    http://forums.oracle.com/forums/message.jspa?messageID=4029371
    You can directly post your JDBC related querries to JDBC Forum directly to get to get Quick/appropriate/correct answers and attention from JDBC experts... WebLogic Server - JDBC (Forum ID)
    Thanks
    Jay SenSharma
    Edited by: Jay SenSharma on Jan 16, 2010 10:38 AM

  • Can´t create a datasource in workspace in MSAD integrated environment

    We are instaled Hyperion 11.1.1.3, with sql server 2005 and with MSAD autentication.
    In that environment, autenticate in the database is doing using MSAD not sql user login.
    When we configre the database we specifiy parameter to indicate that use MSAD autentication, and test all conection and was ok, and the configuration finish witout errors
    When we finish, we configure Shared Services and give permission to the MSAD user (using admin user). After that we login in workspace with the same user that we use to configure the database before.
    When we try to create a application, first we must create a datasource. For tha use Navigate->Administer->Classic Application Administration -> Planning Administration. And after, select Manage Data Source.
    In that point we introduce de parameters and test de datasource and appear a message  indicating that the connection is not possible and is not posssible create the data source (the essbase data source was ok) ._
    The database was created before, and the user used to test the datasource, is the dbo in the database (and in the other database of shared services)
    To inspect the problem we do the following task
    - We create a datasource in windows to test the user and was ok too.
    - We test with the database indicated for Shared Services and test again and not work.
    - We copy the data direct dll to windows/system 32 and test agian and not work.
    - We restart the machine and don´t work.
    Someone had idea how to solve this problem?
    Thanks a lot for your help.
    Edited by: user1044125 on 31/08/2009 07:52 AM

    You maybe right, did you follow all of the post installation instructions?
    Check out page 27 of the installation guide, this maybe the case I'm not sure ...
    Locate the line containing PlsqlNLSLanguage.
    The PlsqlNLSLanguage setting determines the language setting of the DAD.
    The character set portion of the PlsqlNLSLanguage value must be set to
    AL32UTF8, regardless of whether or not the database character set is AL32UTF8.
    For example:
    PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8

  • Can't create a Datasource

    Hi, i'm trying to create a Datasource with the Visual Administrator and I'm getting this error:
    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 2178150:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "MS_SQL_DS_II".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
         at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
         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:400)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
         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:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         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:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: javax.resource.ResourceException: java.lang.NullPointerException
         at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:145)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:151)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
         at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
         at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
         at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
         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:400)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
         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:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         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:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:162)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
         at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
         at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
         ... 41 more
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:658)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
         at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
         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:400)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
         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:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         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:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 2178150:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "MS_SQL_DS_II".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
         at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
         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:400)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
         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:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         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:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: javax.resource.ResourceException: java.lang.NullPointerException
         at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:145)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:151)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
         at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
         at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
         at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
         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:400)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
         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:157)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
         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:294)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:162)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
         at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
         at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
         ... 41 more
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:230)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
         ... 31 more
    Here is an export of the dataSource:
    <?xml version='1.0' encoding='UTF-8'?>
    <!DOCTYPE data-sources SYSTEM 'data-sources.dtd'>
    <data-sources>
      <application-name>myJarProject</application-name>
      <data-source>
        <data-source-name>MS_SQL_DS_II</data-source-name>
        <driver-name>MSSQL</driver-name>
        <init-connections>1</init-connections>
        <max-connections>10</max-connections>
        <max-time-to-wait-connection>120</max-time-to-wait-connection>
        <expiration-control>
          <connection-lifetime>600</connection-lifetime>
          <run-cleanup-thread>300</run-cleanup-thread>
        </expiration-control>
        <sql-engine>vendor_sql</sql-engine>
        <jdbc-2.0>
          <cpds-class-name>org.apache.commons.dbcp.BasicDataSource</cpds-class-name>
          <object-factory>org.apache.commons.dbcp.BasicDataSourceFactory</object-factory>
          <properties>
            <property>
              <property-name>user</property-name>
              <property-value>juan</property-value>
            </property>
            <property>
              <property-name>password</property-name>
              <property-value>******</property-value>
            </property>
            <property>
              <property-name>portNumber</property-name>
              <property-value>1433</property-value>
            </property>
            <property>
              <property-name>database</property-name>
              <property-value>examples</property-value>
            </property>
            <property>
              <property-name>serverName</property-name>
              <property-value>p4p800d-6</property-value>
            </property>
            <property>
              <property-name>driverClassName</property-name>
              <property-value>com.jnetdirect.jsql.JSQLDriver</property-value>
            </property>
            <property>
              <property-name>username</property-name>
              <property-value>juan</property-value>
            </property>
            <property>
              <property-name>url</property-name>
              <property-value>jdbc:JSQLConnect://p4p800d-6:1433/database=examples</property-value>
            </property>
          </properties>
        </jdbc-2.0>
      </data-source>
    </data-sources>
    Regards,
    Juan Manuel

    Mauricio,
    you have 2 options...
         1. Try to add Reference field in the view if you can add WAERS.
          2. If you can't able to add WAERS, delete NETWR from View. Create your datasource on View (Z*). Enhance your Datasource for NETWR(use different Data Element which you can add). Populate Data using User Exit for NETWR)
    all the best.
    Regards,
    Nagesh Ganisetti.

Maybe you are looking for