Error in RWB

Hi
while i am monitoring in RWB under message monitoring
Status System Error
Error Category XI_J2EE_ADAPTER_FILE
Error Code PROCESSING_ERROR
It is in adapter engine
In auditlog i am getting error like this
Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error during variable substitution: java.text.ParseException: Security violation encountered during variable substitution: Content of variable po is not safe: A.Hoorsun/: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: java.text.ParseException: Security violation encountered during variable substitution: Content of variable po is not safe: A.Hoorsun
How to solve this type of error.
thanks in adavance
rao

Rao,
Try checking the flag 'Disable Security Checks' in the communication channel.
Regards,
Koen

Similar Messages

File to Soap error in RWB

Dear Friends,
I am working on File to Soap scenario,In this scenario File is picking succssfully and posting to target side I got the error in RWB like
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 read request. ---> There is an error in XML document (1, 2205). ---> Input string was not in a correct format.
How to correct the input string , Please suggest how to resolve this issue.
Thanks & Regards,
Shalini Shah.

This error occurs when:
1) Incorrect data structure is send to the SOAP application ..... compare the payload that you are sending to the SOAP application with the WSDL structure that you have imported in IR .... both should match exactly....also confirm that the WSDL you are using the latest one.
2) Target URL/ Action is not properly configured in the receiver SOAP channel
3) Is your target system up and running?
Regards,
Abhishek.

Jdbc receiver error in RWB

My scenario is Idoc to jdbc..
I m able to successfully send the idoc from R3 and it is received in XI also.
However the message does not reach to database and am getting the following error in RWB of XI.
"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:@172.25.XX.XXX:1521:<SID>': SAPClassNotFoundException: oracle.jdbc.driver.OracleDriver"
Kindly tell me where the problem is.

Hi,
refer the below link for step by step process:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
Thnx
Chirag

Getting error in RWB

Scenario:file to file
Source Structure: 2 fields( Fname & Lname)
Target Structure :1 field(Full_name)
i m getting below error in RWB when i start sender communication channel.
error"Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 1 according to structure 'ROW':java.lang.Exception: ERROR in configuration / structure 'ROW.': More elements in file csv structure than field names specified!"
my csv file has only two fields that is "aaaaa,bbbbbb" and i saved it as hello.txt
help me how to resolve it.
send your solutions simple as possible

hi,
i took pay load from sxmb_moni and checked it in mapping and it showed error
payload form SXMB_MONI
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_SNDRSUN1 xmlns:ns="http://suntosun">
- <Recordset>
- <ROW>
<FNAME>BBBBBBBBBB</FNAME>
<LNAME>aaaaaaaa</LNAME>
</ROW>
</Recordset>
</ns:MT_SNDRSUN1>
Below Xml Code is normaly i copied from test->source text view from message mapping
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_SNDRSUN1 xmlns:ns0="http://suntosun">
 <ROW>
 <FNAME/>
 <LNAME/>
 </ROW>
</ns0:MT_SNDRSUN1>
*can u mention wat error it may be

Analyze error in RWB

After some performace testing I have an error in rwb (sender )
Transmitting the message to endpoint http://xi:8000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Internal Server Error.
smq1/smq2 doesn't show messages
runtime cache is updated
Message status is waiting
How to analyze what's happen with Integration Engine?

Denis
A HTTP Response in the Adapter Framework can be caused by the following:
The J2EE server might be overburdened and cannot accept the call. The 'Receive'servlet is not called. You will find further details on the HTTP status code definitions under "http://www.w3.org". Check the accessibility of the server by calling: http://<hostname>:<port>/MessagingSystem/receive/AFW/XI.
The Listener Beans of the affected connection (AFW, Marketplace, BC,see above) were not registered or the log-specific Event Handler was not found.
To debug this go to SAP Notes: 803145
---Mohan

Configuration error in RWB

Hi all,
    I am getting the following error in
RWB-->configuration.              com.sap.aii.proxy.framework.core.BaseProxyException: User XIISUSER has no RFC authorization for function group SXI_PMI_CONFIG ., error key: RFC_ERROR_SYSTEM_FAILURE Logon Data For nw4sr1.corp.miraclesoft.com
             It is giving authorization error while trying to login using sapuser.
             Is configuration related to alerts and alerts configuration?
Could anybody idea about this issue ?
Thanks & Regards,
sekhar

Hi michal,
           we did not change the password.
          We are facing one more problem with alert configuration.
          I am able to create alert categeory through the direct transaction(alrtcatdef). But while creating through RWB it is giving the following error.
URL http://nw4sr1.corp.miraclesoft.com:8000/sap/public/bc/its/mimes/system/99/page/hourglass.html call was terminated because the corresponding service is not available.
Could u help me to solve this issue..?
Thanks,
sekhar.

Error in RWB For File 2 RFC 2 FIle ?

Hi Experts
I Got a error in RWB -> Configuration - >
No ports that send to the Integration Server could be found for the following ALE logical systems: PIDCLNT120: Name or password is incorrect (repeat logon) .

Hi
In Sender RFC check --> SM59 --> Test Connection (Also Check if user got locked by this time)
In receiver RFC check in the configuration
Rgds
srini

ECC Connectivity Error from RWB (SXMB_CONF_ITEMS)

We are able to connect PI 7.1 to ECC 6.0 on our QA server successfully however when we attempt to connect to the ECC 6.0 on Prod we get the following errors from the RWB
Errors:
Are roles in SXMS_CONF_ITEMS and SLD Consistant? RED
Has an integration server destination been defined ? RED
Function SXMB_GET_IS_ENDPOINT failed (return code = 1)
Resolutions Attempeted:
1) In PI 7.1 We have created TS and BS for the production ECC 6. We get the above error in RWB.
Result: Works in QA. Green Lights in RWB when we point it to QA ECC system (create TS and BS for the QA ECC 6 system).
2) We checked the corresponding role for the business system as Intgration Server in SXMB_ADM and SLD Pipeline URL in Integration_server_xxx BS.
We cleared cache and rebooted system twice. We have the same settings in Prod however for some reason its not applying successfully.
3) We have the appropriate roles and profiles set for PIRWBUSER on the ECC side and PI side.
Could anyone please give me some clues to fix. Thank you for your time in advance.

Thanks.
We just fixed this.
We set the Role of Business system as Application System in SXMB_ADM in Production ECC system to fix.

FCC Error in RWB

Hi All,
My scenario is Idoc to File scenario in which i am using FCC at the target end,
My data type structure was
RootNode
Level -
1
5 Fields
Level -
2
5 Fields
Level -
3
5 Fields
and my FCC parameters was ..
Level1.fieldFixedLengths --- 0,0, (As i dont want all these fields i marked as 0,0,....)
Level1.fixedLengthTooShortHandling -- Cut
Level1.endSeparator                           -- 'nl'
Level2.fieldFixedLengths                    --- 10,15,10,12,15
Level2.fixedLengthTooShortHandling -- Cut
Level2.endSeparator                           -- 'nl'
Level3.fieldFixedLengths --- 10,15,10,12,15
Level3.fixedLengthTooShortHandling -- Cut
Level3.endSeparator                           -- 'nl'
but, unable to find where actaully the error is..
This is the folllowing error which i am getting in Receiver comm channel monitoring in RWB.. I think the error is with FCC
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error occurred while connecting to the FTP server "rps37ykf.rim.net:21": java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:RootNode' found in document', probably configuration error in file adapter (XML parser error)'
request your inputs to solve this issue..
regards,
sai

Hi..
RootNode ..is it the name of your Message type?
Yes Root Node is my message Type
Also are Level1,Level2,Level1 on same level?
Yes all the levels are in same level ..
If i need to suppress any one level at the output end how can i suppress it..
If i alter the Data type structure i can do it but the values which is populated at that level will be used by the other levels
Eg: i want to suppress level 1 but some functionality of that level will be used by the other 2 levels. so in the structure it is essential but at the target end i need to suppress those values..
can i suppress it using any other fixedlength funcitonality
regards,
sai

Ping error in RWB for J2SE Adapter Engine

Hi,
we have several external J2SE adapter engines and they function great other than from a monitoring perspective. In RWB "Ping Status" I'm getting the following:
HTTP request failed. Error code: "401". Error message: "Authorization Required"
Suggestions?
Cheers,
Mattias

This is not an answer to your question.
I've tried to get an answer for: how to register J2SE adapter with Integration Server ?
I tried using SLDAccess service on J2SE adapter with no luck (with this J2SE Adapter Engine is registered in the SLD). My J2SE adapter was never available in the configuration means, in the communication channel ex: file adapter, for the adapter engine drop down all I have is Integration Server, my J2SE adapter was never listed there.
If you know an answer please post.
thanks
SKM

Regarding mapping error in RWB

Hi Every one
I am doing idoc to file scenario. In the message mapping
i tested the mapping it shows executed successfully.
but when i tested the RWB the receiver communication channel
it shows following error.
can anyone please help me how to solve this error
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:MT_VendorMaster' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:MT_VendorMaster' found in document', probably configuration error in file adapter (XML parser error)'

HI,
As with prakasu and latika..
it is not an mapping problem.. it may be due to wrong configuration in the adapter communication channel configuration .. during receiver configuration the record set structure will be defaultely present, try to remove that and provide ur message type which u created in the IR..
and try to check with the test tab..
regards,
Kishore

"The page cannot be displayed" error in RWB with IE6 on Windows XP SP2

The following screens in the RWB give an error "The page cannot be displayed":
- End-to-end monitoring
- Alert Configuration
- Alert Inbox
My colleague who is on IE6 on Windows 2000 can display the pages. We have the same roles.
I searched on SAP notes and in the XI forum but could not find any response to this issue yet.
Any ideas?
Thanks.
Cedric

Not really an answer for you, but I run SP2 with IE6 and have no problems. Could be a problem with the host being defined for the Windows 2000 user, but not yourself. Some RWB connections are internally using the Fully qualified domain name while others don't. I know this was an issue with our adapter engine set-up at one point after we applied SP13.

Business Server Page error in RWB -alertConfig

In XI, RWB, when i click to open 'Alert Configuration', it gives an error message:
Business Server Page (BSP) error
What happened?
Calling the BSP page was terminated due to an error.
SAP Note
The following error text was processed in the system:
BSP Exception: the Application Name sap in URL /sap/bc/bsp/sap/sxms_alertrules/main.do?sap-client=400&adaptertypes=RFC%20BC%20Mail%20Marketplace%20File%20XIRA%20SOAP%20RNIF11%20JMS%20JDBC%20RNIF%20XI%20CIDX%20 is invalid.
I tried testing the related service in SICF:
it gave almost the same error:
The following error text was processed in the system:
BSP Exception: the Application Name sap in URL /sap/bc/bsp/sap/sxms_alertrules?sap-client=400 is invalid.

run RSXMB_ACTIVATE_ICF_SERVICES in se38.
or go to SICF and follow the path: sap/bc/bsp/sap/sxms_alertrules and make sure it is active!

Message monitoring link error in RWB

hi,
When we select adapter engine in RWB in SAP XI It throws an error:
java.lang.AbstractMethodError: com/sap/aii/mdt/api/server/AdapterFrameworkHome.create(Ljava/util/Locale;Ljava/util/TimeZone;Ljavax/ejb/Handle;Ljavax/management/ObjectName;Ljava/lang/String;Z)Lcom/sap/aii/mdt/api/server/MessageMonitoring;
Exception id: [E41F131007D0007300000041001E90FE000491736486E774]
kindly help.
Regards,
Priya

hi vijay,
I have upgraded the patch level of LMtools,SAP_XIAFC, and SAP_XIAF to the latest level.
Infact i have updated the entire Java patches to the latest support patch.
Try this. hope this will solve your problem.
Regards,
Priya

Proxy Runtime Error in RWB.

Hi All,
I am getting following error,
Please, help me to solve this problem
Message: Neither the messager server nor the application server can be reached for system DSM
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Neither the messager server nor the application server can be reached for system DSM
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:863)
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:726)
at com.sap.aii.rwb.core.R3System.getJCOPool(R3System.java:698)
at com.sap.aii.rwb.core.R3System.getRepository(R3System.java:910)
at com.sap.aii.rwb.core.BusinessSystem.getRepository(BusinessSystem.java:802)
at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:97)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:580)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:307)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:381)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:397)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:348)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.java:24)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks In Advance
Mahesh

Hi Seshagiri,
Actually, i am getting this error in message Monitoring dropdown, i have Proxy Runtime Receiver System option. when i am selecting the same i am getting the following error.
javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
javax.ejb.CreateException: Neither the messager server nor the application server can be reached for system DSM
     at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:456)
     at com.sap.aii.mdt.api.server.IntegrationEngineHomeImpl1_0.create(IntegrationEngineHomeImpl1_0.java:195)
     at com.sap.aii.mdt.api.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:57)
     at com.sap.aii.mdt.util.MonitoringBeanCache.getMonitoringBean(MonitoringBeanCache.java:305)
     at com.sap.aii.mdt.util.WebUtil.getMonitor(WebUtil.java:351)
     at jsp_monitor_new1221049881372._jspService(jsp_monitor_new1221049881372.java:140)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
     at com.sap.aii.rwb.web.messagemonitoring.viewcontroller.MmDynPage.doProcessBeforeOutput(MmDynPage.java:69)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
     at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at jsp_FC_Secure1221049856634._jspService(jsp_FC_Secure1221049856634.java:24)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Error in RWB

Similar Messages

Maybe you are looking for