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

Similar Messages

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

When i doing cache connectivity test , i am getting below error

When i doing cache connectivity test , i am getting below error, could you please suggest me what action need's to be done
Integration repository, Integration Directory,Integration server ABAP, Integration server java is green, only adapter engine is showing red.
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_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem
[Fetch Data]: com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:490)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
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.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem)
at com.sap.aii.ib.server.sldquery.SLDQuery.dammiIlMioCentralAdapterFramework(SLDQuery.java:70)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:191)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
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.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
[Data Evaluation]:

Check Surya's reply: Cache-Connectivity-Test in RWB
The same procedure in detail manner is given in this How-to guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34
Are you using any Business System? If yes then make sure that you have imported it properly into ID....in this case ID --> Environment --> Clear SLD Cache.
Regards,
Abhishek.

I completed a full system recovery. Still getting a configuration error. (code purple).

I have a completed a full system recovery using vista. completely redid the hard drive with recovery disk. When startup occurs, I get a message saying a configuration error. contact HP. (code purple). Is this a hard drive issue? Help where to go next.

***Windows 7 code purple or Windows Vista code purple***
With the code purple error on the screen, press shift+f10 (the shift key and the F10 key (at the top of the keyboard) at the same time) to open a little screen called a command prompt. (So, you get a little black screen with white text that says something about your Windows verison first and a little ways down you'll see "C:\>". It's all ready for you to start typing.)
Type the following line, just as you see it here...
notepad C:\hp\bin\checkdmi\checkdmi.cmd
so it will look like this
C:\>notepad C:\hp\bin\checkdmi\checkdmi.cmd
Press Enter.
You will see the text for the file listed in a window using a simple text editor.
Go to the beginning of the text. Press enter to make a space. Type this...
goto cleanup
So, whatever comes after, the first line looks like this...
goto cleanup
Save the file and exit notepad and restart your PC. You are good to go.

SSO Configuration Error

Hi,
I have installed Oracle 9iAS Release2.For installation of the infrastructure and 9iAS, it needed a fully qualified domain name of the machine(say,9iASMachine and InfraMachine).To enable this, we made entries in the host files of these machines as
ip1 InfraMachine.com
ip2 9iASMachine.com
And using these virtual names,the installation went fine.
The problem now is that when we configure any J2EE application as SSO app,by making entries in mod_osso.conf,
and access the app as say,
http://9iASMachine:7778/myapp/index.html
then for authentication,it goes to http://InfraMachine.com:7777/pls/orasso/orasso.wwsso_app_admin.ls_login
After the user authentication,instead of coming back to
http://9iASMachine:7778/myapp/index.html
it goes to
http://9iASMachine.com:7778/myapp/index.html
and we get an error as :
Oracle SSO Warning - Unable to process request
Either the requested URL was not specified in terms of a fully-qualified host name or OHS single sign-on is incorrectly configured.
The same things works perfectly fine,if we access the SSO J2EE App as
http://9iASMachine.com:7778/myapp/index.html
Can we do some configuration setting in 9iASMachine Apache,so that both,9iASMachine.com and 9iASMachine, give the same results?
Thanks,
Shipra
Please notify your administrator.

Hi
Did you import the portal certificate into ECC using transcation STRUSTSSO2
login/create_sso2_ticket parameter is set in ur profiles.
Login to the below url - ECC
http://servername:Port/nwa
click on configuration
select Trusted Systems
add the Trusted system "portal" by selecting the " BY Querying the SELECTED SYSTEMS"
it will add the portal certificate to ECC
Test your connection again
Hope it works this time.
Thanks
Kiran Nekkanti

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 Landscape connection test fail

Dear EP expert,
I try to do a System Connection Tests for my system landscape and some part of the test failed.. Anyone have idea what is wrong with the configuration. Below are the test result and mainly are the HTTP/S connection and user mapping failed.
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check whether the system can be retrieved
3. Check whether 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 backend 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 (devportal01:50000)
5. HTTP/S connection failed
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 whether the system can be retrieved
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. Check the validity of any user mapping in the system object
7. Check HTTP/S connectivity to the defined backend 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 (absmrq01:8001)
6. User mapping is not valid
7. HTTP/S connection failed
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.
Thanks,
Regards
Bryan

Hello gurus,
I am facing the same problem, could you please help me, the problem is http error detailed below
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 whether the system can be retrieved
3. Check whether 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 backend 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
5. HTTP/S connection failed
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 whether the system can be retrieved
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. Check the validity of any user mapping in the system object
7. Check HTTP/S connectivity to the defined backend 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
6. User mapping is valid
7. HTTP/S connection failed
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 successful
Thanks
Edited by: Akbar Gudur on Jan 15, 2009 6:24 PM
Edited by: Akbar Gudur on Jan 15, 2009 6:24 PM

Cache Connectivity Test in RWB fails

Hi Guys,
When I go to RWB in Cache Connectivity Test, I get the following error:
" Error during last test run executed by EGKATZIOS, on 10 u039Du03BFu03B5 2009 3:35:37 u03BCu03BC: Error executing testClientServerException exception:Communication with JMS server failed
com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Communication with JMS server failed"
Any ideas ?
Also in IR, in Cache Notifications, remain in Red Status "Not Yet Started" and I have to manually Execute them.
Which I realized is related to an error I get when I activate the Change List in IR "Communication with JMS server failed Repeat the last action. If the problem continues to occur after multiple attempts, contact your system administrator to check the availability of the JMS provider service". However, activation works with a second attempt.
Everything else, SXI_CACHE, HTTP Connections, SLDCHECK, Service Users, HTTP and JMS services in VA work fine.

Hi,
Pls follow this path,
login to J2EE Visual aadmin>cluster>services.JMS connector>runtime(Righ hand side tab)->check the factories / destinations (if anything is in red color X mark).
Ask your basis admin to correct this.Final possible solution is to restart the server....
Hope dis will help.
Regds,
Pinangshuk.

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

CPA Cache Connectivity test fails

Hi All,
We are facing the following issues that have to do with the Adapter Engine:
1) In RWB, the Adapter Engine is in error/red status with the following details: Adapter Engine, message: fatal DeleteJob (Default Delete Job) failed.
2) In RWB, the Cache Connectivity Test fails with the following error: Communication with JMS server failed.
3) The CPA Cache refresh gives erros.
Any ideas? There are no Service users locked, SLDCHECK works fine etc.

Hi,
It seems to like problem with your JMS Connector.
For this, login into Visual admin -->cluster >services>JMS connector-->runtime (tab)->check the factories / destinations. Please contact with your basis team, they will might be helpful to you. After that restart your server, it will solve your issue.
Regards,
P.Rajesh
Edited by: Rajesh_1113 on Jun 5, 2011 9:01 AM

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>

Workflow configuration error - System Account connection test failed

Hi,
Has anybody faced a problem with Workflow configuration? The version we are using is 2.6.2 on Oracle database 9.2.0.5 on AIX5L. The workflow installation from 9.2.0.1 installation CDs goes through without any problem. But when the workflow configuration tool comes up it fails with the following error.
"SYSTEM account connection test failed".
The system and sys accounts are fine as verified by sqlplus. Any help is greatly appreciated.
The log file is shown below.
Workflow Configuration Assistant-AIX
WorkflowCA:
WorkflowCA: Workflow Configuration in progress...
WorkflowCA:
WorkflowCA: Screen width -2304-, screen height -1024-
WorkflowCA: Graphics User Interface mode
WorkflowCA:
WorkflowCA: Language - US
WorkflowCA:
WorkflowCA: Start testing connection, which takes less than 3 minutes.
WorkflowCA:
WorkflowCA: Account connection test for SYSTEM
WorkflowCA: SQL Thread: Thread[TstSQL,5,main]
WorkflowCA: chkSQL: true
WorkflowCA: cmdLine: /app/oracle/product/9.2.0/bin/sqlplus system/<Masked Password> @/app/oracle/product/9.2.0/wf/sql/wftstcon.sql
WorkflowCA: envVar[0]: -ORACLE_SID=rsdb-
WorkflowCA: envVar[1]: -ORACLE_HOME=/app/oracle/product/9.2.0-
WorkflowCA: envVar[2]: -WF_RESOURCES=/app/oracle/product/9.2.0/wf/res/wfus.res-
WorkflowCA: envVar[3]: -TZ=EST5EDT-
WorkflowCA: envVar[4]: -WF_NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1-
WorkflowCA: envVar[5]: -PATH=/app/oracle/product/9.2.0/bin:/app/oracle/product/9.2.0/lib:$PATH-
WorkflowCA: envVar[6]: -LD_LIBRARY_PATH=/app/oracle/product/9.2.0/lib-
WorkflowCA: envVar[7]: -WF_TNS_ADMIN=/app/oracle/product/9.2.0/network/admin-
WorkflowCA: envVar[8]: -WF_SHLIB_PATH=/app/oracle/product/9.2.0/lib-
WorkflowCA: Exit Val : 126
WorkflowCA: chkSQL is alive after 1 seconds: false
WorkflowCA: SYSTEM account connection test failed.
WorkflowCA: Terminating...
Thanks,
Chethan

We had this problem on 2 machines.
On the 1st machine, we tried the local install option after a few days (Local option with no connect string) and it worked with no problems!
On the 2nd machine, we could never get it to work even after opening a tar with Oracle. Finally we did a remote install from the 1st machine into the database on the 2nd machine. During the remote install while running wfinstall on the 1st machine, we just had to choose the remote option and the database service name for the connect string.
Thanks,
Chethan

Power Bi for o365 - Odata connection test worked but "The server encountered an error processing the request. See server logs for more details". Port 8051? Authority\System

We set up the Data Management Gateway and created a new data source (odata to SQL via sqL user)
Did a connection test and it was successful!
Tried the URL (maybe it needs more):
https://ourdomain.hybridproxy.powerbi.com/ODataService/v1.0/odatatest
That resolves to some :8051 port address and then spits out this message:
The server encountered an error processing the request. See server logs for more details.
I checked and the data management gateway is running.
Does that 8051 port need to be opened on our firewall for this server? How can I confirm that is the issue.. I see no event on the server indicating this is the issue?
I am seeing this event:
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'PowerBiTest'. [CLIENT: IP of the Server]

O365,
Is this still an issue?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Error in SSO Configuration

Hello,
I am configuring SSO between Portal 7.4 and ECC production system.
I am getting following connection test error:-
Please guide me to resolve it.
Thanks and regards,
Akshay

Hi,
My SSO working fine from sapgui option but it is giving following error when selecting option HTML.
Please guide me.Whether it is due to browser.
Thanks and Regards,
Akshay

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

System connection test in EP: SSO configurated error

Similar Messages

Maybe you are looking for