Error in RFC test connection

Hello Friends
I am running a program which is using a RFC destination (PS_ACCESS_2).
The program runs well when I run it in the foreground but in the background it gave error.
To over come the error I made some changes to the RFC destination.
The changes are as below.
1)If you check the Rfc dest PS_ACCESS_2 in sm59 it is pointing to a exe file. I kept this file in application server and checked the radio button "start on application server".
2) I clicked the radiobutton "specify timeout" and increased the timeout value.
Inspite of these changes when I try to test the connection it gives error.
the error says " logon Error".
Kindly help me resolve this error
Thanks in Advance
Sudheendra

Hi kishore
There is no option to enter User name and password though there is a tab "logon & Security".
In the tab "Logon & Security" I can see the below things
Send SAP logon ticket -> This is checked in my case.
Status of secure protocol -> This is set to inactive in my case.
Any help will be greatly appreciated

Similar Messages

RFC error with SAPOSS (test connection)

Hello All,
RFC error with SAPOSS Test connection
Language:EN
Client      :001
User        :OSS_RFC
Target system settings:
Balace load = Yes
RFC error is below:
                          Connection test SAPOSS
Connection type:    R/3 connection
Connection error        Error opening an RFC connection.
ERROR                  partner not reached (host 209.94.207.139, service sapdp99)
LOCATION              SAP-Server orionbw_QBW_00 on host orionbw2 (wp 0)
DETAIL                   NiPConnect
CALL                      connect
COMPONENT         NI (network interface)
COUNTER               9
ERROR TEXT           Network is unreachable
ERROR NUMBER    101
MODULE                 nixxi.cpp
LINE                        8628
RETURN CODE       -10
SUBRC                   0
RELEASE               640
TIME                      Wed Jul 30 10:06:05 2008
VERSION               37
Please let me know how to proceed.
Thanks in advance.
Best Regards,
Pratyusha

Hi Markus,
I went to OSS1 transaction Menu ---> Parameter --> Settings -
> SAP Routers at Customer Site ---> SAP Router 1
i have Added Name and IP address and instance No.
Now its throwing another error:
=============================================
ERROR                   rgcwebsrv: route permission denied (orionbw2.rgc.corp to 147.204.2.5,
LOCATION                SAProuter 37.11 on rgcwebsrv
COMPONENT            NI (network interface)
COUNTER                 5580
MODULE
LINE
RETURN CODE          -94
SUBRC                       0
RELEASE                   640
TIME                           Wed Jul 30 10:41:28 2008
VERSION                     37
=============================================
We are struck here.
Thanks in advance
Best Regards,
Pratyusha

RFC - XI - WebService, scenario error in RFC Test

Hi
I am following this scenario
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
and did sender RFC Adapter configuration according to michal's weblog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
when I did RFC connection test it gives me the following error
http://www.flickr.com/photo_zoom.gne?id=1202592205&size=o
<b>Connetion test:</b>
Connection type: TCP/IP connection
Connection error: Program sdnweblogs not registered/ CPI- C error CM_ALLOCATE_FAILURE_RETRY
Can you pls let me know what is this error , how to solve this ?
Thanks
srinivas

> The Program name which you have defined in the TCP/IP
> Connection needs to be registered in the J2EE Visual
> Admin. until you do that this will not work.
This is not needed at all.
Your RFC adapter and the TCP IP Connection should use the same Program ID. No need for registering it in the VA.
Just make sure that the Gateway Host and Service in the Sender RFC adapter and in the TCP IP Connection use the Gateway Host and service of the R3 system.
Regards
Bhavesh

Empty HTTP request received in SAP RFC test connection type G

Hi all,
While checking the RFC connection i am getting error,
response_line               HTTP/1.0 500 Empty HTTP request received
server_protocol             HTTP/1.0
status_code                 500
status_reason               Empty HTTP request received
Please let me know if this is right.

Hi,
We are trying to connect to an external server. So, we are using Connection Type as G.
RFC connection Test status is 500.
But in our case, Idoc is getting generated but it is in the XI Box, throwing the below error,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="SECURITY">SECURITY_VERIFY_ERROR</SAP:Code>
<SAP:P1>Check Signature</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Signature error Error while valdiating the digital signature. Theerror was com.sap.security.core.ws.wss.NoSecurityHeaderException No wsse:Security header has been defined for role soap:finalActor. Please verify the</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during message security handling in inbound channel: Security profile 'Check Signature'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Since the RFC is working now, we were not able to find what is the issue. Even SSL certificates are valid.

RFC Test Connection

Hi !
Is there any function module to test whether the RFC call from one system to other system is successful.
Regards,
Priti

Hi,
You can use the below FM to check whether the RFC connection is successfull or nor.
CALL FUNCTION 'RFC_PING'
    DESTINATION XXXX(lv_DESTINATION) " Your destination number
    EXCEPTIONS
      COMMUNICATION_FAILURE = 1
      SYSTEM_FAILURE        = 2.
You can get the destination using below code.
select single ZR3IDEXIST from ZRFCDESTINATION
                       into lv_DESTINATION
                    where   SYSID   = sy-sysid
                      and   ZCLTID = sy-mandt.
Please do not forget to reward if it is helpful for you.
Thanks,
GSK

Latest ODBC driver 9.0.1.5.0 does not work/ test connection

Hello,
I am using an Oracle 9.0.1 database. Before, I installed the 9.0.1.4.0 (6/25/02) and the test connection in the ODBC Administrator works perfectly. I have problems to access a timestamp column. So I installed the latest available driver 9.0.1.5.0 (11/1/02). The installation did not report any errors but the test connection fails with "Unable to connect ...[Driver Manager] driver's SQLAllocHandle on SQL_HANDLE_ENV failed". What's wrong? Can I have both drivers installed in parallel?

You can only have one ODBC driver installed per Oracle home. Unless you have multiple Oracle 9.0.1 homes, you can't have multiple 9.0.1 ODBC drivers installed.
Have you tried re-creating the DSN you're using? This generally isn't necessary, but it's in the README that comes with new drivers because there are occasionally circumstances where it is necessary.
Justin

Unable to create RFC iviews - connection test of the system failed

hello,
I always try to configure my system to run an RFC iView...
The connection of myt system is failed for 1 of the 4 tests.
i don't know why.
I have filled this fields :
- application host
- ITS host name
- ITS path
- ITS protocol
- Logical system name (not sure it's correct)
- Sap client
- Sap system ID
- SAP system number
- Server port (not sure it's correct)
- System type
- Web as host name
- Web as path
- Web as protocol
and i have this error :
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
5. HTTP/S connection successful
ITS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if the system object has a valid system alias
4. Check if a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Check the validity of any user mapping in the system object
7. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
6. HTTP/S connection successful
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
Test Connection through the DQE
Test Details:
The test consists of the following steps:
1. Checks the existence of a backend admin user ID/password in the system properties.
2. Checks the existence of a default alias for the system.
3. Checks the DQE connection.
Results
1. DQE admin user ID or password is missing in the system properties. Make sure those properties exist for this system object.
2. Default alias of the system exists.
3. DQE connection successful. If you continue to experience problems, verify the DQE admin user ID and password properties for this system object.
can you help me to end this configuration?
thanks a lot.
(reward points for helful answers...)
Adrien

doesn't work, doesn't work... :o(
I found this in "analysis" -> "Debug"
error 3 mai 2007 16:49:32:168 Failed to get connection for system final
/System/Server com.sap.portal.ivs.connectorService sap.com/irj admin ITEM-31892 Server 0 0_33638
error 3 mai 2007 16:49:32:168 (R3/BW) Failed to get connection. Please contact your admin.
/System/Server com.sap.portal.connectors.R3 sap.com/irj admin ITEM-31892 Server 0 0_33638
i found too a -BIG- file in the directories, "last block" of the file
#1.5#000D56D8CEA2005D0000001500000FC400042F9201A5E5D2#1178204046283#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
Exception id: [000D56D8CEA2005D0000001300000FC400042F9201A5E071]#
#1.5#000D56D8CEA2005D0000001600000FC400042F9201A76132#1178204046383#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
     at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:209)
     at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:193)
     at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:952)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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)
#1.5#000D56D8CEA2005D0000001800000FC400042F9201A765B7#1178204046383#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)].
The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
Exception id: [000D56D8CEA2005D0000001600000FC400042F9201A76132]#
and with another test connector
#1.5#000D56D8CEA200600000001800000FC400042F921D02D625#1178204505301#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
Exception id: [000D56D8CEA200600000001600000FC400042F921D02D1AE]#
#1.5#000D56D8CEA200560000001600000FC400042F921D39B77B#1178204508896#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> enter#
#1.5#000D56D8CEA200560000001700000FC400042F921D3AE547#1178204508977#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###connectToSystem()->Selected Systemnull#
#1.5#000D56D8CEA200560000001800000FC400042F921D3BE964#1178204509037#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#sap.com/tcwddispwda#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###getElement(String, Filter, int):NamedLocatedElement!ConfigManagerReader.SEARCH_FOR!CTC#
#1.5#000D56D8CEA200560000001900000FC400042F921D414CF2#1178204509397#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> leave success#
#1.5#000D56D8CEA200560000001A00000FC400042F921E69A639#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> enter#
#1.5#000D56D8CEA200560000001B00000FC400042F921E69A953#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> success#
#1.5#000D56D8CEA2006E0000010500000FC400042F9231C81C6F#1178204853786#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA204E70000000100000FC400042F9231C90EA8#1178204853846#com.sap.engine.services.dqe#sap.com/irj#com.sap.engine.services.dqe#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#Thread[Log_Worker_6,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server/DQE#Plain###mai 03, 2007 17:07:33.786 [SAP_HOST|4039|SAPEngine_Application_Thread[impl:3]_9] <CONNECTOR.ERROR> Error trying to establish connection to the EIS : final Connection Failed: Nested Exception. Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA200690000001E00000FC400042F92335B4C9E#1178204880215#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA200690000002000000FC400042F92335B4FE3#1178204880215#com.sap.portal.ivs.connectorService#sap.com/irj#com.sap.portal.ivs.connectorService#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Java###Failed to get connection for system #1#final#
i happy to carry my life's number one goal with another guy
(thanks, again and again)
Adrien
Message was edited by:
        Adrien Loire

Error while testing connection

Hi
i am trying to configure an RFC destination, I am getting the error msg
""Program id" not registered. CPI-C error CM_ALLOCATE_FAILURE_RETRY"
while testing the connection.
How to register a program.
Thanks

Any suggestion pl

Test connection generates error.

Hi,
I'm defined RFC destination for xMII in SAP ECC 6.0 system.
When I pres test connection button.
The error below is generate.
What must I do to solve it?
Thanks.
Connection Test IDOC_MII
Connection Type TCP/IP Connection
Logon     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: SAP gateway connection failed. Is SAP gateway started?
Error Details     LOCATION: SAP-Server erp2005_EC6_01 on host erp2005 (wp 0)
Error Details     COMPONENT: CPIC
Error Details     COUNTER: 50
Error Details     MODULE:
Error Details     LINE:
Error Details     RETURN CODE: 236
Error Details     SUBRC: 0
Error Details     RELEASE: 700
Error Details     TIME: Sat Dec 20 17:51:32 2008
Error Details     VERSION:

Hi,
Try to ping the SAP ECC 6.0 server from MII server and vice versa.
If you are able to ping, then check firewall settings too with system administrater.
Thanks
Rajesh Sivaprakasam.

Error during RFC connection

Hi
I am trying to edit test partner script from eca script, but i am getting one error 'ecatt error ECATT_STORE_BLOB(2)
saving of blob denied for security reasons. you may not be in the edit mode of ecatt ' when i click on ok button it is telling error during RFC connection and whatever changes i made in test partner is not saved.
How to solve this problem. Please help me.

Is it working fine in the standalone mode?
Refer to the below checklist for trouble shooting:
1) Maintenance of DSN settings to the databases - TP_EDIT and TP_EXEC
2) Maintenance of R/3 connection parameters
3) Refer eCATT Security guide
4) Refer OSS note - 519858
Please note that for an integration Scenario, the connection and user information is required so that appropriate rights are established automatically.
Hope this helps!

"COMMUNICATION FAILURE" during JCo call. Error opening RFC connection

Hi
I am trying the following scenario
/people/varadharajan.krishnasamy/blog/2007/05/11/how-to-use-digital-certificates-for-signing-encrypting-messages-in-xi
In SM 59 test connection of AI_RUNTIME_JCOSERVER throws error " Error opening RFC connection"
Do I need to activate any service in SICF and do I need to do any IE configuration (sxmb_adm)
pls let me know the steps to solve this
thanks
manian

Hi Manian,
pls chk with ABAP system tha tu have given the correct PWD and CLNT No
Use
You need to create the following RFC destinations with both transaction SM59 (ABAP) and the Visual Administrator (Java):
●     AI_RUNTIME_JCOSERVER
Points from the Integration Server to the mapping runtime. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used for the mapping runtime, value mapping, and the exchange profile).
●     AI_DIRECTORY_JCOSERVER
Points from the Integration Server to the Integration Builder. The program ID corresponds to the entry under JCo RFC provider for the J2EE Engine (used to refresh the runtime cache).
●     LCRSAPRFC
The RFC destination LCRSAPRFC is required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile.
●     SAPSLDAPI
The RFC destination SAPSLDAPI is required for the connection to the SLD. It is used by the ABAP API.
Depending on your client settings, it may be necessary to log on to your Integration Server host as SAP system user with the authorization to maintain customizing tables and to release transport orders.
User SAP* or DDIC does not have these authorizations
Thanx
Sampath

Error while Test Connection with Connector

hi all:
     there is an error while Test Connection with Connector , I also test it through sys administration->sys configuration->
suport -> sap transaction, I got all errors, I put these two errors as folows, could you please tell me how to sovle it
***************ERROR 1 while *error while Test Connection with Connector ******************************************************
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this
system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
************error sys administration->sys configuration-> suport -> sap transaction        ********************** 1.5 #0025B3E02892006100000A0800001798000487530FB0122E#1274690722265#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt
.runtime#guodongdong#47472##n/a##690347f0670e11df98cc0025b3e02892#SAPEngine_Application_Thread[impl:3]
9##0#0#Error##Java###04:4524/05/10_0077_6087550
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Application URL
&\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid!
Please check the protocol and host entries for system &\#39;sapdev&\#39;.
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass
(AbstractIntegratorComponent.java:123)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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)

Hi,
As per this part of the trace:
Exception in SAP Application Integrator occured: Application URL &\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid! Please check the protocol and host entries for system &\#39;sapdev&\#39;. at ...
You can clearly see that the system object 'sapdev' is not configured correctly/at all - you are trying to launch transaction iView
(WEBGUI) and in order to do so you should configure the 'internet transaction server' category of the system object
with the hostname of the ITS server.
Generally the template is
<System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/webgui?\....
So that's why you got
Please check the protocol and host entries for system ..

CTS1.4.1 Samples JDBC test failing with Error in allocating a connection

Tests under CTS1.4.1 samples>>JDBC>>ee>>testConn>> are failing with the following error :
Sep 14, 2005 4:27:55 PM com.sun.gjc.spi.DSManagedConnectionFactory createManagedConnection
WARNING: RAR5113 : Error creating connection from supplied information: Reason - Error while parsing address
Sep 14, 2005 4:27:55 PM com.sun.enterprise.resource.LocalTxConnectorAllocator createResource
WARNING: RAR5038:Unexpected exception while creating resource
Sep 14, 2005 4:27:55 PM com.sun.enterprise.connectors.ConnectionManagerImpl internalGetConnection
WARNING: RAR5117 : Failed to obtain/create connection. Reason : Connection could not be allocated because: Error while parsing address
Sep 14, 2005 4:27:55 PM com.sun.gjc.spi.DataSource getConnection
WARNING: RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Connection could not be allocated because: Error while parsing address ]
ERROR: SQL Exception : Error in allocating a connection. Cause: Connection could not be allocated because: Error while parsing address
ERROR: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: Error while parsing address
at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:72)
at com.sun.ts.tests.samples.jdbc.ee.testConn.testConnClient.getConnection(testConnClient.java:252)
at com.sun.ts.tests.samples.jdbc.ee.testConn.testConnClient.setup(testConnClient.java:91)
But the mystery is that the main set of JDBC tests (outside of samples) in CTS1.4.1 are running fine.
One difference I notice is that the tests that are failing use "createManagedConnection".
The main configurations file "ts.jte" present under %TS_HOME%\bin has all the settings correct. Thats why the main JDBC tests go through fine.
I wonder where these failing tests pick up the bad "address" from.
Any help on this would be greatly appreciated.
Thanks !

CTS is a paid product and any question regarding that should be answered by a Licencee Engineer. Pls contact the LE regard the setup of CTS or any TCK.

I've had an iWeb site running for 4 months and I publish a monthly newsletter. Since August I've been unable to republish. The test connection under FTP settings works but I get an error message when I try to upload newsletter. Am I missing something mis

I've had an iWeb site running for 4 months and I publish a monthly newsletter. Since August I've been unable to republish. The test connection under FTP settings works but I get an error message when I try to upload newsletter. Am I missing something?

Where are you hosting the site a what are you using to upload the site files to the server?
OT

RFC system error: Screen output without connection to user

After running transaction SMWP, we nagivate to the "Parameters for object load management" node using the following path:
Runtime Information -> Adapter Status Information -> Parameters in R/3 Backend(s) -> ECC -> Parameters for object load management
Under the node Parameters for object load management, when we double click any of the entries we receive the following error message in the form of a pop-up: RFC system error: Screen output without connection to user.
Has anyone encountered the aforementioned error?

Hi,
while creating the syncbo you have to give the RFC destination for corresponding Bapi wrappers
so plz check that.
and can you please explain the exact error in detail and add the trace..
Regards
Manohar

Error in RFC test connection

Similar Messages

Maybe you are looking for