Receiver JMS Adapter Communication channel Error

Hi Experts,
The Error is given below
Cannot connect because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing: ensure that JMS Provider library 'aii_af_jmsproviderlib.sda' contains all required resources.
when i searched SDN , i found the MQ JMS Library need to deployed in XI/PI . For clarification check SAP NOTE 1138877 is given .
What should I do ?
pls advice
Regards,
Jude

Hello Experts,
I am encountering the same error that you faced. I am using PI 7.0 and MQ adapter 6.0. I would like to know where to get the following jar files:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
I know that I am supposed to add the above files to aii_af_jmsproviderlib.sda on the PI server. As I not a basis person, it'll be great if you could direct me to some detailed instructions. I am trying to follow SAPNote: 747601.
Please correct me if I am wrong.
Thanks,
Bhanu.

Similar Messages

ALERT MAIL FOR FILE ADAPTER COMMUNICATION CHANNEL ERRORS

Hi,
I need to send an alert by mail to a list of configured receivers if any error( Application as wel as System Errors ) occurs in the FILE ADAPTER Communication Channel .
Please suggest how to do it......
Regards,
Sriparna

Can anything be configured in the communication channel to run a mail unix script if the communication channel is throwing
error.Other than alert rule can we configure this.
Why do you intend to use script? Define Alert....create Rule....set parameters using SCOT.....you will get the alert as email (if you need it)
Can you please help with how do I create this rule specific to File Adapters only ?
Other than selecting FILE as Adapter Type in RWB --> Alert Rule definition we dont do anything special....this setting should help.
Regards,
Abhishek.

Sender Soap Adapter communication channel error

Dear Experts,
When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
"Processing Errors in the Last 50 Minutes"
Thanx in advance

Aamir,
My other interface is working fine by giving the following url:
http://kpmgvm015:8001/XISOAPAdapter/MessageServlet?channel=:KPMG_AU_ALL:RetrieveOpportunityRecord_SOAP_Sender
I am not using the propsed url.
Moreover when i try to give this url in the browser . It is asking of user id and password.
I am giving user as : PIAPPLUSER.It gives message servelet is ok.
In my communication channel monitoring the corresponsing communication channel:
RetrieveclientRecord_SOAP_Sender is in Red - Processing Errors In the Last 40 Minutes
Error meesage in Webclient:
java.security.AccessControlException: PIAPPLUSER has no permission for accessing binding com.sap.aii.af.service.cpa.Binding@d046043a

JDBC Adapter Communication Channel error

I am getting this error for a JDBC Adapter, I waondering if anybody could point me in the right direction.
I have installed the driver:
JDBC Driver: oracle.jdbc.driver.OracleDriver
Connection: jdbc:oracle:thin:@146.146.78.74:1521:ts1
Error:
Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@146.146.78.74:1521:ts1': SQLException: Io exception: The Network Adapter could not establish the connection
Any help would be appreciated.

The driver has been deployed into the XI server, I just deployed the testing tool from OSS note 1085539.
I am still getting this error.
Exception Occurred : Io exception: The Network Adapter could not establish the connection
Exception Stack Trace : java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)
     at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:420)
     at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:165)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
     at java.sql.DriverManager.getConnection(DriverManager.java:559)
     at java.sql.DriverManager.getConnection(DriverManager.java:189)
     at com.sap.util.TestJDBCUtil.testDriverManagerConnect(TestJDBCUtil.java:52)
     at com.sap.tests.TestJDBCConnectionServlet.processRequest(TestJDBCConnectionServlet.java:41)
     at com.sap.tests.TestJDBCConnectionServlet.doPost(TestJDBCConnectionServlet.java:74)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Any suggestions?

File to JMS Scenario - Error is Receiver JMS Adapter

Hi,
I am working on File to JMS scenario. I have deployed all required jars for MQ 6.0.2 in SDM. Create all MQ related objects. I am getting following error for Receiver JMS adapter in CC Monitoring.
Please let me know if I have missed anything. Is there anything to do in Visiual Administrator->JMS Provider or JMS Connector for these kind of Scenarios?
Thanks in Advance...
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Hi,
I have made my Qmanager as default Qmgr. Now the error is :- Socket connection attempt refused
Recv JMS Communication Channel Error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Receiver SOAP Communication Channel Error

Hi,
I am trying to post a file to a WebService but facing the below error in the communication channel :
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object variable or With block variable not set.
Has anyone encountered such an error?
Please let me know.
Regards,
Anuradha.

Hi,
First of all check the URL in your receiver SOAP adapter. The error comes from the web service server. It says that the request message is wrong.
1.fill field SOAPAction in the receiver soap adapter
2.fPlease find the related information here
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
Please check this one also:
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
There are multiple soap actions listed there.
Regards,
Divya

Error in Recever Mail Adapter (Communication Channel)

Hello Experts,
I am getting below error in recever Adapter Communication Channel. I have given SMTP, XIALL,PLAIN parameters, i have given proper: SMTP://compnay.com & correct user id and password, i browse throug all most all related links.
Exception caught by adapter framework: java.io.IOException: server does not support PLAIN or LOGIN authentication
Mail: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server does not support PLAIN or LOGIN authentication
Delivery of the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: server does not support PLAIN or LOGIN authentication.
Thanks,
Siva

HI Siva
Are you trying to send Email from any file send by system or Read by PI and send as Email.
Please describe your Scenario.
If your email is generated from the content provided by Integraton engine use Message protocol XI PAYLOAD instead of XIALL.
Using Authentication you change from Plain to CRAM-MD5. then it might not give any error
Your URL should be SMTP://mailhost.company.com
For reference check Help URL
http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/frameset.htm
Thanks
Gaurav Bhargava

Error in Receiver RNIF1.1 communication channel

Hi ,
We are getting the below error in the Receiver RNIF1.1 communication channel
Transmitting the message to endpoint https://TTT.com.tw:4443/invoke/wm.ip.rn/receive using connection RNIF11Adapter failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: <BODY bgcolor=#dddddd> <TABLE bgcolor=#dddddd border=1> <TR> <TD valign="top">$errorDump</TD> <TD>Server error occurred</TD> </TR> <TR> <TD valign="top">$errorInfo</TD> <TD><TABLE bgcolor=#dddddd border=1> <TR> <TD valign="top">$errorDump</TD> <TD>Server error occurred</TD> </TR> <TR> <TD valign="top">$error</TD> <TD>com.wm.estd.rosettaNet.TransportNotFoundException: The transport '' is not a registered RosettaNet transport. Ensure that the required package is activated. If the package is activated, then reload the pac
Please suggest,what caused this error.
Regards,
AR

Please check the Transport Parameters.
Refer for configuration
http://help.sap.com/saphelp_nwpi71/helpdata/en/3d/99743f3d4b0866e10000000a114084/frameset.htm
Regards
Raj

Error with the Receiver JMS Adapter (Connection On-Demand feature)

Hi,
In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
The message status was set to WAIT.
Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
Any idea?
PI 7.1 EHP1
Thanks,
Martin
/people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

JMS Sender Communication Channel problem

Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
Thanks

HI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup

JMS sender communicaton channel error

Hi,
The JMS sender communication channel throws the following error in Communication Channel monitoring in RWB.
Channel started but Inactive
"Channel removed; check whether channel was deleted or moved to another Adapter Engine"
But the channel is active and a copy object of the same channel works succesfully.
Has anyone faced such an issue?
Thanks,
Ambili

Hi Abhishek,
Thanks for ur reply.
1. Already tried it, but still the same status.
2. Yes, i can see the channel in sxi_cache.
3. Tried this several times, same message.
The issue is just for this channel and as I mentioned before, a copy object of the same channel works perfectly fine.
Thanks,
Ambili
Edited by: Ambili Jose on Jan 19, 2010 7:30 AM

JDBC to JDBC Scenario - Communications Channel Error

I am following the published JDBC to JDBC Scenario:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/step-by-step+guides
I am a 3rd Party Vendor, and I'm using NX7: SAP Exchange Infrastructure. My goal is to have a JDBC Sender that sends MS Access data from my PC to NX7, and have a JDBC Receiver that receives MS Access data, and map the data from one database to the other via XI per the scenario, with both databases on my PC.
I set up the NX7 SAP XI per the scenario, but I'm getting an error on the NX7 Communications Channel:
Error during database connection to the database URL 'jdbc:odbc:Driver={Microsoft Access Driver(.mdb)};DBQ=//204.245.44.232/C:/Documents and Settings/All Users/Documents/XI_FILES/SENDER/STUDENT_Database.mdb' using the JDBC driver 'sun.jdbc.odbc.JdbcOdbcDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver(.mdb)};DBQ=//204.245.44.232/C:/Documents and Settings/All Users/Documents/XI_FILES/SENDER/STUDENT_Database.mdb': SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified'
The data source is in
C:/Documents and Settings/All Users/Documents/XI_FILES/SENDER/STUDENT_Database.mdb on my PC and it is a shared folder. My PC IP 204.245.44.232 is a public IP address. It should be using the JDBC-ODBC bridge driver in the JDK.
Why am I getting the error?
Thanks,
Ed Culnane

Hi
Connection Parameters are of given below check
Transport Protocol: JDBC 2.0
Message Protocol: XML SQL Format
Adapter Engine: Integration Server
JDBC Driver: jdbc.odbc.JdbcOdbcDriver
Connection: jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//xiserver/xitemp/db/TestDB.mdb
5) In my case there is no userid and password required, but if you have userid and password, then the parameter for Connection becomes,
jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//xiserver/xitemp/db/TestDB.mdb;Uid=yourid;Pwd=yourpwd;
Well ms access file should be in the XI Server path or it should be able to accessed by the XI
Try this above option of keeping u r file in the XI Server path instead of the local
rgd
srini

IDoc adapter inbound channel: Error Error while read

Dear All
I am sending idoc from SAP 4.6C to PI. But on SM58 I am getting an error
IDoc adapter inbound channel: Error Error when reading
Which is not complete because field length is 50 characters , double clicking on this message is asking for message class. How can i see the complete message.
Can any one send me configuration detail of receiving IDOC at PI end , I don't want send to it forward from PI.

Please clear these points.
In PI system:
1. Create RFC destination of type 3 pointing to R/3 system.
2 . create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system.
3. Using IDX2 import the IDOC meta data in to your PI system.
RFC destination to which direction , towards sender of IDOC ?
Port of which system sender system or receiver system?
What about configuration in Integration Directory , is there any configuration required on integration repository and on integration directory.
What will be the procedure of seeing complete message on SM58.
-->In PI system while ur creating the RFC destination of type 3 give the hostname and system number of ur R/3 system ie SAP 4.6 c.
-->In PI create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system and in that RFC destination option, maintaine the destinatination name which we created using sm59.
-->coming to IR you need to create the:
                    1. Receiver data type.
                    2. receiver message type
                    3. receiver message interface. No need to create the above 3 for sender.
                   4.while mapping source is your Idoc and target is your receiver message type.
                   5. while interface mapping source is Idoc and target is receiver interface.
-->Coming to ID no need to create sender communication channel and no need to create sender agreement.
-->create receiver communication channel and receiver agreement.
--->create Interface determination.
-->create receiver determination.
-->If message got stuck in SM58, unlock it by using double click or activate the selected message.
Thanks

XI Communication Channel Error Explanation

Hi All,
Does anyone happen to know :-
1) Is it possible to use CCMS to email the errors coming from a communication channel error Explanation field
2) Are these messages stored in a table I can check
The reason I need to know this is because we sometimes encounter an error such as "Conversion of file content to XML failed at position 838: java.lang.Exception: ERROR converting document line no. 839 according to structure 'XXX_XXX_XXX':java.lang.Exception: ERROR in configuration / structure 'XXX_XXX_XXX.': More elements in file csv structure than field names specified!
This tells us exactly where the error occurred but using Communication Channel Monitoring the error message only remains for a little while before the polling messages remove it from the display. Since the process runs early hours of the morning we never get to see these messages.
Any help appreciated.
Thanks
Craig

Hi Raquel,
Let me try to clear out some things in this thread . First of all you do your alert configuration which you say you have already done. Thats good . Now you ask that you want only to monitor the communication channels and you want specific guide . Here is the specific guide.
If you have configured alerts you will know that when you create an alert rule you have the option to choose radio button where did the error occur it could be no restriction , integration engine or adapter engine. You need to choose adapter engine.
Now whenever the colour of the lights change to red. You will get your alerts.
Regards
joel
Edited by: joel trinidade on Apr 9, 2009 9:41 AM

Issue on file sender adapter communication channel

Hi All,
I have an issue on some of the file sender adapter communication channels .The channels are failing with the error :
(u201CAttempt to process file failed with com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.xi.swift.ParserException: com.sap.xi.swift.ParserException: Message does not start with character '0x1f'u201D).
Please let me know the procedure to get this message processed.
Thanks & Rgards
Vishnu

Hi Vishu,
Find out in what encoding the file is in. for that download Notepad++ and open the file with in.
In Encoding tab you will see the encoding format.
1. If its not UTF-8 or ANSI then you should set the correct encoding in Sender File channel.
2. Check for BOM characters which will not be visible directoly.
3. Use Notepad++ to convert the content to HEX and check for hidden values. i bet there will be some Encoding BOM in the file which is creating problem while picking the file.
Since you are using SWIFT module: try to validate the XML file using Altova XML and check weather is correct.
also ref to this thread:http://scn.sap.com/thread/2134946
Regards,
Senthilprakash

Receiver JMS Adapter Communication channel Error

Similar Messages

Maybe you are looking for