- 浏览: 490028 次
- 性别:
- 来自: 北京
文章分类
最新评论
-
cloudfile:
谢谢分享!
MyEclipse配置Tomcat(图解) -
dotjar:
有效没?
治咳嗽秘方 -
jyslb:
设置密码长度大于10位,其中包含%$#&等符号,你这个 ...
奶瓶无线破解介绍 -
廖乐逍遥:
还是不行。。
eclipse里不支持泛型的解决方法 -
cue2008:
http://backtrack.unixheads.org/ ...
Intel 3945ABG无线网卡破解无线路由器密码 BT3
Here’s a list of common errors/problems in SAP XI and their possible resolutions. This Guide will help you troubleshoot your integration scenarios in SAP XI/PI. This is in no way an exhaustive list. You can add your points/ideas to this list. Please feel free to post your inputs using the comments form at the end of this article.
Cache Update Problems
Use transaction SXI_CACHE to update the Integration Directory cache. Alternatively, you can use the following URLs to update the CPA cache. Use XIDIRUSER to refresh the cache.
For complete cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=full
For delta cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=delta
If this does not solve the issue, check transaction SLDCHECK to ensure that connection to SLD is available. If the connection fails, check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked.
Now in the Integration Repository go to Environment → Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment → Clear SLD Data Cache.
Open the XI Start Page and click on Administration. On the Repository tab, choose Cache Overview. Refresh the cache using the buttons/icons on the right. Use XIDIRUSER to refresh the cache. Carry out cache refresh in the same way on the Directory and Runtime tabs.
If you are facing cache update problems in your BPM (say you have modified the BPM, but when executed old version of the BPM is picked up instead of the new one), run the transaction SWF_XI_CUSTOMIZING and press F9 carry out automatic BPM/Workflow Customizing.
Routing Errors
•NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
This means no receiver could be found. Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
•TOO_MANY_RECEIVERS_CASE_BE
More than one receiver found. Check your ID configuration to ensure that there is exactly one receiver for the synchronous message. Multiple receivers for synchronous interfaces are not permitted.
Mapping Errors
•JCO_COMMUNICATION_FAILURE
Check whether RFC destination AI_RUNTIME_JCOSERVER is correctly configured
•NO_MAPPINGPROGRAM_FOUND
Ensure that mapping program exists and is activated. If it exists then update the cache.
•EXCEPTION_DURING_EXECUTE
This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
Messages stuck in queues
Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
Conversion Errors
•Unable to convert the sender service XXXX to an ALE logical system
This error occurs in case of scenarios with IDoc adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.
Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service → Adapter Specific Identifiers. Click the button that says ‘Compare with System Landscape Directory’ and chose Apply. Save and activate your change list.
In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP system’s partner profiles.
Errors on the outbound side
Sometimes the link between SAP XI and the target system (say ERP) goes down and messages fail on the outbound side. It may not be possible to restart them from using RWB or the transactions like SXI_MONITOR/SXMB_MONI. In such cases, you can follow the procedure outlined in the following article - Dealing with errors on the outbound side.
As I said, this is not an exhaustive list. Feel free to add troubleshooting tips that you may have encountered while working with SAP XI. Use the comments form below to add your ideas.
Cache Update Problems
Use transaction SXI_CACHE to update the Integration Directory cache. Alternatively, you can use the following URLs to update the CPA cache. Use XIDIRUSER to refresh the cache.
For complete cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=full
For delta cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=delta
If this does not solve the issue, check transaction SLDCHECK to ensure that connection to SLD is available. If the connection fails, check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked.
Now in the Integration Repository go to Environment → Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment → Clear SLD Data Cache.
Open the XI Start Page and click on Administration. On the Repository tab, choose Cache Overview. Refresh the cache using the buttons/icons on the right. Use XIDIRUSER to refresh the cache. Carry out cache refresh in the same way on the Directory and Runtime tabs.
If you are facing cache update problems in your BPM (say you have modified the BPM, but when executed old version of the BPM is picked up instead of the new one), run the transaction SWF_XI_CUSTOMIZING and press F9 carry out automatic BPM/Workflow Customizing.
Routing Errors
•NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
This means no receiver could be found. Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
•TOO_MANY_RECEIVERS_CASE_BE
More than one receiver found. Check your ID configuration to ensure that there is exactly one receiver for the synchronous message. Multiple receivers for synchronous interfaces are not permitted.
Mapping Errors
•JCO_COMMUNICATION_FAILURE
Check whether RFC destination AI_RUNTIME_JCOSERVER is correctly configured
•NO_MAPPINGPROGRAM_FOUND
Ensure that mapping program exists and is activated. If it exists then update the cache.
•EXCEPTION_DURING_EXECUTE
This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
Messages stuck in queues
Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
Conversion Errors
•Unable to convert the sender service XXXX to an ALE logical system
This error occurs in case of scenarios with IDoc adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.
Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service → Adapter Specific Identifiers. Click the button that says ‘Compare with System Landscape Directory’ and chose Apply. Save and activate your change list.
In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP system’s partner profiles.
Errors on the outbound side
Sometimes the link between SAP XI and the target system (say ERP) goes down and messages fail on the outbound side. It may not be possible to restart them from using RWB or the transactions like SXI_MONITOR/SXMB_MONI. In such cases, you can follow the procedure outlined in the following article - Dealing with errors on the outbound side.
As I said, this is not an exhaustive list. Feel free to add troubleshooting tips that you may have encountered while working with SAP XI. Use the comments form below to add your ideas.
发表评论
-
Gateway Access Control Lists
2015-10-12 11:34 1195Source:http://wiki.scn.sap.com ... -
SLD_UC registration failes with return code 748
2015-10-12 09:44 2194The managed ABAP systems shoul ... -
SLD Related Gateway Serivces Unavaliable
2015-10-12 09:01 751转自:http://www.sapnew.com/212. ... -
JDBC/JMS driver deployment - now more forceMode=true
2012-11-07 19:36 1235转自:http://scn.sap.com/people ... -
JDBC Receiver Adatper的同步场景设计
2012-10-18 15:15 1087转自:http://scnblogs.techweb. ... -
XML Anonymizer Bean in Communication Channel to remove namespace prefix in XML P
2012-07-24 16:14 1414转:http://www.saptechnical.com/T ... -
Step-by-Step Guides - Connectivity > CIDX Message eStandards
2012-05-29 11:36 1339http://wiki.sdn.sap.com/wiki/di ... -
Chem XML Message eStandards and CIDX Scenario Part III
2012-05-25 00:32 948http://scn.sap.com/people/suraj ... -
Chem XML Message eStandards and CIDX Scenario development – Part II
2012-05-25 00:30 1104http://scn.sap.com/people/suraj ... -
Chem XML Message eStandards and CIDX Scenario – Part I
2012-05-25 00:28 1102http://scn.sap.com/people/suraj ... -
SLDDSUSER in SLD is getting Locked
2012-05-24 17:59 1228******* LOCAL to Solution Manag ... -
How to Start the Visual Administrator
2012-05-22 16:24 955http://help.sap.com/saphelp_nw7 ... -
利用XI同步调用(JDBC)oracle数据库的返回值。
2012-02-13 18:03 1148今天用CCBPM做一串业务操作,具体的操作是:我先异步更 ... -
XI/PI Tables LIST
2012-02-09 15:28 1090ABAP ABAP schema Database Trans ... -
(MID)com.sap.SOA.apt_rfc.0303
2012-02-02 11:51 849MessageID com.sap.SOA.apt_rfc.0 ... -
FAQ XI 3.0/ PI 7.0/ PI 7.1 RFC Adapter
2012-02-01 16:52 2449转自:http://www.saptechies.com/fa ... -
如何排查mapping报错。
2012-01-18 15:50 969XI/PI在开发过程中最容易也是出错最多的地位就是map ... -
RFC Sender to JDBC receiver scenario中值得注意的三个问题
2012-01-17 17:09 1467转自:http://scnblogs.techweb.com. ... -
copyValue用法
2012-01-05 15:24 1167copyValue目的就是实现可以取到一个LIST的任意值。 ... -
PI动态生成字段方法
2011-12-28 18:48 1080今天遇到这样一种情况,PI更新数据库时,有的字段是动态更新 ...
相关推荐
在升级 SAP CIM (Common Information Model) 至版本 1.5 的过程中,可能会遇到几种常见的错误。本文档旨在帮助您理解这些错误的原因,并提供相应的解决措施。以下是更新过程中可能遇到的主要问题: 1. **MaxLen ...
"The list of Nastran errors"显然是一份详尽的Nastran错误代码和解释的文档,对于理解和解决Nastran在运行过程中可能出现的问题至关重要。 Nastran错误信息通常分为几类,包括语法错误、数据错误、计算错误和系统...
If you want to know how... 1. Improve Your Punctuation & Grammar.... How to improve your performance in coursework and examinations Write with Confidence Solutions and examples for everyday writing needs
"common-debug.rar_Common Errors"这个压缩包文件显然与通用错误调试有关,而"common_errors"标签进一步强化了这一主题。文件列表中包含"common-debug.c"和"common-debug.h"两个文件,这通常表明我们正在处理C语言...
### 《The A-Z of Correct English》:常见英语错误纠正指南 #### 一、书籍概述 本书名为《The A-Z of Correct English》,是一本专为学生及非母语英语学习者设计的英语语言纠错指南。它旨在帮助读者纠正日常学习...
"C-99-common-errors.zip" 包含了一个名为 "C 99个常见错误.pdf" 的文件,该文件详细阐述了99个C语言初学者可能会遇到的问题。以下是对这些常见错误的概述: 1. **语法错误**:这是最常见的错误类型,包括拼写错误...
For a list of common errors, exceptions and pitfalls that you are likely to run into when coding see: http://docs.python.org/release/3.1.3/library/exceptions.html#bltin-exceptions ...
本资源"Common Errors"是一个针对C++编程中的常见错误进行汇集的文档,旨在帮助读者更好地理解和解决这些问题。下面将详细讨论一些C++编程中常见的错误类型及其解决方案。 1. **语法错误**:这是编程中最直观的错误...
(Geophys Res Lett 34:<BR>L13302, 2007), for reducing the correlated errors in the Stokes coefficients (SCs) of the spherical harmonic expansion<BR>of the GRACE determined monthly geopotential ...
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this...
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within ...
OK, this is a long list but in my own defense, this code // has undergone two major rewrites. Many of the improvements became // necessary after I rewrote the code as a template. Others helped me /...
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this...
这将将 404 错误重定向到 "/errors/{statusCode}" URL,其中 {statusCode} 是错误状态码。 在 MVC Controller 中,我们可以创建一个 ErrorsController 来处理自定义错误页面。例如: ``` public class ...
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this...
### 检测涉及介词的语法错误 #### 背景与意义 本文献探讨了一个重要的自然语言处理(NLP)应用领域:检测非英语母语者在使用英语时出现的涉及介词的语法错误。介词用法是英语语法中最难掌握的部分之一,对于非英语...
"前端开源库-common-errors" 就是一个专注于处理前端开发过程中常见错误的库,它包含了一系列错误处理类和实用的工具函数。这个库旨在帮助开发者更好地识别、预防和解决在开发过程中遇到的问题,提升代码质量和稳定...
Experience Report: A Characteristic Study on Out of Memory Errors in Distributed Data-Parallel Applications