RFC SDK connect call fails for NW2004s SPS13 if password in lowercase

Hi all,
I am running a sample rfc program on solaris m/c.
SAP server details
2004s SPS13
I am using a communication user to connect to server using RFC SDK.
If i connect to the server with password in smaller case it gives aerror message
"Name or password is incorrect"
But if i give the password in capital case,it works fine.
BAsically i have to create a user with acapital password to work fine on SPS13
ON SPS12 it worked fine for lower case password.
Best Regards
Manoj

Please note the header of this forum: "This forum is dedicated to all other development-related questions which are not directly addressed by other forums. This includes Business Objects SDKs, products, or technologies which do not fall under BusinessObjects Enterprise, BusinessObjects Edge, Crystal Reports Server, or Crystal Reports (for example Desktop Intelligence SDK, Universe Designer SDK, Portal Integration Kits, Java User Function Libraries, and other third party technologies or development languages). "
I do not think you are using any of the products described above. Please post to the correct forum.
Ludek

Similar Messages

  • Connection verification failed for data source using mySQL

    Hi,
    I having problem with mySQL datasource and getting the above error. This is only happening in our staging server. We are using ColdFusion 8 running JRUN4 and trying to connect to mySQL v 5.1.41. I tried adding DSN from my localhost using ColdFusion 9 developer edition and I am able to connect without error.I know that mysql server, username & password is valid. I can access the mysql also using mySQL gui tool from different pc and it works fine. I'm believe that this has something to do with mySQL driver? Can somebody shed some light on how can I fix my DSN connection problem? Thank you.
    here's the error:
    Connection verification failed for data source: forum
    com.mysql.jdbc.CommunicationsException: Communications link failure  due to underlying exception:   ** BEGIN NESTED EXCEPTION **   java.net.ConnectException MESSAGE: Connection timed out: connect  STACKTRACE:  java.net.ConnectException: Connection timed out: connect      at java.net.PlainSocketImpl.socketConnect(Native Method)      at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)      at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)      at java.net.Socket.connect(Socket.java:519)      at java.net.Socket.connect(Socket.java:469)      at java.net.Socket.(Socket.java:366)      at java.net.Socket.(Socket.java:208)      at  com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:173)       at com.mysql.jdbc.MysqlIO.(MysqlIO.java:267)      at com.mysql.jdbc.Connection.createNewIO(Connection.java:2739)      at com.mysql.jdbc.Connection.(Connection.java:1553)      at  com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)       at  coldfusion.server.j2ee.sql.pool.JDBCPool.createPhysicalConnection(JDBCPool.java:589)       at  coldfusion.server.j2ee.sql.pool.ConnectionRunner$RunnableConnection.run(ConnectionRunner. java:67)       at java.lang.Thread.run(Thread.java:619)   ** END NESTED EXCEPTION **    Last packet sent to the server was 0 ms ago.

    http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=6ef0253
    HTH
    Tim Carley
    www.recfusion.com
    [email protected]

  • Connection verification failed for data source:

    Hi,
    I having problem with mySQL  datasource and getting the above error. This is only happening in our  staging server. We are using ColdFusion 8 running JRUN4 and trying to  connect to mySQL v 5.1.41. I tried adding DSN from my localhost using  ColdFusion 9 developer edition and I am able to connect without error.I  know that mysql server, username & password is valid. I can access  the mysql also using mySQL gui tool from different pc and it works fine.  I'm believe that this has something to do with mySQL driver? Can  somebody shed some light on how can I fix my DSN connection problem?  Thank you.
    here's  the error:
    Connection verification failed for data  source: forum
    com.mysql.jdbc.CommunicationsException: Communications  link failure  due to underlying exception:   ** BEGIN NESTED EXCEPTION  **   java.net.ConnectException MESSAGE: Connection timed out: connect   STACKTRACE:  java.net.ConnectException: Connection timed out: connect       at java.net.PlainSocketImpl.socketConnect(Native Method)      at  java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)      at  java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)       at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)       at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)       at java.net.Socket.connect(Socket.java:519)      at  java.net.Socket.connect(Socket.java:469)      at  java.net.Socket.(Socket.java:366)      at  java.net.Socket.(Socket.java:208)      at   com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:173)        at com.mysql.jdbc.MysqlIO.(MysqlIO.java:267)      at  com.mysql.jdbc.Connection.createNewIO(Connection.java:2739)      at  com.mysql.jdbc.Connection.(Connection.java:1553)      at   com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)        at   coldfusion.server.j2ee.sql.pool.JDBCPool.createPhysicalConnection(JDBCPool.java  :589)       at   coldfusion.server.j2ee.sql.pool.ConnectionRunner$RunnableConnection.run(Connect  ionRunner.java:67)       at java.lang.Thread.run(Thread.java:619)   **  END NESTED EXCEPTION **    Last packet sent to the server was 0 ms ago.

    Also make sure your firewall has the required port open (1433
    default) and if you are running 2003 on the SQL box, especially if
    you ran the security Wizard, make sure the IPSec is allowing the CF
    box to communicate with it, and vise verse.

  • TCP connectivity check failed for subnet

    hi
    im trying to add a node to my 11.2 grid infrastructure and the cluster verification is returning error
    Check: TCP connectivity of subnet "152.15.123.0"
    Source Destination Connected?
    inode2:127.0.0.1 inode2:152.15.123.4 failed
    Result: TCP connectivity check failed for subnet "152.15.123.0"
    this happens when i run cluvfy with pre nodeadd option, there is no other failure ...
    any idea what it could be ?

    Hello Buddy,
    Please note that inode2:127.0.0.1 is using loopback IP, please check your network configuration and retry the cluvfy operation.
    Cheers,
    Rodrigo Mufalani
    www.mufalani.com.br/blog

  • RAC - Cluvfy - TCP connectivity check failed for subnet

    Hi ...this is Oracle RAC 10.2.0.4.0 .. has anyone witnessed this check failure or is able to comment on how I should debug the same
    ./runcluvfy.sh stage -post hwos -n all -verbose
    Check: TCP connectivity of subnet "172.30.182.0"
    Source Destination Connected?
    sekiazu0230:172.30.182.67 sekiazu0231:172.30.182.68 failed
    sekiazu0230:172.30.182.67 sekiazu0231:172.30.182.68 failed
    Result: TCP connectivity check failed for subnet "172.30.182.0"
    Interface information for node "sekiazu0230"
    Name IP Address Subnet Gateway Def. Gateway HW Address MTU
    en0 172.30.182.67 172.30.182.0 172.30.182.67 172.30.182.1 1E:40:3D:1C:96:02 1500
    en0 172.30.182.67 172.30.182.0 172.30.182.67 172.30.182.1 1E:40:3D:1C:96:02 1500 ===> Duplicated ?
    en1 172.30.190.48 172.30.190.0 172.30.190.48 172.30.182.1 1E:40:3D:1C:96:03 1500
    en2 10.252.34.9 10.252.34.0 10.252.34.9 172.30.182.1 1E:40:3D:1C:96:04 65390
    Thank you for all feedback
    Steve

    Hello Buddy,
    Please note that inode2:127.0.0.1 is using loopback IP, please check your network configuration and retry the cluvfy operation.
    Cheers,
    Rodrigo Mufalani
    www.mufalani.com.br/blog

  • Connection verification failed for data source on port 1433

    Trying to set up a DSN for a SQL Server database on a new computer and it's failing every time.
    Connection verification failed for data source: csf
    java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: SANDYPC:1433. Reason: Connection refused: connect
    The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: SANDYPC:1433. Reason: Connection refused: connect
    Now, when I installed CF 11, it installed on port 8500.  However, when I try changing the port in the setup to 8500, I get this error:
    Connection verification failed for data source: csf
    java.sql.SQLException: Timed out trying to establish connection
    The root cause was that: java.sql.SQLException: Timed out trying to establish connection
    I cannot find anything online on how to fix this!  HELP!!! 

    Hi,
    Is that SQL Express edition? If so perhaps TCP protocol is not enabled. Is Windows firewall turned on? Check port 1433 is open.
    Normally you would not create a datasource to apache port 8500, that is a web server not database server port.
    HTH, Carl.

  • WebService Call Fails for Communication Users

    Hi
    I am calling a BAPI through web service in VB.NET windows application.
    The application works fine with Dialog users but when I use Communication User then it thows this message.
    The Request Failed with HTTP Status 401: Unauthorized
    Where as if i call the same BAPI through RFC with for this Communication User it is successful.
    What can be the reason ?
    Regards
    Rajendra

    The Web Service uses the HTTP protocol, whereas the BAPI is using RFC protocol.
    The reason for the "unauthorized" error in HTTP is that you need to embed the user / password combination into the web service URL (assuming you have set the Web Service authentication method to user / password).
    Regards,
    D.

  • Random Net connection call failed errors

    Hi All,
    I've built a Flex application which is calling coldfusion CFC through remote objects in order to retrieve data.
    2 days ago, I've updated the server with coldfusion 9 and my issue is that I have sometime those kind of error messages :
    [RPC Fault faultString="error" faultCode="Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: Failed"]
    [RPC Fault faultString="error" faultCode="Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: Status 503"]
    [RPC Fault faultString="error" faultCode="Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: Status 500"]
    [RPC Fault faultString="error" faultCode="Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: Status 504"]
    [RPC Fault faultString="Send failed" faultCode="Client.Error.MessageSend" faultDetail="Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: 'http://servername/flex2gateway/'"]
    It was also happening on Coldfusion 8 and even on one other sever with another application.
    (but same logic  Flex -> remote Objects -> CFC -> sql2005).
    When we were still running CF8 I added this <add-no-cache-headers>false</add-no-cache-headers> to the service-config.xml file but with no success.
    I do not know if it's related to this but I also sometimes have this error message :
    [RPC Fault faultString="Channel disconnected" faultCode="Client.Error.DeliveryInDoubt" faultDetail="Channel disconnected before an acknowledgement was received"]
    Most if time the application is running fine, but I want to avoid this errors.
    For example yesterday I recieved +- 50 times the NetConnection.Call.Failed error and 20 times Channel disconnected error.
    Do not hesitate to ask if I need to post CF9 settings summary or something else.
    Thank you for your help.
    Aubry

    That's a pity, but thanks for the reply.
    Dik

  • SCCM Console issue, SQL connectivity login failed for SCCM machine account

    Hi ,
    As part of resolving the corrupt SCCM 2012 R2 environment, we have uninstalled the site from the Standalone primary site and restored it from the last backup. The database is on remote server on SQL 2012 SP1. Only Site recovery is run.
    Post the restoration on unable to launch the SCCM console, Error Could not connect to the site.
    When I checked the logs in the log file SmsProv.log in the program filles\Microsoft Configuration manager\logs, the error is as below
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspobjectquery.cpp(6260) : SQL Connection attempt timed out~ SQL Error: [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
    *~*~SQL Connection attempt timed out [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
    <*><*> CANT CONNECT TO SQL, RETURNING ERROR <*><*>
    Regards
    Leela

    Duplicate post.
    https://social.technet.microsoft.com/Forums/en-US/6b26502b-ac07-426c-abe4-6cfdaa45b33b/sccm-console-launch-fails-sql-connectivity-issue-with-sccm-machine-account?forum=configmanagergeneral
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • SQLException thrown by the physical connection: Login failed for user

    Hi Experts,
    I am creating a custom data source on Visual Administrator (2004s 7.01 SP3) for SQL 2008 with a named instance. Using Logon, System databases are getting connected. But Visual Administrator throws the below exception trace while attempting to connect to any custom created databases.
    Please help me to resolve this.
    Thanks in Advance,
    Nikhil

    java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during runtime changes of application "sap.com/JDBCConnector_QIDB.xml". [id = ConfigError]
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:705)
         at sun.reflect.GeneratedMethodAccessor647.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: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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: java.rmi.RemoteException: Error occurred while making runtime changes with application sap.com/JDBCConnector_QIDB.xml; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3640850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "QIDB".
         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: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.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
         at sun.reflect.GeneratedMethodAccessor647.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'xxxx'.
         at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:193)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:168)
         at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:134)
         at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:294)
         at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:316)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
         ... 40 more
    Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'xxxx'.
         at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
         at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(Unknown Source)
         at com.microsoft.sqlserver.jdbc.TDSParser.parse(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(Unknown Source)
         at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
         at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
         at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:163)
         ... 45 more
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:346)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
         ... 28 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3640850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "QIDB".
         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: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.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
    com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:316)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
         ... 40 more

  • RFC SDK, connect with japanese username to a unicode SAP system

    Hello everybody,
    I try to connect with a japanese username to a unicode SAP system. I use VC++ and make the call like this:
         BYTE utf8_byteArray[10] = {0xE3, 0x81, 0x8A, 0xE3, 0x81, 0x99, 0xE3, 0x81, 0x99, 0x00 };
         CString sJapUser(utf8_byteArray);
         sConnectParam.Format( cU("CLIENT=%s USER=%s PASSWD=%s LANG=%s SYSNR=%d ASHOST=%s PCS=2"),
                             "800",
                             sJapUser,
                             "password",
                             "EN",
                             1,
                             "9.22.104.145");
         hRfc = ::RfcOpenEx( (char*)(LPCTSTR)sConnectParam, &error_info);
    I tried it with different codepages and PCS settings (1/2) too but i always get the error:
    "Name or password is incorrect (repeat logon)"
    When I connect to a non unicode japanese system in locale encoding it works.
    Another thing i saw is that the utf8 string is truncated after 12 bytes (12 character/bytes is the limit of user name length). When I use a japanese username with 6 japanese symbols (18 bytes in utf8) I see the following in the RFC trace:
    rfcOpenHooked
        destination             <unknown>
        mode                    3
        conopt 3 hostname       9.22.104.145
        conopt 3 sysnr          1
        conopt 3 use_l_bal      0
        conopt 3 use_sapgui     0
        client                  800
        user                    おすすめ (here the username misses 2 japanese characters)
        language                E
        trace                   0
    L-GetCodePage (DEFAULT-CP) rc = 0: 1100
    Here the username is correct:
    >>> RfcOpenEx ...
    Got following connect_param string:
       CLIENT=800 USER=おすすめダウ PASSWD=******* LANG=EN SYSNR=1 ASHOST=9.22.104.145 CODEPAGE=4110 PCS=2
    Send RFCHEADER: 01/LIT/IEEE/SPACE/4110
    Send UNICODE-RFCHEADER: cp:4110/ce:IGNORE/et:5/cs:1/rc:0x00000023
    In the RFC trace the username is truncated (only 12 bytes(4 characters) instead of 18 bytes (6 characters))
    000160 | 44657369 676E0130 0111000C E3818AE3 |Design.0........|
    000170 | 8199E381 99E38281 01110117 000C905F |..............._|
    000180 | E417BBAC 1DDD543E CE540117 01140003 |......T>.T......|
    To connect with japanese usernames using the SAP-GUI works fine but the rfc traces show that the connection is established in another way.
    Can anyone help me with this or is it just impossible to use japanese usernames for logon with RFC.
    Thank you in advance.

    Please note the header of this forum: "This forum is dedicated to all other development-related questions which are not directly addressed by other forums. This includes Business Objects SDKs, products, or technologies which do not fall under BusinessObjects Enterprise, BusinessObjects Edge, Crystal Reports Server, or Crystal Reports (for example Desktop Intelligence SDK, Universe Designer SDK, Portal Integration Kits, Java User Function Libraries, and other third party technologies or development languages). "
    I do not think you are using any of the products described above. Please post to the correct forum.
    Ludek

  • OCI calls failing for Oracle 11g 11.1.0.7 (64 bit)

    Hi,
    I have a 32bit app which we build and compile in a 32 bit OS, we then deploy this in a 64 bit Windows 2008 R1 machine which has a 11g 64 bit DB;
    when the code make the OCI calls the app terminates.On debugging we found out that its failing to make OCI calls on the connect() method of a .cpp file.
    This connect code is a custom wrapper class created for OCI which only accepts a complete SQL statement mainly used for looking after rollback segments, etc.
    The code runs perfectly fine when we internally call the ORACMD of sqlplus and directly execute the sql from a script.
    It only fails when our code tries to connect to the DB and make OCI calls.
    I have also installed a 32 bit Oracle 11g Client 11.1.0.7 since I am using a 32 bit app.
    Is there any compatibility issues between these 2 versions or the dll's?
    Why is it failing while making OCI calls and is there any resolution?
    My machine and setup details:
    OS: Windows 2008 R1
    DB : Oracle 11g R1 11.1.0.7 (64 bit)
    Client: Oracle 11g R1 11.1.0.7 (32 bit)
    Our App: 32 bit
    ORACLE_HOME = // this is pointing to the 64 bit DB
    I tried pointing the oracle_home to the client still no go.
    Any suggestions on this will be appreciated.
    Regards
    Roy

    user13376823 wrote:
    how do i find that my database is using big file tablespace management or not ?
    SQL> select TABLESPACE_NAME,BIGFILE from dba_tablespaces;
    TABLESPACE_NAME                BIG
    SYSTEM                         NO
    UNDOTBS1                       NO
    SYSAUX                         NO
    USERS                          NO
    UNDOTBS2                       NO
    TEMP1                          NO
    TEMP3                          NO
    TEMP2                          NO
    8 rows selected.For tablespaces with smallfile datafile maximun datafile size is 32GB, where as bigfile datafile size is 8 exabytes.

  • Cache Connectivity Test fails for PI on MSCA

    Hi all,
    I experience the following problem with newly installed PI 7.0 SP12 system on MSCA.
    When I go to RWB and press "Cache Connectivity Test" I got the following error for central adapter engine:
    Attempt to fetch cache data from Integration Directory failed; cache could not be updated
    [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.74.sapxi03, string], target element type: SAP_BusinessSystem)
    Tx: SLDCHECK - reports no problems.
    Tx:SLDAPICUST - is set to virtual host name and port.
    Appreciate your help.

    hi,
    here u have to clear the delta cache in SXI_CACHE.
    Open Tcode SXI_CACHE -
    >from menu  XI Runtime cache----->start Delta Cache Refresh(F6     or  CNTRL + F6 )
    reward points  if helpful
    regards
    sreeni

  • JNI static method call fails for the 6th time

    Hello,
    I have a JNI Method which calls the static method which gets reference to singleton class(getReference()), JVM crashes.
    what might be the problem?
    is it due to insufficient memory or any other reason?
    Here is my code.
    eScannerClass = gEnv->FindClass("com/elvista/jscaner/EScanner");
    eScannerContructId = gEnv->GetStaticMethodID(eScannerClass,"getReference","()Lcom/elvista/jscaner/EScanner;");
    eScannerUpdateMethodId = gEnv->GetMethodID(eScannerClass,"updateScanStatus","(Lcom/elvista/jscaner/EScanEvent;)V");
    eScannerObjectRef = gEnv->NewObject(eScannerClass,eScannerContructId);Thanx for any help on this.

    Hi,
    the eScannerContructId is refering a static method, not a constructor. Therefore you must not use gEnv->NewObject, which is only allowed for constructors. Instead you have to use gEnv->CallStaticObjectMethod to call getReference().
    Martin

  • SQL connection string failed for $ password

    Hi Team,
    I am not able to connect to SQL DB when password contains $ symbol. Please help me to open connection for this scenenrio.
    $sqlconstr = "Data Source=Server1;Initial Catalog=DB;User ID=User;pwd='$$XXXXX0';"
    $sqlconn = New-Object system.Data.SqlClient.SqlConnection
    $sqlconn.connectionstring = $sqlconstr
    $sqlconn.open()

    Thanks I tried below string & it worked
    $sqlconstr = 'Data Source=Server1;Initial Catalog=DB;User ID=User;pwd=$$XXXXX0;'

Maybe you are looking for