Hi @all,
this is not my first webservice and everytime it worked that way, by now i
got following exception when trying to call http://<url>?wsdl in my
browser:

I have seen examples of people saying that in the soap header you can pass a
username and password.  Is there a reason why putting username and password
information in the header would be better than just including it as an input
in the web service?

I recently published a web service that works on my workstation to my ISP.
I have no authenication restrictions on the site, nor do i have restricitons
on the web service itself (<authentication mode="None"/>).   I am behind a
corporate firewall, however.

I am a novice .Net 2 developer and have only been developing in Csharp
for the last 3 months.  I have develped a number of WebServices that
are being consumed by ASP.NET website.  Currently for developing, I
have everything running on one machine but deployment will result in

I created a webservice with ASP.NET and C#. I can invoke it and test it
without any problem. but when I call it from javascript, it gives me a error
sait "Service unavalible" and the result.errorDetail.code is "Client"
Have any idia?

Can someone help to access C#.NET web service from PHP. I check online but
there is no such a good article on this with step by step information.
Thanks
Chand

We have a web app that is running under Integrated Windows
Authentication. It must consume to a web service we are publishing on
another server, also running under Integrated Windows Authentication.
In order to make this work, we have to impersonate a user account with

Hi,
  I have a C#.net Web application which calls a web service
(http://eutils.ncbi.nlm.nih.gov/entrez/eutils/soap/eutils.wsdl). It has run
just fine for months. Recently I started getting "System.Net.WebException:

All:
I have prepared a .NET 1.1 client application that consumes a remote,
public web service. All the functions work as expected, and, in
general, the application has been successful for my purposes.

I was wondering if it is common practice to use some sort of messaging
(MSMQ, WebSphere MQ) with web services.  I understand the need for messaging
for insert / update transactions, but do you think using messaging for
inquiry transactions is overkill?

I read an article on implementing multiple Attributes for a method
using [AttributeUsage(AttributeTargets.All, AllowMultiple = true)]
attribute.
How to enable AllowMultiple in SoapClient & SoapService implements?

I have created a web service name "TestWS" and published it to my SBS2003
server that uses IIS6 as a web server.
I have set NO anonymous access to TestWS virtual directory and I have
created a simple user account from the User template with the name of

Does anybody know of any good web sites for looking for local developers
that are skilled with porting a VB app to an asp.net app?
Thanks

I have been using a webservice to return a dataset to a WinForms application
and it has been working 100%. Recently data have increased and I have
started looking for a way to compress the dataset. I found a number of
articles the one I started using was:

I've set up the SAML STS Quickstart to have the Token Issuer server use
Username & Password over SSL.  The SampleService still uses the SAML token
returned by the Token Issuer.
I did this so as to avoid installing x509 certificates on the client's