dotnet web services: Moving a working web service to another server produces the following error. -- dotnet web services

RE: Moving a working web service to another server produces the follow

Claus Konrad [MCSD]
11/20/2006 1:17:02 PM

dotnet web services:

Classic error.
Are you able to see the default webform presented by any microsoft webservice?
And are you able to see the wsdl using address?wsdl in IE?

If so - your connection is fine. From the error details, I would consider
verifiying that you have the same .NET version installled (Undefined data
type: anytype). Are you sure you are presenting the same environment on both
servers?

--
rgds.
/Claus Konrad
MCSD.NET (C#)

[quoted text, click to view]

Moving a working web service to another server produces the following error.

UJ
11/20/2006 2:31:33 PM

I've got a working web service that we are moving to another machine and now
I suddenly get the following error.

While transferring the files, got the following message:
System.Web.Services.Protocols.SoapException: Server was unable to read
request. ---> System.InvalidOperationException: There is an error in XML
document (1, 1422). ---> System.Data.DataException: Undefined data type:
'anyType'.
at System.Data.XSDSchema.FindNameType(String name)
at System.Data.XSDSchema.HandleElementColumn(XmlSchemaElement elem,
DataTable table, Boolean isBase)
at System.Data.XSDSchema.HandleParticle(XmlSchemaParticle pt, DataTable
table, ArrayList tableChildren, Boolean isBase)
at System.Data.XSDSchema.HandleComplexType(XmlSchemaComplexType ct,
DataTable table, ArrayList tableChildren, Boolean isNillable)
at System.Data.XSDSchema.InstantiateTable(XmlSchemaElement node,
XmlSchemaComplexType typeNode, Boolean isRef)
at System.Data.XSDSchema.HandleTable(XmlSchemaElement node)
at System.Data.XSDSchema.HandleDataSet(XmlSchemaElement node)
at System.Data.XSDSchema.LoadSchema(XmlSchema schemaRoot, DataSet ds)
at System.Data.DataSet.ReadXSDSchema(XmlReader reader, Boolean
denyResolving)
at System.Data.DataSet.ReadXml(XmlReader reader, XmlReadMode mode,
Boolean denyResolving)
at System.Data.DataSet.ReadXmlSerializable(XmlReader reader)
at
System.Data.DataSet.System.Xml.Serialization.IXmlSerializable.ReadXml(XmlReader
reader)
at
System.Xml.Serialization.XmlSerializationReader.ReadSerializable(IXmlSerializable
serializable)
at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read14_SaveRegisteredSoftware()
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader
xmlReader, String encodingStyle)
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader
xmlReader)
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.Invoke()
at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()

Any thoughts?

Re: Moving a working web service to another server produces the following error.

John Saunders
11/21/2006 10:32:18 AM

[quoted text, click to view]

Re: Moving a working web service to another server produces the following error.

John Saunders
11/21/2006 10:35:33 AM

[quoted text, click to view]

....
[quoted text, click to view]

This may not seem too helpful, but my thought is that the exception message
is telling you the truth. 'anyType' is undefined.

Now, all you have to do is get a look at the XML being sent to see how
'anyType' is being used at line 1, character 1422, and to figure out why you
and .NET disagree on whether it is defined.

A hint: perhaps there is a namespace mismatch.

Another hint: you may want to use something like the tracing tools at
http://www.pocketsoap.com/. I understand the Microsoft Soap Toolkit also has
a tracing tool. There are also commercial tools, of which SoapScope by
MindReef is reasonably priced.

John

RE: Moving a working web service to another server produces the following error.

Fabrice Durieu
8/8/2007 1:17:26 AM

I had the same problem

This was due to .Net 2.0/1.1 both installed on the server, so by default IIS use the 2.0, but the webservice was done for 1.1.
You have to go in IIS righ click on the website (or application) the last tab allow you to select the .net version to use.

Hope it help

From http://www.developmentnow.com/g/27_2006_11_0_0_853804/Moving-a-working-web-service-to-another-server-produces-the-following-error-.htm

Posted via DevelopmentNow.com Groups

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet web services group.