Error in SAP WSRP Consumer XML

Hello,
the SAP EP WSRP Consumer sends the following request with a wrong xml:lang code. It uses java locales instead. It sends 'en_US' instead of 'en-US'. My producer sends as a response no portlet title, because it has no title for this unknow language code and as a consequence, SAP consumer throws an error saying ' No content defined for this user '. Any ideas?
<SOAP-ENV:Body><prt0:getServiceDescription xmlns:prt0="urn:oasis:names:tc:wsrp:v1:types">
    <prt0:registrationContext>
        <prt0:registrationHandle>GNF5FRAAAAAAHKP4DGAQAAA</prt0:registrationHandle>
    </prt0:registrationContext>
    <prt0:desiredLocales>en_US</prt0:desiredLocales>
    <prt0:desiredLocales>fr_FR</prt0:desiredLocales>
    </prt0:getServiceDescription>
</SOAP-ENV:Body></SOAP-ENV:Envelope>
Regards,
Andreas.

Hi Andreas,
we got kind of the same problem with WSRP and different portal languages. Did you find any kind of solution?
Kind regards and THX,
Christoph

Similar Messages

Error in SOAP Adapter because XML is big

<b>Hi guys! I have a SOAP Adapter (Sender) that works fine when the XML it receives is small. If the XML is big, this error happens:</b><br><br><br>
java.lang.NullPointerException; nested exception caused by:
java.lang.NullPointerException; nested exception caused by:
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at com.sap.aii.messaging.util.StreamXMLScannerImpl$EventProducer.run(StreamXMLScannerImpl.java:598)
     at java.lang.Throwable.<init>(Throwable.java:56)
     at java.lang.Throwable.<init>(Throwable.java:67)
     at org.xml.sax.SAXException.<init>(Unknown Source)
     at org.xml.sax.SAXParseException.<init>(Unknown Source)
     at com.sap.engine.lib.xml.parser.NestedSAXParseException.<init>(NestedSAXParseException.java:23)
     at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at com.sap.aii.messaging.util.StreamXMLScannerImpl$EventProducer.run(StreamXMLScannerImpl.java:598)
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
     ... 3 more
<br><br><br>
<b>ps: the big XML is well formed! It seems the application server refuses the http request (the message does not appear at SXMB_MONI)</b><br><br>
thanks in advance<br><br>
Julio

Julio,
Are you sure that XML is correct?
No data allowed here: (hex) 6e, 74, 6f(:main:, row:1, col:3)
I also see Parse exceptions at different lines?
check the NOTE : 931765 @
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=931765
Check if the incoming XML has style informaton associated with it. Refer to following link for more info.
http://schemas.xmlsoap.org/soap/envelope/
If the problem still persists, Restart J2EE Instance.
Regards,
Venkat.
Edited by: Venkat Anusuri on Jun 3, 2009 5:34 PM

WSRP Consumer - producer registration error : (100)continue return code

I am trying to get an ALI WSRP Consumer working with the ALI WSRP Producer. Whenever I try to register the producer wsdl, the consumer fails with the error :
Failed to get a service description from WSRP provider!
Error message from WSRP provider: (100)Continue
Any clues? I can successfully register this producer with a different portal's consumer. Is there a configuration property that needs to be set to allow the (100) response code? Or perhaps my Producer should avoid that response code in the first place? Has anybody run into this?
Below is the stack trace generated by my consumer on the back-end (from ALI Logging Spy) :
Failed to get service description from WSRP provider: http://scollins.sd.defenseweb.net:80/wsrpproducer1.1/1.0/WSRPBaseService.asmx
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (100)Continue
faultActor:
faultNode:
faultDetail:
     {}string: return code: 100
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.1
Date: Wed, 22 Apr 2009 23:31:53 GMT
X-Powered-By: ASP.NET
Connection: close
X-AspNet-Version: 2.0.50727
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=utf-8
Content-Length: 3084
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><soap:Header><wsa:Action>urn:oasis:names:tc:wsrp:v1:getServiceDescriptionResponse</wsa:Action><wsa:MessageID>uuid:dc3a3069-320a-4a6d-a997-45313098bc00</wsa:MessageID><wsa:RelatesTo>uuid:c827c145-c82d-4958-a201-30e7a86c053b</wsa:RelatesTo><wsa:To>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:To><wsse:Security><wsu:Timestamp wsu:Id="Timestamp-18d05f2a-c5dd-4519-8d1d-24b68f27b9e5"><wsu:Created>2009-04-22T23:31:54Z</wsu:Created><wsu:Expires>2009-04-22T23:36:54Z</wsu:Expires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><getServiceDescriptionResponse xmlns="urn:oasis:names:tc:wsrp:v1:types"><requiresRegistration>false</requiresRegistration><offeredPortlets><portletHandle>simple</portletHandle><markupTypes><mimeType>text/html</mimeType><modes>wsrp:edit</modes><modes>wsrp:help</modes><modes>wsrp:view</modes><windowStates>wsrp:maximized</windowStates><windowStates>wsrp:minimized</windowStates><windowStates>wsrp:normal</windowStates><windowStates>wsrp:solo</windowStates><locales>en</locales></markupTypes><description xml:lang="en"><value>Simple view portlet to test WSRP viewing</value></description><shortTitle xml:lang="en"><value>View</value></shortTitle><title xml:lang="en"><value>View Portlet</value></title><displayName xml:lang="en"><value>SimpleView</value></displayName><userProfileItems>UserProfileName/PropertyName</userProfileItems><templatesStoredInSession>true</templatesStoredInSession><doesUrlTemplateProcessing>true</doesUrlTemplateProcessing></offeredPortlets><offeredPortlets><portletHandle>helloworld</portletHandle><markupTypes><mimeType>text/html</mimeType><modes>wsrp:edit</modes><modes>wsrp:help</modes><modes>wsrp:view</modes><windowStates>wsrp:maximized</windowStates><windowStates>wsrp:minimized</windowStates><windowStates>wsrp:normal</windowStates><windowStates>wsrp:solo</windowStates><locales>en</locales></markupTypes><description xml:lang="en"><value>Hello world portlet to test WSRP viewing</value></description><shortTitle xml:lang="en"><value>View</value></shortTitle><title xml:lang="en"><value>Hello World Portlet</value></title><displayName xml:lang="en"><value>HelloWorld99</value></displayName><userProfileItems>UserProfileName/PropertyName</userProfileItems><templatesStoredInSession>true</templatesStoredInSession><doesUrlTemplateProcessing>true</doesUrlTemplateProcessing></offeredPortlets><registrationPropertyDescription><propertyDescriptions name="ConsumerName" type="xsd:string" /><propertyDescriptions name="BuildDate" type="xsd:dateTime" /></registrationPropertyDescription></getServiceDescriptionResponse></soap:Body></soap:Envelope>
(100)Continue
     at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:695)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:129)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2575)
     at org.apache.axis.client.Call.invoke(Call.java:2564)
     at org.apache.axis.client.Call.invoke(Call.java:2259)
     at org.apache.axis.client.Call.invoke(Call.java:2182)
     at org.apache.axis.client.Call.invoke(Call.java:1702)
     at com.plumtree.wsrp.base.WSRP_v1_ServiceDescription_Binding_SOAPStub.getServiceDescription(WSRP_v1_ServiceDescription_Binding_SOAPStub.java:857)
     at com.plumtree.wsrp.consumer.impl.ServiceDescriptionManager.getServiceDescription(ServiceDescriptionManager.java:118)
     at com.plumtree.wsrp.consumer.servlet.AdminPreference.renderSetRegistrationPage(AdminPreference.java:992)
     at com.plumtree.wsrp.consumer.servlet.AdminPreference.service(AdminPreference.java:117)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Unknown Source)

This seemed promising, but the proposed solution (adding 'servicePointManager expect100Continue="false"' to Web.config) had no effect.
My consumer request actually does not include the "Expect: 100-continue" header and receives the 100 response anyways. My understanding now is that this is okay (thought I'm not sure why) and that the client should be expected to handle that response code in any case.
I am wondering if there is an issue with the combination of products in my environment that is not supported by this product?? I am using
IIS 5.1,
.Net 2.0
AquaLogic WSRP Producer 1.1/WebCenter WSRP Producer 10.3.0 (tried both)
I am testing this producer in two environments -
- AquaLogic Consumer running on AL Portal 6.5. When the WSRPConsumer is configured with the producer wsdl, it fails with message "Failed to get service description from WSRP Provider: .... faultString: (100) Continue".
- Liferay - AFTER successful registration, attempts to deploy my registered .Net portlet (simple hello-world) result in an internal exception thrown in the Producer [Bea.Portlet.Management.PortletManager.LoadPortlet(PortletManager.cs:line 114)] Error loading PortletContainer: Bad PortletState. No request is made to my .Net application.
It appears from both of these tests that both my producer and consumer are having fundamental problems that do not seem overly exotic (although I have successfully registered other WSRP portlets with the AL Consumer). However, I have not come across much information on these sorts of problems.

Error while parsing or executing XML-SQL document

friends,
my scenario is based on file to jdbc.i am facing an error in receiver CC in RWB.
The error states that '
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'MATMAS' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]String or binary data would be truncated.'
My SOAP xml message is
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:TimeSent>2008-02-06T22:30:21Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>ECC</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<sap:Service>BS_JDBC</sap:Service>
</sap:Receiver>
<sap:Interface namespace="http://file_to_jdbc">MI_JDBC_RECEIVER</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>
</sap:ReliableMessaging>
- <sap:DynamicConfiguration xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="Directory">
sapecc50\sapmnt\trans</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileEncoding">UTF-8</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileType">txt</sap:Record>
<sap:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">matmas1.txt</sap:Record>
</sap:DynamicConfiguration>
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info />
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:21Z" wasRead="false">
<sap:Engine type="IS">is.01.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
<sap:Info>3.0</sap:Info>
</sap:Hop>
- <sap:Hop timeStamp="2008-02-06T22:30:22Z" wasRead="false">
<sap:Engine type="AE">af.e6e.sapecc6eval</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>18f17dd0-d503-11dc-cb4d-001635b02bfd</sap:MessageId>
</sap:Hop>
</sap:HopList>
- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:TraceLevel>Information</sap:TraceLevel>
<sap:Logging>Off</sap:Logging>
</sap:Diagnostic>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>MainDocument</sap:Name>
<sap:Description />
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
and payload message is
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
- <STATEMENT>
- <ROW action="INSERT">
<TABLE>MATMAS</TABLE>
- <access>
<MATNR>38</MATNR>
<MTART>HALB</MTART>
<MATKL>00107</MATKL>
<MEINS>pc</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>10</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>88</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.04.05</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>13</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>89</MATNR>
<MTART>FERT</MTART>
<MATKL>02004</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2008.03.02</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>14</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>98</MATNR>
<MTART>HALB</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.09.01</ERSDA>
<BRGEW>12</BRGEW>
<NTGEW>12</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>170</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2005.03.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>178</MATNR>
<MTART>NLAG</MTART>
<MATKL>4</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.03.06</ERSDA>
<BRGEW>3</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>188</MATNR>
<MTART>NLAG</MTART>
<MATKL>5</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.05.02</ERSDA>
<BRGEW>2</BRGEW>
<NTGEW>3</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>288</MATNR>
<MTART>HALB</MTART>
<MATKL>101</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2006.02.11</ERSDA>
<BRGEW>5</BRGEW>
<NTGEW>4</NTGEW>
<GEWEI>KG</GEWEI>
</access>
- <access>
<MATNR>358</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.09.09</ERSDA>
<BRGEW>500</BRGEW>
<NTGEW>500</NTGEW>
<GEWEI>G</GEWEI>
</access>
- <access>
<MATNR>359</MATNR>
<MTART>HAWA</MTART>
<MATKL>2</MATKL>
<MEINS>PC</MEINS>
<ERSDA>2007.08.01</ERSDA>
<BRGEW>20</BRGEW>
<NTGEW>10</NTGEW>
<GEWEI>G</GEWEI>
</access>
</ROW>
</STATEMENT>
</ns0:MT_JDBC_RECEIVER>
Could anybody help me in sorting out this issue.My advance thanks

hi,
ypur structure is bad defined.
if you want to do an insert, the DT should be
<ns0:MT_JDBC_RECEIVER xmlns:ns0="http://file_to_jdbc">
___<StatementName>
______<dbTableName action=INSERT>
_____<table>MATMAS</table>
_______ <access>
___________<MATNR>38</MATNR>
___________<MTART>HALB</MTART>
___________<MATKL>00107</MATKL>
___________<MEINS>pc</MEINS>
___________<ERSDA>2008.04.05</ERSDA>
___________<BRGEW>10</BRGEW>
___________<NTGEW>12</NTGEW>
___________<GEWEI>KG</GEWEI>
______</access>
_____</dbTableName>
__ </StatementName>
</ns0:MT_JDBC_RECEIVER>
the ROW field is used when you wait receive data from DB for example you execute and SQL Query from Sender communication channel "SELECT name FROM TABLE Names"
so, the result of this query would be, for example:
<row>
____<name>joge</name>
</row>
<row>
____<name>pepe</name>
</row>
<row>
____<name>nicola</name>
</row>
See this link
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:40 AM
Edited by: Rodrigo Pertierra on Feb 8, 2008 8:42 AM

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

SAP 4.7 XML data exchange using XSLT

Hello All,
Hopefully the right place to post such article but here goes any way.
My project involves producing XML files and then reading them back into to SAP internal tables. I am ok with writing SAP data to external XML file but reading it back in is causing a lot of head scratching.
I am able to double click the XML file and it launches Ok in Internet Explorer.
I am also able to debug the xslt file from within SE80 and the correct output is displayed.
However, where I am trying to read the contents of the xml file via the Call Transformation procedure call my output table is not getting populated but instead I am recieving an error message saying the following is not correct:
xmlns:sapxsl="http://www.sap.com/sapxsl
but the above line is placed automaticlly in the XSLT when you create a new one from within SE80.
I am new to SAP ABAP development so not sure what's exactly wrong.
Any help on this issue will be greatfully appreciated. Thanks in Advance,
Wasif
REPORT z_hp_xml_test                                               .
TYPE-POOLS: ixml.
TABLES: tstc, tstct.
TYPES: BEGIN OF ty_transactions,
      tcode LIKE tstc-tcode,
      ttext LIKE tstct-ttext,
      sprsl LIKE tstct-sprsl,
END OF ty_transactions.
DATA: itab_transactions TYPE STANDARD TABLE OF ty_transactions.
TYPES: BEGIN OF t_xml_line,
        data(256) TYPE x,
      END OF t_xml_line.
DATA: l_ixml            TYPE REF TO if_ixml,
      l_streamfactory   TYPE REF TO if_ixml_stream_factory,
      l_parser          TYPE REF TO if_ixml_parser,
      l_istream         TYPE REF TO if_ixml_istream,
      l_document        TYPE REF TO if_ixml_document,
      l_node            TYPE REF TO if_ixml_node,
      l_xmldata         TYPE string.
DATA: l_elem            TYPE REF TO if_ixml_element,
      l_root_node       TYPE REF TO if_ixml_node,
      l_next_node       TYPE REF TO if_ixml_node,
      l_name            TYPE string,
      l_iterator        TYPE REF TO if_ixml_node_iterator.
DATA: l_xml_table       TYPE TABLE OF t_xml_line,
      l_xml_line        TYPE t_xml_line,
      l_xml_table_size TYPE i.
DATA: l_filename        TYPE string.
PARAMETERS: pa_file TYPE char1024 DEFAULT 'C:     emp     ransactions.xml'.
Validation of XML file: Only DTD included in xml document is supported
PARAMETERS: pa_val TYPE char1 AS CHECKBOX.
START-OF-SELECTION.
Creating the main iXML factory
l_ixml = cl_ixml=>create( ).
Creating a stream factory
l_streamfactory = l_ixml->create_stream_factory( ).
PERFORM get_xml_table CHANGING l_xml_table_size l_xml_table.
wrap the table containing the file into a stream
l_istream = l_streamfactory->create_istream_itable( table =
l_xml_table
                                                  size =
l_xml_table_size ).
Creating a document
l_document = l_ixml->create_document( ).
Create a Parser
l_parser = l_ixml->create_parser( stream_factory = l_streamfactory
                                    istream        = l_istream
                                    document       = l_document ).
Validate a document
IF pa_val EQ 'X'.
    l_parser->set_validating( mode = if_ixml_parser=>co_validate ).
ENDIF.
Parse the stream
If any errors then disply else convert XML to table
IF l_parser->parse( ) NE 0.
    IF l_parser->num_errors( ) NE 0.
      DATA: parseerror TYPE REF TO if_ixml_parse_error,
            str        TYPE string,
            i          TYPE i,
            count      TYPE i,
            index      TYPE i.
      count = l_parser->num_errors( ).
      WRITE: count, ' parse errors have occured:'.
      index = 0.
      WHILE index < count.
parseerror = l_parser->get_error( index = index ).
i = parseerror->get_line( ).
WRITE: 'line: ', i.
i = parseerror->get_column( ).
WRITE: 'column: ', i.
str = parseerror->get_reason( ).
WRITE: str.
index = index + 1.
ENDWHILE.
ENDIF.
ELSE.
TRY .
CALL TRANSFORMATION (`Z_HP_TEST_XSLT`)
SOURCE XML l_xml_table
RESULT outtab = itab_transactions.
DATA: xslt_err TYPE REF TO cx_xslt_exception .
CATCH cx_xslt_exception INTO xslt_err.
DATA: s TYPE string.
s = xslt_err->get_text( ).
WRITE: ': ', s.
STOP.
ENDTRY .
Process the document
    IF l_parser->is_dom_generating( ) EQ 'X'.
      PERFORM process_dom USING l_document.
    ENDIF.
ENDIF.
*&      Form get_xml_table
FORM get_xml_table CHANGING l_xml_table_size TYPE i
                            l_xml_table      TYPE STANDARD TABLE.
Local variable declaration
DATA: l_len      TYPE i,
        l_len2     TYPE i,
        l_tab      TYPE tsfixml,
        l_content TYPE string,
        l_str1     TYPE string,
        c_conv     TYPE REF TO cl_abap_conv_in_ce,
        l_itab     TYPE TABLE OF string.
l_filename = pa_file.
upload a file from the client's workstation
CALL METHOD cl_gui_frontend_services=>gui_upload
    EXPORTING
      filename   = l_filename
      filetype   = 'BIN'
    IMPORTING
      filelength = l_xml_table_size
    CHANGING
      data_tab   = l_xml_table
    EXCEPTIONS
      OTHERS     = 19.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Writing the XML document to the screen
CLEAR l_str1.
LOOP AT l_xml_table INTO l_xml_line.
    c_conv = cl_abap_conv_in_ce=>create( input = l_xml_line-data
replacement = space ).
    c_conv->read( IMPORTING data = l_content len = l_len ).
    CONCATENATE l_str1 l_content INTO l_str1.
ENDLOOP.
l_str1 = l_str1+0(l_xml_table_size).
SPLIT l_str1 AT cl_abap_char_utilities=>cr_lf INTO TABLE l_itab.
WRITE: /.
WRITE: /' XML File'.
WRITE: /.
LOOP AT l_itab INTO l_str1.
    REPLACE ALL OCCURRENCES OF cl_abap_char_utilities=>horizontal_tab
IN
      l_str1 WITH space.
    WRITE: / l_str1.
ENDLOOP.
WRITE: /.
ENDFORM.                    "get_xml_table
*&      Form process_dom
FORM process_dom USING document TYPE REF TO if_ixml_document.
DATA: node      TYPE REF TO if_ixml_node,
        iterator TYPE REF TO if_ixml_node_iterator,
        nodemap   TYPE REF TO if_ixml_named_node_map,
        attr      TYPE REF TO if_ixml_node,
        name      TYPE string,
        prefix    TYPE string,
        value     TYPE string,
        indent    TYPE i,
        count     TYPE i,
        index     TYPE i.
node ?= document.
CHECK NOT node IS INITIAL.
ULINE.
WRITE: /.
WRITE: /' DOM-TREE'.
WRITE: /.
IF node IS INITIAL. EXIT. ENDIF.
create a node iterator
iterator = node->create_iterator( ).
get current node
node = iterator->get_next( ).
loop over all nodes
WHILE NOT node IS INITIAL.
    indent = node->get_height( ) * 2.
    indent = indent + 20.
    CASE node->get_type( ).
      WHEN if_ixml_node=>co_node_element.
        element node
        name    = node->get_name( ).
        nodemap = node->get_attributes( ).
        WRITE: / 'ELEMENT :'.
        WRITE: AT indent name COLOR COL_POSITIVE INVERSE.
        IF NOT nodemap IS INITIAL.
          attributes
          count = nodemap->get_length( ).
          DO count TIMES.
            index = sy-index - 1.
            attr   = nodemap->get_item( index ).
            name   = attr->get_name( ).
            prefix = attr->get_namespace_prefix( ).
            value = attr->get_value( ).
            WRITE: / 'ATTRIBUTE:'.
            WRITE: AT indent name COLOR COL_HEADING INVERSE, '=',
                             value COLOR COL_TOTAL   INVERSE.
          ENDDO.
        ENDIF.
      WHEN if_ixml_node=>co_node_text OR
           if_ixml_node=>co_node_cdata_section.
        text node
        value = node->get_value( ).
        WRITE: / 'VALUE     :'.
        WRITE: AT indent value COLOR COL_GROUP INVERSE.
    ENDCASE.
    advance to next node
    node = iterator->get_next( ).
ENDWHILE.
ENDFORM.                    "process_dom
Section 3: My XSLT file:
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sapxsl="http://www.sap.com/sapxsl"
<xsl:strip-space elements="*"/>
<xsl:template match="TransList">
     <xsl:apply-templates />
</xsl:template>
         <xsl:template match="Tcode">
              Tcode <xsl:apply-templates />
         </xsl:template>
         <xsl:template match="ttext">
              ttext <xsl:apply-templates />
         </xsl:template>
         <xsl:template match="sprsl">
              sprsl <xsl:apply-templates />
         </xsl:template>
</xsl:transform>

The exact error message I'm getting is :
ABAP XML formatting error in XML node of type "element", name: "abap"

Error while parsing or executing XML-SQL document attribute "action" missin

Hi All,
I am doing a scenario for IDOC to JDBC, When I push IDOC from R/3 , IDOC sent to XI System successfully,
I have also checked in SXMB_MONI it is showing the successful staus without any errors, and I have also copied the xml structure from main document of payloads and tested the mapping in Integration Designer, and it is showing successfull message.
here is the xml structure from payloads of Request Message Mapping ........
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">1000001</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">1</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">1</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">1</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">1</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">2</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">2</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">2</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">6</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">6</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">4</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">6</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">3</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">3</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">3</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">5</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">5</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">5</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">9</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">7</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">7</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">7</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">12</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">8</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">8</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">8</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</ns0:RTACOGRP_RECEIVER_MT>
When I checked for component monitoring in runtime workbench....
these are the messages........
<i>Error while parsing or executing XML-SQL document: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)</i>
Here are the messages from message monitoring ......
2007-06-07 12:42:17 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2007-06-07 12:42:17 Success JDBC adapter receiver channel RTACOGRP_COM_Chan: processing started; party , service WSORTABS
2007-06-07 12:42:17 Error No "action" attribute found in XML document ("action" attribute missing or wrong XML structure)
2007-06-07 12:42:17 Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Exception caught by adapter framework: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2007-06-07 12:42:17 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure).
2007-06-07 12:42:17 Error The message status set to NDLV.
Can any body please resolve the problem.....
Thanks in Advance
Murthy

Bhavesh,
Now I have changed the data structure , and the resultant structure is like this...
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:RTACOGRP_RECEIVER_MT xmlns:ns0="http://prospecta.com/wsorta/cosmas/idoc2jdbc">
- <Statement>
- <COGRP_TMP_PROC action="EXECUTE">
<IDOCNUMBER isInput="TRUE" type="CHAR">100002223</IDOCNUMBER>
<E1COGH_NUMBER isInput="TRUE" type="CHAR">1</E1COGH_NUMBER>
<E1COGH_HIGHERSEGMENT isInput="TRUE" type="CHAR">1</E1COGH_HIGHERSEGMENT>
<E1COGH_MSGFN isInput="TRUE" type="CHAR">H</E1COGH_MSGFN>
<E1COGH_GROUPTYPE isInput="TRUE" type="CHAR">H</E1COGH_GROUPTYPE>
<E1COGH_GROUPNAME isInput="TRUE" type="CHAR">H</E1COGH_GROUPNAME>
<E1COGH_KOKRS isInput="TRUE" type="CHAR">H</E1COGH_KOKRS>
<E1COGHT_NUMBER isInput="TRUE" type="CHAR">1</E1COGHT_NUMBER>
<E1COGHT_HIGHERSEGMENT isInput="TRUE" type="CHAR">2</E1COGHT_HIGHERSEGMENT>
<E1COGHT_LANGU isInput="TRUE" type="CHAR">T</E1COGHT_LANGU>
<E1COGHT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGHT_DESCRIPT>
<E1COGHT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGHT_LANGU_ISO>
<E1COGV_NUMBER isInput="TRUE" type="CHAR">1</E1COGV_NUMBER>
<E1COGV_HIGHERSEGMENT isInput="TRUE" type="CHAR">3</E1COGV_HIGHERSEGMENT>
<E1COGV_FROMVALUE isInput="TRUE" type="CHAR">V</E1COGV_FROMVALUE>
<E1COGV_TOVALUE isInput="TRUE" type="CHAR">V</E1COGV_TOVALUE>
<E1COGS_NUMBER isInput="TRUE" type="CHAR">1</E1COGS_NUMBER>
<E1COGS_HIGHERSEGMENT isInput="TRUE" type="CHAR">5</E1COGS_HIGHERSEGMENT>
<E1COGS_SUBGROUP isInput="TRUE" type="CHAR">S</E1COGS_SUBGROUP>
<E1COGHR_NUMBER isInput="TRUE" type="CHAR">1</E1COGHR_NUMBER>
<E1COGHR_HIGHERSEGMENT isInput="TRUE" type="CHAR">7</E1COGHR_HIGHERSEGMENT>
<E1COGHR_SNAME isInput="TRUE" type="CHAR">R</E1COGHR_SNAME>
<E1COGHR_PRTCLASS isInput="TRUE" type="CHAR">R</E1COGHR_PRTCLASS>
<E1COGHR_AUTHGR isInput="TRUE" type="CHAR">R</E1COGHR_AUTHGR>
<E1COGSR_NUMBER isInput="TRUE" type="CHAR">1</E1COGSR_NUMBER>
<E1COGSR_HIGHERSEGMENT isInput="TRUE" type="CHAR">8</E1COGSR_HIGHERSEGMENT>
<E1COGSR_XSUPPRESS isInput="TRUE" type="CHAR">S</E1COGSR_XSUPPRESS>
<E1COGSR_PRTCLASS isInput="TRUE" type="CHAR">S</E1COGSR_PRTCLASS>
<E1COGSR_LNAME isInput="TRUE" type="CHAR">S</E1COGSR_LNAME>
<E1COGVT_NUMBER isInput="TRUE" type="CHAR">1</E1COGVT_NUMBER>
<E1COGVT_HIGHERSEGMENT isInput="TRUE" type="CHAR">10</E1COGVT_HIGHERSEGMENT>
<E1COGVT_LANGU isInput="TRUE" type="CHAR">T</E1COGVT_LANGU>
<E1COGVT_DESCRIPT isInput="TRUE" type="CHAR">T</E1COGVT_DESCRIPT>
<E1COGVT_LANGU_ISO isInput="TRUE" type="CHAR">T</E1COGVT_LANGU_ISO>
<E1COGVR_NUMBER isInput="TRUE" type="CHAR">1</E1COGVR_NUMBER>
<E1COGVR_HIGHERSEGMENT isInput="TRUE" type="CHAR">11</E1COGVR_HIGHERSEGMENT>
<E1COGVR_XSUPPRESS isInput="TRUE" type="CHAR">E</E1COGVR_XSUPPRESS>
<E1COGVR_PRTCLASS isInput="TRUE" type="CHAR">E</E1COGVR_PRTCLASS>
<E1COGVR_LNAME isInput="TRUE" type="CHAR">E</E1COGVR_LNAME>
</COGRP_TMP_PROC>
</Statement>
</ns0:RTACOGRP_RECEIVER_MT>
Now in message monitoring error is showing like this...
<i>Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error</i>
Now in Component Monitoring error is showing like this....
<i>Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC' (structure 'Statement'): java.sql.SQLException: General error</i>
I have tested the stored procedure in sql by giving the same values , it was successfully executed..
Can you please tell me where is the error still in structure ...
Thanks in Advance,
Murthy.

FPN error: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException

Hi, all.
I am trying to initiate a webdynpro page from the producer to the consume portal via RDL. It works fine for a day. Then it starts giving me the error:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page ...
This error cannot be cleared by clearning the FPN cache or synchronize with the producer. Of course, you can also delete the page from the consumer and copy it over from the producer again. It will work. But this is not a good workaround for a production system. We also don't know the cause either. Here is the stack trace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:528)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     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(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)
Caused by: com.sap.portal.fpn.exception.unchecked.FpnUnMarshallingException: Could not find a marshaller for 'com.sapportals.portal.page' from path 'pcd:consumer_content/DEP/portal_content/ca.ottawa.sap.supportcentre/ca.city.ottawa.OttawaRoles/ca.city.ottawa.ManagerInfo/ca.city.ottawa.ManagerInfo-FinanceOnly/ca.city.ottawa.ManagerInfo_MSS_Finance/ca.city.ottawa.Mileage_Parking_Managers'
     at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:323)
     at com.sap.portal.fpn.entrypoint.RuntimeFederatedPersistance.retrieveDLRemoteState(RuntimeFederatedPersistance.java:103)
     at com.sap.portal.fpn.FpnRuntimeService.bringRemoteState(FpnRuntimeService.java:134)
     at com.sap.portal.fpn.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:97)
     at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:49)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:526)
     ... 31 more
Caused by: com.sap.portal.pcm.OperationFailedException: Creating DL outside the PCD
     at com.sap.portal.pcm.iviewserver.CiViewSLObjectsManager.instantiateDescriptor(CiViewSLObjectsManager.java:687)
     at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:79)
     at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:71)
     at com.sap.portal.fpn.marshal.IViewMarshaller.instantiateRelatedItemDescriptor(IViewMarshaller.java:582)
     at com.sap.portal.fpn.marshal.IViewMarshaller.performSemanticActions(IViewMarshaller.java:506)
     at com.sap.portal.fpn.marshal.PageMarshaller.performSemanticActions(PageMarshaller.java:499)
     at com.sap.portal.fpn.marshal.IViewMarshaller.unmarshalResolvedDLChain(IViewMarshaller.java:715)
     at com.sap.portal.fpn.marshal.PageMarshaller.unmarshalResolvedDLChain(PageMarshaller.java:328)
     at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:320)
     ... 38 more
So far I found nothing on OSS or SDN on this FpnUnMarshallingException. Has anyone seen this error before?
Thanks.
Jonathan.
Edited by: Jonathan Ma on Apr 23, 2009 12:25 AM

Hi Jonathan,
you may deactivate the GPN cache as well as the old navigation cache. About the GPN there is note 1172433. Both caches are not used in FPN scenario and can lead to such strange problems. If this won't help please open a support message for this that we can analyse further.
Cheers,
Anja

Consistency error:more fields found in XML structure than specified in conv

Hi,
I am doing a File 0 RFC- File in PI 7.1 and facing the following error:
2009-12-07 09:45:05 Error        MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.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 '20000000|3022|800.99|10.11.2009|Testing 22222|')', probably configuration error in file adapter (XML parser error)'
2009-12-07 09:45:05 Error File processing failed with com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.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 '20000000|3022|800.99|10.11.2009|Testing 22222|')', probably configuration error in file adapter (XML parser error)'
my output file record structure :
DT_out
    itab_out                       0.........1
       item                          0...... unbounded
         STR                        0........1
So i have given in the receiver FCC parameters as:
Record structure : item
Content conversion parameters:
item.fieldFixedLengths               255
item.endSeparator                      'nl'
could anyone pls help me in solving this error at the earliest.
thanks

my problem has been solved by giving the FCC parameters as shown below:
my output file record structure :
DT_out
itab_out 0.........1
item 0...... unbounded
STR 0........1
So i have given in the receiver FCC parameters as:
Record structure : item,ITAB_OUT
Content conversion parameters:
item.fieldFixedLengths 255
item.endSeparator 'nl'
ITAB_OUT.fieldFixedLengths 255
ITAB_OUT.endSeparator 'nl'

Error in UseOneAsMany Function Error in SAP XI

Error in UseOneAsMany Function Error in SAP XI
Hi Experts,
I am trying the Example of function UseOneAsMany. My Input and Output XML Files are provided below:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_MM4 xmlns:ns0="http://test/mapping.test">
   <Header>
      <MatNo>MatNo</MatNo>
      <MatDesc>MatDesc</MatDesc>
   </Header>
   <Item>
      <MatNo>MatNo1</MatNo>
      <ItemNo>ItemNo1</ItemNo>
      <MatGroup>MatGroup1</MatGroup>
      <Mattype>Mattype1</Mattype>
      <Plant>Plant1</Plant>
   </Item>
   <Item>
      <MatNo>MatNo2</MatNo>
      <ItemNo>ItemNo2</ItemNo>
      <MatGroup>MatGroup2</MatGroup>
      <Mattype>Mattype2</Mattype>
      <Plant>Plant2</Plant>
   </Item>
</ns0:MT_MM4>
My Expected Output should be :
<?xml version="1.0" encoding="UTF-8"?>
-<ns0:MT_MM4R xmlns:ns0="http://test/mapping.test">
-<Header>
<MatNo>MatNo</MatNo>
<MatDesc>MatDesc</MatDesc>
<MatGroup>MatGroup1</MatGroup>
</Header>
-<Item>
<MatNo>MatNo1</MatNo>
<ItemNo>ItemNo1</ItemNo>
<Mattype>Mattype1</Mattype>
<Plant>Plant1</Plant>
</Item>
-<Header>
<MatNo>MatNo</MatNo>
<MatDesc>MatDesc</MatDesc>
<MatGroup>MatGroup2</MatGroup>
</Header>
-<Item>
<MatNo>MatNo2</MatNo>
<ItemNo>ItemNo2</ItemNo>
<Mattype>Mattype2</Mattype>
<Plant>Plant2</Plant>
</Item>
</ns0:MT_MM4R>
But for me Headers are coming first and then followed by two items. Please let me know how to solve the issue and also please provide the explanation.
Thanks,
GIRIDHAR

Hello,
Change ur structure little bit (add parent node "Record") and then use java mapping pasted in below blog to remove Record node to get ur desired structure.
File Conversion using 'Nodeception'
<?xml version="1.0" encoding="UTF-8"?>
-<ns0:MT_MM4R xmlns:ns0="http://test/mapping.test">
<Record> --- 0..Unbounded
-<Header>
<MatNo>MatNo</MatNo>
<MatDesc>MatDesc</MatDesc>
<MatGroup>MatGroup1</MatGroup>
</Header>
-<Item>
<MatNo>MatNo1</MatNo>
<ItemNo>ItemNo1</ItemNo>
<Mattype>Mattype1</Mattype>
<Plant>Plant1</Plant>
</Item>
</Record>
<Record>
-<Header>
<MatNo>MatNo</MatNo>
<MatDesc>MatDesc</MatDesc>
<MatGroup>MatGroup2</MatGroup>
</Header>
-<Item>
<MatNo>MatNo2</MatNo>
<ItemNo>ItemNo2</ItemNo>
<Mattype>Mattype2</Mattype>
<Plant>Plant2</Plant>
</Item>
</Record>
</ns0:MT_MM4R>
Thanks
Amit Srivastava

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.

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
     <gesellschaft>03</gesellschaft>
     <filiale>000</filiale>
     <satzart>11</satzart>
     <datum>00000000</datum>
     <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

File failing with ICM_HTTP_CONNECTION_BROKEN error in SAP PI

Hi Expert,
We have file to proxy senario in our production environment where, while sending the file from PI to ECC syestem via proxy, it fails below with error in call adapter step.
Have tried with many options mentioned in scn.sap.com site like
1. Increasing the HTTP ICM PROCTIMEOUT paramaters.
2. restarted ICM in both sender and receiver system.
But still it is not resolved yet. Please help.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_BROKEN</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://cimbp05.hsec.emeadc001.philips.com:8005/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP NetWeaver Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://cimbp05.hsec.emeadc001.philips.com:8005/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://cimbp05.hsec.emeadc001.philips.com:8005/sap/public/icman/img/graybar_tile.jpg" height="31"> </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2>500 Network connection broken</H2><br><hr> <table border="0"> <tr><td>Error:</td><td>-8</td></tr> <tr><td>Version:</td><td>7210</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Mon May 4 14:12:57 2015 </td></tr> <tr><td>Module:</td><td>icxxthrio_mt.c</td></tr> <tr><td>Line:</td><td>848</td></tr> <tr><td>Server:</td><td>cimyp25_MYP_25</td></tr> <tr><td>Error Tag:</td><td>{-}</td></tr> <tr><td>Detail:</td><td>Connection to partner broken</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 401, error text: ICM_HTTP_CONNECTION_BROKEN)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Regards,
Vishnu Srivastava

Hi Praveen,
As per the solution mentioned in the link we have checked for the icm/HTTP/max_request_size_KB parameter in Quality and production environment. It is maintained as icm/HTTP/max_request_size_KB= 102400.
Also we are able to process the same file in quality but not in production though the parameters are same.
Please help..!!
Regards,
Vishnu

HTTP to RFC Mapping error:com.sap.aii.utilxi.misc.api.BaseRuntimeException:

hi all,
I am doin a http to rfc scenario.In moni it is showing a mapping error in the request mapping and showing this error.In IR my mapping is working fine but in payload runtime i found the error is because it is showing <?xml version="1.0" encoding="UTF-8" ?> twice.Below is the payload message
<i><?xml version="1.0" encoding="UTF-8" ?>
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Lspm_Request_SampledueGrid_MT xmlns:ns0="http://satyam.com/xi/LSPM">
<KUNNR>100000</KUNNR>
<FROM_DATE>15.11.2006</FROM_DATE>
<TO_DATE>10.12.2006</TO_DATE>
- <EQUIPMENTID>
- <item>
<EQUIPID>wb</EQUIPID>
</item>
</EQUIPMENTID>
+ <LOCATIONID>
- <item>
<LOCID>1</LOCID>
</item>
</LOCATIONID>
- <OILID>
- <item>
<OILID>BP260</OILID>
</item>
BP260
</OILID>
</ns0:Lspm_Request_SampledueGrid_MT></i>
I tested using view source code and removing the extra ]<?xml version="1.0" encoding="UTF-8" ?> in IR and it is working fine.
Now my problem is how to rectify this error can anyone help me out please??
thanks,
Nisheeta

hi,
I tried to post the XML in the http page without the header and now it it showing a new error
Result:
<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon)</SAP:AdditionalText></SAP:Error>
http://cgnsap27:8000/sap/xi/adapter_plain?namespace=http%3A//satyam.com/xi/LSPM&interface=Lspm_SampledueGrid_Syn_MI&service=SATYAM_LSPM_BS&party=&agency=&scheme=&QOS=BE&sap-user=shailesh&sap-password=shailesh&sap-client=100&sap-language=EN
wat does this mean??
nisheeta

Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_MAPPINGPROGR

Hi all,
I am currently doing a File --> RFC --> File synchronous interface ( I am not using RFC lookup functionality here ).
I am doing this scenario according to the following Wiki link,
[http://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File(Without+BPM)]
When testing the interface, i am getting an error "Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_MAPPINGPROGRAM_FOUND:" in the sender communication channel. I don't have any idea about this error, could anyone help me in this issue.
Cheers,
Sherin Jose P

Hi Sherin Jose P,
Please recheck your Integration Directory configuration for the scenario. Specially please check inbound interface determination settings. Here the communication channel is unable to find the interface mapping after receiving XML message. Did you use java mapping ? then please check the code again since it might not be producing exact target xml structure. Finally please ensure all mapping programs are existing and activated. If all mapping are activated then refresh the cache.
Please check in st22 transaction all errors in PI, whenever you get this message. There may be other reasons of error as well. There can be occasional short dumps due to data lengths or validations in ABAP programs. These short dumps in ERP may cause failures raised in PI.
Finally if there are some exception in mapping then this error you can expect.
Hope this helps.
regards
Anupam

Error in SAP WSRP Consumer XML

Similar Messages

Maybe you are looking for