ERROR in adapter monitoring

Hi all,
I am working on File-xi-RFC scenario.
i have done IR and ID working.
Now I have Done test cofiguration in ID there is NO ERROR ......working
File is picked .....as mode is delete.......working..
I check in Adapter Monitoring...............there i got a ERROR. That is..........below
"- Error: 2006-12-16 15:59:57 IST: Message processed for interface MIIS_filetorfc: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was "
please help me...........
what i have to do??
Regards,
Umesh Laxkar

Hi Mr.Umesh
U can check ur RFC Connection is properly Working or not .. In SM59 Tcode...
U can go through the below link...
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
i hope it will be help full for u..
thanks,
vikram.c

Similar Messages

More fields in XML structure error in Adapter Monitor

Hi all
I am getting the following error in the adapter monitor
Error: Message processing failed: Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value ' ')', probably configuration error in file adapter (XML parser error)'
I am using FCC in the rx adapter. I have also checked the fields for any extra fields but there isnt any.
kindly suggest what could be throwing the error
regards
krishna

Hi raj
here are the CC parameters.
BEGIN.addHeaderLine     0
BEGIN.fieldFixedLengths     2,1,3,2,4,1,8,12,8,2,307,12,8,12,18
BEGIN.fixedLengthTooShortHandling     Ignore
BEGIN.endSeparator     '0x0D''0x0A'
CLIENT_RECORD.addHeaderLine     0
CLIENT_RECORD.fieldFixedLengths     2,12,9,4,15,15,4,20,12,9,8,1,1,25,10,1,25,10,1,6,1,1,1,1,1,10,8,1,25,2,1,1,1,106,12,38
CLIENT_RECORD.fixedLengthTooShortHandling     Ignore
CLIENT_RECORD.endSeparator     '0x0D''0x0A'
RELATION_RECORD.addHeaderLine     0
RELATION_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,9,8,1,25,10,1,25,10,1,6,1,1,181,12,38
RELATION_RECORD.fixedLengthTooShortHandling     Ignore
RELATION_RECORD.endSeparator     '0x0D''0x0A'
ADDRESS_RECORD.addHeaderLine     0
ADDRESS_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,5,6,8,24,24,2,35,15,4,15,4,70,8,8,1,50,12,38
ADDRESS_RECORD.fixedLengthTooShortHandling     Ignore
ADDRESS_RECORD.endSeparator     '0x0D''0x0A'
GIVING_REC.addHeaderLine     0
GIVING_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,1,1,1,1,1,1,1,1,1,1,281,12,38
GIVING_REC.fixedLengthTooShortHandling     Ignore
GIVING_REC.endSeparator     '0x0D''0x0A'
ZIKT_REC.addHeaderLine     0
ZIKT_REC.fieldFixedLengths     2,12,9,4,20,9,2,3,2,8,1,1,277,12,38
ZIKT_REC.fixedLengthTooShortHandling     Ignore
ZIKT_REC.endSeparator     '0x0D''0x0A'
BEPER_REC.addHeaderLine     0
BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,291,12,38
BEPER_REC.fixedLengthTooShortHandling     Cut
BEPER_REC.endSeparator     '0x0D''0x0A'
SCORE_BEPER_REC.addHeaderLine     0
SCORE_BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,3,4,1,1,284,12,38
SCORE_BEPER_REC.fixedLengthTooShortHandling     Ignore
SCORE_BEPER_REC.endSeparator     '0x0D''0x0A'
INDBES_REC.addHeaderLine     0
INDBES_REC.fieldFixedLengths     2,12,9,4,20,9,9,2,2,8,8,8,1,256,12,38
INDBES_REC.fixedLengthTooShortHandling     Ignore
INDBES_REC.endSeparator     '0x0D''0x0A'
FUNCTIONAL_REC.addHeaderLine     0
FUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,8,8,1,4,2,2,1,1,1,1,8,1,1,233,12,38
FUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
FUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ACT_REC.addHeaderLine     0
ACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,3,5,1,263,12,38
ACT_REC.fixedLengthTooShortHandling     Ignore
ACT_REC.endSeparator     '0x0D''0x0A'
SCORE_REC.addHeaderLine     0
SCORE_REC.fieldFixedLengths     2,12,9,4,20,9,3,4,1,1,285,12,38
SCORE_REC.fixedLengthTooShortHandling     Ignore
SCORE_REC.endSeparator     '0x0D''0x0A'
ZFUNCTIONAL_REC.addHeaderLine     0
ZFUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,12,3,2,8,8,5,1,8,8,8,4,2,2,1,1,1,1,210,12,38
ZFUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
ZFUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ZACT_REC.addHeaderLine     0
ZACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,3,5,8,8,5,8,1,242,12,38
ZACT_REC.fixedLengthTooShortHandling     Ignore
ZACT_REC.endSeparator     '0x0D''0x0A'
COMMENT.addHeaderLine     0
COMMENT.fieldFixedLengths     2,12,4,140,1,191,12,38
COMMENT.fixedLengthTooShortHandling     Ignore
COMMENT.endSeparator     '0x0D''0x0A'
END_REC.addHeaderLine     0
END_REC.fieldFixedLengths     2,6,6,6,6,6,6,6,6,6,6,6,6,6,6,6,1,257,50
END_REC.fixedLengthTooShortHandling     Ignore
END_REC.endSeparator     '0x0D''0x0A'
REgards
krishna

Error in Adapter monitor

Hi all,
I am trying to complete this blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1345. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] After complete this i just checked my adaper Monitor there file adapter but i got one error as
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair.
what is that error? i did same configuration whatever that blog says.
Thanks in Advance.

Thaks vijaya,
I changed whatever u mentioned in last as Row,*. Then i checked my adapter monitor i got error as
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter 'Row.fieldFixedLengths' or 'Row.fieldSeparator' is missing
Mandatory parameter 'Row.fieldNames': no value found
Can u figure out this error. what are fields i should give in sender. Could u please send me exactly.
Thanks

Error in Mail Adapter Monitor......

Hi....
I have done the mail adapter and i got following error in Adapter Monitor(Mail Adapter)
error occured: [2006-05-31T05:53:34Z] 0 new messages found; no action takenexception caught during processing mail message; com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
how to recover this....
I am using pop3 mail server
Thanks & regards
Ravi Shankar B

hi,
check if you don't have quality of service Best Effort - BE in your mail sender channel
if so change it to EO - Exactly Once
and activate and your channel once more
this setting will eliminate:
NO_RECEIVER_CASE_BE error
change this setting and let me know if it worked
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Error RFC Adapter (as receiver)

Dear All,
My scenario is: File --> XI --> RFC.
I used RFC adapter as a receiver.
I got checkered flag in SXMB_MONI, but i got following error in adapter monitoring:
"com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling /POSDW/CREATE_TRANSACTIONS_EXT in remote system (RfcClient[RFC_Receiver_Adapter]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Error determining transaction category for code 1503"
Please advise on what to do/to check. Thanks.
Best Regards,
Victor.

Hi Sarvesh,
That note is seems apply to my case.
I will ask my basis team to implement it and see whether it will fix my problem.
I will update this thread again once it has been implemented.
Thanks,
Victor.

Wrong port in FTP receiver adapter - no errors in message monitoring?

Hello all
We're on XI 3.0 SP16 and have created / configured a HTTP XML -> XI -> FTP Server scenario. In the receiver comm. channel (ftp) we had specified a wrong port number and always wondered, why we never got errors in message monitoring. Everything seemed to be processed correctly... but no file arrived on the FTP server (receiver) side!
After correcting the wrong FTP port number in the receiver FTP comm. channel everything went fine.
We now encountered a similar problem with a RFC receiver adapter. We're using it in another scenario HTTP XML -> XI -> RFC to SAP R/3 (4.7).
For some reason it died (red status in adapter monitor) and it was no more possible to do RFC calls from XI to SAP R/3 (normal RFC adapter, NO proxies).
In XI message monitor everything seemed to be ok but no message arrived till SAP R/3. Nothing in any queue...
After deactivating and reactivation the RFC receiver comm. channel it worked again BUT ALL PREVIOUSLY SENT messages seem to be lost.
Is it really the way it works? Does XI integration engine at runtime NOT catch whether or not a RFC or FTP receiver adapter died, thus is not able to tell somewhere in message monitor that a message could not be delivered at all?
I'm really confused here but hopefully I simply don't understand some easy principles to take into account...
Our SAP R/3 is on rel. 4.70 with Web AS 6.20. The XI 3.0 plugin is not installed. Do we need to go with server proxies there and use QOS = best effort?!?
Thanks for some suggestions.
Best regards,
Renaud

Hi Michal
Thanks... works great for normal XML based messages!
Now, what if I wanted to pass binary files from one ftp server via BPM to another ftp server in order to enable the transport acknowledgment?
The files polled from ftp server using the ftp sender adapter are all in binary format (ARJ). No xml data in there. How should the message format look like in BPM for the receiving step? Or: how to make sure not to loose the binary content when passing through BPMs?
I need this sort of scenario because of the tansport acknowledgment and because I need to have some sort of message splitting (send the binary file over to a second ftp server and additionally send some kind of info message to SAP R/3 regarding thin binary file).
BTW: in the MessagingSystem/monitor/monitor.jsp I do not see sender / receiver information. Is this normal? It's quite of a bad thing to look inside each message in order to find out what message I'm having in front of me...
Thanks a lot for your support and patience!
Kind regards,
Renaud

Error in File Adapter Monitoring

Hi,
I have created a Sender Communication Channel to pick the file:
The following error message is being displayed in Adapter Monitoring:
Sender Adapter v2622 for Party '', Service 'BS_TRD_PILOT_YOGS':
Configured at 2006-12-19 05:52:17 UTC
History:
- 2006-12-19 05:56:01 UTC: Retry interval started. Length: 60.000 s
- 2006-12-19 05:56:01 UTC: Error: Conversion of complete file content of 'OB10_input.xml' to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 14: missing structure(s) before type 'E1EDK14'
- 2006-12-19 05:56:00 UTC: Processing started
- 2006-12-19 05:55:01 UTC: Error: Conversion of complete file content of 'OB10_input.xml' to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 14: missing structure(s) before type 'E1EDK14'
- 2006-12-19 05:55:00 UTC: Processing started
Please anybody do the needful.
Thanks,
Yogi.

Hi Yogi,
Just go thru your source structure once again.Such type of errors usally come when your source structure is not proper adn also when the parameters for comm'n channel are not mentioned properly.
Usually the Content Conversion Parameters(recordset structure and recordset sequence fileds).
regards
Madhu

Mail Adapter Error occured in Adapter Monitoring....

Hi
I have done the Mail>XI>File senario.... the xi server is sometimes its picking up the mails but some times its not picking... i have give trasport protocol as IMAP4 and url as pop://ipaddress.... I have created the asyncronus message types...n i have given the quality service as Exactly Once... when ever the server is picking file from mail inbox its sending file to the destination directory successfully but in destination side i am getting only the complex tags like the following
<?xml version="1.0" encoding="UTF-8"?>
<ns0:File_Message_Type xmlns:ns0="http://mailtofiledemo.com/ravi"></ns0:File_Message_Type>
i am not getting any nodes inside those tags.... In adapter monitoring i am getting the following error:
error occured: [2006-06-05T05:44:06Z] 0 new messages found; no action takenexception caught during processing mail message; com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
I am using SquirrelMail(webmail) server... so please help me...
I have tried with pop3 alos but its not working
Thanks & Regards
Ravi Shankar B
Message was edited by: RaviShankar B

Hi,
Try giving POP3.
and correct address.. pop3://etc... Remember to give the name of the folder from where the message have to be picked.
Regards
Suraj
Message was edited by: S.R.Suraj

Adapter Monitor Error and SQLServer JDBC Test

Hello !
I have a problem with communication in scenario RFC>XIJDBC !
How i can test my JDBC Coonnection ...database is SQL Server !
In Adapter Monitor i have two errors:
1 - JDBC Error:
Receiver Adapter v2112 for Party '', Service 'BS_IBATCH':
Configured at 2006-06-01 14:45:27 BRT
History:
- 2006-06-06 16:08:47 BRT: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
- 2006-06-06 16:08:47 BRT: Processing started
- 2006-06-06 16:03:46 BRT: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
- 2006-06-06 16:03:46 BRT: Processing started
- 2006-06-06 15:58:46 BRT: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2 - JPR Error:
Error getting JPR configuration from SLD. Exception: No entity of class SAP_BusinessSystem for NWD.SystemHome.euro11 found
No access to get JPR configuration
Someone can help mme in this question?
Regards.
MBoni

Hi,
The JDBC adapter error looks like- your xml document is not correct. ie. the structure which is given to JDBC adapter.
Have a look into this-
http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
Also look into this-for structure
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Regards
Moorthy

Reg: Error in adapter Engine Monitoring

Hi Guys,
In my RFC to File Scenario i got error as Adapter message property was configured was mandatory element but there is no Dynamic ocnfiguration elementin XI MEssage Header. This is occur in adapter engine monitoring in RWB.
Thanks

This error comes if you there is a problem in passing the file via dynamic configuration
for this if you want temporary solution like filename not necessarily be dynamic then go to receiver file adapter then
adapter specific message attributes deselect filed Failif file name does not.... sme option where you can uncheck the failure option
and in this case need to provide the filename and file will get generated with this filename if there is no filename generates using dynamic configuration
for this to resolve permanently then check the filename is passed or not to file adapter in moni in dynamicconfiguratuoin tab of callAdapter pipeline service
HTH
Rajesh

False Error in the Adapter Monitor/File Adapter

I have a receiver file adapter that is showing a 553 Permissions error when the file is actually delivered. This shows up in the adapter monitor and the message monitor.
I've been looking around but I couldn't find anyone who had this problem.

Hi Mark,
I think this error is because of Spaces/or and Invalid Characters like -!"£$%^&*'#... in the file name.
Just check it. ARe you using FTP server ? or NFS ?
If it is FTP then also check that user has a file write permission in the FTP server
>>Also this may be because of you don't have righ to write the directory/file(file permissions) with the name already exists i.e overwrite rights..
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

Error while opening Adapter Monitoring

Dear All,
We have changed the hostname of the server. I have modified all the parameters in the Exchange Profile where host name was given. But when I am opening Adapter Monitoring, it is not taking the new host name rather it is taking the old host name and thn is throwing an error.
Kindly help in resolving this error.
Warm Regards,
N.Jain

Hi,
take the XI HA guide and do all changes related to your XI hostname.
http://service.sap.com/nw04installation --> SAP Netweaver --> SAP Netweaver 2004 --> Operations --> SAP XI --> High Availability Guide - SAP XI 3.0.
For changing the hostname in your J2EE Engine refer to SAP note 757692.
It is not only chaning values in Exchange Profile.
Cheers,
Juergen

FTPS connection error in the adapter monitoring

Hi people,
I make a FTPS connection and the adapter monitor give me this error:
Error: Error connecting to ftp server 'ithppbd0':
ConnectException: Connection timed out (errno:238)
I use a certificate to make this connection.
Is obligatory the use of the private key? or I can use a public key and how?
Thanks!

You may verify the URL, Login ID and Password with logging in via a browser or command prompt.
Some FTP sites allow only a limited number of connections, so check with the FTP site administrator. In the adapter, make sure that you have specified the correct Connection Security and the Command Order.
FTPS does not need the keys, unless you have specified the X.509 Cetificate for Client Authentication.
Lastly, Make sure that the connect mode is per File Transfer.
Hope this helps,
Bhanu

Communication channel monitoring, adapter monitoring error

Hi ,
I am using SAP PI 7.0 with HP-UX.
Here we have 6 logical hosts in one physical host.
Physical host name is u2013 xyz
Integration server name u2013 sappid
The Central SLD: sappid
URL for sappid: sappid: 50300
When I monitoring RWB----
>communication channel monitoring, adapter monitoring, in Development system It's detecting another logical host ( like www://sapard:50300 ) and getting page cannot find error.
1.SLDCHECK
   http://xyz:50300/sld
   host name: xyz
port number: 50300
user : SLDDSUSER
2.SXMB_IFR
   http://xyz:50300/rep/start/index.jsp
3.SMICM
   icm/server_port_0 = PROT=HTTP,PORT=8003
   icm/server_port_1 = PROT=SMTP,PORT=0
   icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=50300
   icm/host_name_full = sappid
4. SLDAPICUST
    SAP_CONFIG   1   xyz   50300   SLDDSUSER
5. SXMB_ADMIN
    Role of Business System Integration Server
    Corresponding Integ. Server http://sappid:8003/sap/xi/engine?type=entry
   Integration Engine Configuration Data -> Check button
6.When I opened the http://xyz:50300/rep/start/index.jsp I got the
XI start page.
    when I opened the http://sappid.AIG.com:50300/
   the page not found issue, when I opened http://sappid:50300/ I got the
   XI start page.
plz help me for this issue.
thanks in advance.
regards,
reddy.

Hello,
I think the FQDN is not set properly.
Problem in the parameter
SMICM
icm/server_port_0 = PROT=HTTP,PORT=8003
icm/server_port_1 = PROT=SMTP,PORT=0
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=50300
*icm/host_name_full = sappid *
Replace this parameter in instance profile
icm/host_name_full = sappid.AIG.com
Then in the host entry of your server please add an entry
172.18.23.233(ip your ur Xi server)       sappid.AIG.com
Then let us know the result.
Thanks and Regards
Vijay

J2EE adapter monitoring problem/no error description found

Hi!!!
I have a problem with J2EE adapter monitoring.
When I use SOAP adapter (receiver, asynchronous mode)
and there is an error in Web Service (for example,
the structure of the message is incorrect) then in Workbench
(in an adapter monitoring) I can only find information that
there is "application error" and nothing more
(I searched also logs and I didn't find anything).
But when there is an error in Web Service then
there are details about this error in ACK message,
for example that required tag is omitted
(I can see this information in the TCPMonitor when
I configure it between SOAP adapter and Web Service).
In "old days" when I use plain Adapter Engine
I could find all information about errors
in Integration Engine Monitoring (sxmb_moni):
- error message (like "application error") was in the "error" node,
- and details about this error (like "java.io.FileNotFound" (...), for example)
were in the "trace" node.
I suppose there is something wrong with my eyes now that I can't see these details,
so please tell when can I find that.
We have SP12.
Regards,
Andrzej

Hi Andrzej
Check this OSS Note 856597
cheers
Sameer

ERROR in adapter monitoring

Similar Messages

Maybe you are looking for