Damien McGivern - All Comments

» Probleme beim Ver??ffentlichen von ASP.Net kompatibler WCF Services BeagleOutOfBoundsException

Wed, 27 Jan 2010 16:41:27 GMT

Pingback from » Probleme beim Ver??ffentlichen von ASP.Net kompatibler WCF Services BeagleOutOfBoundsException

More User Group Member Benefits

Simon Phillips — Mon, 11 Jan 2010 10:01:04 GMT

Last month Damien blogged about an offer for NIMTUG members from O’Reilly ( Special offer from O'Reilly

links for 2010-01-08 « dstelow notes…

links for 2010-01-08 « dstelow notes… — Fri, 08 Jan 2010 23:08:17 GMT

Pingback from links for 2010-01-08 « dstelow notes…

Ensuring WCF Correctly Reports Errors | Exigency In Specie

Ensuring WCF Correctly Reports Errors | Exigency In Specie — Thu, 10 Dec 2009 17:33:42 GMT

Pingback from Ensuring WCF Correctly Reports Errors | Exigency In Specie

re: WCF CommunicationObjectFaultedException " cannot be used for communication because it is in the Faulted state" MessageSecurityException "An error occurred when verifying security for the message"

Sunil Bindra — Mon, 02 Nov 2009 06:33:41 GMT

Hi Dear

I have same issue. I am trying this on same machine. As my client and server is on same machine so issue of time. I am using even maxClockSkew=infinite. Even then i am getting this exception. Can any help me out?

Below is my Code at client Machine

HealthCheck.McmSecurityService.SecurityServiceClient SctyClient = new HealthCheck.McmSecurityService.SecurityServiceClient();

//SctyClient.ClientCredentials.UserName.UserName = "MCM" + "~" + "MCM" + "~" + "MCM";

//SctyClient.ClientCredentials.UserName.Password = "MCM";

//if(SctyClient.State!=CommunicationState.Faulted)

SctyClient.ClientCredentials.UserName.UserName = "sf" + "~" + "suneelk" + "~" + "infogain";

SctyClient.ClientCredentials.UserName.Password = "infogain";

SctyClient.Open();

//SctyClient.

//HealthCheck.McmSecurityService.UserInfo objUserInfo = SctyClient.ValidateUser("suneelk", "sf", "infogain");

//SctyClient.ValidateUser("suneelk", "sf", "infogain");

//DateTime date = DateTime.Today;

string Sec_Str = SctyClient.HealthCheck();

SctyClient.Close();

The exception I am getting is :

{"An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail."}

Inner Exceoption is :

{"An error occurred when verifying security for the message."}

Stack Trace is :

"\r\nServer stack trace: \r\n at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout)\r\n at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)\r\n at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)\r\n at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)\r\n at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)\r\n at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)\r\n at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)\r\n\r\nException rethrown at [0]: \r\n"

thanks in advance

re: WCF CommunicationObjectFaultedException " cannot be used for communication because it is in the Faulted state" MessageSecurityException "An error occurred when verifying security for the message"

nk17 — Wed, 21 Oct 2009 08:15:36 GMT

I also have below error.

"Async End called on wrong channel." at the time of nor.EndProductList(ar);

Begin handler is as below

nor.BeginProductList(acb, extraData);

re: WCF requires precompiled ASP.Net sites to be updatable

Araik — Tue, 08 Sep 2009 04:26:49 GMT

Really helped, thanks.

re: WCF CommunicationObjectFaultedException " cannot be used for communication because it is in the Faulted state" MessageSecurityException "An error occurred when verifying security for the message"

sunny — Wed, 19 Aug 2009 21:03:35 GMT

Hi mate i have similar issue. but i don't get exception. in the client trace i found this error:

Description Failed to open System.ServiceModel.Security.SecuritySessionClientSettings`1+ClientSecurityDuplexSessionChannel[System.ServiceModel.Channels.IDuplexSessionChannel]

i have tried to find a fix but been unsuccessful. Can you help me with it?

sunny

s26f84 at gmail

Google Page Speed - Firefox/Firebug Add-On - Web Developer Tool - Damien McGivern

DotNetShoutout — Tue, 11 Aug 2009 09:20:30 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout

Google's Page Speed tool for web developers - similar to YSlow

DotNetKicks.com — Tue, 11 Aug 2009 09:06:25 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

re: WCF CommunicationObjectFaultedException " cannot be used for communication because it is in the Faulted state" MessageSecurityException "An error occurred when verifying security for the message"

Steve — Fri, 07 Aug 2009 16:14:46 GMT

I love the helper method with the lambda approach you took. However, this won't work when calling WCF methods asynchronously. You end up getting an error, "Async End called on wrong channel."

The reason, of course, is because you're creating a new client and closing it within the Using<>() method.

Any suggestions for modifying this to get it to work with Async method calls?

re: WCF CommunicationObjectFaultedException " cannot be used for communication because it is in the Faulted state" MessageSecurityException "An error occurred when verifying security for the message"

Ken Smith — Thu, 16 Jul 2009 04:47:55 GMT

Very helpful pointer about the using() bit. I was running into the same error (on the server), and I couldn't figure out where that error message was coming from. I knew about the problems with the using() pattern on WCF, but I was using somebody else's code, and didn't notice it -- and didn't realize that it was hiding the real error. I got rid of the using wrapper, and now I just have to figure out the real error :-).

re: XML Linq requires correct namespace for all XElements

John Kaster — Tue, 09 Jun 2009 06:38:20 GMT

FWIW, I just ran into that same implementation issue today. It is indeed onerous to have to reference the namespace in every XElement reference. I hope better default behavior is supported in the future.

re: 2 Free VB.Net Books (PDF)

Dhiraj Dhakal — Thu, 21 May 2009 16:31:33 GMT

your links do not open

re: 2 Free VB.Net Books (PDF)

Hammad Mughal — Mon, 04 May 2009 07:01:17 GMT

I want ot work in VB.net so kindly provide me books.