Com.sap.aii.adapter.file.ftp.FTPEx: 550 You are not allowed to issue this

hi All,
We are getting below error while connecting to an FTP location through File Adapter:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: An error occurred while connecting to the FTP server XYZ. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 You are not allowed to issue this command'. For details, contact your FTP server vendor.
Also when we tried to connect to this FTP location through PI server we able to connect, but when we connect to it through channel we are getting above error.
Please Help!
Thanks,
Mayank

hi All,
The usedid we are using to connect to FTP location has appropriate access to write(we have an receiver file adapter) the files, when we connected to FTP location from PI server using same useid(as used in channel) we are able to connect to FTP location and also able to write the file there.
Now error soming is:
An error occurred while connecting to the FTP server XYZ. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Operation is not supported under Connect:Enterprise FTP server.'. For details, contact your FTP server vendor.
Thanks,
Mayank

Similar Messages

Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550

Hi Experts,
We have many File to EDI scenarios wherein XI System pick up the XML and sent to customers via EDI. Recently we faced a problem so created a Back-up System (Production copy) and tested successfully. After sometime the messages were routed to this back-up system and when we notice it and then stopped the back-up system. All the messages that were routed to back-up system, we try to send the same messages from the actually Production system to our customers. Now the problem is XI system (Production system) is unable to pick these files and I check the communication monitoring and encountered the below error message.
Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550.550
Can anyone let me know how to fix the issue or what needs to be done?
Your help is highly appreciated.
Regards
Faisal

Hi,
It seems to be problem with permission of files. Please ask your basis to do following:
1. Set the permissions to FTP User you are using as 777 rights(full access to read , write and delete)
2.If you have access to PI server, try to telnet /connect to ftp using command prompt (open ftp .....) the FTP server form there, you should see the same error there , inform this to your network guys.
3.Clear all the files places already in the ftp (take backup) and test afresh after permissions are set by basis team.
Regards
Aashish Sinha

Com.sap.aii.adapter.file.ftp.FTPEx: 550

Hi,
I have the below error in my sender file channel. I also read the following thread
FTP Error
Error:
An error occurred while connecting to the FTP server '10.12.12.101:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 C:Inetpubftproot: The filename, directory name, or volume label syntax is incorrect. '. For details, contact your FTP server vendor.
The above thread suggests me to change the setting in the IIS. Should do that settings in the PI server or the source FTP server.
Also does anybody have any other solution to this problem.
Rgds,
Mithun

HI,
If you're using an FTP server you need to know the path to the file on the FTP.
To do this I suggest to connect to the FTP using Internet Explorer and navigating the FTP folders until reaching the right one.
Then on the url bar you should got something like this: "ftp://server:21/path/to/file/". Use "/path/to/file" as value for the file adapter configuration.
Please refer below blogs:
unable to send file to FTP server
FTP to Windows Server
thanks,

File to File-CC 'error com.sap.aii.adapter.file.ftp.FTPEx: 550 Access deni'

Hi friend,
I am doing file to file scenario in which i wan to move one file from input folder to output folder.
I had created as FTP on one system that i am able to access and have full authorization to read and write.
and created that two input and output folder in it,n kept an xml file in input folder.
When i see sender communication channel in RWB it is showing error, "com.sap.aii.adapter.file.ftp.FTPEx: 550 Access denied'
I checked password,it correct also I tried to test it using Anonymous Login, but the same things.
SO i am not sure where i had done mistake.
Plz give ur suggestions.
Thanks

Hi,
Please Check below few steps:
Check if the username and the Password is created to write the file in the desired directory.
Check the username is provided the authorization to write the file in the desired directory. ... IS Guys will help you..
Confirm if the directory created have all the authorization to write the file.
ls - lrt
chmod 777 Directory Name
all the authorization will then be provided
Confirm if the directory is created with the root id then it there might be some problem with the user name u r trying to create..
Hope this will help.
Assign points for helpful answer..
Thanks
JAY.

Com.sap.aii.adapter.file.ftp.FTPEx: 421

Hi Guys,
I am getting these two error messages:
1) com.sap.aii.adapter.file.ftp.FTPEx: 421 Maximum session time exceeded - closing
2) com.sap.aii.adapter.file.ftp.FTPEx: 421 Too many users - please try again later
when XI Sender File Adapter tries to pick the files from the FTP server.
I have not set any limit to the number of session for the user that I have mantianied in the adapter. (Niether I know it -:) how to set.)
Any idea or help, how to resove this error.
Thanks in adavance,
Namadev

Hi Namdev,
Your this error is coming as your FTP server maximum allowed connection is reached. so as the solution I would suggest to change the Connection mode property of your communication channel as Per File Transfer as default property is Permanently which reserves connection forever.
So other communication channels cannot communicate. Make this changes to all the communication channel you have configured.
And your problem is solved.
enjoy....
Thanks & Regards,
Gaurav Patwari

'com.sap.aii.adapter.file.ftp.FTPEx: 501 Unknown error

Hello ,
I am facing an error in communication channel while trying to post the file to the FTP server,
The error is " Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: An error occurred while connecting to the FTP server '10.100.5.00:20'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 501 Unknown error'. For details, contact your FTP server vendor"
Please could you advice what need to be done to resolve this.
Thanks ,
Siva

Hi ,
FTP 501 Error is: "Syntax error in parameters or arguments"
Also, i see that the ftp address and port mentioned in your case is:
10.100.5.00:20
Hence, i see three probable issues here.
1. FTP Port :
Just check if the FTP server's port number '20' mentioned in your case is open as this is the data connection port. Moreover, the default port mentioned while creating a file channel is 21. Just check about the port number '20' with the FTP server administrator if this port number is opened and functioning.
2. FTP server address:
Also, try giving your FTP Server's address as 10.100.5.0
3. Also, check if the FTP server is reachable from the PI Server by using a simple ping command.

Could not process file 'Input 110110b.txt': com.sap.aii.adapter.file.

I have a FILE Adapter using FTP as a transport that is generating a very odd error.
The FTP sender channel is giving the following error is set up to retreive all files (*) from a specific directory. If you look at the error, it indicates an error processing the file 'Input 110110b.txt' as a file -- the only way this filename woudl be visible is if the adapater interrogated the directory, or the filename was hard-coded in the file mask. But the error indicates it can't change to the directory. The only way it would have come up with the file is if it had already CD'd t that directory.
1/7/11 8:12:01 AM   Retry interval started. Length: 60.0 seconds
1/7/11 8:12:01 AM   Could not process file 'Input 110110b.txt': com.sap.aii.adapter.file.ftp.FTPEx: 550 Failed to change directory.
1/7/11 8:12:00 AM   Processing started
My first thought was a simple permission issue, so I opened a connection to server with FileZilla (an FTP client) and was able to retrieve the file without a problem. I was also able to drop a file in the directory. There is no permissions problem.

Hi
Please check the below points before processing any file
a) check the File placing by a Local Plant FTP owner is using the same authentification credentials It means both PI and source team needs to use same FTP User ID and login credentials otherwise if suppose if source team is placing with one User and PI cannot able to pick that file as this User cannot have permissions in this case also u will get 550 error
b) I know what ur telling is u manualy palced one file and able retrive...but do one thing u can login with same PI FTP login server credentials and then place the file with different name also I suggest lets test the channel by simply keeping
. not simply * if you keep simply * then u cna use in receiver chanel while using dynamic connfiguration.
Else give *.txt and then activate the channel and also please check the CACHE as well
Regards
Amar Srinivas Eli

FTP error-Unable to create new pooled resource: com.sap.aii.adapter.file.ft

Hi,
We have a scenario where XI receives a Idoc and based on the contents of Idoc, It will generate 5 different files and send it to the external FTP server.We configured 5 receiver channels for these 5 files.
When this interface runs, most of the files will be delivered but some of the messages will be errored out.
The receiver channel has shown the following error-
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: com.sap.aii.adapter.file.ftp.FTPEx
I tried to resend them by temperorily stopping other channels to reduce connections to this FTP server.But these messages again resulted with same error.
Can someone suggest what might be the cause for this error.
Thanks in advance.

Hi ,
As I am not sure about the problem so U just try all of the option I am writing below. It may help u as these are the probable solutions for this problem.
1.perform Full CPA cache refresh using PIDIRUSER
2.The problem seems to be in establishing the connection with the File server . This could be due to
a. Wrong user name or password in receiver adapter .
b. Firewall connection are not open
actually you are saying that some files are being delivered so all the file has to be deliverd on same server on diffrent directory or all files are going on diffrent server at present I am assuming that all files are going on diffrent server so please check UID & PWD properly.if they are on same server but diff. directory it can be easily done using one Communication channel only.
3. Finally please check the errorneous communication channel .
to check your communication channels are working fine or not you can check in channel monitoring in PI7.0, adapter monitoring in Xi3.0.
if you are on PI7.0, goto RWBCache monitoring select AE and cilck disply-select the date todays--check everything is greent here
4.Please check your maximal connection pool .
Regards,
Saurabh

PI 7.1 and Oracle JDBC driver: missing com.sap.aii.adapter.lib.sda

Hello,
I want to deploy the JDBC driver for Oracle databases as described in OSS 1138877 on a brand-new PI7.1 (SP06 Stack) installation. Unfortunately, I can't find com.sap.aii.adapter.lib.sda on the system, so I can't add the ojdbc14.jar file and deplay it using JSPM.
Where can I get it from?
Thank you and best regards,
Herwig

hey,
The JDBC driver installation is different for PI 7.1.
The dowload/modify/deploy .sap.aii.adapter.lib.sda method was used in the earlier versions.(mentioned in the How to guides)
Look at the SAP documentation below -
http://help.sap.com/saphelp_nwpi71/helpdata/en/cf/128a42f802a01ae10000000a155106/frameset.htm
Arvind R

Com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc don't start

Hello,
In order to configure JMS Receiver Adapter to access Websphere Application Server 7.0, I have recently deployed file com.sap.aii.adapter.lib.sca with the following libraries:
com.sap.aii.adapter.lib_api.jar
com.ibm.ws.ejb.thinclient_7.0.0.jar
com.ibm.ws.orb_7.0.0.jar
com.ibm.ws.sib.client.thin.jms_7.0.0.jar
com.ibm.ws.runtime.jar
javax.j2ee.jms.jar
The communication channel can reach the queue but when I send a message it fails because services sap.com/com.sap.aii.adapter.jdbc.svc and com.sap.aii.adapter.jms.svc are not started.
Checking dev_server0 file I found the following error.
==============================================================================================
Service com.sap.aii.adapter.jdbc.svc start ================= ERROR =================
com.sap.engine.frame.ServiceException: Could not obtain an initial context due to a communication failure. Since no provider
URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure that any
bootstrap address information in the URL is correct and that the target name server is running. Possible causes other than
an incorrect bootstrap address or unavailable name server include the network environment and workstation network configurati
on.
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:151)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,
port=2809 vmcid: 0x4942f000 minor code: 3586 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jdbc.SapAdapterServiceFrameImpl.start(SapAdapterServiceFrameImpl.java:100)
... 6 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=sapdpi-lpar,port=2809 vmcid: 0x4942f0
00 minor code: 3586 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:425)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:120)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:209)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 16 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:522)
at java.net.Socket.connect(Socket.java:470)
at java.net.Socket.<init>(Socket.java:367)
at java.net.Socket.<init>(Socket.java:180)
at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:270)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
... 28 more
Service com.sap.aii.adapter.jms.svc start ================= ERROR =================
com.sap.engine.frame.ServiceRuntimeException: Could not obtain an initial context due to a communication failure. Since no pr
ovider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make sure t
hat any bootstrap address information in the URL is correct and that the target name server is running. Possible causes othe
r than an incorrect bootstrap address or unavailable name server include the network environment and workstation network conf
iguration.
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:171)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.start(AdapterServiceFrameImpl.java:125)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
Caused by: javax.naming.ServiceUnavailableException: Could not obtain an initial context due to a communication failure. Sinc
e no provider URL was specified, the default provider URL of "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService" was used. Make
sure that any bootstrap address information in the URL is correct and that the target name server is running. Possible caus
es other than an incorrect bootstrap address or unavailable name server include the network environment and workstation netwo
rk configuration. [Root exception is org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor co
de: 775 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2228)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1414)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:944)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:865)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:545)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:242)
at com.ibm.ws.naming.util.WsnInitCtx.rebind(WsnInitCtx.java:255)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at javax.naming.InitialContext.rebind(InitialContext.java:367)
at com.sap.aii.adapter.jms.core.service.AdapterServiceFrameImpl.bindAdapter(AdapterServiceFrameImpl.java:163)
... 7 more
Caused by: org.omg.CORBA.TRANSIENT: Connection state: State: ABORT (5) vmcid: 0x4942f000 minor code: 775 completed: No
at com.ibm.rmi.iiop.Connection.checkEstablished(Connection.java:3091)
at com.ibm.rmi.iiop.Connection.send(Connection.java:2145)
at com.ibm.rmi.iiop.Connection._locate(Connection.java:463)
at com.ibm.rmi.iiop.Connection.locate(Connection.java:439)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3721)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3256)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3619)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1524)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1389)
... 17 more
==============================================================================================
Could anyone tell me why is trying to connect to "corbaloc:iiop:1.0(at)sapdpi-lpar:2809/NameService"? Do I have to configure a default provider URL for SAP PI server? If so, where I configure it? Any help will be appreciated.
Thank you in advance.
Roger Allué i Vall

Hi Roger,
we also experience the same issue and would be very keen to understand how you resolved this problem.
Many thanks.
Dieter

Commit fault: com.sap.aii.adapter.rfc.afcommunication.RFCAFWExpection: lo

Hi,
we are doing a RFC to file scenario. it works fine in DEV and QA. but in production sporadically it shows commit fault: com.sap.aii.adapter.rfc.afcommunication.RFCAFWExpection: lo error in SM58.
I have refreshed the cache and all the necessary componets like Sender C.C, receiver C.C, Receiver determination, interface determination, sender agreement and receiver agreement is present.
how to solve this issue. its production issue. pls help ASAP

Hi,
The ECC's business system has Technical System,Client number and Logical System Name.
Also the same is reflected in BS of Integration Builder. it has the logical system, R/3 system and client number in Adapter specific identifiers.
Can you also let me know how to check the complete error message in Tcode SM58. when i double-click on the error it just shows "Commit fault: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:lo". how can i view the full message

Path to com.sap.aii.adapter.lib.sda: PI 7.1

Hi all,
I understand that this topic has been brought up many a times. I am posting my own as I din't find any proper answers.
We are to include a 3rd party JDBC Database driver for PI 7.1. We find a Path to com.sap.aii.adapter.lib at the as /usr/sap/XD1/DVEBMGSXX/j2ee/cluster/bin/ext in the HP-UX server. This is NOT A.SDA file as is required. I have checked the contents in the installation DVD too. I couldn't find it there too.
A .sda file is crucial as the whole configuration depends on that.
Any kind of inputs will be greatly appreciated.
Regards,
Rosun

Hi Ivan,
I do not know how to use the NW studio. New to JSPM too.
Here is the MANIFEST.MF file:
Manifest-Version: 1.0
Specification-Title: XPI Adapter Library
Implementation-Title: com.sap.aii.adapter.lib
sap-perforceserver: perforce3710.wdf.sap.corp:3710
Specification-Vendor: SAP AG
Implementation-Vendor-Id: sap.com
Implementation-Version: 7.1100.20081021173332.0000
Implementation-Vendor: SAP
sap-changelistnumber: 28471
and the SAP_MANIFEST.MF file:
Manifest-Version: 1.0
Ext-SDM-SDA-Comp-Version: 1
softwaretype: primary-library
JarSAP-Standalone-Version: 20080124.1000
JarSAPProcessing-Version: 20080124.1000
changelistnumber: 28471
perforceserver: perforce3710.wdf.sap.corp:3710
projectname: xpi.adapters
deployfile: primary-lib-dd.xml
csncomponent: BC-XI-CON-AFW
docfile: buildinfo.xml
JarSAP-Version: 20080124.1000
keyname: com.sap.aii.adapter.lib
keyvendor: sap.com
keylocation: SAP AG
keycounter: 7.1100.20081021173332.0000
componentelement: <componentelement name="com.sap.aii.adapter.lib" vendor="sap.com" com
ponenttype="DC" subsystem="NO_SUBSYS" location="SAP AG" counter="7.110
0.20081021173332.0000" scvendor="sap.com" scname="SAP-XI3RDPARTY" delt
aversion="F" updateversion="FB-20081028013734" componentprovider="SAP
AG" servertype="P4" sourceserver="perforce3710.wdf.sap.corp:3710" chan
genumber="28471" projectname="xpi.adapters"/>
dependencies: <dependency Implementation-Title="engine.j2ee14.facade" Implementatio
n-Vendor-Id="sap.com" />
dependencylist: <dependency keyname="engine.j2ee14.facade" keyvendor="sap.com" />
JarSL-Version: 20080116.1000
compress: true
Regards,
Rosun

Where is the directory for "com.sap.aii.adapter.lib.sda" - PI 7.1 ?

Hi,
I want to install new JDBC driver in PI 7.1 EHP1, base on notes 1138877 i have to modified file "com.sap.aii.adapter.lib.sda".
please advise in which directory the file is ?
Best Regards
Fernand

Hi
you can go to the drive in which your PI is installed for example if it is E then path will be like
E:/usr/sap/<SID>/DVEBMGS00/j2ee/cluster/bin/ext/com.sap.aii.adapter.lib
copy this file on your local desktop unzip it using winzip and add the driver jar to this
make the entry of your driver jar file in provider.xml file and again zip the folder
then using SDM deploy this file
for complete process search on SDN "how to install and configure external drivers for jDBC and JMS"
Thanks
sandeep

JSPM SPS13 Problem : com.sap.aii.adapter.axis.app

Hello all,
For the PI 7.00 SP10 server we have applied a SP13 patch .All the Java patches are applied except SAP_XIAF we are gettting an error :
Error: Aborted: development component 'com.sap.aii.adapter.axis.app'/'sap.com'/'SAP AG'/'7.0013.20071224120620.0000'/'1', grouped by software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot register EarLoader for application sap.com/com.sap.aii.adapter.axis.app..
Log File ::::::::
Info: Begin of log messages of the target system:
08/02/10 08:48:06 - ***********************************************************
08/02/10 08:48:08 - Start updating EAR file...
08/02/10 08:48:08 - start-up mode is lazy
08/02/10 08:48:10 - EAR file updated successfully for 1292ms.
08/02/10 08:48:10 - Start deploying ...
08/02/10 08:48:11 - EAR file uploaded to server for 526ms.
08/02/10 08:48:14 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot register EarLoader for application sap.com/com.sap.aii.adapter.axis.app..
                     Reason: null; nested exception is:
                          java.lang.NullPointerException
                          at java.lang.Throwable.<init>(Throwable.java:194)
                          at java.lang.Exception.<init>(Exception.java:41)
                          at java.io.IOException.<init>(IOException.java:40)
                          at java.rmi.RemoteException.<init>(RemoteException.java:71)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:204)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:0)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:117)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
                     Caused by: java.lang.NullPointerException
                          at com.sap.engine.lib.util.HashMapObjectObject.get(HashMapObjectObject.java:601)
                          at com.sap.engine.core.classload.impl0.LoadContextImpl.registerReferenceInternal(LoadContextImpl.java:537)
                          at com.sap.engine.core.classload.impl0.LoadContextImpl.registerReference(LoadContextImpl.java:296)
                          at com.sap.engine.core.service630.container.LoadContextWrapper.registerReference(LoadContextWrapper.java:54)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.registerEARloader(DeployServiceImpl.java:2101)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:230)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                          ... 9 more
                     For detailed information see the log file of the Deploy Service.
08/02/10 08:48:14 - ***********************************************************
Feb 10, 2008 8:48:15 AM Info: End of log messages of the target system.
Feb 10, 2008 8:48:15 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 10, 2008 8:48:15 AM Error: Aborted: development component 'com.sap.aii.adapter.axis.app'/'sap.com'/'SAP AG'/'7.0013.20071224120620.0000'/'1', grouped by software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot register EarLoader for application sap.com/com.sap.aii.adapter.axis.app..
Reason: null; nested exception is:
*     java.lang.NullPointerException*
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 10, 2008 8:48:15 AM Info: Starting to save the repository
Feb 10, 2008 8:48:18 AM Info: Finished saving the repository
Feb 10, 2008 8:48:18 AM Info: Starting: Update: Selected software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1' updates currently deployed software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.10.3.20070321093500''/'0'.
Feb 10, 2008 8:48:18 AM Error: Aborted: software component 'SAP_XIAF'/'sap.com'/'SAP AG'/'1000.7.00.13.4.20071226125540''/'1':
Failed deployment of SDAs:
development component 'com.sap.aii.adapter.axis.app'/'sap.com'/'SAP AG'/'7.0013.20071224120620.0000'/'1' : aborted
Feb 10, 2008 8:48:22 AM Error: -
At least one of the Deployments failed -
Any idea how to resolve this issue
Thanks,
GangaPrasad

Hello Prasad,
Seems like this one is similar to the other post from you. I responded in that one :
XIAF and XITOOLS packages depend on XIAFC package. It is first recommended you first upgrade XIAFC to the latest one if already not done.
After this, try to deploy the XIAF and XITOOLS.
Please also check SAP Note 1028961 .
Hope that helps !
Regards,
Snehal

Unable to start service 'com.sap.aii.adapter.jms.svc'

Hi people,
After I have successfully deployed the external drivers jdbc/jms drivers on a PI 7.1 system trough JSPM using the com.sap.aii.adapter.lib.sda file but now the com.sap.aii.adapter.jms.svc and the com.sap.aii.adapter.jdbc.svc do not want to start up. When checking the log DefaulTrace log file I found the following error Reported reason: Service com.sap.aii.adapter.jms.svc is not loaded Any ideas on what the problem could be?

Hi people,
Thanks for all the ideas. I have followed all the notes and guides to prepare the SDA file ie editing the XML file and adding the JAR files.
The problem was that somewhere along the line the provider.xml file of the old aii_af_jmsproviderlib.sda and the new com.sap.aii.adapter.lib.sda file seeming ot "merged" during my struggles.
The provider.xml file of the SDA which I tried to uploaded had the two reference entries which actually belong to the old aii_af_jmsproviderlib.sda in as well as the correct reference entry. Once I removed these incorrect reference entries the services started up correctly.
I found the error mention above by firstly renaming the DefaultTrace_X.trc file and restarting the JAVA stack. I then stepped through each line of the newly created DefaultTrace_X.trc file from the top down and found the following entries:
1) Cannot resolve component library:sap.com/com.sap.aii.adapter.lib because referenced component Reference strong to library com.sap.aii.messaging.runtime not found#
2) Cannot resolve component service:sap.com/com.sap.aii.adapter.jdbc.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
3) Cannot resolve component service:sap.com/com.sap.aii.adapter.jms.svc because referenced component library:sap.com/com.sap.aii.adapter.lib not resolved#
In line line 1 I saw that it was referencing the com.sap.aii.messaging.runtime which seemed suspect. Luckily I still had the original SDA file and when comparing it to the uploaded SDA file I found the incorrect entry.
Thanks again for all the help

Com.sap.aii.adapter.file.ftp.FTPEx: 550 You are not allowed to issue this

Similar Messages

Maybe you are looking for