Thanks for your reply but no luck with that code..I am sending you complete config files related to service and application ....Give me any valuable suggession.
Service web.config
application web.config
Thanks in advance
Thanks for your reply but no luck with that code..I am sending you complete config files related to service and application ....Give me any valuable suggession.
Service web.config
application web.config
Thanks in advance
The wsHttpBinding
has message-level security and by default it uses Windows authentication. If that is not what you want perhaps you meant to use the basicHttpBinding
? This binding is not secured by default.
The BasicHttpBinding uses HTTP as the transport for sending SOAP 1.1 messages. A service can use this binding to expose endpoints that conform to WS-I BP 1.1, such as those that ASMX clients access. Similarly, a client can use the BasicHttpBinding to communicate with services exposing endpoints that conform to WS-I BP 1.1, such as ASMX Web services or Windows Communication Foundation (WCF) services configured with the BasicHttpBinding.
Security is turned off by default, but can be added setting the BasicHttpSecurityMode to a value other than None in the BasicHttpBinding(BasicHttpSecurityMode) constructor. It uses a "Text" message encoding and UTF-8 text encoding by default.
The WSHttpBinding is similar to the BasicHttpBinding but provides more Web service features. It uses the HTTP transport and provides message security, as does BasicHttpBinding, but it also provides transactions, reliable messaging, and WS-Addressing, either enabled by default or available through a single control setting.
Edit: Try this configuration:
<system.serviceModel>
<client>
<endpoint
address="http://miplserver02:9050/UserManagementService/UserManagementService.svc"
binding="basicHttpBinding"
contract="UMS.IUserManagementService">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
</client>
</system.serviceModel>
It is probably that authentication is set to anonymous instead of windows.
Check your IIS configuration and web.config for difference between your local machine and the test machine that is failing.
Also are you trying to access IIS on a remote machine while you are logged in as a local user.