-error in XML document- when migrating from BPEL 10.1.3.3 to 10.1.3.4

Hi,
I've just been handed as set of BPEL processes which were developed in 10.1.3.3 and I'm working on migrating them to 10.1.3.4.
Migration of most processes was straight forward, however, there is one process (SendMessage) that accepts an XML document as its input. The message payload is successfully sent in the older version, however, in version 10.1.3.4, I keep on getting the following error.
Server was unable to read request. ---> There is an error in XML document (195, 99). ---> Input string was not in a correct format.
The line number is the end line number of the xml document message.
I've checked both versions and in 10.1.3.3 the ValidateXML option is set to false, whereas in 10.1.3.4 its 'none', which is equivalent to false.
Are there any other settings in 10.1.3.4 that could be causing this error? Has anyone else come across this issue when migrating upgwards from 10.1.3.3?
I would greatly appreciate any suggestions.
Kind regards,
Shiraz

I had recently done the same migration. One of the issues I had faced was while specifying the nillable elements I used to get an error if the namespace definition was in the header. The error was occuring while sending the message to AQ.
I do not know if this will help. Also it would be useful if you could provide details of where the process is failing is it failing at the receive activty or later. What does the process do....
Best of luck with the problem.

Similar Messages

Creating new analysis gives "Error loading XML Document from ..."

Trying to create analysis and getting "Error loading XML Document from saw.dll/answers/answersproperties.xml?fmapId=S1clug.
The response given was:" after choosing subject area. Analysis editor is opened but Subject Areas is empty and can't do anything.
The problem is on Mozilla 12 (16.0.2, 17.0.1) and IE 8. Chrome works fine.
My system is Win 7, BI 11.1.1.6.0 is on Oracle Linux (and by the way Mozilla from Linux system works fine)
What could be the reason of this?
Edited by: 898973 on 4/12/2012 15:11

Reinstalling Mozilla with "Remove personal data" option checked resolved the problem.

Error loading XML Document from /analytics/saw.dll/common/privileges.xml

I tested my procedure for upgrading from OBI 11.1.1.5 to 11.1.1.6 which was successful. I had to rollback to OBI 11.1.1.5 using my database backup and VM snapshot due to project requirements.
The OBI application successfully comes up but users who login just get "Error loading XML Document from /analytics/saw.dll/common/privileges.xml?fmapID=KqIJCw. The response given was: ". They can't close this message box so are unable to do anything.
How can I fix this?

Hi All,
You can face this issue with other versions of OBIEE 11.*
Problem cab be solved as follows:
Go to http://localhost:7001/em > coreapplication > Capacity Management > Scalibility >
1. Lock and edit
2 .increase number of presentation services to 2
3. restart opmn component.
Go to coreapplication > Availibility > processes
1 .please note that in deployment > catalog > change path of catalog field from $coreapplication to path where your catalog resides.
2. Take down your primary instance.
3. As your secondary is up, it will grant you to browse you through catalog and dashboards.
If you want to run primary instance of presentation services
Go to path \Middleware\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips2
except catalog and catalog manager > Copy all other files to coreapplication_obips1
restart opmn component > problem solved.!!!
Regards,
Akshay S.
please like if you find it helpful

Get error (There is an error in XML document (3, 4)) when consuming web service HelpDesk_QueryList_Service with New-WebServiceProxy

Dear all,
I'm using the powershell cmdlt New-WebServiceProxy to query ITSM incidents. I'm able to get the WSDL definition ..
$uri='http://pitsm/arsys/WSDL/public/pitsmapp/HPD_IncidentInterface_WS'
$myitsm=New-WebServiceProxy -Uri $uri -Namespace ITSM -Verbose true
$auth= New-Object ITSM.AuthenticationInfo
$cred=get-credential
$auth.username=$cred.username
$auth.password= [System.Runtime.InteropServices.marshal]::PtrToStringAuto([System.Runtime.InteropServices.marshal]::SecureStringToBSTR($cred.password))
$auth.authentication="Domain Authentication"
$myitsm.AuthenticationInfoValue=$auth
$myitsm.RequestEncoding = [System.Text.Encoding]::UTF8
$tid="INC000002237910"
$criteria="'Incident Number' = ""$tid"""
When i'm consuming now the web service i get back an error messages:
$answer=$myitsm.HelpDesk_QueryList_Service($criteria,0,100)
Exception calling "HelpDesk_QueryList_Service" with "3" argument(s): "There is an error in XML document (3, 4)."
At line:1 char:1
+ $answer=$myitsm.HelpDesk_QueryList_Service($criteria,0,100)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException
Has anybody an idea what could be wrong?
Any idea how to debug the commandlet New-WebServiceProxy?
Best Regards
Chris

Hello Christian,
i know this reply is really late ;) I am actually the author of the blog post mentioned by @AnnaWY, the post she mentioned is in regards of a situation 'where everything' is how it should be. Basically, (i think) sometime administrator, or the
person who implements ITSM webservices makes an error, hence this script will not run. You will end up with that issue mentioned, in order to fix it, either you should contact the person who is responsible for that service, OR rewrite the wsdl for it yourself.
It might be a bit problematic, but, it is for sure doable, as in my latest blog post about this issue.
I am writing it here, because i also saw this page, while googling for explanation, i guess there are more people who are looking for this so here is the link to the explanation:
http://wp.me/pAXaY-ht
I hope that helps !
Regards,
Greg

Error calling a third party WSDL from BPEL

Hi,
I am trying to invoke a third party WSDL. This WSDL belongs to Oracle OPPM. When I call this wsdl from SOAPUI or even from the Enterprise Manger, it works fine.
However, when I call it from BPEL, it is giving me an error. Here is the request and error response:
Request
<messages>
<input>
<Login_Input>
<part name="sUser">
<sUser xsi:type="def:string">Username</sUser>
</part>
<part name="sPassword">
<sPassword xsi:type="def:string">Password</sPassword>
</part>
<part name="lTimeOut">
<lTimeOut xsi:type="def:int">10</lTimeOut>
</part>
</Login_Input>
</input>
Response
<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>Server was unable to read request. ---> There is an error in XML document (1, 2168). ---> <Login xmlns='http://tempuri.org/'> was not expected.</summary>
</part>
<part name="detail">
<detail>oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : Server was unable to read request. ---> There is an error in XML document (1, 2168). ---> <Login xmlns='http://tempuri.org/'> was not expected.</detail>
</part>
<part name="code">
<code>{http://schemas.xmlsoap.org/soap/envelope/}Client</code>
</part>
</remoteFault>
</bpelFault>
</fault>
<faultType>
<message>0</message>
</faultType>
</messages>
I checked the diagnostics logs and it is not giving me any further information.
I think the issue is with the WSDL file. I tried importing the WSDL locally too, but I cannot get rid of this error.
I also tried to import the namespace in the <WSDL:Types> area, but no luck.
WSDL
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions
     targetNamespace="http://tempuri.org/"
     xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
     xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
     xmlns:s="http://www.w3.org/2001/XMLSchema"
     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
     xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
     xmlns:tns="http://tempuri.org/"
     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
     xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
     xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    >
    <wsdl:types>
    </wsdl:types>
    <wsdl:message name="DebugSoapIn"/>
    <wsdl:message name="DebugSoapOut"/>
    <wsdl:message name="LoginSoapIn">
        <wsdl:part name="sUser" type="s:string"/>
        <wsdl:part name="sPassword" type="s:string"/>
        <wsdl:part name="lTimeOut" type="s:int"/>
    </wsdl:message>
    <wsdl:message name="LoginSoapOut">
        <wsdl:part name="Result" type="s:string"/>
    </wsdl:message>
    <wsdl:message name="ReleaseSecurityTokenSoapIn">
        <wsdl:part name="sSecurityToken" type="s:string"/>
    </wsdl:message>
    <wsdl:message name="ReleaseSecurityTokenSoapOut"/>
    <wsdl:message name="GetCurrentUserIDSoapIn">
        <wsdl:part name="sSecurityToken" type="s:string"/>
    </wsdl:message>
    <wsdl:message name="GetCurrentUserIDSoapOut">
        <wsdl:part name="Result" type="s:int"/>
    </wsdl:message>
    <wsdl:portType name="psPortfoliosSecurityRpcSoap">
        <wsdl:operation name="Debug">
            <wsdl:input message="tns:DebugSoapIn"/>
            <wsdl:output message="tns:DebugSoapOut"/>
        </wsdl:operation>
        <wsdl:operation name="Login">
            <wsdl:input message="tns:LoginSoapIn"/>
            <wsdl:output message="tns:LoginSoapOut"/>
        </wsdl:operation>
        <wsdl:operation name="ReleaseSecurityToken">
            <wsdl:input message="tns:ReleaseSecurityTokenSoapIn"/>
            <wsdl:output message="tns:ReleaseSecurityTokenSoapOut"/>
        </wsdl:operation>
        <wsdl:operation name="GetCurrentUserID">
            <wsdl:input message="tns:GetCurrentUserIDSoapIn"/>
            <wsdl:output message="tns:GetCurrentUserIDSoapOut"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="psPortfoliosSecurityRpcSoap" type="tns:psPortfoliosSecurityRpcSoap">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="Debug">
            <soap:operation style="rpc" soapAction="http://tempuri.org/action/psPortfoliosSecurity.Debug"/>
            <wsdl:input>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:output>
        </wsdl:operation>
        <wsdl:operation name="Login">
            <soap:operation style="rpc" soapAction="http://tempuri.org/action/psPortfoliosSecurity.Login"/>
            <wsdl:input>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:output>
        </wsdl:operation>
        <wsdl:operation name="ReleaseSecurityToken">
            <soap:operation style="rpc" soapAction="http://tempuri.org/action/psPortfoliosSecurity.ReleaseSecurityToken"/>
            <wsdl:input>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:output>
        </wsdl:operation>
        <wsdl:operation name="GetCurrentUserID">
            <soap:operation style="rpc" soapAction="http://tempuri.org/action/psPortfoliosSecurity.GetCurrentUserID"/>
            <wsdl:input>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="psPortfoliosSecurityRpc">
        <wsdl:port name="psPortfoliosSecurityRpcSoap" binding="tns:psPortfoliosSecurityRpcSoap">
            <soap:address location="http://dc01oppmsv01.molina.mhc/ProSightSOAP/psPortfoliosSecurityRpc.asmx"/>
        </wsdl:port>
    </wsdl:service>
</wsdl:definitions>
Thanks
Asif Hussain

Thanks chrisswhite,
I should have mentioned that I tried this too and it didn't solve the problem. You're right though, I should be compiling with -fPIC anyway.
Jon

Error in webservice call | Error in XML Document(1,358)

Hi all,
We currently have a web service developed in Java, which we're calling from
a dot net coded windows form. this web service is returning an object of type
abc (say). Now, when we try and get a response from java server on the form,
i'm getting the following error:
There is an error in XML document (1, 358)
Does this have something to do with a java serialised object not being able
to get deserialised in dot net? Or is it something else?
Also, I have a web reference that has been created on this java web service.
This I believe means that the object that we're trying to get on the dot net
client would be the java object that is being sent from the web service.
Point to be noted is the fact that this web service was working absolutely fine till about 2 days ago.
Any pointers are gladly appreciated.
Cheers!
Nick

Sorry for not mentioning the product versions:
The bpel process was build and deployed with Jdeveloper Studio edition version 10.1.3.1.0.3984 on a Bpel server/Application Server with version 10.1.3.1 (NT).

SRSS - Error in XML document

Running Report Count all instances of software registered in add remove programs. Run fine in the "old" native SCCM
On Reporting services the report also displays correctly but when drilling down to the linked report "Computers with specific software registered in Add Remove Programs" get the error below
Seems to be for any item in this report - has anyone else seen this ?
There is an error in XML document (1, 478919).
'', hexadecimal value 0x02, is an invalid character. Line 1, position 478919.
Ian Burnell, London (UK)

Hello Grath,
I run the following command in sql & find some updates:-
Select distinct
CHARINDEX(cast(0x28 as varchar(1)),DisplayName0),
DisplayName0
from
dbo.v_Add_Remove_Programs
Where
CHARINDEX(cast(0x28 as varchar(1)),DisplayName0) > 0
Screenshot:-
Mentioned above updates makes problem hows to resolve this.
Please suggest the solution on this.
Thanks Rahul$

JMS issues when migration from weblogic 9.2 to 10.3.5

We are facing some issues when migration from weblogic 9.2 to 10.3.5
In weblogic 9.2 :_
BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>
Company
</ejb-name>
<entity-descriptor>
<pool>
<max-beans-in-free-pool>300</max-beans-in-free-pool>
<initial-beans-in-free-pool>150</initial-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>3500</max-beans-in-cache>
<idle-timeout-seconds>100000</idle-timeout-seconds>
<read-timeout-seconds>0</read-timeout-seconds>
<concurrency-strategy>ReadOnly</concurrency-strategy>
</entity-cache>
Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
migration to Weblogic 10.3.5_
With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
Can some one look into this and provide your inputs to resolve this issue.

I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
Tom

HT4413 When migrating from time machine to my new hard drive, only some files and applications and setting are transferred, not all of them. In my latest back up I have them all. How can I fix that?

When migrating from time machine to a new hard drive, not all is transferd, only partial documents, applications , settings etc. How can I migrate the latest back-up with all the content.

sohs wrote:
When migrating from time machine to a new hard drive, not all is transferd, only partial documents, applications , settings etc. How can I migrate the latest back-up with all the content.
If you want to use Time Machine to recover the contents of one of its a backups to a new drive, follow the instructions in Mac OS X 10.6: Recovering your entire system. Note that you must select the "Restore System From Backup" option from the Utilities menu of the Installer disc to do this.
Also note that if you are transferring files to a hard drive to be used with a different computer, you should use Migration Assistant instead. This intentionally will not copy everything because some settings, applications, etc. are not compatible computer-to-computer. Migration Assistant will copy everything that is.

SAP B1 Studio 9.7 - Error : There is an error in XML document (0, 0)

Hi Friends,
I am using SAP B1 Studio PL-9.7 for form designing.
But now a days i could not open this B1 Studio because of this error :
"System.InvalidOperationException: There is an error in XML document (0, 0). ---> System.Xml.XmlException: Root element is missing."
When open this SAP B1 Studio, it shows one dialog box with the above error. I attached the dialog box image with this. Please help me..
Advance Thanks,
Indra.

Hello Christian,
i know this reply is really late ;) I am actually the author of the blog post mentioned by @AnnaWY, the post she mentioned is in regards of a situation 'where everything' is how it should be. Basically, (i think) sometime administrator, or the
person who implements ITSM webservices makes an error, hence this script will not run. You will end up with that issue mentioned, in order to fix it, either you should contact the person who is responsible for that service, OR rewrite the wsdl for it yourself.
It might be a bit problematic, but, it is for sure doable, as in my latest blog post about this issue.
I am writing it here, because i also saw this page, while googling for explanation, i guess there are more people who are looking for this so here is the link to the explanation:
http://wp.me/pAXaY-ht
I hope that helps !
Regards,
Greg

Getting "error in XML task" when trying to check out projects

I get the following error when I try to check out projects on our SAN (where everything is):
Here's the error in full:
error in XML task: error writing XML document: You do not have appropriate access privileges to save file “002800.xml” in folder “0000000000004f17”.
Anybody got any clue? Appears to be a permissions issue with the Version.bundle file contents. We just set up users and groups on the SAN with LDAP Open Directory, added the Groups to the FCS System Pref Pane, but are getting no joy when logging in as a User who is a member of a Group that has been added.
Ideas, anyone?

Hi Josh, thanks for responding.
No, I did not set up anything like that - this is a pretty plain jane setup, just trying to check out an FCP project. Some work was done on the SAN while I was away, and now we can't get it to work. The IT team (I'm just the FCS guy) says permissions appear to be correct, but it isn't working, and it did before.
I presume that if user A is trying to check out a project, that FCS is doing the dirty work at a permissins level, so it'd be the FCServer machine's admin account that set up the FCS install that needs permissions....right? Or user A? In either case, we can't get it to go.
-mike

There is an error in XML document - TimeStamp

Hi All,
Hope you can help. Captivate has been working great so far on our LMS. But since moving to Captivate 7 when submitting we get the below problem,
<?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"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>System.Web.Service s.Protocols.SoapException: Server was unable to read request. ---> System.InvalidOperationException: There is an error in XML document (2, 1250). ---> System.FormatException: The string '2013-07-24T16:30:41.0+02' is not a valid AllXsd value.
   at System.Xml.Schema.XsdDateTime..ctor(String text, XsdDateTimeFlags kinds)
   at System.Xml.XmlConvert.ToDateTime(String s, XmlDateTimeSerializationMode dateTimeOption)
   at System.Xml.Serialization.XmlCustomFormatter.ToDateTime(String value)
   at System.Xml.Serialization.XmlSerializationReader.ToDateTime(String value)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read19_interactionT ype(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read20_interactions Type(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read32_cocdType(Boo lean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read34_RteDataModel Type(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read36_Commit(Boole an isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read41_Commit()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer4.Deserialize(XmlSer ializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
--- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
--- End of inner exception stack trace ---
   at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>
Is this a problem possibly between the editions of SCORM or is it something in the Captivate product? Perhaps the xml parser version?

Thanks,
I have tested on SCORM Cloud and it is working... The SCORM content has been published with 2004 3rd edition.
We are making use of the Icodeon SCORM player (integrate with Signify LMS), do you perhaps think it could be something on the SCORM player then?

There is an error in XML document (1, 3616).

Hi all,
i got the following error when i m trying to update item master using B1WS.
There is an error in XML document (1, 3616). any solution it's very urgent
Thanks & Regards
B.Lakshmi narayanan

Hi Lakshmi,
Just like the error is stating... The structure of the xml you are sending thru DIS is incorrect.
Export it to a file and have a look at it...
Regards,
Eric

SSRS Reports getting error in XML document (1, 6110).

Hi,
SCCM 2012 R2 Query reports opening error it shows below errors few reports only open properly.
Stack Trace:
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
   at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
   at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
   at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
System.InvalidOperationException
There is an error in XML document (1, 6648).
Stack Trace:
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
   at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
   at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
   at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
System.Xml.XmlException
'', hexadecimal value 0x1F, is an invalid character. Line 1, position 6648.
Stack Trace:
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
   at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
   at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
   at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
Kiran

This has already been discussed and solved, please use the search funtion:
http://social.technet.microsoft.com/Forums/en-US/home?category=systemcenter2012configurationmanager&sort=relevancedesc&brandIgnore=True&searchTerm=There+is+an+error+in+XML+document+
Torsten Meringer | http://www.mssccmfaq.de

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

-error in XML document- when migrating from BPEL 10.1.3.3 to 10.1.3.4

Similar Messages

Maybe you are looking for