WCF - No protocol binding matches the given address
Hi!
I have a problem hosting WCF services. I use Castle and I already have installed the Premotion.AspNet.AppHarbor.Integration dll but the error is No protocol binding matches the given address 'http://gestionesperaservices.apphb.com/xxxx/xxxx.svc'. Protocol bindings are configured at the Site level in IIS or WAS configuration.
What may be going on?
Thanks!!
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by nschmidt on 03 Feb, 2017 10:41 PM
Hi!
I fix this problem added <serviceHostingEnvironment multipleSiteBindingsEnabled="true"/> to the web.config file.
Close de issue.
Thanks.
Support Staff 2 Posted by rune on 03 Feb, 2017 10:43 PM
Hi,
Was just about to follow up on this, but glad to hear you figured it out already! Let me know if there's anything else I can help with.
Best,
Rune
rune closed this discussion on 03 Feb, 2017 10:43 PM.
nschmidt re-opened this discussion on 03 Feb, 2017 11:02 PM
3 Posted by nschmidt on 03 Feb, 2017 11:02 PM
Ok!
Now I'm getting this: The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
Any idea?
Thanks!
Support Staff 4 Posted by rune on 07 Feb, 2017 02:09 AM
Hi,
Can you point me to an URL where this error is returned so I can take a closer look (as it doesn't seem to apply to the endpoints I just tested)?
Best,
Rune
5 Posted by nschmidt on 07 Feb, 2017 10:22 PM
Hi Rune!
Good news! I fix it... it was a config.
Thanks!
rune closed this discussion on 08 Feb, 2017 10:31 PM.