Problem in test environment in RFC2WS service (worked in DEV)

hello
I have RFC2WS sync scenario. every works ok in the dev environment. after import the interface to the test environment, I recieve this error below.
I also tryed to run the unitest and recieved and error in the IM stage that "root element expected" but I think it is ok, since this message I also recieved in the dev environment and as I said before, it is working as expected.
more over, if I take the measse from the sxmb_moni and run it in the MM it is successfully transfer to the WS.
I also tryed to refresh the cache and reimport the RFC and the interface and rewrite the scenario in the ID. any suggestions?
(added the error message and below that message in the SXMB)
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AdobeMail_RFC2WS_REQ_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:463) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) 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.sap.engine.services.rfcengine.RFCDefaultRequestHandler
message in the SXMB
<?xml version="1.0" encoding="UTF-8" ?>
<rfc:ZRFC_SPREAD_FROM_IMAGE xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<DOCIDS>
<item>09002347802f6d70</item>
</DOCIDS>
<MAIL>
<SUBJECT>******************************</SUBJECT>
<MESSAGE>*************************************</MESSAGE>
<FROMADDRESS>#######</FROMADDRESS>
<FROMNAME>AVRAHAMP</FROMNAME>
<TO>
<item>
<ADDRESS>#######</ADDRESS>
<NAME>טסט טסט</NAME>
</item>
</TO>
<CC />
<BCC />
<REPLYTO>
<item>
<ADDRESS>#######</ADDRESS>
<NAME>AVRAHAMP</NAME>
</item>
</REPLYTO>
<BOUNCEADDRESS />
<HOSTNAME />
<HOSTPORT />
<CHARSET />
</MAIL>
<PASSWORD></PASSWORD>
<TARGETAPPLICATION>CRM</TARGETAPPLICATION>
<USERNAME>imagesoa</USERNAME>
</rfc:ZRFC_SPREAD_FROM_IMAGE>

this is the trace
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
<Trace level="1" type="T">Set interface action INIT into *MAST*</Trace>
</Trace>
<Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="1" type="T">Interface Mapping http://Migdal.co.il/CRM/SAP-CRM/AdobeMail AdobeMail_RFC2WS_IM</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AdobeMail_RFC2WS_REQ_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) 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.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451)(:main:, row=7, col=451) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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) ... 4 more</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AdobeMail_RFC2WS_REQ_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AdobeMail_RFC2WS_REQ_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) 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.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor305.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy158.processFunction(Unknown Source) 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.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:107) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113) at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:157) 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) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451)(:main:, row=7, col=451) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser : #0 not allowed in Character data sections(:main:, row:7, col:451) at com.sap.engine.lib.xml.parser.XMLParser.handleContentReference(XMLParser.java:2329) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2460) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) 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) ... 4 more</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

Similar Messages

Problem while testing a ABAP Web Service

Hello,
I'm facing a problem while testing a webservice for the BAPI BUPA_CENTRAL_GET_DETAIL. I have opened the Web Service Home page, and I get no error. I fill in the input values and then when I send the request, I get back an error which says "Authority check failed"
Urgent help needed..
Thanx,
Anupama

you need s_service and s_object authorization objects in your role.
its explained in this document
section 3.1 on page 7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/92d80512-0a01-0010-32a3-cd3735bd9275
Regards
Raja

Problem while testing a BAPI Web Service

i face this problem in web service bapi when i am carrying out the test... so can anyone help me???
HTTP/1.1 500 Internal Server Error
Set-Cookie: <value is hidden>
content-type: text/xml; charset=utf-8
content-length: 803
sap-srt_id: 20080610/144609/v1.00_final_6.40/DD36B8E7DE44B5F19BA900145E6770F3
server: SAP Web Application Server (1.0;700)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><soap-env:Fault><faultcode>soap-env:Client</faultcode><faultstring xml:lang="en">Deserialisation failed</faultstring><detail><n0:SimpleTransformationFault xmlns:n0="http://www.sap.com/transformation-templates"><MainName>/1BCDWB/WSS0080610064309718000</MainName><ProgName>/1BCDWB/WSS0080610064309718000</ProgName><Line>128 </Line><Valid>X</Valid><ReferenceFault><DescriptionText>Error accessing the ref. node 'EMPLOYEENUMBER'</DescriptionText><RefName>EMPLOYEENUMBER</RefName></ReferenceFault><Caller><Class>CL_SRG_RFC_PROXY_CONTEXT</Class><Method>IF_SXML_PART~DECODE</Method><Positions>1 </Positions></Caller></n0:SimpleTransformationFault></detail></soap-env:Fault></soap-env:Body></soap-env:Envelope>

There is SAP Note no. 830340 addressing this issue.
https://websmp106.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=830340&_NLANG=E
Pl try to apply that SupportPack and let us know the results after that.
Also pl reward points as appropriate.

SSRS 2012 Subscription Error in Test Environment

Hi All,
I was trying to set-up Email Subscription for SSRS in my Test Environment using "Reporting Services Configuration Manager" and after providing SMTP server details. I was getting error "Failed to sent Email to [email protected]"
What could be the reason?
I tried pining SMTP IP address from the Machine where SSRS installed and I was able to ping SMTP Server using CMD ping command.
Thanks Shiven:) If Answer is Helpful, Please Vote

Hi All,
I found the issue. The IP address of Machine, where SSRS server installed, was not included in to the SMTP relay and that's why I was getting error "Failed
to sent Email to [email protected]".
Once my network team, added IP address, it started working fine.
Another thing I noticed, due to some reason SQL Server Agent was stopped and was not running and one
of my colleagues was trying to create new subscription and was getting error 'The SQL Agent service is not running. This operation requires the SQL Agent service. (rsSchedulerNotResponding)'.
Once I started SQL Server Agent, My colleague was able to create new subscription.
Thanks Shiven:) If Answer is Helpful, Please Vote

Office Web Apps Integration in a Test Environment

I am trying to test Office Web Apps in an Exchange 2013 test environment and therefore have setup my farm for HTTP only. I have set the WAC Discovery End Point on the Exchange server and I can browse to the XML successfully however when I preview files
they are still being displayed using Web-Ready Document Viewer. I have checked the Event Log and found event ids 140 and 141.
Event 141 lists the following error - There was a failure connecting to or otherwise retrieving Data from the Wac Discovery Service. We will fall back to stellent. Successfully retrieved configuration data from http://server01/hosting/discovery, but
retrieved discovery xml does not contain an external https net zone node.
Do I need to configure HTTPS with a certificate in order to get this working in a test environment or should it work with HTTP?
Thanks

Hi Luke,
Based on my research, I found some people solved this issue via resarting MBX server and CAS server on Exchange 2013 server.
Similar thread for your reference:
Exchange 2013 and Office Web Apps Server Integration
http://social.technet.microsoft.com/Forums/en-US/927a84db-cf54-4546-8b94-374c64eaac2d/exchange-2013-and-office-web-apps-server-integration?forum=exchangesvrgeneral
Please also double check whether there is anything missing during the integration. Offical articles for your reference:
Deploy Office Web Apps Server
http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx
Office Web Apps Server Integration
http://technet.microsoft.com/library/2591b1be-92c4-4192-9f5e-e4e6b319170a
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

SSL-Problems when setting up a test environment with Exchange

Hello everyone,
I am trying to set up a test environment with Exchange 2013 to learn how the stuff works. However, I am facing some problems due to the fact that Exchange is designed for use with SSL certificates. The main thing that makes problems is the connection with
RPC over HTTP. I've used the MS remote connectivity analyzer to find out why it is not working and as I thought it is because of a missing SSL certificate (it seems the self signed doesn't work here). Now in order to get this working I just bought a certificate
for "mydomain.com". Now here is the first problem: This certificate is NOT a wildcard certificate. So if I understood correctly it works for mydomain.com but it won't work for subdomain.mydomain.com. Is this correct? (First question)
If this is correct I will probably another problem: As I said this is a learning-environment so the server is at home behind a router. This means: Only one WAN-IP. I think could get this working by forwarding everything to the Exchange Server (like mydomain.com
goes to the WAN-IP where the router is forwarding everything like port 25 or 443 directly to the exchange Server). This way I wouldn't have any problems I think: mydomain.com has a valid SSL cert, it resolves to my WAN-IP which forwards everything to the internal
Exchange Server. Now here is the problem: I plan to setup a SharePoint Server as well. I thought about using ARR (IIS) to make both available behind the same WAN-IP without using ports inside the url. Ideally the Exchange Server should then be available via
"mail.mydomain.com". This will work fine with ARR but then I probably have SSL problems again? (second question)
Do you have any ideas what I can do to solve such problems? Should I buy another certificate for mail.mydomain.com? But then I would need to buy several certificates (e.g. for autodiscover.mydomain.com to get this working as well). This can become very expensive...
Thanks!
Regards
Christian

Hi,
For your first question, if there is a single certificate just for “mydomain.com”, it cannot work for subdomain.mydomain.com.
Generally, antodiscover.domain.com is used to access the autodiscover service for external users. If you just need test users to access Exchange server from internal environment, it is not necessary to get a certificate for autodiscover.domain.com.
Therefore, for your second question what I can ensure is that if all URLs that used to connect Exchange from internal and external are configured to mail.mydomain.com with all services(IIS,SMTP,POP,IMAP), there will be no certificate problems in Exchange
side.
Best Regards,
Winnie Liang
TechNet Community Support

Problem in Transporting Data in test environment

Hi,
I've added some new attributes to an existing object. I load it in Developement environment, everything is working fine in that. But when I transported the object and Transfer rules in Test environment, the data in new fields is not getting loaded. I tried to run simulation and data is coming correctly in Transfer rules but not getting loaded to new fields in Communication structure.
So, its working fine in developement system but not in Test system
Any clue what's happening.
Regards
Tarun

Yes,
But I found something. I ran the transfer in debugging mode and noticed that code was not being transported correctly to Test environment. Though I don't know the reason behind that, but I've just initiated a new transport request.
Hopefully, this will solve the problem.
Regards
Tarun

Service Reference is blocking a deployment on the test environment

Hello friends,
I made a change in a BPM process and build and deployed on the Development PO envirenment was succesfull and I could check it into the NWDI. When I want to import/deploy the changes into the test environment I get the below error:
I found the service reference and delete it and made another service reference with another ID and I still get this error. It was not a new service reference and it was already deployed on the test.
The system is already restarted but without any success.
Do you have any idea how I can delete this old object that is blocking the deployment?
Thank you in advanced,
Kind regards,
John
com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException:
There are no WSDLs stored for Service Reference:
{http://www.sap.com}bpm_order.com~bpm_order~BPMcomponent_22121756-ac7d-4671-ab9b-d7d0e286a40c_XI
[EXCEPTION]
com.sap.esi.esp.service.server.deploy.ActionException:
com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: There are no
WSDLs stored for Service Reference:
{http://www.sap.com}bpm_order.com~bpm_order~BPMcomponent_22121756-ac7d-4671-ab9b-d7d0e286a40c_XI
at
com.sap.esi.esp.service.server.deploy.sca.actions.XIReferenceDataRemover.perform(XIReferenceDataRemover.java:35)
at
com.sap.esi.esp.service.server.deploy.CompositeAction.perform(CompositeAction.java:46)
at
com.sap.esi.esp.service.server.deploy.CompositeAction.perform(CompositeAction.java:46)
at
com.sap.esi.esp.service.server.deploy.ActionsManipulator.performAction(ActionsManipulator.java:29)
at
com.sap.esi.esp.service.server.deploy.sca.SmartConfigPlugin.deployEventActionWithRollbackSupport(SmartConfigPlugin.java:49)
at
com.sap.esi.esp.service.server.deploy.sca.SmartConfigPlugin.executeEvent(SmartConfigPlugin.java:95)
at
com.sap.engine.services.sca.deploy.ApplicationUpdate.perform(ApplicationUpdate.java:195)
at
com.sap.engine.services.sca.deploy.SCACompositeContainer.invoke(SCACompositeContainer.java:297)
at
com.sun.proxy.$Proxy33.makeUpdate(Unknown Source)
at
com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:409)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:478)
at
com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:234)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:582)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:487)
at
com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)
at
com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)
at
com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at
com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
at
com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at
com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at
com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at
com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at
com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at
com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at
com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at
com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused
by: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: There are
no WSDLs stored for Service Reference:
{http://www.sap.com}bpm_order.com~bpm_order~BPMcomponent_22121756-ac7d-4671-ab9b-d7d0e286a40c_XI
at
com.sap.esi.esp.service.server.storage.WSDLStorageImpl.getServiceReferenceWSDLS(WSDLStorageImpl.java:297)
at
com.sap.esi.esp.service.server.deploy.sca.actions.XIReferenceDataRemover.perform(XIReferenceDataRemover.java:28)
29 more

In your NWDS, go to Window-->Show View-->Others-->Undeploy View.
Search for your BPM DC, double-click on it and then click on the Black Ball on the table in the right hand side.
This will undeploy all the BPM Components from the test server.
Now, go to your BPM project, delete the exiting WSDL, create a new one and then deploy.
This should work fine.

HT4995 My iPad 2 Location Service works fine but does not work on my home Airport router. How can I fix the problem?

My iPad 2 Location Service works fine but does not work on my home Airport router. How can I fix the problem?

lbryan1987 wrote:
I dont want the button problem solved i need to know how to restore the phone without using that button or going into settings
You don't in the condition it's in. You will either have to get the phone replaced by Apple or pay a 3rd party to repair it.
there seriously should be more than two ways to solve this other wise apple is useless and we will never buy another apple product.
Seriously? It's physically broken!

Correct idea to scale out testing environment and test service pack2 installation

Hi
I have a sharepoint 2010 farm it has one sharepoint server, one database server
In one server below services are running
Central administration service
SharePoint Server Search
User Profile Service
Microsoft SharePoint Foundation Web Application
so i want to scale out this form to
1 application server
1 web front end server
1 Search server (index server)
1 databse server
here how i scale out to this form
1)here how i move sharepoint server search service to new index server and
2) here how i move Microsoft SharePoint Foundation Web Application to new webfront end server
and in this single server some web appllications are running also how i move these to new wf server
i want to do like this because i want to test service pack 2 installation, now sharepoint version is : service pack1
my actual production environment has
2 application servers
2 webfront end servers
2 index servers
1 databae server
so this correct idea to scale out testing environment and test service pack2 installation
adil

Hi Adil,
The link below describes how to scale SharePoint Web Front-End with only web applications and the search query server out of one SharePoint server with all roles running.
http://sharepointsolutions.com/sharepoint-help/blog/2011/02/how-to-scale-out-a-sharepoint-2010-farm-from-two-tier-to-three-tier-by-adding-a-dedicated-application-server/
Now you have two SharePoint server with:
Tier 1 – SharePoint Server dedicated as a Web Front-End (WFE) with only the web application(s) and the search query service running on it
Tier 2 – SharePoint Server dedicated as an Application Server with all of the other service applications running on it, but no web applications or query service
Tier 3 – SQL Server for the databases
Then you would scale out WFE server with web applications from tier1. Now please install a new SharePoint server and join it to the existing farm and deploy it as Web Front Server. Enable the relevant services on Web Front servers per the topology picture
below, and stop the services running on the old server.
http://technet.microsoft.com/en-us/library/cc263044(v=office.14).aspx
Regards
Rebecca Tu
TechNet Community Support

In app purchase is not working in testing environment in sandbox for the past 5 days. Please anyone know about this issue.

in app purchase is not working in testing environment in sandbox for the past 5 days. Please anyone know about this issue.
What i did
1 . Added three products more to the existing in-app
2 . Tested with sanbox
i am getting the error "cannot connect to itunes store" with error code "0" when trying to purchase product in sandbox.
Is sandbox is down?Please help guys..

Apple's sandbox has been down practically all month. You can check the status here:
http://sandbox.itunes.apple.com

Export excel option is not working in test environment in Firefox.

In our application 'export excel' option is present in 4 different pages. All the excels working in development environment in both IE and FF. In testing env, all the excels working fine in
IE. But only two excels are working in FF in testing env. Remaining not working and 'The connection was reset The connection to the server was reset while the page was loading' error page appears when we click on 'export excel' button. Can any one help on this issue...

Hello,
You can do one of the following:
Select the table in Firefox and then copy it to the clipboard. In Excel do Paste Special and select either 'Unicode text' or 'text' to copy it into Excel.
Use the Table2Clipboard extension. This will provide the Right-Click menu option, it will copy the data into the clipboard and you can then paste the selection into Excel.
I hope that helps.

I have a problem with my viber.It has stopped working.I tried reinstalliing it again .On the setup option after entering my phone number and continuing ..it either exists or gives no service message .

I have a problem with my viber.It has stopped working.I tried reinstalling it again .On the setup option after entering my phone number and continuing ..it either exists or gives no service message .My other applications are working fine ..other applications that require internet too are working fine.

Please get in touch with Viber's customer support.

DCN Notification stops working after 10 to 12 hour in test environment

Hi
We are using Oracle 11G and Java 5 (ojdbc5.jar).
We are using Oracle database change notification (DatabaseChangeRegistration) in java code to refresh the table cache (records of tables are stored in java hashtable for caching) in app server. The same code is working fine in production and was working fine in the test environment.
But from past one month we are facing issues in with our four application servers stop receiving the notification at the same time from the database, and we need to restart all the four application servers at the same time.
We are trying to find out if this issue is happening due to oracle database of some thing getting wrong with the java DatabaseChangeRegistration thread.
One more scenario is noticed if we are not restarting the app servers for almost one hour then this functionality start working again automatically, but some time it took more than hour too to get working without restart of the app servers.
We are using following code to register the Database change notification,
Properties prop = new Properties();
          prop.setProperty(OracleConnection.DCN_QUERY_CHANGE_NOTIFICATION,"false");
          prop.setProperty(OracleConnection.DCN_IGNORE_DELETEOP,"true");
cr = ((OracleConnection) ((WrappedConnection)(((WrappedConnection)conn).getUnderlyingConnection())).getUnderlyingConnection()).registerDatabaseChangeNotification(prop);
               // Add the call back method to the oracle server for the jdbc layer
               logger.info("Adding DCN Listener");
               dcnList = new DCNListener(this);
          dcr.addListener(dcnList);
          // second step: add objects in the registration:
               logger.info("Add Object in the registration");
          stmt = ((WrappedConnection)(((WrappedConnection)conn).getUnderlyingConnection())).getUnderlyingConnection().createStatement();
          // associate the statement with the registration:
               logger.info("Associate the statement with the registration");
          ((OracleStatement)stmt).setDatabaseChangeRegistration(dcr);
          logger.info("Execute registered SQL : "+REGISTERED_SQL);
          rs = stmt.executeQuery(REGISTERED_SQL);

Hi
We are printing the DCN status and registration id in app server log, and it says that registration id is active, and also checked the table USER_CHANGE_NOTIFICATION_REGS.
App server log, after during this issue :
Getting DCN Status --------
DCN RegistrationId (dcr.getRegistrationId()) : 71390
DCN State (dcr.getState()) : ACTIVE
Records from the table :
REGID REGFLAGS CALLBACK OPERATIONS_FILTER CHANGELAG TIMEOUT TABLE_NAME
71390 0 net8://(ADDRESS=(PROTOCOL=tcp)(HOST=IP_ADDRESS)(PORT=XXXX))?PR=0 6 0 4294967295 dcn_queue_table
The registration id at client and at the database matches during this issue and at client log it prints this registration id as ACTIVE during the issue.
According to our logic we read the newly inserted data from table "dcn_queue_table", through select query and and delete the records after the success of read operation .
Hence if there is any record in table dcn_queue_table, then it is an issue for us.
Now during the issue there were records in table, app server didn't receive and notification through the DCN listner thread . Now after 15 min i had updated new record in our application form, and now after 15 min, after the insertion of the new record the notification starts working now for this same DCN RegistrationId 71390.
Please suggest if it look like the issue with app server code that is handling this DatabaseChangeRegistration logic, and not an issue with the database ?

Working in test environment. Need help with creating a notification subscription

I am pulling my hair out here. Whatever I have left. I am experimenting in my test environment. I am trying to create a notification subscription. Under criteria, when I select Support Group, I only have a choice of 3. Since my test is a copy of Prod, I
am confused here because in Prod, I have about 20 Support Groups to choose from. I found a List under Library --> Lists called Incident Tier Queue and the 3 Support Groups I see are in this list. Thing is, I can't edit the list. I get some kind of validation
error. What I would like to know is when you are creating a Subscription and you select Support Group in the Criteria, where is it looking or what List if any is it looking at to get that information and how would I change it?

if OOB when creating an email subscription the Support Group check box above points to the List Incident Tier Queue, how does one change that to point to the Service Request Support Group? There has to be a change somewhere else that allows it to point to
the customized list.
You can't change that. The Support Group property defined on the Incident class is an enumeration property that uses the IncidentTierQueue enumeration (list). This property's proper name is "TierQueue".
The Support Group property defined on the Service Request class is an enumeration property that uses the ServiceRequestSupportGroupEnum enumeration (list). This property's proper name is "SupportGroup".
Those two properties are unrelated.
You can't "point" an existing property to a different list. You can only modify the values in the list by adding values in an unsealed management pack.
If, in your production environment, you have a bunch of options in your Incident's "Support Group" property beyond Tier 1, Tier 2, and Tier 3, then somewhere in your production environment is an MP that contains those new properties. That MP happens
to be the "ServiceManager.IncidentManagement.Configuration" MP. The friendly name, in the management packs list, is "Service Manager Incident Management Configuration Library".
Now, as you say, if there are a bunch of list values in the Incident support group in your production environment, then you need to import that MP into your test environment. Then, when managing Incident criteria, you'll be able to choose from all of those
options.
Furthermore..let's say that your support groups are only defined in the ServiceRequestSupportGroupEnum..then you can't use them in your Incident criteria. Neither in your test nor your production environments. The IncidentTierQueue enum has to be updated
with any options you want to use during Incident subscription creation.
Lastly (if the above is true)..are you sure you want to create an Incident subscription and not a Service Request subscription?

Problem in test environment in RFC2WS service (worked in DEV)

Similar Messages

Maybe you are looking for