This is the stack trace if it helps anyone to get to the bottom of the
problem. Most of it is buried under the web services thing.
at System.Data.XmlDataTreeWriter.XmlDataRowWriter(Dat aRow row, String
encodedTableName)
at System.Data.XmlDataTreeWriter.SaveDiffgramData(Xml Writer xw, Hashtable
rowsOrder)
at System.Data.NewDiffgramGen.Save(XmlWriter xmlw, DataTable table)
at System.Data.DataSet.WriteXml(XmlWriter writer, XmlWriteMode mode)
at
System.Data.DataSet.System.Xml.Serialization.IXmlS erializable.WriteXml(XmlWriter
writer)
at
System.Xml.Serialization.XmlSerializationWriter.Wr iteSerializable(IXmlSerializable
serializable, String name, String ns, Boolean isNullable, Boolean wrapped)
at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlS erializationWriter1.Write19_ClientStateUpdate(Stri ng
n, String ns, ClientStateUpdate o, Boolean isNullable, Boolean needType)
at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlS erializationWriter1.Write27_ClientReturnData(Strin g
n, String ns, ClientReturnData o, Boolean isNullable, Boolean needType)
at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlS erializationWriter1.Write175_SelectByPointResponse (Object[]
p)
at
Microsoft.Xml.Serialization.GeneratedAssembly.Arra yOfObjectSerializer285.Serialize(Object
objectToSerialize, XmlSerializationWriter writer)
at System.Xml.Serialization.XmlSerializer.Serialize(X mlWriter xmlWriter,
Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String
id)
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Serialize(X mlWriter xmlWriter,
Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String
id)
at System.Xml.Serialization.XmlSerializer.Serialize(X mlWriter xmlWriter,
Object o, XmlSerializerNamespaces namespaces, String encodingStyle)
at System.Web.Services.Protocols.SoapServerProtocol.W riteReturns(Object[]
returnValues, Stream outputStream)
at System.Web.Services.Protocols.WebServiceHandler.Wr iteReturns(Object[]
returnValues)
at System.Web.Services.Protocols.WebServiceHandler.In voke()
--- End of inner exception stack trace ---
at SPComp.Prod.App.TargetServer.Invoke(String method, Object[] args) in
D:\development\Prod\Source\App\ServerComm\ProdServ er.cs:line 80
at SPComp.Prod.App.TargetServer.DoStuff(Point selectGeometry,
SelectionModifiers mods) in
D:\development\Prod\Source\App\ServerComm\ProdServ er.cs:line 1928
at SPComp.Prod.App.PointSelectTask.DoStuffWorker.Run( ) in
D:\development\Prod\Source\App\Features\Stuff\DoSt uffTask.cs:line 149
at SPComp.Prod.App.StateManager.Run() in
D:\development\Prod\Source\App\State Management\StateManager.cs:line 763
"SP" <sp****@yupitsme.comwrote in message
news:eq**************@TK2MSFTNGP03.phx.gbl...
>I have a web service application which uses 3rd party assemblies. I
recently
upgraded my solution to use .NET Framework 2.0 instead of .NET Framework
1.1. The 3rd party assemblies that I refer are built on .NET Framework 1.1
(but they are supposed to work under .NET Framework 2.0)
Since upgrading the solution, I get an error saying :
System.Web.Services.Protocols.SoapException: Server was unable to process
request. ---System.InvalidOperationException: There was an error
generating the XML document. ---System.InvalidOperationException:
<Details
of a datatype from 3rd party assemblydoes not implement IXmlSerializable
interface therefore can not proceed with serialization.
I tried to get to the bottom of this but could not. Now I have started
thinking that this might be because of the assembly mismatch or somthing.
Or is it possible that this is not supported altogether or is there a
workaround to fixing this problem.
I am quite new to web services, so don't even know how to look at the
messages being passed across the web services boundary.
TIA,
--SP
