SAP Receiver Connection Testing

Hi All,
We have an IDOC Receiver running as a service, and runs well. Occasionally we loose communication from the service to the SAP Production Server (AS/400). Is thier anyway I can test the connection, or watch for an event that would signify we need to restart the service. Right now when the communication halts, the SAP Server gets flooded with ARFC jobs. Then the operators stop and restart the Receiver service on the Windows 2003 Server.
Thanks in advance for your comments.
Steve

Integration test - means to test integrity of all your business processes, whether or not it is working as specified
We usually create a roadmap of all business processes we have to check (several scenarios), step by step: for example:
1. Investment in Deposit (creation, settlement, etc).
2. Posting (tbb1, F110/F111)
3. Bank statement
4. Interest
5. Changing condtions, parameters, etc.
6. Defferal/accrual
7. FInal repayment
8. Reports
For this roadmap we create parameters: investment amount, terms, interest structure, etc.
And on the day of the integration test we execute the roadmap with all parameters and putting notes when somting wrong - so called Integration Protocol.
After the integration test we correct everything what was listed in the protocol.

Similar Messages

System Configuration - SAP Web AS Connection - connection tests error

hi
I have a SAP ECC 6.04 and sap portal 7.01
When I entered in option System Administration / System Configuration / System Landscape / Portal Content Tree / Systems / SAP_ECC (System created by me)
I founded the following error (in SAP Web AS Connection / Tests the connection to an SAP Web Application Server )
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (htc-svr-erp.humantech.es:4200)
5. The host name htc-svr-erp.humantech.es was resolved successfully.
6. The Web AS ping service http://htc-svr-erp.humantech.es:4200/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.
7. An HTTP/S connection to http://htc-svr-erp.humantech.es:4200 was not obtained successfully; this might be due to a closed port on the Firewall.
...also see a red "X" near a title SAP Web AS Connection
I have other system (old system). It dont have the last error, I show the properties of the "old system"(without error) and the "new system" (with error) for your analisys
In "old sap system", stack java + abap
http://img830.imageshack.us/img830/9755/oldsysstack.jpg
In "new sap system", stack java separated abap
http://img97.imageshack.us/img97/8627/newsysstack.png
In Portal
In "old system", I created "SAP_HCM" System
In "new system", I created "SAP_ECC" System
The "Connector" view (Object Option)
http://img706.imageshack.us/img706/3776/oldsysconnector.jpg (Old System)
http://img269.imageshack.us/img269/914/newsysconnector.jpg (New System)
*The "Internet Transaction Server (ITS)" view (Object Option)
http://img824.imageshack.us/img824/5043/oldsysits.jpg (Old System)
http://img822.imageshack.us/img822/1314/newsysits.jpg (New System)
The "User Management" View (Object Option)
http://img20.imageshack.us/img20/8646/oldsysuserman.jpg (Old System)
http://img97.imageshack.us/img97/5339/newsysuserman.jpg (New System)
The "Web Application Server" View (Object Option)
http://img101.imageshack.us/img101/6155/oldsyswas.jpg (Old System)
http://img69.imageshack.us/img69/434/newsyswas.jpg (New System)
My question of this view is: Is correct the Server port "4200" in New System? or Is correct the Server port "80+instance" in Old System?
I run tcode RZ10 in backend after "Extended Maintenance"
http://img15.imageshack.us/img15/8711/oldsysrz10.jpg (Old System) (Here do not exist parameter icm/server_port_1 )
http://img512.imageshack.us/img512/9268/newsysrz10.jpg (New System) (Here do not exist parameter icm/HTTP/j2ee_0 , is it correct?)
Which of these two syntax is correct? 80 + instance or 4200 (any number of port)
also in SAP Systems, I run tcode SICF and enter in "Port Information"
http://img265.imageshack.us/img265/5281/oldsysport.jpg (Old System) (two ports)
http://img441.imageshack.us/img441/7905/newsysport.jpg (New System) (three ports)
The "Information" view (Object Option)
http://img13.imageshack.us/img13/2012/oldsysinfo.jpg (Old System)
http://img714.imageshack.us/img714/6941/newsysinfo.jpg (New System)
My question is, Why in "Old System" the parameter "Created By" is "pcd_service"? is automatic?
because the paremeter "Created by" is the user j2ee admin , I created the system manually or Should the user create pcd_service ?
The "No Category" group (Object Option)
http://img827.imageshack.us/img827/8215/oldsysnoncat.jpg (Old System)
http://img193.imageshack.us/img193/3800/newsysnoncat.jpg (New System) (in this System does not exist the parameter sysnr , is it correct?)
The "Permisions" Option
http://img825.imageshack.us/img825/886/oldsyspermin.jpg (Old System)
http://img243.imageshack.us/img243/2057/newsyspermin.jpg (New System)
The "Delta Link Tracer" Option
http://img716.imageshack.us/img716/798/oldsysdelta.jpg (Old System) (two levels)
http://img828.imageshack.us/img828/8057/newsysdelta.jpg (New System) (three levels, is it correct?)
the other view the same (Old Sytem and New System)
The "Connection Test" Option
http://img412.imageshack.us/img412/5789/oldsystest.jpg
http://img243.imageshack.us/img243/5237/newsystest.jpg
Edited by: Ivan Quiroz on Sep 21, 2010 12:42 PM

 Excuse me, because the message Editor has problems, I edited with html tags for best view 
 
 hi
 
 I have a SAP ECC 6.04 and sap portal 7.01
 
 When I entered in option System Administration /System Configuration /System Landscape / Portal Content Tree / Systems /SAP_ECC (System created by me)
 
 I founded the following error (in SAP Web AS Connection / Tests the connection to an SAP Web Application Server )
 
 SAP Web AS Connection
 Test Details:
 The test consists of the following steps:
 1. Checks the validity of system ID in the system object.
 2. Checks if the system can be retrieved from the PCD.
 3. Check whether a SAP system is defined in the system object
 4. Validate the following parameters: WAS protocol; WAS host name
 5. Checks if the host name of the server can be resolved.
 6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
 7. Checks HTTP/S connectivity to the defined back-end application
 
 Results
 1. The system ID is valid
 2. The system was retrieved.
 3. The system object represents an SAP system
 4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (htc-svr-erp.humantech.es:4200)
 5. The host name htc-svr-erp.humantech.es was resolved successfully.
 6. The Web AS ping service http://htc-svr-erp.humantech.es:4200/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.*
 7. An HTTP/S connection to http://htc-svr-erp.humantech.es:4200 was not obtained successfully; this might be due to a closed port on the Firewall.

 
 ...also see a red "X" near a title SAP Web AS Connection
 
 I have other system (old system). It dont have the last error, I show the properties of the "old system"(without error) and the "new system" (with error) for your analisys
 
 In "old sap system", stack java + abap
 
 <a href=http://img830.imageshack.us/img830/9755/oldsysstack.jpg>Stack Java + Abap<a>
 
 In "new sap system", stack java separated abap
 
 <a href=http://img97.imageshack.us/img97/8627/newsysstack.png>Stack Java and Stack Abap</a>
 
 In Portal
 
 In "old system", I created "SAP_HCM" System
 In "new system", I created "SAP_ECC" System
 
 The "Connector" view (Object Option)
 
 <a href=http://img706.imageshack.us/img706/3776/oldsysconnector.jpg> (Old System)</a>
 <a href=http://img269.imageshack.us/img269/914/newsysconnector.jpg> (New System)</a>
 
 The "Internet Transaction Server (ITS)" view (Object Option)
 
 <a href=http://img824.imageshack.us/img824/5043/oldsysits.jpg> (Old System) </a>
 <a href=http://img822.imageshack.us/img822/1314/newsysits.jpg> (New System) </a>
 
 The "User Management" View (Object Option)
 
 <a href=http://img20.imageshack.us/img20/8646/oldsysuserman.jpg> (Old System) </a>
 <a href=http://img97.imageshack.us/img97/5339/newsysuserman.jpg> (New System) </a>
 
 The "Web Application Server" View (Object Option)
 
 <a href=http://img101.imageshack.us/img101/6155/oldsyswas.jpg> (Old System) </a>
 <a href=http://img69.imageshack.us/img69/434/newsyswas.jpg> (New System) </a>
 
 My question of this view is: Is correct the Server port "4200" in New System? or Is correct the Server port "80+instance" in Old System?
 
 I run tcode RZ10 in backend after "Extended Maintenance"
 
 <a href=http://img15.imageshack.us/img15/8711/oldsysrz10.jpg> (Old System) (Here do not exist parameter icm/server_port_1 )</a>
 <a href=http://img512.imageshack.us/img512/9268/newsysrz10.jpg> (New System) (Here do not exist parameter icm/HTTP/j2ee_0 , is it correct?)</a>
 
 Which of these two syntax is correct? 80 + instance or 4200 (any number of port)
 
 also in SAP Systems, I run tcode SICF and enter in "Port Information"
 
 <a href=http://img265.imageshack.us/img265/5281/oldsysport.jpg> (Old System) (two ports) </a>
 <a href=http://img441.imageshack.us/img441/7905/newsysport.jpg> (New System) (three ports) </a>
 
 The "Information" view (Object Option)
 
 <a href=http://img13.imageshack.us/img13/2012/oldsysinfo.jpg> (Old System) </a>
 <a href=http://img714.imageshack.us/img714/6941/newsysinfo.jpg> (New System) </a>
 
 My question is, Why in "Old System" the parameter "Created By" is "pcd_service"? is automatic?
because the paremeter "Created by" is the user j2ee admin , I created the system manually or Should the user create pcd_service?
 
 The "No Category" group (Object Option)
 
 <a href=http://img827.imageshack.us/img827/8215/oldsysnoncat.jpg> (Old System)</a>
 <a href=http://img193.imageshack.us/img193/3800/newsysnoncat.jpg> (New System) (in this System does not exist the parameter sysnr , is it correct?) </a>
 
 The "Permisions" Option
 
 <a href=http://img825.imageshack.us/img825/886/oldsyspermin.jpg> (Old System) </a>
 <a href=http://img243.imageshack.us/img243/2057/newsyspermin.jpg> (New System) </a>
 
 The "Delta Link Tracer" Option
 
 <a href=http://img716.imageshack.us/img716/798/oldsysdelta.jpg>(Old System) (two levels) </a>
 <a href=http://img828.imageshack.us/img828/8057/newsysdelta.jpg> (New System) (three levels, is it correct?) </a>
 
 the "System Aliases" Option
 
 <a href=http://img265.imageshack.us/img265/7574/oldsysalias.jpg> (Old System) </a>
 <a href=http://img256.imageshack.us/img256/9817/newsysalias.jpg> (New System) </a>
 
 The "Connection Test" Option
 
 I based in <a href= http://img64.imageshack.us/img64/6638/essalias.jpg> ESS SAP Documentation </a>
 
 In the seven point is diference (blue box) in the <a href=http://img412.imageshack.us/img412/5789/oldsystest.jpg> (Old System) (SAP_HCM System) (An HTTP/S connection to http://htc-svr-sap.humantech.es:8004 was obtained successfully.) </a> and <a href=http://img243.imageshack.us/img243/5237/newsystest.jpg> (New System) (SAP_ECC System) (An HTTP/S connection to http://htc-svr-sap.humantech.es:8004 was obtained successfully.)</a>
 
 I desactivated Firewall in my SAP Server and reviewed in <a href=https://forums.sdn.sap.com/thread.jspa?threadID=946905>SAP Forums </a> my problem but nothing
 
 Could This error also could be the problem that I get an error in the JCO Destination?
 
 <a href=http://img819.imageshack.us/img819/826/oldsysjcosso.jpg>(Old System) (Succesfully)</a>
 <a href= http://img822.imageshack.us/img822/4226/newsysjcosso.jpg>(New System) (com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Issuer of SSO ticket is not authorized)</a>
 
 because I configure SSO correctly (I configured last year SSO in "Old System"),I run tcode SSO2
 
 <a href=http://img709.imageshack.us/img709/7194/oldsyssso2.jpg>(Old System)SSO2 Tcode</a>
 <a href=http://img830.imageshack.us/img830/9704/newsyssso2.jpg>(New System)SSO Tcode</a>
 
 <a href=http://img185.imageshack.us/img185/9279/newsyssso22.jpg>(Old System) SSO2 Tcode Details</a>
 <a href=http://img227.imageshack.us/img227/416/oldsyssso22.jpg>(New System) SSO2 Tcode Details</a>
 
 <a href=http://img530.imageshack.us/img530/8710/newsyslog.jpg>(New System) In the SAP Logs: *** J2EE_ADM_DA1 | USERMAPPING.USE | USER.R3_DATASOURCE.J2EE_ADM_DA1 | | systemtype=[(none)], system=["UMESystemLandscapeDummy"], uses strong encryption=[false], remote user ID=[(none)] ***
</a>

Error in SAP Web AS Connection Test

Connection Test for Connectors is successful
But
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (semdev.suzlon.com:8000)
5. The host name semdev.suzlon.com was resolved successfully.
6. The server semdev.suzlon.com could not be pinged successfully.
What culd be the pblm ?

Hi PK,
in R/3 go to SE37 and check the FM RSBB_URL_PREFIX_GET it will show the details for WAS, I believe the details you gave for WAS are fine.
Now for the issue go to T.Code SICF navigate to the webas path and activate the ping service. This will resolve the issue.
Hope This helps.
Cheers-
Pramod
Reward points if Helpful.

Connection test for connectors(SAP R3 system) fail

Hi,
I got an EP system and connected to one existing R/3 system.For the same i have defined it in system landscape of EP.System administration ---> system configuration ---> system landscape.In property editor i have deined all the min required properties.
Application Host       172.16.3.68
Gateway Host            172.16.3.68
Gateway Service        sapgw00
Logical System Name    ISCCLNT100
Remote Host Type       3
SAP Client            100
SAP System ID (SID)    ISC
SAP System Number      00
Server Port            3200
System Type            SAP_R3
Trace Mode             1
The system intially works fine.But when
1)There are more users it gives connection error.
2)If there are not much users then also After some time it automatically shows connection error.
Then when I do Connection Test for Connectors,it shows "X" failed.
What I usally try to do,I restart the SQL server.
But this method does not work.I have to restart the EP.Then again the system works fine.
I think there are something wrong input in the property value of SAP R3 object setting.
Hey folks can u please help me in sorting out this problem?Why such connection error happens again and again?

Hi Rajeev,
Thanks for your answer.Actaully I have miss interpreted the problem.Sorry Problem is not with in the SAP R3.
Connection problem is like this::
I have defined a system EPSQL(system alias for MS SQL sever DB) for my EP instance
To connect to database.
The connection tests to the alias is ok.
But as more and more users try connecting to the db the connection test fails.
Restarting the SQL server doesnt help.
I have to restart the EP instance to get over the problem
I think there are something wrong input in the property value of object setting.or,EP maintains some timeout or max user info...
Do u have any solution?

Error during connection test in C4C

Hi,
during connection test in C4C i receive Service-Ping-Error: Internal Server Error (500).
The following error shown in HCI.
Inbound processing in endpoint at https://iflmapgbt104xxxxavtaio-xxxx.intaas.hana.ondemand.com/cxf/COD/ERP/SimpleConnect failed with message "Error reading XMLStreamReader.", caused by "WstxEOFException:Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]"
Message Processing Log{
IntermediateError   = true
MessageGuid         = AFUUKFubmbS4sE_0LvLxGiXTI0v4
Node                = xxxxxxxx.od.sap.biz
OverallStatus       = FAILED
StartTime           = Thu Mar 26 15:40:11 UTC 2015
StopTime            = Thu Mar 26 15:40:11 UTC 2015
Children [
    An error has occurred in CXF Inbound Request{
      Error               = Inbound processing in endpoint at https://iflmapgbt104xxxxxavtaio-xxxxx.intaas.hana.ondemand.com/cxf/COD/ERP/SimpleConnect failed with message "Error reading XMLStreamReader.", caused by "WstxEOFException:Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]"
      StartTime           = Thu Mar 26 15:40:11 UTC 2015
      Status              = FAILED
Can anyone help me on this issue?
Cheers
Florian

Hi Ginger,
somehow, yes :-) I deployed the iFlow for customer master replication. After creating a customer the trace looked different and terminated at the reverse proxy. So the simple connect somehow is not able to do the same...
Cheers
Florian

HTTP Connection Test

Hi All,
Iam using File to Proxy scenario.
When testing for HTTP connection test in SM59, it is giving reply as " Empty HTTP Request Received Message processing not possible "
Iam also attaching the generated warning message.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
</SAP:Error>
Any additional settings are to be done or it works.
My BASIS PEOPLE are tilling it is not a problem.
But, my sence is not permitting.

Hi,
I guess that you run sm59 on XI server towards business system on which you want to implement server proxy.
The RFC destination H type. If it is right, then the response that you have received from business system is correct.
You can go further with your development.
Regards,
Jakub

Adapter Engine : Cache Connectivity Test

Hi,
We have recently migrated our PI system's database from one host to the other and as a result there were some duplicate entries for exchange infrastructure components in SLD.
At this besides other problems we have noticed the Adapter Cache Connectivity test is failing.
We have deleted these entries and check that all the required entries are there and they are correct.
After this we did the Adapter Engine Cache connectivity test it still failed. But after some time we noticed that the connectivty test is successfully happening without doing any changes.
We see green bulbs with cache notification from integration server received successfully and cache data fetched successfully and update.
We are just wondering how it happened ? appreciate if anybody can help us understand.
Thanks & regards
Mrutyunjay

hi,
check the below blog....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
check the point 4 (troubleshooting) in the above link
reward points if helpfull
regards
kummari

SAP_PROXY_ESR: Problem with the 'Connection Test' on transaction SM59

Hi,
I have a problem when eject the 'Connection Test' command on Transaction SM59.
I made the RFC Destination SAP_PROXY_ESR with:
Technical Settings
Conection Type: G
Target Host: my_host
Path Prefix: /rep
Service No: 1080
Logon Security
Basic Authentication: X
SSL: Inactive
SSL Client Certificate: DFAULT SSL CLIENT (Standard)
User: ers_user
Password: ers_password
Especial Option
No Time Out: X
HTTP Version: HTTP 1.0
Compression: Inactive
Compressed Response: YES
Accept Cookies: NO
I completed the transaction SPROXSET with:
IFR_ADDRESS             ESR_USER     http://my_host:1080/rep
IFR_PASSWORD     ESR_USER     esr_password
IFR_USER             ESR_USER     ESR_USER
In the transaction SM59 (RFC Destination SAP_PROXY_ESR) I'm making the 'Connection Test' but this command give the Message: ICM_HTTP_CONNECTION_FAILED.
In the program SPROX_CHECK_IFR_ADDRESS
Message: 'Cannot determine repository version'
Log_1- No vendor specified
Log_2- No vendor specified
I don't know the reason of this messaje.
I tried change the Service No. with others Ports but, the error is the same everytime.
Can anyone help me please?
NOTE: In my landscape, i dont have the Stack JAVA installed.
Thanks and Regards

But the Enterprise Services Repository is Java.
the /rep points to the folder of the Repository.
the ESR is part of SAP PI or CE.

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 in Connection Test when connecting to R/3

Hi All,
Although I am able to connect to the R/3 server through the portal (SAP screen is visible and the transactions are running,) the Connection Test fails at the second step i.e. the Connector settings and User Mappings. I have checked these settings and they appear to be fine.
The Test connection results are as follows:
a> Retrieval of default aliases successful.
b> Connection Failed. Make sure User Mapping is set correctly and all connection properties are correct.
I am also unable to connect to the data source through the Visual Composer. Although the systems are visible, the Bapis are not retrieved. It returns the same error. I have even installed the Portal Add-ons for Visual Composer.
Please help.
Regards,
Deepak.

Hi Guys,
Thanks to you all for the suggestions. Rajiv, the settings are as per your suggestions, yet its not working. Also, we are using UIDPW method to logon to the R/3 system. We are able to connect to the R/3 system through the portal and even the transactions are running. The problem is when we test the connection. It fails on step 2. The problem this is causing is that we cannot connect retrieve the data from the R/3 system through Visual Composer. We can connect to the portal thru it though and even the systems are available. But once we select the system and try to retrieve the BAPIs, it throws an error.
We are using EP6.0 SP9 and Visual Composer 6.0 Patch 5.
Regards,
Deepak

System Connection Test was not fully tested but all web dynpro java app and Transaction iviews working fine.Any problem for this Kind of activity Lets give some idea.

System Connection Tests
You can test the connectivity to the backend application represented by the current system object. Choose the relevant tests.
Note: The test is based on the properties currently defined in the system object. It does not check if the system properties are correct.
System Connection Tests
Test Name
Description
Status
SAP Web AS Connection
Tests the connection to an SAP Web Application Server
ITS Connection
Tests the connection to an SAP ITS server
Connection Test for Connectors
Tests the connection to a backend system using an associated connector
Test
Clear Results
Results
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name
5. The host name ssprdxi.stylespasapnet.com was resolved successfully.
6. The Web AS ping service was pinged successfully.
7. An HTTP/S connection to was obtained successfully.
ITS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether the system object has a valid system alias
4. Check whether a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Checks if the host name of the server can be resolved.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
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 ()
6. The host name ssprdxi.stylespasapnet.com was resolved successfully.
7. An HTTP/S connection to was obtained successfully.
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
regards
Antony

Hi Stefan,
This correct see SAP Note [947081|https://service.sap.com/sap/support/notes/947081]
If the locale for the Web Dynpro iView is changed in the portal (through portal personalization), this is not reflected in the running login session. The user needs to logoff and login again, in order to see the locale change in the Web Dynpro iView.
Regards,
Leo

Connection test to database failed: could not connect to server

I restarted one of my HPOV NNMi 9.23 servers this morning and NNMi is no longer loading. I am seeing the following errors in the logs indicated:
/var/opt/OV/log/nnm/public/nmsdbmgr.log
04/06/2015 09:28:05 AM Connection test to database failed: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
/var/opt/OV/log/nnm/public/postgres.log
2015-04-06 09:25:55.312 EDT: :8580:0LOG: could not translate host name "localhost", service "5432" to address: Name or service not known
2015-04-06 09:25:55.312 EDT: :8580:0WARNING: could not create listen socket for "localhost"
2015-04-06 09:25:55.312 EDT: :8580:0FATAL: could not create any TCP/IP sockets
I checked /etc/hosts and found the following entry:
#; Local
127.0.0.1 localhost
From the command line I can ping localhost with no issue. Not sure why NNMi is not starting at this point.
This question was solved.
View Solution.

I also attempted to do a reset using nnmresetebdb.ovpl. I recieved the following:
Attempting to reset the embedded database...
Starting nmsdbmgr process for database reset...
nmsdbmgr process did not restart successfully - please try reset again.
When I run ovstart -c I receive the following:
Name PID State Last Message(s)
OVsPMD 29831 RUNNING -
pmd 29832 RUNNING Initialization complete.
nmsdbmgr - NOT_RUNNING - Exit(1)
ovjboss - UNSTARTABLE -
nnmaction - UNSTARTABLE -
ovspmd: Attempt to start HP OpenView services is complete.
I definitely need some help with this please!
Thanks!

PI : unable to connect to IR with cache connectivity test via RWB

Hi,
Please help to resolve the issues.
Server Details: SAP PI 7.0, SUNSOLARIS with DB2.
PI server was working fine without any issues for the past 2 weeks, Unfortunately issue is the connection failure.
PI services were unable to interlink internally.
cache connection Test Error Below:
Connection to system null using application null lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/conntest/int?" with user "PIRWBUSER". Response code is 404, response message is "Not Found"
SLDCHECK done with success,SPROXY no issues,
users are not locked & password not changed.
Thanks,
Bala

After full cache refresh. with SXI_CACHE i got cache error "UPDATE" detail error as below.
com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/hmi_service_swc_manager/int?container=any" with user "PIDIRUSER". Response code is 404, response message is "Not Found"
     at com.sap.aii.ibdir.server.abapcache.content.CacheSwc.addContent(CacheSwc.java:63)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:360)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:324)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doGet(HmisServletImpl.java:640)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     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)

Define R/3 system in EP: System Connection Test failes

Hi all
I want to configure a R/3 system (fixed application server) in SAP EP Netweaver 04. I am pretty sure that the connection details and the user mapping is ok. When I test the connection I get
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
I now used the tool described in OSS Note 785029:
- When I test connection for the JCO Client Service using the system alias the test is successful
- When I test connection for the Connector Gateway Service for the same system alias I get an exception:
com/sap/portal/connectivity/ConnectivityRuntimeException
Any idea? What can go wrong between the Connector Gateway Service and the JCO?
Bye
Michael

Hi Jan
Thanks for your help. I could only find trace files under
/usr/sap/<SID/><instance>/j2ee/cluster/server0. They seem to contain only the successful calls from testing the JCO Client Service.
I guess the UIDPW and JCO must be working because the JCO Client Service returns success. Only the Connector Gateway Service returns an exception.
I looked at various traces and log files, also used the RFC trace on the backend instance (SAP R/3 4.7). It looks like the Connector Gateway Service returns and exception before as actual call is done. Where would I find more information about the exception thrown in the Connector Gateway Service ?
Thanks
Michael

System connection test in EP: SSO configurated error

hi experts, i get a problem in EP conncet SRM . i don't know too much is this area, please give some advices.
what i have done:
   1 download Certification file from EP (*.der)
   2 import certification firle into SRM system thorugh TCode: STRUSTSSO2, and restart server
   3 Check Tcode：SSO2 in SRM System, get the greed light. then i add this SRM system into Trusted system in the http://hostname:port/ SSO
   4 logon EP(http://hostname:port/irj/portal ) , >>System administration >>system configuration , create New System and maintain related parameters and alias:
      1) Application Host =u201Dgexiaoduu201D
   2)Logical System name=u201DLCSRMu201D
   3)SAP Client= 001
      4)SID=SRM
      5)System type =SAP R3
      6)User mapping type = admin, user
      7)Web AS Protocal = http
5 when i made a "connection test", i got messages as below:
      check the connction to the backend application using defined in the system object results
      Retrival of default alias successful
     Connection failed. make sure that Single Sign-on in configured correctly.
what should i do to correct this problem?
      claud

Hi ,
Please take a look at the below links.
http://wiki.sdn.sap.com/wiki/display/EP/8EstablishSingleSignOnbetweenPortal%28frontend%29andESS6.0%28backend%29
Connecting SAP systems to Enterprise portal with SSO.
http://wiki.sdn.sap.com/wiki/display/EP/HowdoItestSSO
Thanks,
Sandip

SAP Receiver Connection Testing

Similar Messages

Maybe you are looking for