An error occurred when verifying security for the message

Your question is a bit too vague. If you mean how does a stand-alone application call a web service implemented in WCF follow the following steps and look at the samples in the Windows SDK.

1) Use the context menu on the "References" entry in your project to add a web reference.

2) In the dialog select the URL for your service and it will import the WSDL and create the client stub for the service named <service>Client.

3) The stub will have methods on it that let you call the web service operations on the service.

You may have to do it form first principals , if it the service does not support retreiving the wsdl . This is more in the .NEt world anyway ( real programers code all XML and web services proxies by hand ;-) )

Please note i had the same issue with a WCF server that it crashed when there was an empty message so i changed the server . Supporting proxies is crtical unless you want to spend a month doing it from scratch.

You really need to get a hold of the wsdl of the server either as a file or sometimes you can go 'http://localhost:8080/InOut?wsdl ' this works on .NET asmx web services and WCF web services,

If you have the wsdl as a file you can use the wsdl.exe tool to create a proxy from it.

Regards,

Ben

please check this SDK sample

http://windowssdk.msdn.microsoft.com/en-us/library/ms751433.aspx

I am trying to use an ASP.Net application to communicate with a WCF service. I am able to reference the web service in my client. But when I invoke the WCF service, it just times out. I tried to consume the same service using a windows app and did not have any problems. Is there some configuration i am missing?

Abhishek

Hi Jason,

Do you need TransportWithMessageCredential ? most non WCF clients only support transport (https) as basic http binding is not WS compliant. This is the error you got... the client did not include the information. Pre WS there was no support for any authentication/user identification so i used to just put it in a SOAP header.

What clients are you trying to get up and running ? You mention wsdl is generating the proxy is this .NET1.0 , 2.0 , WSE or WCF . Only WSE and WCF support username authentication for web services.

Regards,

Ben

I am not sure if you are having the same problem as I did some months ago. I was trying to make my web application to talk to my (WCF service) 3.0 web service the same way I used to make the web application talk to my 2.0 web service. This method works if your application is a windows application but does not work for a web application. But here is what I had to do to make it work:

1. Use svcutil.exe on the command line to create the web proxy file and the app.config file.

2. Rename the app.config file to web.config file.

3. Copy the web.config file into the Visual studio application.

4. Copy the web proxy file into the webreference folder in your application.

Let me know if that works.

Abhishek