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

Similar Messages

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

Cache connectivity test failing

Hi XI Experts,
The cache connectivity test fails in our XI system. The error appears as:
Cache notification from Integration Repository failedError when accessing the Integration Directory.
This happens almost daily at the same hour of the day. Can you tell me what items I can check within the system?
Thanks in advance.
Regards,
Regina

Hi,
did you have a look at this doc:
https://websmp204.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Regards,
michal

Cache connectivity test failed, points guaranteed

On WBR, we get errors when doing above test:
<b>Protocol Integration Server - JAVA
Hide Detailed Error Message
Mar 12, 2007 4:14:02 PM - Cache notification from Integration Directory not yet started or being edited
Attempt to fetch cache data from Integration Directory not yet started or still in process
[Fetch Data]: Error when accessing the Integration Directory
Detailed Error Message
[Fetch Data]: Connection to system null using application null lost. Detailed information: Error accessing "http://DEV.local.com:50100/dir/cachestatus/int?" with user "PIREPUSER". Response code is 401, response message is "Unauthorized"</b>
Please help. Thanks and points.

This problem disappeared.
However, my adapter engine is still red.
When I click the CCMS button, I get:
<b>Error when processing your request
What has happened?
The URL http://dev.local.com:8001/sap/bc/gui/sap/its/webgui/! was not called due to an error.
Note
The following error text was processed in the system DEV : Template interpretation cancelled, syntax error.
The error occurred on the application server DEV_PDV_01 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
SYSTEM-EXIT of program SAPMSSY0
Function: RS_TREE_LIST_DISPLAY of program SAPLSEUT
Function: SALM_MONITOR_LOAD of program SAPLSALM
START-OF-SELECTION of program RSXMB_RZ20_CALL
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system PID in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server DEV_PDV_01 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server DEV_PDV_01 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 001 -u: CHARLESZ -l: E -s: PID -i: DEV_PDV_01 -w: 0 -d: 20070312 -t: 163119 -v: RABAX_STATE -e: ITS_CANT_LOAD_INCLUDE
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
</b>

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.

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

RWB - Cache Connectivity Test - Adapter Engine shows error

Hello Friends,
In our one production system (PI 7.1), while do 'Cache Connectivity Test' from RWB -> Component Monitoring, it shows the following error for Adapter Engine under Integration Directory.
Error:
Cache notification from Integration Directory failed Error when accessing the System Landscape Directory.
No SLD elements of type SAP_XIAdapterFramework found
But, Integration Server - ABAP, Integration Server - JAVA shows green color. The messages are flowing through the Adapter Engine fine. i.e I am seeing 2 Adapter Engines under Integration Server in Component Monitoring. One Adapter Engine is in grey and another Adapter Engine shows green color.
When I click the grey color adapter engine, it immediately turns to red color and some different host name url is displayed (http://<wronghost>:53000/AdapterFramework/rtc).
So, what could be the problem ?
Kindly clarify, friends.
Thanking you.
Kind regards,
Jegathees P.

Hello Jegathees
Apply the solution in note #804124 HTTP communication with XI Adapter Engine fails. Set the parameters:
SLD.selfregistration.hostName
SLD.selfregistration.httpPort
SLD.selfregistration.httspPort
as described in the note.
Regards
Mark

RWB Component Monitoring - Cache Connectivity Test failure

Hi,
I have done the Cache Connectivity test in RWB-Component monitoring.
For the Integration Server - Integration Engine XYZ.
I am getting error
Result of Self-Test
   Can the SLD be reached?   ... Details OK
   Does the Integration Engine know the business system?   ... Details   OK
   Are roles in SXMS_CONF_ITEMS and SLD consistent?   ... Details Error
   Is Web service security available?   ... Details
The error message os
Details for 'Are roles in SXMS_CONF_ITEMS and SLD consistent?'
Inconsistent roles. System Landscape: Integration Server. SXMSGLOBAL: Application System
How to solve this issue.
Regards
Farhat

Hi
Use Tcode SXMB_ADM -> integration engine ,Assign proper Client to Integration Server.
look this similar thread
Are roles in SXMS_CONF_ITEMS and SLD consistent?

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)

INTEGRATION_DIRECTORY_HMI Connection test fails

Hi ,
I am trying to configure INTEGRATION_DIRECTORY_HMI but the connection test fails as user cannot be authenticated. I found out that I need to put user XIISUSER in the logon tab. Now problem for me is that I do not know the password for XIISUSER.
Then I tried to search the user XIISUSER in SU01. For my surprise it was not there.
Can anyone tell me the steps to create XIISUSER and what roles I need to assign and where I have to register this user.
Thanks.
Regards,
Rahul

Hi,
Try to use PIISUSER instead.Its default password is the master password that you can be given from the basis.
Regards
Yu Ming

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

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.

Proxy connect test failed

Hello all,
Proxy connect test failed because proxy server answers with 403 - Forbidden for tested domain: www.internic.net.
The check itself was correct as the proxy answers with used user login crendentials but the testing routines itself does not respect that.
Regards
Alex

Hi vshiller,
Could you share us more detailed information about this issue? For example, which kind of test type you were running? How did you run it in your side, local or remote?
>>Failed to initialize client proxy: could not connect to test process vstest.discoveryengine.x86.exe.
If you run your VS as the admin, how about the result?
Like this connect report here:
https://connect.microsoft.com/VisualStudio/feedback/details/807771/visual-studio-2013-test-explorer-only-works-if-run-as-administrator
You'd better check that whether it is related to the third party software.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Connection verification failed for data source using mySQL

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

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

Connection verification failed for data source:

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

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

Cache Connectivity Test fails for PI on MSCA

Similar Messages

Maybe you are looking for