Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • The security settings between your service and your client don't match. Your service is specifying message security, with transport set to Basic ClientCredentialType and message set to UserName ClientCredentialType, and your client is using message security with transport set to Windows ClientCredentialType. Not sure if that is the problem, but you might want to look into that area. Commented Aug 10, 2011 at 7:58
  • @Tim: thanks for your reply. when i reference service by default authentication is set to windows although i am using username as authentication type in my service. I have made correction to my client web.config still same problem is occurring. Commented Aug 10, 2011 at 8:04
  • Because the mode is set to Message it doesn't matter what is configured for Transport's ClientCreadentialType. Commented Aug 10, 2011 at 8:30
  • @Ladislav Mrnka - I was wondering about that, but didn't have a chance to research the answer. Does setting the mode to Message essentially render the Transport element useless? Commented Aug 10, 2011 at 10:32