XI3.0 Inbound File Adapter Error on ModuleSLDAccessir.

Greeting,
I have just installed the technical Adapter for XI.3 I tried to use the Inbound File adapter, unfortunately I had two big issues:
1- I was able to execute run_adapter.bat but nothing was reaching the XI system.
When I checked the Log File: I found the following error:
Oct 13, 2004 1:22:08 PM ...aii.messaging.adapter.ModuleSLDaccess [Thread-9] Error: Initializing ModuleSLDaccessor failed with 'java.lang.NoClassDefFoundError: com/tssap/dtr/client/lib/protocol/HTTPException'
2- Second issue: when I try to access the adapter via the browser, the HTML page are not correct ! there is no text displayed. I just got code like : {!%5124_G_XMIT%!}
is there other setting to do ? I followed exactly the install book !
Thanks for your help.
Regards.
M. Zehana
Any help is more than welcome.

Check that you are using XI 3.0. You dont have to use the run_adapter.bat unless you are using the J2SE adapter ( which is 2.0 ) to communicate with an XI3.0 IS. If you have XI3.0 the adapters are configured in the integration directory which are now called communication channels. Therefore an inbound file adapter will be called a sender communication channel. You can create a communication channel either within a scenario or directly in the objects area for the Service ( business system etc ).
Mark

Similar Messages

Inbound file adapter error

Hi,
I have inbound file adapter and when i run the test, the XML message displays the following error
HTTP_STATUS_CODE_NEQ_OK
HTTP status code 401 : Unauthorized
please do help me .
thankx

Hi,
Yes, i m using standalone xi2.0 , the configuration code is as below
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
mode=FILE2XMB
Integration Engine address and document settings (example, see docu)
XMB.TargetURL=http://<host:port>/sap/xi/engine?type=entry
XMB.User=XIAPPLUSER
XMB.Password=XIPASS
#XMB.SenderBusinessSystem=ExtAdapterSender
XMB.SenderBusinessSystem=b2
#XMB.SenderInterfaceNamespace=http://sap.com/xi/xidemo
XMB.SenderInterfaceNamespace=int1
XMB.SenderInterfaceName=FILEINBOUND
XMB.ReceiverBusinessSystem=b1
#XMB.ContentKind=B
XMB.ContentKind=T
XMB.ContentType=text/xml
XMB.QualityOfService=EO
##File Adapter specific parameters (example, see docu)
file.sourceDir=c:/temp
file.sourceFilename=test.txt
file.processingMode=archive
file.archiveDir=c:/temp_archive
file.pollInterval=0
##xml conversion properties if mode FILE2XMBWITHROWCONVERSION specified (example, see docu)
#xml.fieldFixedLengths=15,25
#xml.processFieldNames=notAvailable
xml.fieldSeparator=~
Please let me whether this is correct or im missing some configuration.
thankx

Inbound file adapter error - Guarenteed delivery...

Hi,
I am configuring inbound file adapter and I get an error:
"Guarenteed delivery - operation for 1 file pending"
The adapter does not work for the files pending.
Can anyone help?
Oded.

Hay guys , I am realy stuck,can anybody share his experience with me?
Oded

Inbound File Adapter Error - NullPointerException

Hi,
We are on XI 3.0. We have a scenario of input file via inbound file adpater to R/3 using proxies.
When activating the communication channel (file adapter), an error is raised in the adapter monitor. The error states, "Error: Module Exception 'com.sap.aii.af.mp.processor.ModuleProcessorException' found, cause: java.lang.NullPointerException".
Does anyone have any ideas on this error?
Thanks in advance.
Best Regards,
Doo

Hi,
Can you check the communication channel - "Module" tab. A module processor has to be specified here. For the File Adapter the default value for the Module Processor should be "localejbs/CallSapAdapter" and the Type will be "Local Enterprise Bean".
Warm regards,
Venki.

Error in Inbound File Adapter

Hello,
The scenario :
Flat File => XI => Enterprise (4.7)
I'm getting the following error in the Adapter Engine at time of Reloading the new inbound file adapter.
==========
<i>***** Tue Jul 06 11:46:54 EDT 2004 *****
11:46:59 (4023): File adapter initialized successfully
11:46:59 (4007): File adapter started
11:47:03 (4050): ERROR: Unexpected exception "com.sap.aii.messaging.adapter.ftp.FTPEx: Unknown extension in database file name." occurred</i>
==========
The inbound file adapter is as below ... :
==========
<i>classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
mode=FILE2XMB
XMB.TargetURL=http://host123:8001/sap/xi/engine?type=entry
XMB.SenderBusinessSystem=Sender_System
XMB.SenderInterfaceNamespace=http://abc.com/xi/
XMB.SenderInterfaceName=DataFile_Out
XMB.User=xisuper
XMB.Password=xipass
XMB.ReceiverBusinessSystem=ENT
XMB.ContentType=text/plain
XMB.ContentKind=T
XMB.QualityOfService=EO
file.sourceDir=
file.sourceFilename=DATAFILE
file.processingMode=test
file.pollInterval=060
ftp.host=100.200.300.400
ftp.port=21
ftp.user=userid
ftp.password=passwd
ftp.mode=Text</i>
==========
Any help is greatly appreciated.
Thanx in advance.
Homiar.

All,
Problem is solved. I changed the value for the Source directory & the adapter started to poll.
Thanx,
Homiar.

XI 2.0 Inbound file adapter : Connection reset by peer

I am using XI 2.0 and have an inbound file adapter. It polls every 5 minutes. But at least 1 or twice a day the file adapter stops with the following error message.
"java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read" occurred \par
There have been times when this runs for days or weeks without any problems.
Has anyone else seen this issue and how do your correct it?
Currently I have to go into the file adpaters and restart them manually. It would be nice if there was some way to automate this function. Any ideas?
Regards,
Jim

With JDK 5.0 use ojdbc5.jar instead of ojdbc14.jar.

File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)

File adapter error after updating to SP19 (INBOUND_BINDING_ERROR)
Hi all,
im having some troubles after the installation of SP19 (from SP16 in NW04) with File Adapter (File->Idoc scenario).
In message monitoring (Adapter Engine), I have several messages with status "System Error". The error text is :
<i>Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR
ErrorText: ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace 'http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,</i>
Im sure that the Integration Directory settings have not been changed. So I tried the following, but the problem persists:
- Deactivation/Activation of File Adapter channel
- check that user XIISUSER is not locked
- checked SXI_CACHE (it seems ok)
- Many CPA full refresh
- Dummy modifications of File Adapter channels (a dummy modification of the description)
- Reboot J2EE
I've seen that someone else had problems after upgrading to SP19. I'd really appreciate any suggestion of how to solve my issue.
Thank you
Manuel

Hi Prabhu,
I've already tried to restart server, but nothing happened. (Before update to SP19, the interface worked well).
This is the error log from message monitoring:
<i> 2007-01-16 16:37:34 Success Channel cc_File_Snd_Bolle: Entire file content converted to XML format
2007-01-16 16:37:34 Success Send binary file "BOLLE_20061229142059.CSV" from FTP server "AS810T:/sapinbound", size 8733 bytes with QoS EOIO
2007-01-16 16:37:34 Success Application attempting to send an XI message asynchronously using connection AFW.
2007-01-16 16:37:34 Success Trying to put the message into the send queue.
2007-01-16 16:37:35 Success Message successfully put into the queue.
2007-01-16 16:37:35 Success The application sent the message asynchronously using connection AFW. Returning to application.
2007-01-16 16:37:35 Success The message was successfully retrieved from the send queue.
2007-01-16 16:37:35 Success File "BOLLE_20061229142059.CSV" successfully archived on FTP server "AS810T" as "/sapinbound/bolle/20070116-163735-245_BOLLE_20061229142059.CSV"
2007-01-16 16:37:35 Success The message status set to DLNG.
<b>2007-01-16 16:37:35 Error Received XI System Error. ErrorCode: INBOUND_BINDING_ERROR ErrorText: ErrorStack: Error in sender agreement for party '', service 'LEGACY_DEV', interface namespace http://XXXXX.com/XXXXXX', interface 'INTERFACE_OB' No sender agreement found for , , , , ,
2007-01-16 16:37:35 Error Transmitting the message to endpoint http://SERVERNAME:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: INBOUND_BINDING_ERROR:. </b>
2007-01-16 16:37:35 Success The asynchronous message was successfully scheduled to be delivered at Tue Jan 16 16:42:35 CET 2007.
2007-01-16 16:37:35 Success The message status set to WAIT.
2007-01-16 16:42:35 Success Retrying to send message. Retry: 1</i>
After this, the system try to resend the message, and the same error appears several times.
Ty,
Manuel

File Adapter errors!!!

I am FTPing a file from a system within our firewall through XI. In Message monitoring the first part of the message (from unix to XI) fails after three retries..
But then somehow before the first retry attempt is kicked off, inbound message gets triggered (from XI to file system) and file is successfully stored to file system.
On the other hand, the original outbound message (to XI) fails after three retry attempts with 'Transmitting the message to endpoint' fails.
What is happening here?

>>Try with "Connect Mode" of the File adapter >>configuration will make the difference
I am using 'Per file transfer' for the Connect mode in FIle adapter config.
I am checking in message monitoring (adapter).Usually there are two message. One message from Unix server to XI and second message from XI to local file system.
Krishna, the file gets picked up from my unix server and is also archived. It is when it tries to transfer the file to XI, that it actually fails. it tries to send this file for 20-25 minutes. And then it gives an error,
"Unable to contact target server hostname:port after 1 tries..". And then the message is rescheduled to be delivered after 5 minutes..
But in that interval,before the next retry attempt is triggered, Second part of the message (XI -> local file system) is executed.. And the file is successfully stored in local file system.
Even though second part (XI -> FILE) of the original message is executed, XI still tries to complete the first part of message (FTP -> XI) and gives an error messages after 3 retries.
This scenario happens only once in a while.Also this error happens irrespective of the File / FTP scenario.

Receiver File Adapter error

Hi all,
I am trying to convert the XML to Plain file in receiver file adapter. I am using module - StrictXml2PlainBean
My target structure is -
<MT_Name>
    <records>
        <Header>
        </Header>
        <Item>
        </Item>
    </records>
</MT_Name>
<Header> and <Item> are at same level.
When I use --
1. Header.fieldSeparator = ,
2. Item.fieldSeparator = ,
3. recordTypes = Header,Item
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: Invalid structure name encountered during conversion: records at XML element MT_Name,records
When I use --
1. records.fieldSeparator = ,
2. singleRecordType = records
Then I get this error -
Message processing failed. Cause: com.sap.aii.af.app.modules.conversion.xml2plain.ConversionException: The element nesting level for the structure MT_Name is too deep (reference: 3 levels, found: 4 levels) at XML element MT_Name,records,Header,Item
To add more details to the scenario, multiple records can be generated but one record will have only one Header, with multiple Items.
Any help in this regard will be highly appreciated.
Thanks,
Abhi

Hi Abhi,
Here you go....
For your target structure as:
<MT_Name>
<records>
<Header>
</Header>
<Item>
</Item>
</records>
</MT_Name>
Where I have assumed that <Header> and <Item> are at same level.
DO NOT use any Module just simply configure the receiver channel as below:
In the file Receiver Channel
Recordset Structure = Header,Item
Name                                                                    Value
Header.fieldSeparator                                             ,
Item.fieldSeparator                                                  ,
I have tried this and it works.
Let me know if you are facing any issues.
Cheers
Dhwani

Receiver file adapter error for special char.

I am using MTB in my receiver file adapter. I am getting a special character from source system at end of the string. How to resolve this type of error u2013 please advice.
This error is not coming for every message.
Error message:
Column value xxxx Â too long - must stop, probably configuration error in file adapter
Thanks
Vick

Hi,
Itu2019s basically IDOC to file scenario.
This error is coming for name field.
What I am thinking at this stage to do changes in MTB by define parameters like (NameA.enclosureConversion)

FTP connection error whil,e using flat file adapter error

while using file adapter in the reciever end for proxy to file
i am giving paranters like server IP address and the port , i dont know which port to give by default it is giving me 21 , anyway how to check whether the connection is correct
and more over
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: ConnectException: Connection timed out: connect
please help me in this thanks

HI Sridhar ,
First check wether server started or not and then check you are connecting to FTP server by
go to run -> cmd and write ping and ipaddress which is used and see whether u r getting reponse from teh FTP server.
Try to login to the ftp server which you have mentioned in CC using the user name and pwd, to chk whether you have the permissions to login to the server.
Also the check whether the folder you are trying to access is having permission for delete/read/write.
Restart the FTP server and try it again.
Regards
Sridhar Goli

File adapter error

Hi ,
While monitoring file adapter it is showing the error.
Processing Error: No suitable sender agreement found
In the integration directory i have defined Sender Agreement and also defined Sender communication channel.
The communication channel for file adapter is defined in the business sytems.
The file adapter is not picking the file from the file system.
Kindly suggest what could be the error
Thanks & Regards
Monzy

The sender agreement you have created may not be matching, you have to check your sender system/sender interface & sender namespace parameters again and see if your converted XML ouput by the adapter is matching these 3 parameters.
possible issue could be with ur sender namespace. are u reading XML file or CSV file. If CSV check the namespace definition in ur file content conversion config. it may not match the sender namespace definition in sender agreement. Hope it helps
-Saravana

Flat file with fixed lengths to XI 3.0 using a Central File Adapter---Error

Hi
According to the following link
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
In Adapter Monitor I got the following error,
In sender Adapter,
Last message processing started 23:47:35 2008-10-25, Error: Conversion of complete file content to XML format failed around position 0 with java.lang.Exception: ERROR converting document line no. 1 according to structure 'Substr':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
last retry interval started 23:47:35 2008-10-25
length 15,000 secs
some one help me out ?
Thanks
Ram

from the blog you referenced -
<u> /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
<b>goto step 4</b>
<u>additional parameters</u>
add as the last entry
<recordset structure>.lastFieldsOptional Yes
e.g.,
Substr.lastFieldsOptional Yes

FILE ADAPTER ERROR IN FTP

Hi,
Iam getting the following error in sender file adapter:
Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550 *** ERROR *** NO BATCHES FOR TRANSMISSION
Could anyone help me in this.
Thanks &Regards,
Y.Raj

Hi Raj,
1. Check whether the user you are using has access control i.e Read/Write Access from the folder in FTP server..
2. Check it at OS level by directly pasting or pick the files..
3. From SAP end check the user credientials provided in the file adapter i.e username of the FTP server and the Password of the FTP server it is case-sensitive.
4. Try to give the exact path from where the file is to be picked and reactivate the scenario.
5. what is the file size of the file that is going to be picked from the ftp server.
6. Then finally check in Communication channel monitoring detailed log what is the error it was coming and check the log in XI server you can clearly notice the error.
Even some times it will access at OS level but not through the server for this reactivate the adapter and provdie the user credentials and the path once again..
regards,
Kishore.

Sender File Adapter Error reading file

Hello!
I have a problem with reading a file using the FTP adapter.
I have configured everything according to the steps of weblog "FILE to JDBC Adapter using SAP XI 3.0" (/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30).
I know the sender FTP adapter can connect to the directory and file because:
1) it has complained about wrong format in the content conversion (has been fixed)
2) when there is no file for it there to pick up, the FTP flag in the adapter monitor is green
When I put a file in the specified directory I get the following error:
- 2006-06-21 09:52:23 CDT: Retry interval started. Length: 10.000 s
- 2006-06-21 09:52:23 CDT: Error: Retrieving file 'test_file.dat' failed unexpectedly: FTPEx: Public: The system cannot find the file specified.
- 2006-06-21 09:52:20 CDT: Processing started
- 2006-06-21 09:52:13 CDT: Error: Retrieving file 'test_file.dat' failed unexpectedly: FTPEx: Public: The system cannot find the file specified.
- 2006-06-21 09:52:10 CDT: Processing started
I also get the same error if I skip the content conversion and put a "ready" XML file there.
There should be no auth problems at all. Public server, and I can log on, get, put, delete etc. Also it can apparently read it since it can complain about the content format. Anyone seen this before?
Please advise. Thanks!
Nam

Hi Nam,
Is your User Id and User Id/Password is correct ?
Is connection mode is per file transfer in File Adapter configuration?
Also you can see the log from Visual Admin..
Regards,
Moorthy

XI3.0 Inbound File Adapter Error on ModuleSLDAccessir.

Similar Messages

Maybe you are looking for