on 11-11-2005 12:55 PM
Hi guys...
I'm having Cache problems ...
I've been checking the logs and I've discovered the error. I thought that the error could be a cache problem but when I was at the Integration Directory -Cache Notifications, I noticed that my Integration Server(ABAP Cache) was having problems.
I went to the problems tag and saw the same error from the log.
At the Cache Instance, Integration Server(Central Adapter Engine), I had the same error for my communication channel.
This error is not enabling the file adapter to be created... can anyone help me...?
I'm over this error for the last couple of days, I've read all the howtos (maybe not...) and helps...
Any suggestions?
ERROR
com.sap.aii.af.service.cpa.CPAException: Schema not available for File|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)
at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)
at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1826)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1722)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2298)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2701)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
Hi,
use SXI_cache to see to whether ur cache as been updated or not . if you dont find ur updated cache we have option in menubar "XI Runtime Cache" menu under that select refresh display or F5 function key to get the latest cache update.
Hope this helps to slove ur problem
Thanks
sreeram reddy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, the problem is not knowing where to refresh the cache, the problem is that the cache is not performing the refresh...
I'm having this error:
<?xml version="1.0" encoding="UTF-8"?>
<CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.xir.srv04</EngineName>
<RefreshMode>C</RefreshMode>
<GlobalError>
<Message>
CPA Cache not updated with directory data.
</Message>
<Trace>
com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Couldn't open Directory URL (http://srv04:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xir.srv04), due to: HTTP 503: Service Unavailable
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDataFromDirectory(DirectoryAccess.java:382)
at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaCacheUpdateXML(DirectoryAccess.java:545)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:551)
at com.sap.aii.af.service.cpa.impl.cache.CacheManager.initializeCPACache(CacheManager.java:260)
at com.sap.aii.af.service.cpa.impl.startup.StartupManager.initializeCPACache(StartupManager.java:220)
at com.sap.aii.af.service.cpa.impl.j2ee.sapengine630.ServiceFrameImpl.startCPACache(ServiceFrameImpl.java:129)
at com.sap.aii.af.service.cpa.impl.j2ee.sapengine630.ServiceFrameImpl.start(ServiceFrameImpl.java:49)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
</Trace>
</GlobalError>
meaning that there is a service, i suppose that this service will perform the full refresh, is unavailable.
Can you help me figuring this out?How can I activate the service?
I've launched the logviewer and i've seen that the service "SAP XI AF CPA Cache" is active, so it's not this service that is responsible... Can anyone help?
Your answer was really good, and I've discovered that the connection is not working.
I'm getting an "Application error during the request procession. javax.Servlet.ServletException: REQID not found"
That's the cause of my problem.
With that I've discovered a lot of new things related to the user management from the ID, IR and IS.
Now my problem is to what field does the "REQID" refer to?
Where can i find this config?
Any suggestions? Naveen can you come with another brilliant solution, please ?
Thanks for your answers...but i'm losing hope...I've watched the users configs and they are ok...i really don't know what seems to be the problem...
In the document Anand suggested, it says the internal error means it's ok.(it doesn't seem so...but ok)
Now...i still have the problem with the adapter...
It still says the same error above...
The schema was not found...any ideas...please...
hi,
1. you are still getting error when testing using the test button on INTEGRATION_DIRECTORY_HMI
2. did you make sure XIISUSER has the right password
3. go to su01 and check if XIISUSER status
locked/unlocked
I strongly feel the password would be a worng one. Please check the password.
naveen
Sorry for only answering now...I was unable to test the server during the last two days....
I'm still getting the same error, when I'm testing the INTEGRATION_DIRECTORY_HMI.
When I test the connection, the first thing I get is the popup for entering the user name and ID. After placing the values with the XIISUSER and the corresponding password, I'm asked for accepting cookies and then I get the same error...
I've checked and the user is unlocked.
But I don't think the error is from the password Naveen because if I place a wrong password then the error will not be the same, but a 401 with Unauthorized....
I've checked the docs that you suggested it...
I will now check the notes Anand suggested...
Thank you all for your replies
Ok...I was able to go through the initial error
I've now encountered another one.
Remembering I was trying to implement a File-XI-IDOC.
After passing the first error, I went to the RWB-Adapter Monitoring to check if the adapters are all rightly configured. I'm getting the File Adapter well configured, but I'm not getting the IDOC adapter...
I've seen some weblogs related to IDOC implementation but I'm not getting the trick...
Any quick ideas?
IDOC adapter will not be visible in the RWB -> adapter monitoring , only adapters in the Java stack are visible there, so that's ok . If you had made sure you have the required partner profile configuration in the end system, specified the required config params in IDOC commn channel and activated , you should be ok to proceed and test.
Regards
Saravana
Hi Goncalo,
You cannot monitor the adapter but you can monitor the IDoc messages in the IDoc adapter in transaction IDX5 once you start sending/receiving the messages.
http://help.sap.com/saphelp_nw04/helpdata/en/c1/bab13bb3acd607e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards
Anand
Message was edited by: Anand Torgal
I was wondering if the problem for the non-generation of the IDOC was from the IDOC adapter, but i came to the fact that it isn't.
After being in message monitoring and watching the message data that composed the message I watched that I was getting the error:
2005-11-14 14:57:26 Success Application attempting to send an XI message asynchronously using connection AFW.
2005-11-14 14:57:26 Success Trying to put the message into the send queue.
2005-11-14 14:57:26 Success Message successfully put into the queue.
2005-11-14 14:57:26 Success The application sent the message asynchronously using connection AFW. Returning to application.
2005-11-14 14:57:26 Success Channel GV: Send binary file "c:\usr\sap\XIR\SYS\global\vendor.xml". Size 379 with QoS EO
2005-11-14 14:57:26 Success The message was successfully retrieved from the send queue.
2005-11-14 14:57:26 Success File "c:\usr\sap\XIR\SYS\global\vendor.xml" deleted after processing
2005-11-14 14:57:26 Success The message status set to DLNG.
2005-11-14 14:57:26 Error Transmitting the message to endpoint http://server:port/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404.
I've looked to the http connection and it's working.
I've looked to some questions on the forum, does the http connection to the R3 needs to be an https?
Hi,
404 means that the application couldn't be found. This could mean that it simply isn't deployed on the server you are accessing, but I think in this case it is more likely that you have a DNS problem. The server that the AFW is on might be having problems resolving the <server> part of your url, i.e. it can't find the right IP address to actually access. Hopefully that helps.
Cheers,
Steve
-
If you find a post useful, please help keep the community going by setting a good example and rewarding the poster with points.
Hi Goncalo,
Check the pipeline URL specified in the SLD in
the business system of the Integration Server.
In your case from Audit log i think it is http://server:port/sap/xi/engine?type=entry
Are your above server and port(HTTP) valid ? if not change it in SLD(Integration Server Business System) and restart the J2EE Engine.
Regards
Anand
I've checked the Pipeline and the server and the correspondent port seems to be ok.
I've read the suggestion from Sameer but the result is same.
I'm trying to get clean some problems first. Maybe the problem with " Transmitting the message to endpoint http://server:port/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404.." is due to the fact that the sender agreement does not appear on the sxi_cache.
Here go some doubts:
1 - When I do sxi_cache on the sender agreement should my sender agreement appear?
1.1 - Still on sxi_cache, on the communication channels the business system related to the IDOC channels appears but, the business system related to the comm channel from the file adapter that is used on the sender agreement don't...
I'd like to clear this first, and then see if i'm still getting the same error.
Any ideas?
Hi Goncalo,
This error(404) happens when server/port is/are invalid.
Try this..
Take the URL specified in SLD for integration server busness system ( http://server:port/sap/xi/engine?type=entry ) and try to execute the URL in the browser using the user XIAFUSER.
Let me know what error you get...
Regards
Anand
I got:
<SOAP:Envelope>
<SOAP:Header>
</SOAP:Header>
-
<SOAP:Body>
-
<SOAP:Fault>
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
-
<detail>
-
<SAP:Error 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. No message processing possible
</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Any ideas?
ok, i'm not having any cache problems now...but i still have the problem from before...:
Transmitting the message to endpoint http://server:port/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404.....
any ideas Anand?
For error 503 check OSS note 881276.
If you still get the error with cache, SICF -> sap -> xi -> cache and click on change button and put the client number. This was mentioned longtime ago but I could not find the thread.
Do not forget to activate the service SICF -> sap -> xi -> cache
regards
Shravan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.