Service Account which used to run the application was locked and someone has changed its credentials. We updated the service account, and that fixed the issue. So checking credentials of service account and making sure they are valid is one important thing to look for with such issues. I hope...

Add a mex endpoint to your service <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/> Then add httpGetEnabled to the service's metadata <serviceBehaviors> <behavior name="MyServiceBehavior"> <serviceMetadata httpGetEnabled="true"/> </behavior> </serviceBehaviors> Then you should be able to browse the mex endpoint's url with http EDIT: changed binding to mexHttpBinding instead of mexTcpBinding...

new BasicHttpBinding() will give you an instance of BasicHttpBinding with the default values - I don't think it will read anything from the config file (even a default configuration) unless a configuration section name is passed in (which doesn't help for a default binding defined in the config file). What...

I found this in the msdn forum, I hope this helps you: Since you have specified Security Mode= none for WsHttpBinding, when it make request to WCF service , service will try to authenticate client using Aninymous credentials, but in case of different domains this will not work, so try...

Not sure if this can be achieved without creating two services. If you're trying to create two endpoints, this is what you should try: Give the two endpoints different service name: <service name="Namespace.ServiceA" behaviorConfiguration="ServiceBehaviorA"> <endpoint binding="wsHttpBinding" bindingConfiguration="ServiceBindingHttp" contract="Namespace.IServiceHttp" /> </service> <service name="Namespace.ServiceB" behaviorConfiguration="ServiceBehaviorA"> <endpoint binding="netTcpBinding"...

Using the above configuration if i navigate to http://localhost:12345/Service1.svc/InsertData/name/surname i get the error "Method Not Found" When you do this trough your browser you are actually doing a GET request, which your method does not support. When you do it trough Fiddler you issue a POST. You can do...

Your service host config file is not the same as your client application's config. In fact, increasing maxReceivedMessageSize does not really have any effect when placed in the server-side web.config. When your service is added as a reference in another application. It will generate a client configuration much like the...

Starting with WCF 4.0, by default (with no endpoints or bindings explicitly defined) WCF will create default endpoints with basicHttpBinding. This makes the configuration less cluttered, but also means you get the default values for the binding. There are two ways to resolve this when you need non-default settings for...

the host.Credentials.ClientCertificate.SetCertificate("A", ...); does not mean that only clients with certificate A are allowed to connect. If you want to allow only some kinds of certificates, you need to inspect the CertificateValidator on the serverside. take a look: https://msdn.microsoft.com/en-us/library/aa354512%28v=vs.110%29.aspx if you have more questions feel free to ask me EDIT:...

This response can happen for a several reasons. The two that I suspect the most are: You are sending the incorrect client credentials to the server. I see you are sending a UserName and Password as "xxx". However, your server is expecting a UserName of "yaron". This is the expected...

The binding was fine, either way, and in fact needed no argument at all. The trouble was with the contract. When I changed to code to: public static class Names { public const string Address = "net.pipe://localhost/CFC/Plugins/GuestAccessService/"; public const string Binding = ""; public const string Contract = "CfcAccessPoint"; }...

that is very easy. you have to generate code exactly same with Web.Config. you must be use the below code: System.ServiceModel.EndpointAddress endpointAddress = new System.ServiceModel.EndpointAddress("net.tcp://YourIpAddress:4502/CTMSEngine/net"); System.ServiceModel.Channels.CustomBinding customBinding = new System.ServiceModel.Channels.CustomBinding(); System.ServiceModel.Channels.BinaryMessageEncodingBindingElement BMEelement = new System.ServiceModel.Channels.BinaryMessageEncodingBindingElement();...

As the article you link to shows, WCF stores the named pipe name in a memory mapped file. To access it, you need to do the following: Endpoint: net.pipe://localhost/TradeService/Service1 Normalized Endpoint: net.pipe://+/TRADESERVICE/SERVICE1/ Base 64 representation: bmV0LnBpcGU6Ly8rL1RSQURFU0VSVklDRS9TRVJWSUNFMS8= Final memory mapped file: net.pipe:EbmV0LnBpcGU6Ly8rL1RSQURFU0VSVklDRS9TRVJWSUNFMS8= Now you take the final MMF name and open...

I were able to communicate on system in workgroup by remoing security. Mean's Setting sercurity to None on both Client and server in case of work group environment. for Domain environment i used same old security settings.

You should make sure that you close your client after you use it. You can follow this pattern (taken from MSDN): MyService.JobsClient Client = new MyService.JobsClient(); Client.Endpoint.Address = new System.ServiceModel.EndpointAddress(ConfigurationManager.AppSettings["ServicePath"]); try { Client.WCFGetSystemState(System.Environment.MachineName); Client.Close(); } catch (TimeoutException timeout) { // Handle the timeout exception. Client.Abort(); } catch (CommunicationException commException) {...

There is no option that I can see that will allow access to a basic ServiceHost to load a configuration config section from an external source. And there is no way that I can see that you can update or replace the system configuration in runtime (plus it doesn't make...

I hope I understand your question, I would suggest going with Idea 1 with some modifications. You could define two jobs with the following flow (a sort of a two-step job): The regular main job fires automatically on schedule. It creates a second job with no trigger (new job id=XYZ)....

This page gives a long explanation about it and a weird workaround that I didn't feel like doing: http://www.codeproject.com/Articles/323097/WCF-ASMX-Interoperability-Removing-the-Annoying-xx What I wound up doing was adding [OperationContract, XmlSerializerFormat(Style = OperationFormatStyle.Rpc)] to my methods and I also added [ServiceContract,XmlSerializerFormat] to my interface attribute and now they act like I would expect....

OK, after a few more tries I figured it out. Posting this in case others run into the same issue. I should continue by mentioning that this behavior really needs to be mentioned somewhere on MSDN, in a location that is really visible for anyone looking for WCF security information...

You can do SSL/Transport encryption with BasicHTTPBinding. That doesn't need to change; you just need to set up the host side with "Transport" security, add some code and a certificate, and you should be able to proceed without changing too much code. I can include a small code sample below,...