WCF : Error when adding a New netNamedPipeBinding Endpoint -


friends,

i have iis hosted web service (

http://localhost/directory.server/services/v2/directory.svc/ws 

) works wshttpbinding. consumed webapp. need additional endpoint same service named pipe can access service project running on same machine.

i made changes in web.config expose namedpipe endpoint. but, before test new namedpipe endpoint, existing wshttpbinding endpoint started throwing error change.

error consuming webapp - requested service, '' not activated. see server's diagnostic trace logs more information.

there no doubt addition of namedpipe endpoint causing issue. if fix namedpipe issue, both endpoints work.

here web.config changes -

  <system.servicemodel> <servicehostingenvironment aspnetcompatibilityenabled="true" multiplesitebindingsenabled="true" /> <bindings>   <wshttpbinding>     <binding name="wshttp" maxbufferpoolsize="524288" maxreceivedmessagesize="10485760" messageencoding="mtom">       <readerquotas maxdepth="0" maxstringcontentlength="0" maxarraylength="0" maxbytesperread="0" maxnametablecharcount="0" />       <security mode="none">         <transport clientcredentialtype="none" />         <message clientcredentialtype="none" />       </security>     </binding>   </wshttpbinding>   <netnamedpipebinding>     <binding name="binding10" closetimeout="00:01:00" opentimeout="00:01:00" receivetimeout="00:10:00" sendtimeout="00:01:00" transactionflow="false" transfermode="buffered" transactionprotocol="oletransactions" hostnamecomparisonmode="strongwildcard" maxbufferpoolsize="524288" maxbuffersize="65536" maxconnections="10" maxreceivedmessagesize="10485760">       <security mode="transport">         <transport protectionlevel="encryptandsign"/>       </security>     </binding>   </netnamedpipebinding> </bindings> <behaviors>   <servicebehaviors>     <behavior name="default_directory">       <datacontractserializer maxitemsinobjectgraph="2147483647" />       <servicemetadata httpgetenabled="true" httpsgetenabled="false" />       <servicedebug includeexceptiondetailinfaults="true" />     </behavior>     <behavior name="">       <servicemetadata httpgetenabled="true" />       <servicedebug includeexceptiondetailinfaults="false" />     </behavior>   </servicebehaviors> </behaviors> <services>   <service behaviorconfiguration="default_directory" name="directory.server.services.v2.directory">     <endpoint address="ws" binding="wshttpbinding" bindingconfiguration="wshttp" name="wshttp_directory" contract="directory.server.services.v2.idirectory" />     <endpoint address="mex" binding="mexhttpbinding" name="mex_directory" contract="imetadataexchange" />     <endpoint address="net.pipe://localhost/directory.server/services/v2/directory.svc/np" binding="netnamedpipebinding" bindingconfiguration="binding10" name="namedpipe_directory" contract="directory.server.services.v2.idirectory" />   </service> </services> 

what doing wrong? pls help.

is enabled on iis? named pipes require enabled. reference - http://msdn.microsoft.com/en-us/library/ms752253.aspx


Comments

Popular posts from this blog

php - Calling a template part from a post -

Firefox SVG shape not printing when it has stroke -

How to mention the localhost in android -