Error in XAI Receiver
i created xai inbound service for add operation using bussiness service and i tested that inbound service with
add xai submission its working sucesfully.After that i created xai recevier using FILESCANRCVR and started the Receiver,but i am not getting
the record in the database.i created another xai inbound service using maintanace object its working for filescanrcvr(record is inserting in database) why it is failing with BS,do i require any additional opertaions
the xml file i am giving is scan directory is payment.xml
Payment.xml
<SOAP-ENV:Envelope xmlns:SOAP-ENV="urn:schemas-xmlsoap-org:envelope">
<SOAP-ENV:Body>
<CM_COl_TND5>
<a1>
<paid>2378158431</paid>
<tdcd>CASH</tdcd>
<tdamt>222</tdamt>
<tdctrl>2625028516</tdctrl>
<curr>IND</curr>
</a1>
</CM_COl_TND5>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
FilescanRcvr is
xaiclass:FILESCANRCVR
executerid:CM_XAIURL
XAI JDBC Connection:DEV_04
Scan Directory :D:\spl\DEV_4\ExternalSystem
Scan File:*.*
XAI Inbound Service: CM_COl_TND5(internally i am using Bussiness Service)
pls let me the errors.
1. if i take filescanrcvr as xai class its not allowing any sendor as respose,how can i get response if i take filescanrcvr
2. how can i translate external system text file into soap request using xslt,pls explain me procedure
thanks in advance
1. if i take filescanrcvr as xai class its not allowing any sendor as respose,how can i get response if i take filescanrcvrFile Scan Receiver creates a Staging Control record, there is no "response" applicable for this.
2. how can i translate external system text file into soap request using xslt,pls explain me procedureYou are using a XML file, have you defined appropriate XML Groups and have referenced them on the Receiver?
What Service you are referring in the Business Service?
Similar Messages
-
Anyone can help with the below issue please? Much appreciated.
We have about 2k+ messages in sys.transmission_queue
Telnet to the ports 4022 is working fine.
Network connectivity has been ruled out.
The firewalls are OFF.
We also explicitly provided the permissions to the service account on Server A and Server B to the Service broker end points.
GRANT
CONNECT ON
ENDPOINT <broker> <domain\serviceaccount>
Currently for troubleshooting purposes, the DR node is also out of the Availability Group, which means that we right now have only one replica the server is now a traditional cluster.
Important thing to note is when a SQL Server service is restarted, all the messages in the sys.transmission queue is cleared immediately. After about 30-40 minutes, the errors are continued to be seen with the below
The
connection was
closed by the
remote end,
or an
error occurred while
receiving data:
'64(The specified network name is no longer available.)'We were able to narrow down the issue to an irrelevant IP coming into play during the data transfer. We tried ssbdiagnose runtime and found this error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>SSBDIAGNOSE -E RUNTIME -ID 54F03D35-1A94-48D2-8144-5A9D24B24520 Connect to -S <SourceServer> -d <SourceDB> Connect To -S <DestinationServer> -d <DestinationDB>
Microsoft SQL Server 11.0.2100.60
Service Broker Diagnostic Utility
An internal exception occurred: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
P 29830 Could not find the connection to the SQL Server that
corresponds to the routing address tcp://XX.XXX.XXX.199:4022. Ensure the tool is connected to this server to allow investigation of runtime events
The IP that corresponds to routing address is no where configured within the SSB. We are yet unsure why this IP is being referred despite not being configured anywhere. We identified that this IP belongs to one of nodes other SQL Server cluster, which has
no direct relation to the source server. We failed over that irrelevant SQL Server cluster and made another node active and to our surprise, the data from sys.transmission_queue started flowing. Even today we are able to reproduce the issue, if we bring
back this node [XX.XXX.XXX.199] as active. Since, its a high business activity period, we are not investigating further until we get an approved downtime to find the root cause of it.
When we get a approved downtime, we will bring the node [XX.XXX.XXX.199] as active and we will be running Network Monitor, Process Monitor and the SSB Diagnose all in parallel to capture the process/program that is accessing the irrelevant IP.
Once, we are able to nail down the root cause, I will share more information. -
A Kerberos Error Message was received: on logon session
Hi i am getting this error in event viewer in a client machine, from where powershell sccripts collecting data from our sharepoint servers
Log Name: System
Source: Microsoft-Windows-Security-Kerberos
Date: 9/16/2014 11:09:42 PM
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PortalHealthChe.XYZportal.com
Description:
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 20:9:42.0000 9/16/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XYZPORTAL.COM
Server Name: HTTP/XYZWFE01.XYZPORTAL.COM
Target Name: HTTP/[email protected]
Error Text:
File: 9
Line: f09
Error Data is in record data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Kerberos" Guid="{98E6CFCB-EE0A-41E0-A57B-622D4E1B30B1}" EventSourceName="Kerberos" />
<EventID Qualifiers="32768">3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-16T20:09:42.000000000Z" />
<EventRecordID>5466</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>PortalHealthChe.XYZportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="LogonSession">
</Data>
<Data Name="ClientTime">
</Data>
<Data Name="ServerTime">20:9:42.0000 9/16/2014 Z</Data>
<Data Name="ErrorCode">0x7</Data>
<Data Name="ErrorMessage"> KDC_ERR_S_PRINCIPAL_UNKNOWN</Data>
<Data Name="ExtendedError">0xc0000035 KLIN(0)</Data>
<Data Name="ClientRealm">
</Data>
<Data Name="ClientName">
</Data>
<Data Name="ServerRealm">XYZPORTAL.COM</Data>
<Data Name="ServerName">HTTP/XYZWFE01.XYZPORTAL.COM</Data>
<Data Name="TargetName">HTTP/[email protected]</Data>
<Data Name="ErrorText">
</Data>
<Data Name="File">9</Data>
<Data Name="Line">f09</Data>
<Binary>3015A103020103A20E040C350000C00000000001000000</Binary>
</EventData>
</Event>
adilHi
i am getting this error in a client machine
Log Name: System
Source: Microsoft-Windows-Security-Kerberos
Date: 9/16/2014 11:09:42 PM
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PortalHealthChe.XYZportal.com
Description:
A Kerberos Error Message was received:
on logon session
Client Time:
Server Time: 20:9:42.0000 9/16/2014 Z
Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
Extended Error: 0xc0000035 KLIN(0)
Client Realm:
Client Name:
Server Realm: XYZPORTAL.COM
Server Name: HTTP/XYZWFE01.XYZPORTAL.COM
Target Name: HTTP/[email protected]
Error Text:
File: 9
Line: f09
Error Data is in record data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Kerberos" Guid="{98E6CFCB-EE0A-41E0-A57B-622D4E1B30B1}" EventSourceName="Kerberos" />
<EventID Qualifiers="32768">3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-09-16T20:09:42.000000000Z" />
<EventRecordID>5466</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>PortalHealthChe.XYZportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="LogonSession">
</Data>
<Data Name="ClientTime">
</Data>
<Data Name="ServerTime">20:9:42.0000 9/16/2014 Z</Data>
<Data Name="ErrorCode">0x7</Data>
<Data Name="ErrorMessage"> KDC_ERR_S_PRINCIPAL_UNKNOWN</Data>
<Data Name="ExtendedError">0xc0000035 KLIN(0)</Data>
<Data Name="ClientRealm">
</Data>
<Data Name="ClientName">
</Data>
<Data Name="ServerRealm">XYZPORTAL.COM</Data>
<Data Name="ServerName">HTTP/XYZWFE01.XYZPORTAL.COM</Data>
<Data Name="TargetName">HTTP/[email protected]</Data>
<Data Name="ErrorText">
</Data>
<Data Name="File">9</Data>
<Data Name="Line">f09</Data>
<Binary>3015A103020103A20E040C350000C00000000001000000</Binary>
</EventData>
</Event>
adil -
Error in file receiver adapter (Directory does not exist / cannot be create
I have a NFS reiceiver file NFS adapter with target directory:
10.128.68.38\arbo2000\UploadPinfos\arbodev
if I run this line in windows, windows access to this folder.
Full Error log:
Receiver Adapter v2123 for Party '', Service 'BS_0000_ARBO_DEV':
Configured at 2006-04-06 18:08:26 CEST
History:
- 2006-04-06 18:08:35 CEST: Error: Message processing failed: Exception: Message processing failed - configuration error in file receiver adapter (Directory does not exist / cannot be created)
Can somebody help me please??Hi Alvaro,
If your XI server is running on Unix platform then you'll get the access only after mounting 10.128.68.38 this system as a drive. This is equivalent to the windows network mapping.
Next thing is that once that is done then you can access the path /arbo2000/UploadPinfos/arbodev by mentioning it in your directory path.
To check whether the above mentioned is the problem then pls do try by doing it with FTP protocol. If it works then for acting as a local directory for NFS you need to mount the drive.
Cheers
JK -
Error in File Receiver Channel
Dear All,
I am Getting below error in File Receiver Channel.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: User ABC cannot log in.
Regards,
ManikandanHi Manikandan,
Check the username and the password for the FTP server. If the username or the password is wrong then you would be able to post the message.
Also, there might be a timout issue, In the timeout parameter enter some value.
Ref: FTP Server connection Problem
Check and update us.
Thanks, -
Error in HTTP_AAE receiver communication channel, PI 7.4 dual stack
Dear Experts,
I am facing the below certificate error in HTTP_AAE receiver communication channel while using the third party (bank) private key. Third party bank server is HTTPS enabled, moreover they have generated the public and private keys on their server, and they shared the corresponding private keys in .p12 format to us. Our scenario in SAP PI is synchronous ABAP Proxy to HTTP_AAE, when I see the message in SXMB_MONI after testing, we get he below certificate error, though we have provided the correct path from keystorage view and keystorage entry in HTTP_AAE receiver communication channel
“com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SENDING_HTTP_REQUEST, sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target”
We have imported the private key provided by bank in Netweaver admin key storage, by following the below steps.
NWA -> Certificates -> Key Storage -> TrustedCA->Import Entry->Entry Type->PKCS#12 Key Pair->select the .p12 file->import.
Please see the attached doc for related screenshots.
Please experts help me experts as this is on high priority from client, also suggest me if I am doing anything wrong here.
Thanks,
FarhanHi Farhaan,
do you have only one certificate or multiple certificate? HTTPS can have 2 or 3 certificates (Root, Intermediate [optional, if any 3rd party person is there in the middle then we can get this certificate] and system certificates).
The issue is with the certificate and it can be because All the certificate is not present or path is not correct.
Please refer the below wiki in which solution is given for this peroblem.
Troubleshooting 7.1 - End-User Experience Monitoring - SCN Wiki
The similar issue is resolved by applying SP level patch, please refer the below discussion
SAP PI 7. 3 HTTP_AAE Receiver with SSL
Please check the below blog -
Configure the HTTP_AAE receiver communication channel with SSL
please also check the below discussion
Where to Import Clients SSL certificate for HTTP_AAE
regards,
Harish -
Hi Experts,
I am facing an error in one of the file to Proxy scenario. It's giving the following error.
SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411 Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411 Error when parsing receiver listLength of XML Document 411 An error occurred when deserializing in the simple transformation program SXI_PARSE_RECEIVERS Data loss occurred when converting ExceptionMessage: LookupValueNotFound: SourceContext: http://sap.com/xi/XI SourceAgency: SenderBusinessService SourceScheme: Payments TargetContext: http://sap.com/xi/XI TargetAgency: ReceiverBusinessSystem TargetScheme: ReceiverCheck KeyValue: BusService</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The same scenario is working fine in production but in quality,its giving teh above error. We have used the value mapping. I have checked each and everything. Every thing is matching with teh production. The XSLT mapping program is working well in production but in quality same program is not working. I have also checked the extended receiver configuration setting. Everything is same as in production.
Please help me out. I would be greatful to every one.
Thanks
VeeruHI,
Error clerly says that there is error in value mapping ..
Check the target values exist for the source scheme and agency..
Check the cache is updated in RWB..
HTH
Rajesh -
Finger Print error in SFTP receiver adapter
Hi Experts ,
I am getting following error in SFTP receiver channel, here I have nominated the password based authentication rather than certificate authentication method in channel. And I have created finger print in NWA and shared with SSH server admin to import , then I maintained the same in my receiver channel also. And I have done the vice-versa created the finger print in SSH server side and given the same in channel . Still error is persist in channel, experts please suggest .
Error :
Message could not be forwarded to the JCA adapter. Reason: com.jcraft.jsch.JSchException: Fingerprint invalid. Fingerprint is: 6b:f4:38:e7:13:31:59:c8:76:4f:e1:93:10:ac:73:ca
Error MP: exception caught with cause javax.resource.ResourceException: com.jcraft.jsch.JSchException: Fingerprint invalid. Fingerprint is: 6b:f4:38:e7:13:31:59:c8:76:4f:e1:93:10:ac:73:ca
Error Exception caught by adapter framework: com.jcraft.jsch.JSchException: Fingerprint invalid. Fingerprint is: 6b:f4:38:e7:13:31:59:c8:76:4f:e1:93:10:ac:73:ca
Screen shots :
Thanks in advance,
RAJAAnd I have created finger print in NWA and shared with SSH server admin to import
>>>> Though i'm not sure how it works, you can validate the fingerprint of the FTP server with one which is configured in the channels.
If you have file zilla/coreFTP try to connect with the credentials and then you'll get a pop-up which should have the finger print information. -
Kind people, I'm getting this error with an InterConnect FTP adapter (the adapter is on one box, the directory it reads from on another box):
Transport logs:
[IPT_FileRecMonitorError] Error in ftp receiver monitor.
oracle.oai.agent.adapter.transport.TransportException: Unable to enter passive mode. rc = 425 425 Can't open passive connection: Too many open files.
at oracle.oai.agent.adapter.transport.basic.ftp.FTPAgent.getFileList(FTPAgent.java:259)
at oracle.oai.agent.adapter.transport.basic.FileSource.getFileList(FileSource.java:210)
at oracle.oai.agent.adapter.transport.basic.FileSourceMonitor.processMessages(FileSourceMonitor.java:399)
at oracle.oai.agent.adapter.transport.basic.FileSourceMonitor.run(FileSourceMonitor.java:185)
Caused by: java.io.IOException: Unable to enter passive mode. rc = 425 425 Can't open passive connection: Too many open files.
at oracle.oai.agent.adapter.transport.basic.ftp.FTPClient.establishDataConnection(FTPClient.java:206)
at oracle.oai.agent.adapter.transport.basic.ftp.FTPClient.listFiles(FTPClient.java:431)
at oracle.oai.agent.adapter.transport.basic.ftp.FTPAgent.getFileList(FTPAgent.java:253)
It seems to me (maybe) that what is happening is that InterConnect is not closing the FTP connections after it FTPs a file, and after a while there are too many connections open. If I bounce the adapter, it works fine again for a period of time. I also delete the log files, but don't know if that has any relationship to this. Is there some parameter in the adapter.ini file I can set, or do I need to see a Unix sys admin about this???
Thanks in advance for any insight you might be able to provide!This was addressed in a similar TAR: 4380173.994. Here is the solution I remember:
### Detailed Problem Statement: ###
When FTP adapter has run for some time (1 or 2 days) it keeps on failing with
error message:
Caused by: oracle.oai.agent.adapter.transport.TransportException: Unable to
enter passive mode. rc = 425 425 Can't open passive connection: Too many open files
at oracle.oai.agent.adapter.transport.basic.ftp.FTPAgent.getFileNames(FTPAgent.java:
253)
at oracle.oai.agent.adapter.transport.basic.FileSource.getFileNames(FileSource.java:190)
at oracle.oai.agent.adapter.transport.basic.FileSourceMonitor.processMessages(FileSourceMonitor.java:323)
at oracle.oai.agent.adapter.transport.basic.FileSourceMonitor.run(FileSourceMonitor.java:123)
Caused by: java.io.IOException: Unable to enter passive mode. rc = 425 425
Can't open passive connection: Too many open files
at oracle.oai.agent.adapter.transport.basic.ftp.FTPClient.establishDataConnection(FTPClient.java:205)
at oracle.oai.agent.adapter.transport.basic.ftp.FTPClient.listNames(FTPClient.java:455)
at oracle.oai.agent.adapter.transport.basic.ftp.FTPAgent.getFileNames(FTPAgent.java:246)
... 3 more
This error was already reported in tar 14948114.6. The solution back then was
to increase no of open files in server running the adapter. We have done that
but it does not seem to help (it might take some more time to run to this error
though).
POTENTIAL SOLUTION(S)
======================
Set the following adapter.ini parameters:
sender.keep_connections=false
receiver.keep_connections=false -
Errors about 'No receiver could be determined'
Hi all:
I am setting up one scenario about ' IDOC to file '.
When I send IDOC from one R3 system to XI , I meet with the following errors.
No receiver could be determined
The SOAP Error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Grouping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The trace is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Grouping
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- <!-- ************************************
-->
<Trace level="1" type="T">User: KEN</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = 2B74B179E6789D40BCC4A22D826EBDEF</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0012</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0012</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 800</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = KEN</Trace>
<Trace level="1" type="Timestamp">2006-03-06T13:55:08Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace>
Could anybody give me some clue to debug this problem ?Hi Jianhong,
Since you are doing an idoc to file scenario, you would not require a sender idoc adapter, you would have to configure only a receiver file adapter. Since i guess this is your first idoc to file scenario refer this blog to check if you have followed the steps correctly in the repository and directory:
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] The blog does not talk about partner profile setup, and i hope you are aware of how to do this.
Configure your receiver file adapter according to this:
http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm
Do ask if you require further information.
Regards,
Chandra -
Error with the Receiver JMS Adapter (Connection On-Demand feature)
Hi,
In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
The message status was set to WAIT.
Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
Any idea?
PI 7.1 EHP1
Thanks,
Martin
/people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PMPlease ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).
-
ALEAUD back to ECC when we have an error in the receiver adapter engine
Hello friends,
My scenario is ECC (async) to SOAP (sync) and back to ECC (async = ALEAUD). I'm using aync/sync bridge is receiver SOAP adapter.
Is it possible to send back an ALEAUD automatically when I have an error in my receiver SOAP adapter? If so can you please explain how to achieve that?
Your help is greatly appreciated,
Thank you in advance,
Kind regards,
JohnHi,
The below reports will helps you to get alerts when any error in target end..
IDX_NOALE - you can configure what kind of acknowledgement you want to request for the send message type. for example you can configure for only error acknowledgements.
IDX_ALEREQUEST - you can configure to send back an acknowledgement as PI message, so that you can control the ALEAUD content by mapping.
Thanks & Regards,
A.Neelima. -
Error in Extended Receiver Determination
Hello Experts,
We are working on a scenario where, we are using Extended Receiver Determination.
In this reveiver determination mapping we are doing JDBC lookup and some receivers are determined on that basis.
Also, we have a default receiver in mapping.
We are using: SAP PO 7.4 SP 7
We are getting below error while testing from WSnavigator/SOAP UI, but mapping works when we test it in ESR.
Error:
<s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
<text><![CDATA[
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: Error while executing receiver determination mapping.
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:773)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:530)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
Kindly help.hi,
you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
please find the link which deals with how to impliment lookup for file adapter.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
regards,
navneet. -
Hi Friends, mails from SAP are sent to HR users from WF-BATCH.The users are unaware why the message have been sent.
The message that is being sent is given below:
Messages received from: Batch WF-BATCH
Subject: Error in event receiver
Body of message:
Error processing following event linkage:
KNA1 STATUSCHANGE WORKITEM
Following error occurred:
WL 605
000003807054
Message text:
Work item 000003807054 locked by user (enqueue error)
Event container appended as attachment.
Event linkage not changed.
Event stored temporarily.
Events can be redelivered via event queue
administration (transaction SWEQADM).
Kindly help.Hi,
Please refer the link [Workflow System Administrator Role|http://help.sap.com/saphelp_nw70ehp2/helpdata/en/8c/1923ce932b11d2a5ea0060087a79ea/content.htm] - The administrator needs to be assigned with these roles mentioned in this hellp documentation.
The error message in your case indicates that there is some problem in the "Event Linkage". KNA1 is the Customer Master Table. I guess it is the "STATUSCHAGED" event of Customer Object is having some event linkage problem. You can check the event type linkages in SWETYPV Transaction. Thanks.
Regards
Suresh -
Error on SOAP Receiver for Axis
Hi all,
Is there anybody to help for solution?
Thanks.
Error on SOAP Receiver for axis
Error Message
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Exception raised from invocation of public void com.sap.aii.adapter.axis.modules.AFAdapterBean.ejbCreate() throws javax.ejb.CreateException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@3ff5ea5d for bean sap.com/com.sap.aii.axis.appxml|com.sap.aii.adapter.axis.ejb.jarxml|AFAdapterBean; nested exception is: javax.ejb.CreateException: java.lang.NoClassDefFoundError: org/apache/axis/types/URI$MalformedURIException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>We deployed com.sap.aii.af.axisproviderlib.sda to use SOAP for axis.
We sent data from SAP to Axis, error below ocured?
What must we do to solve problem?
Thanks.
Error
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: org.apache.axis.ConfigurationException: handler is not instantiated org.apache.axis.ConfigurationException: handler is not instantiated at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:73) at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75) at sun.reflect.GeneratedMethodAccessor360_10000.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2634_10000.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1431_10000.process(Unknown Source) at com.sap.aii.af.app.listener.AFWListenerBean.onMessage(AFWListenerBean.java:332) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1479_10000.onMessage(Unknown Source) at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:314) at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1000) at com.sap.engine.messaging.impl.core.queue.consumer.RequestConsumer.onMessage(RequestConsumer.java:73) at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:921) at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56) 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:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Maybe you are looking for
-
Can't mount database using Oracle 8i on linux
I am not able to mount an Oracle database. I am new to Oracle and am working on an Oracle8i installation on an Intel Linux Suse 6.3 platform. I am using only one harddrive and am not using the 4 mount points as mentioned for efficiecy purposes in the
-
Hi Apple Support Communities: I need your help in order to know exactly ¿What to do with a copy corrupted of iTunes, after a clean installation of Mavericks OX 10.9.5 in a desktop iMac, 2.7 GHz Intel Core i5, 8 GB 1600 MHz DDR3, 1 TB storage. The mes
-
Using .png images in a website?
Being new'ish to Fireworks and the .png format I am really amazed at the quality of png's in a webpage and how the hold their quality. In web design I tend to like placing text over images and this can often have quality issues as text tends not to w
-
Payment information updated but iTunes still billing old bank
Who do I need to contact about making sure ITunes is billing the correct account. Correct billing information is showing in iTunes payment information but iTunes is still billing my old bank information that I iTunes shows as updated. Please help!
-
Hi all, When I try to access a JSP from my Global creation in OBPM 10GR3, sometimes this message appears:- [<W> 0830 15:19:41.296] Main (<5> [ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'): Error workspace-131478298092