WCF Contract Name 'IMyService' could not be found?

Question

The contract name 'IMyService' could not be found in the list of contracts implemented by the service 'MyService'.. ---> System.InvalidOperationException: The contract name 'IMyService' could not be found in the list of contracts implemented by the service 'MyService'.

This is driving me crazy. I have a WCF web service that works on my dev machine, but when I copy it to a Virtual Machine that I am using for testing, I get the error that seems to indicate that I am not implementing the interface, but it does not make sense because the service does work on my windows xp IIS. the Virtual machine uses Windows Server 2003 IIS. Any ideas?

One thing to note here is that I get this error on my VM even while just trying to access the service in a web browser as the client.

Note: I am using principalPermissionMode="UseWindowsGroups", but that is not a problem on my local machine. I just add myself to the appropriate windows group. But no luck on my VM.

Config:

<configuration>
    <system.serviceModel>
        <diagnostics>
            <messageLogging logEntireMessage="false" maxSizeOfMessageToLog="2147483647" />
        </diagnostics>
        <services>
            <service behaviorConfiguration="MyServiceBehaviors" name="MyService">
                <endpoint binding="basicHttpBinding" bindingConfiguration="basicHttpBinding"
                  name="MyService" bindingName="basicHttpBinding" bindingNamespace="http://my.test.com"
                  contract="IMyService">
                </endpoint>
            </service>
        </services>
        <bindings>
            <basicHttpBinding>
                <binding name="basicHttpBinding" maxReceivedMessageSize="2147483647">
                    <readerQuotas maxStringContentLength="2147483647" />
                    <security mode="TransportCredentialOnly">
                        <transport clientCredentialType="Windows" proxyCredentialType="None" />
                    </security>
                </binding>
            </basicHttpBinding>
            <netTcpBinding>
                <binding name="WindowsClientOverTcp" maxReceivedMessageSize="2147483647">
                    <readerQuotas maxStringContentLength="2147483647" />
                </binding>
            </netTcpBinding>
            <wsHttpBinding>
                <binding name="wsHttpBinding" maxReceivedMessageSize="2147483647">
                    <readerQuotas maxDepth="32" maxStringContentLength="2147483647"
                      maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                </binding>
            </wsHttpBinding>
        </bindings>
        <behaviors>
            <serviceBehaviors>
                <behavior name="MyServiceBehaviors">
                    <serviceMetadata httpGetEnabled="true" />
                    <serviceAuthorization principalPermissionMode="UseWindowsGroups"
                      impersonateCallerForAllOperations="false" />
                    <serviceCredentials />
                </behavior>
            </serviceBehaviors>
        </behaviors>
    </system.serviceModel>
</configuration>

Is the assembly with the interface visible to the application? Also, did you specify the namespace as part of the interface name in the config file? — casperOne, Mar 27 '09 at 23:10

score 107 · Answer 1 · edited Jun 17 '12 at 12:44

107

[ServiceContract] was missing in my case.

edited Jun 17 '12 at 12:44

abatishchev

98,240
88
296
433

answered Apr 01 '10 at 15:41

Leblanc Meneses

3,001
1
23
26

This also happened to me. I spent a few minutes reviewing the app.config because the error wasn't very clear :\. – Megacan Aug 09 '11 at 10:41
6

ARGH!!!! Damn it all to hell,... I get caught by this every sodding time! Thanks :-) – EightyOne Unite Nov 07 '11 at 11:14
1

In my case I had changed the name of the interface and forgot to update ConfigurationName on ServiceContractAttribute. – Fernando Correia May 23 '12 at 18:50
I've been searching for almost an hour, then I read that answer, then *facepalm* ! – Dec 05 '12 at 19:08
oh same here :) just wasted more than 1 hr thanks bro:) – kbvishnu Apr 21 '14 at 16:45
Good job I seen this answer, otherwise goodbye another few hours – Mimi Lauren Sep 25 '14 at 13:13

score 32 · Answer 2 · answered Mar 23 '10 at 04:21

32

@Garry (a bit late, I know)

If your ServiceContract attribute defines a ConfigurationName, this should be the value in the endpoint, not the fully qualified name. I just had this problem now as described by the OP, and this was the solution for me. Hope this helps someone else who stumbles across this.

answered Mar 23 '10 at 04:21

masty

1,539
1
17
20

2

This answer helped me solve my problem. The `ServiceContractAttribute` on the contract interface had defined values for `Name`, `Namespace` and `ConfigurationName`. I changed `name`, `bindingNamespace` and `contract` on the `endpoint` element in the web.config of the implementing service to match and the problem was solved. – John Mills Mar 18 '11 at 03:51
thanks for this, was banging my head off a brick wall for half an hour until I found this. – handles Nov 24 '11 at 12:21
renamed a configuration binding but ConfigurationName in the ServiceContract attribute and had this problem.. fixing the name conflict was the solution, hurray! – Erikest Mar 28 '12 at 23:21

score 13 · Answer 3 · answered Feb 02 '11 at 00:57

This is a slightly more uncommon solution, that applied to my situation with the same error:

It's possible that the contract namespace can be overridden, with the following attribute:

[System.ServiceModel.ServiceContractAttribute([...], ConfigurationName = "IServiceSoap")]
public interface ISomeOtherServiceName

Which would require:

<endpoint address="" binding="basicHttpBinding" contract="IServiceSoap" />

Rather than the usual (namespace).ISomeOtherServiceName.

This can be a result of code generation, in my case WSCFBlue

this was my case the configuration created a mess to resolve after 2 hours — Sundara Prabu, Nov 01 '13 at 16:02

score 10 · Answer 4 · answered Feb 08 '12 at 10:30

10

Your name attribute in the service element and the contract attribute in endpoint element are not correct. They need to be fully qualified names:

<service name="namespace.MyService">
      <endpoint contract="namespace.IMyService" >

Once you change the values to be fully qualified names that should resolve your error.

answered Feb 08 '12 at 10:30

Rajesh

7,766
5
22
35

Wow, I had part somehow deleted [ServiceContract] and after correcting it, the IIS error message still showed that the endpoint should NOT be namespace qualified, and the service SHOULD. Gaah. Both qualified finally worked. – Jonas Apr 06 '18 at 14:46

score 8 · Answer 5 · answered May 18 '09 at 12:41

8

Doesn't the contract attribute on the endpoint need to be the fully qualified namespace?

answered May 18 '09 at 12:41

Garry

1,291
1
11
19

2

This was the solution my problem also. What was confusing was that many examples online did not include the namespace. – angularsen Apr 15 '11 at 21:25
This was the solution for my problem too. – yonexbat Aug 06 '11 at 14:07

score 6 · Answer 6 · answered May 19 '09 at 05:02

yes @Garry you are right. contract in endpoint should be fully qualified name

<endpoint binding="basicHttpBinding" bindingConfiguration="basicHttpBinding"      name="MyService" bindingName="basicHttpBinding" bindingNamespace="http://my.test.com"  contract="Namespace.IMyService">

score 3 · Answer 7 · answered Feb 08 '12 at 10:13

I have a habit of doing this ...

<system.serviceModel>
    <services>
      <service name="Service" behaviorConfiguration="wsHttpBehaviour">
        <endpoint 
            binding="wsHttpBinding" 
            contract="IService" 
            bindingConfiguration="wsHttpBinding" 
            />
        <endpoint contract="IService" binding="mexHttpBinding" address="mex" />
      </service>

when i should do this ...

<system.serviceModel>
    <services>
      <service name="namespace.Service" behaviorConfiguration="wsHttpBehaviour">
        <endpoint 
            binding="wsHttpBinding" 
            contract="namespace.IService" 
            bindingConfiguration="wsHttpBinding" 
            />
        <endpoint contract="namespace.IService" binding="mexHttpBinding" address="mex" />
      </service>

See what i mean ... It's the dumbest thing ever (especially when the app only has 1 or 2 items in it) but a "fully qualified" classname seems to make all the difference.

score 1 · Answer 8 · answered Sep 15 '14 at 15:29

1

Using the visual studio 2013 "Add"->"Service" menu option created the web config sections for me but with the "endpoint" "contract" set to the name of the concrete class not the interface.

As soon as I corrected that all started working.

answered Sep 15 '14 at 15:29

rob

8,134
8
58
68

score 1 · Answer 9 · edited Jun 20 '20 at 09:12

I had the same error but the source of the problem was different. I was learning as I going and I first created a service using the Silverlight-enabled WCF service from the Silverlight templates in Visual Studio. I called this TerritoryService. When you create a service in this way the web.config is altered as below:

 <services>
      <service name="Services.TerritoryService">
        <endpoint address="" binding="customBinding" bindingConfiguration="Services.TerritoryService.customBinding0"
          contract="Services.TerritoryService" />
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
      </service>
    </services>

The examples that Im working off however use DomainServices.i.e. when using these you inherit from DomainService. So i deleted the TerritoryService I had created and then created a DomainService Class from the template off the Web templates menu in Visual Studio. I carried on working and everything compiled just fine. But when i ran it i got an error as per the title of this question.

The problem it turns out is that when you inherit from a domain service no such entry is created in the web.config file. It doesn't need it. But when you delete a service created via the Silverlight-enabled web service it does NOT delete the entry in the web.config file.

So because I had named both services the TerritoryService when the service was being called the entry in the web.config was pulled into play and the server went looking for a service defined in that manner which it could not find because i had deleted it.

So the solution was to simply delete the entry stubs as above that had been auto created by Visual Studio in the config file but not auto deleted by Visual Studio when i deleted the service. Once i did that the problem was resolved.

It took me a half hour to work this out though because of the naming "conflict". It "looked" very much right and was in line with many examples. So if you're inheriting from a domain service class you do not need/should not have an entry in the config file as you do when you've created a wcf service.

This one led me on the right path. I got this error after: 1) I created a normal WCF service (which updated my web.config). 2) Then I deleted that service. 3) Then I created a WCF Data Service with the same name. Removing the web.config change fixed me. — Josh Mouch, Jan 04 '13 at 17:28

score 1 · Answer 10 · answered May 18 '09 at 12:27

1

can you post code of your interface...? as normally this occurs if you haven't specified ServiceContract attribute in your Interface...

answered May 18 '09 at 12:27

Usman Masood

1,937
2
17
33

score 1 · Answer 11 · answered Feb 21 '12 at 15:41

1

In my case, the problem was a misnamed namespace. HTH

answered Feb 21 '12 at 15:41

joseluisrod

82
1
7

M3NTA7 · Answer 12 · 2009-03-31T00:07:28.887

0

Ok, this doesn't really satisfy my question, but one way that I found to resolve it was to install .NET 3.5. because both of my other environments had 3.0.

So I really haven't determined why it would work in one environment and not the other, especially with that interface error.

Go figure?

edited Mar 31 '09 at 00:07

answered Mar 30 '09 at 22:24

M3NTA7

1,307
1
13
25

score 0 · Answer 13 · edited Aug 17 '11 at 12:11

0

There's 2 mistakes in my case:

The config sections are copied from another proxy project, and I forgot to change the namespace to full path.
As a client, I copied the endpoint section into services node - the client is also a wcf service.

edited Aug 17 '11 at 12:11

Bo Persson

90,663
31
146
203

answered Aug 17 '11 at 06:53

flaugh

1,517
1
10
5

WCF Contract Name 'IMyService' could not be found?

13 Answers13

Linked