When my .NET program makes a Web Service call I get this response...
System.Net.WebException: The request failed with HTTP status 413:
Request Entity Too Large
1. The server the Web Service is running on is *not* MS IIS

I've the same problem. I found reply stating following:
I haven't seen mention of this in any of the documentation or HOL's but here
it is. Running Win 2k, you have to grant the ASPNET account "Act as part of
the operating system" in the local policies.

i have one problem with a method of an xml web service that use a datetime data type input variable, and may be all is caused by international settings.
The XML web service (localized in italy, with italian settings) have the following method:
MYXWS.MyMethod(input_var as datetime)

I've been having a lot of problems getting X509 decryption to work but that's
another story. I've commented out all the code so it's now just a call with
no encryption, no signature and no username token.
On the server I get the following error when request is processed by WSE 2.

I have two different scenarios:
1.         I have an application that calls a web service and passes an
object. Web Service takes that object and does some stuff with it, which
could take some time. It seems to me that in this case it would be

Can I execute assembly compiled for the 1.0 framework's version with the
latest version of framework?
I must keep the old version of framework or can I delete it?

Hello Readers,
I'm trying to create a web service client using VS .NET 2003 along
with WSE 2.0 under Win2K Prof.  I'm having trouble using a X.509
digital certificate as it seems my app generates a windows exception

The WS-Addressing and WS-Messaging support in WSE 2.0 allow exchanging
EndpointReferences between services clients and providers (e.g.
WS-Eventing).  Typically,  a Web Service may store the EndPointReference in
a database.  What is the WS recommended way to handle EndPointReferences

I'm having serious performance issues in connecting from a Win 2003
Server machine to a SQL Server database on a different Win 2000 Server
machine. There is nothing other than our application running on these
machine. They are connected via 100mb ethernet. I can ping with

I have begun experimenting with web services, and I created some
simple web services in C# and was able to install them with IIS and
create an equally simple C# client to consume them.
My next experiment was to use Python to consume these same web

What would be teh proper way to encrypt a SOAP response from a Web Service
without using x.509 or Kerberos?  I know I could do it using straight
symmetric encryption algorithms like DES, but I'd rather use something more
secure.

From what I understand of WSE2.0 and Policy you can declare a service as
requiring say  a Kerberose token and the .net client will automatically wrap
your windows identity in a Kerberose tocken and send it to the server. Is
that basically right? I'm not saying this is all policy ...

I'm trying to pass an X509SecurityToken from my client to my web
service. The certificate was made using makecert.exe, so it obviously
isn't trusted by the system. The problem now is that my service rejects
the call outright with the following message:

I have created a web service that access a database and retrieves record
then returns them as a dataset. I am having a problem coding a client
application to use the dataset. Here is the relevent code:
Web Service Code:

the .net tools are not really suited for that kind of approach, which is called ContractFirst. but it is possible.
first you have to generate some .net types from the schema your webservice has to conform to. use the xsd.exe tool included in the sdk with the /classes switch.
use ...