Adapter Monitor

Hi,
I'm activating a communication channel, adapter type RFC, but in the adapter monitor give me the following error:
Sender channel 'CC_4431_OUT_RFC_YYFM_OPM_COLLECT_ABKRS_DEV' for party '', service 'DEV_211'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=der3dev SYSNR=10 GWHOST=der3dev GWSERV=sapgw10 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 10.128.49.13, service sapgw10)
TIME Mon Apr 24 17:31:33 2006
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r.cpp
LINE 8675
DETAIL NiPConnect2
SYSTEM CALL SiPeekPendConn
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 26
I'm confused because time it's from day 24, and I've activated know (27.04.06). And in my R3, when I test the RFC connection give me the following error:
"program RFC_DEV_TO_XIS not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY."
Could anybody help me?
Kind regads

Hi
Just check this SAP Help
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
RFC_ERROR_COMMUNICATION
Error in JCo Connection creation
Hope this helps,
Regards,
Moorthy

Similar Messages

Link to Communication Channel and Adapter Monitoring not opening

Hello All,
we are on PI 7.0. In teh RWB, we are not able to see the Communication Channnel Monitoring as well the Adapter Monitoring It is giving Page cannot be Displayed.
please tell us the way ahead.
Regards
Chakra and Somnath

Hi Somnath,
when the error occurs check the url of the page that cannot be displayed and verify if the hostname is correct.
It could be a problem of not right setting in exchange profile.
Also verify that you have enough authorization, trying to logon with PISUPER user if you can.
Hope it helps,
Regards,
Sergio

Error while opening Adapter Monitoring in Runtime Workbench

Hi,
I am unable to open Adapter Monitoring from
Runtime Workbench -> Component Monitoring -> Adapter Monitoring
When I tried to open, I am getting following message in the new window:
"The page cannot be displayed"
Please let me know where I can enable this option.
Thanks,
Yogi.

Hi,
Go thru this SAP Note- 768456,928862
Also this doc may help u-https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e1ba1a-e86e-2910-ee83-b73b54abc7d4
Regards,
Moorthy

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

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>

Sender ADapter Monitor- ArrayIndexOutOfBOunds Exception

Hi
As me subject line reads, I am getting an "ArrayIndeXOutofBOunds 9" exception at the sender adapter monitor logs in the RWB.
I have an adapter monitor module that picks up the file from the source and pushes the file to a target directory based on some condition. I am able to see the file being pushed to the target directory but not able to view the "pipeline steps" in the message monitor.
Do you think a restart of the server might fix the issue/ do you think there is a problem in my code. I have used just one array and i have checked that array if it is being accessed out of its bounds?
Thanks
krishna

Hi,
>>>>>ArrayIndeXOutofBOunds 9"
looks like an error in code
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

No Access to Adapter Monitor /

Hello Experts,
everytime i try to take a look on the Adapter Monitor, the page in the ie is not able to be shown. Does anyone know the reason for this ?
We connect our xi to a R/3 4.6c system and when we call the xi from the r/3 we get the following message: "parameter JCO.Request and JCO.Response where <null> (server: RfcServer[RFC_NEU]1)". Do you have any hints?
We already checked that the SAP XI Adapter:RFC is running.
I reward every answer!!
Thx and best regards Phil

Hi,
Ithink u just check the Logical System name and the RFC connection with the XI.
Take the following step:
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
 The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
 The Client must be the client number of the backend SAP system.
 Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
 Double-click on the business system in the Integration Directory.
 Switch to Edit mode.
 Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
 The RFC Destination is from step 3.1.
 The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
Reward points if find helpful

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

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

Cannot send file to XI ,and File Adapter Error in RWB- Adapter Monitor

i develop the file to file scenario, and everything in Integration Builder is right, and the configuration is no problem
but it cannot send file to XI, so the whole process
cannot start. The file adapter seems not work
how can i solve the problem?
Thank you for your reply

Hi Leo,
I Guess you should first see if the file is being picked... for that do the following.
While configuring your Sender File Adapter, let the mode be DELETE. This way, we will know if the file is being picked by the File adapter. The file will be deleted and you can be sure that it has been picked up.
In your runtime workbench home, there will be a tab, Component Monitoring, click on it. Select status as all, and click on display. The components will be displayed on ur screen. In that, under Integration Server, there will be a link for Adapter Engine. Click on it. Now, scroll down, and u will see a link to adapter monitoring, there under FILE ADAPTER see the log of the file adapter
and also, you can see the flow of your message in the integration engine in SXMB_MONI.
Do this and let us know what is happening...
Meanwhile i would also suggest you to go through the explanation of a simmilar scenario that i have explained below and compare it with what you have done..
Please go thru the following links and clear all your doubts.
Communication channel:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/65/b11c409ce22402e10000000a1550b0/frameset.htm">Assigning Communication Channels</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/2b/d5653fd1d3b81ae10000000a114084/content.htm">Communication Channel</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm">Configuring the Sender File/FTP Adapter</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm">Configuring the Receiver File/FTP Adapter</a>
Receiver agreement:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/56/02e63f48e58f15e10000000a155106/frameset.htm">Receiver Agreement</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/c1/5194426b44c56ae10000000a155106/frameset.htm">Creating a Receiver Agreement</a>
Sender agreement:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/db/73e03fc2269615e10000000a155106/frameset.htm">Sender Agreement</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/522041cfb7f423e10000000a155106/frameset.htm">Creating a Sender Agreement</a>
For detailed info, I would suggest that you go through these weblogs:
<a href="/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1">Introduction to simple(File-XI-File)scenario for Starters</a>
<a href="/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2">Introduction to simple (File-XI-File)scenario for starters part2</a>
I hope it helps.
Regards,
Abhy

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

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

Adapter Monitor message--hepl me out

hi,
In a file to file to scenario i am getting the following message in Adapter monitor
Can you clarify me what exactly is the error ?
Receiver Adapter v1027 for Party '', Service 'YAMAHA_BS':
Configured at 18:31:43 2008-10-17
Up and running - no message processing until now "

Hi Pankaj,
This is not an error msg. XI receiver adapter has not processed any msg until now. If the sender has picked the file, check it in SXMB_MONI, may be there are some error. SO your msg is not going till receiver file adapter.
Regards,
Jai Shankar.

Adapter Monitoring

Hi,
My RFC senario is giving me an error,I went to component monitoring-->Adapter Monitoring and saw the list of adapters.I see that the RFC adapter is red,does it mean the adapter is down?how do I troubleshoot it?This is the error I have in RWB.
Sender channel 'CC_RFC_*********' for party '', service 'SYSTEM_XI_010'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: User is locked. Please notify the person responsible
Thanks

Hi,
->According to our error above you have problem with your gatway connection . can you make sure ur using correct gateway service. something like sapgw00 00 is system number. you get this in smgw.
->Check that the RFC Destination that you have created Do Connection Test & Remote LOgon also Re-Enter the User & Pwd Once again.
Please take a look at the below error. It looks like same error what you have.
RFC sender adapter error
Plz do refer the following links:
JCO_ERROR_RESOURCE
/thread/2978 [original link is broken]
Number of connections expiry problem - URGENT
Please reward points if it helps
Thanks
Vikranth

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

Adapter Monitor

Similar Messages

Maybe you are looking for