ansaurus

Question

Answer 1

A:

Two guesses: you've got multiple <endpoint address="" entries in there somewhere.

They might not have the same values but they might resolve to the same name.

Or since it looks like you're using https://, do you use http on the dev machine and https on the live one?

If so, do you have separate endpoint addresses for both? In theory you shouldn't do this - you'd enable transport security on an http base address, which will prevent it from being able to be called on anything other than https.

Technically http and https are both http schemes.

Andras Zoltan 2010-02-04 14:06:48

only one endpoint, and on de dev machine I also use httpsdid a search solution just to be sure, no other endpoints found.It works in devserver I only replace domain name and endpoint location on production

Medo 2010-02-04 14:24:31

looking at the config - have you tried removing the explicit 'address=' from your main service's endpoint? You don't need to specify a base address if the service will 'begin' at the .svc file.

Andras Zoltan 2010-02-05 08:29:12

Answer 2

A:

Try adding a prefix to your production server in ther web config:

<serviceHostingEnvironment>
  <baseAddressPrefixFilters>
    <add prefix="https://www.greenjump.nl:443" />
  </baseAddressPrefixFilters>
</serviceHostingEnvironment>

This would be added to <system.serviceModel>

And your endpoint should look like this:

   <endpoint address="https://www.greenjump.nl:443/WebServices/OrderService.svc" 
              binding="wsHttpBinding"
              bindingConfiguration="wsHttps"
              contract="SharpShop.Services.IOrderService">

Otherwise you can always overload the ServiceFactory like one of the other commentators suggested

Waleed Al-Balooshi 2010-02-04 14:10:30

Answer 3

A:

This is my wcf config, waleeds tip didn't work and should not be different on production or dev. right?

config moved to main question at the top.

Medo 2010-02-04 14:33:58

In the IIS in your production machine, do you have multiple bindings setup for the application? Are they using different ports? If so, then try adding port 80 to both the endpoint address and the prefix.

Waleed Al-Balooshi 2010-02-04 16:03:57

could you move this configuration to the main body of your answer so that it can all go together?

Andras Zoltan 2010-02-05 08:27:30

@waleed The website uses multiple bindings on port 80 (3) and one on 443 https.The webservice should use https only, so should I do this instead of adding port 80: <add prefix="https://www.greenjump.nl:443"/> and<endpoint address="https://www.greenjump.nl:443/WebServices/OrderService.svc" I'm a little bit slow as this is production I can't do it quickly.

Medo 2010-02-05 08:54:30

h t t p://www. was automatically converted to link by stackoverflow

Medo 2010-02-05 08:55:18

@Medo I forgot that you were using https. So, you would do port 443. I edited my original answer to show this

Waleed Al-Balooshi 2010-02-05 11:59:49

Answer 4

+1 A:

If you're hosting in IIS you don't need the base address section - as it's IIS's site configuration that provides it - so remove that section.

There is a "problem" when IIS is configured for multiple host headers though, in which case you need to use a custom factory which removes all the addresses aside from the one you want. A simple example is

namespace Example
{
    public class GenericServiceHostFactory : ServiceHostFactory
    {
        protected override ServiceHost CreateServiceHost(Type serviceType, 
                                                         Uri[] baseAddresses)
        {
            //return the first...
            return new ServiceHost(serviceType, baseAddresses[0]);
        }
    }
}

Then you would use that in your .svc file

<%@ ServiceHost 
    Service="MyImplementationClass"
    Factory="Example.GenericServiceHostFactory"
%>

blowdart 2010-02-05 09:04:46

thanks I was working in that direction will post my result.

Medo 2010-02-05 09:39:13

Answer 5

A:

The problem is caused by IIS handling of multiple host headers. Like blowdart said here. error: This collection already contains an address with scheme http.

and somewhat more elaborate here http://forums.silverlight.net/forums/p/12883/274592.aspx

using the first baseAddresses[0] is not an option for me because my baseAddresses were http://localhost/WebServices/OrderService.svc http://www.greenjump.nl/WebServices/OrderService.svc https://vps2051.xlshosting.net/WebServices/OrderService.svc in this order of course I could do [1] but I don't like this configuration dependency.

It seems my problem is somewhat more complex due to the https binding, this is the ServiceHostFactory I came up with:

 public class MyServiceHostFactory : ServiceHostFactory
    {

        protected override ServiceHost CreateServiceHost(Type serviceType, Uri[] baseAddresses)
        {
            Uri webServiceAddress = baseAddresses[0]; //default to first

            if (HttpContext.Current != null) //this only works when aspNetCompatibilityEnabled=true
            {
                string host = HttpContext.Current.Request.Url.Host;
                var goodAddress = baseAddresses.FirstOrDefault(a => a.Host == host);//try to find address with same hostname as request
                if(goodAddress!=null)
                {
                    webServiceAddress = goodAddress;
                }
                Type[] sslServices = { typeof(OrderService)  };//add all https services here
                if (sslServices.Any(s => s == serviceType))
                {
                    UriBuilder builder = new UriBuilder(webServiceAddress);
                    builder.Scheme = "https";
                    builder.Port = 443; //fails if you use another port
                    webServiceAddress = builder.Uri;
                }
            }
            return new ServiceHost(serviceType, webServiceAddress);
        }
    }

Still this feels hacky, and should be solved by microsoft.

Medo 2010-02-05 12:49:02

@Medo Did you try adding the port to the endpoint and the base prefix? That was one solution so that you wouldn't need to do this custom factory.

Waleed Al-Balooshi 2010-02-05 13:13:25

ansaurus

tags:

views:

answers:

wcf Service could not be activated

related questions