My Experience with WCF

So this time I came across this issue with WCF service which was hosted on IIS. The error that I was getting was something like this,

System.InvalidOperationException: General Error “http://mypublicwebserviceurl” ---> System.InvalidOperationException: The document at the Url ‘http://mypublicwebserviceurl’ was not recognized as a known document type.
The error message from each known type may help you fix the problem:
- Report from ‘http://mypublicwebserviceurl’ is 'The document format is not recognized (the content type is 'text/html; charset=UTF-8').'.
- Report from 'DISCO Document' is 'There was an error downloading ‘http://myinternalurl’.
  - The remote name could not be resolved: 'hostname'
- Report from 'XML Schema' is 'The document format is not recognized (the content type is 'text/html; charset=UTF-8').'.
- Report from 'WSDL Document' is 'The document format is not recognized (the content type is 'text/html; charset=UTF-8').'.
   at System.Web.Services.Discovery.DiscoveryClientProtocol.DiscoverAny(String url)
   at WebServiceStudio.Wsdl.ProcessRemoteUrls(DiscoveryClientProtocol client, StringCollection urls, XmlSchemas schemas, ServiceDescriptionCollection descriptions)
   --- End of inner exception stack trace ---
   at WebServiceStudio.Wsdl.ProcessRemoteUrls(DiscoveryClientProtocol client, StringCollection urls, XmlSchemas schemas, ServiceDescriptionCollection descriptions)
   at WebServiceStudio.Wsdl.Generate()

The service was working without any problem when used on the machine where it was hosted. Problem started when I tried to access it with Public Web service URL outside of the server.
So here the problem was the URL shown in the address bar was different from one in WSDL soap:address and xsd:import schemaLocation.

Say my Public Web service URL is http://thisispublicurl:8888/myservice.svc and in WSDL soap:address attribute URL is something like this.
<wsdl:service name="myservice">
<wsdl:port name="BasicHttpBinding_Imyservice" binding="tns:BasicHttpBinding_Imyservice">
<soap:address location="http://thisisinternalhostname:8888/myservice.svc”/>
</wsdl:port>
</wsdl:service>

Also schemaLocation in xsd:import is something like this,
<xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="http://thisisinternalhostname:8888/myservice.svc?xsd=xsd0" namespace="http://tempuri.org/"/>
<xsd:import schemaLocation="http://thisisinternalhostname:8888/myservice.svc?xsd=xsd1"namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
</xsd:schema>

After hours of googling, I found several blogs saying write permission should be given to application pool account user on %windir%/temp folder. But this didn't make any sense to me as my service was running properly on server machine, but as I was desperate I tried that too and it didn't work. Other thing that I came across was to add binding in the IIS with the host-name. But that also didn't work. So then I started looking at my app.config and comparing it with one provided by Microsoft. So what I came across was my app.config don’t have <serviceHostingEnvironment MultipleSiteBindingsEnabled="true" /> set.

So, I added this attribute and everything started working properly. So when I googled what this element does and I came across this MSDN post https://msdn.microsoft.com/en-us/library/ee358763%28v=vs.110%29.aspx that explains “When hosting a Windows Communication Foundation (WCF) service under Internet Information Services (IIS) 7.0, you may want to provide multiple base addresses that use the same protocol on the same site. This allows the same service to respond to a number of different URIs. This is useful when you want to host a service that listens on http://www.contoso.com and http://contoso.com. It is also useful to create a service that has a base address for internal users and a separate base address for external users. For example: http://internal.contoso.com and http://www.contoso.com.” And this explains what was wrong.

Thanks for reading.
Location: Vadodara, Gujarat, India

Comments

Post a Comment

Popular posts from this blog

PnP Modern Search Extensibility: Creating Custom Layouts

Image
In the last blog  we were looking at the basics of PnP Modern Search Extensibility, what we can customize  and how to create a the library component. In this blog, we will explore how to add custom layouts using extensibility.  Right now, PnP Modern Search Results webpart provides you with these 5 layouts, Details List, Cards, Slider, List and People, which should be sufficient for simpler scanarios. In addition to that, it also allows you to customize the layout by editing the handlebar template using “edit result template” option under Custom layout, or you can create a custom handlebar file, upload it on SharePoint and then add its location in “ Use an external template layout” option. For example, you are setting up a Search Results page for showing projects. If you use the the default List layout, then the results would end up looking like in the image below, it shows page title, author, date modified, project summary and then what all tags the project has been...
Read more

PnP Modern Search Extensibility: Creating Handlebar Helpers

Image
In the blog series of PnP Modern Search Extensibility we have looked at basics of  PnP Modern Search Extensibility , how to add a  custom layout  and how to add custom web components , in this blog we will look at creating custom handlebar helpers. With extensibility you can also create Handlebar helpers that can be used to in HTML templates or while configuring layout fields. There are a lot of handlebar helpers available for common scenarios as well. In the previous blog we created a Custom Simple List layout, and for showing Project Summary we were using the Summary slot mapped to HitHighlightedSummary, but what if you have created a custom column in the library and want to use it show Project Summary and you also want to truncate it at 180 characters and add ellipsis and then when the user expands the collapsible section you want to show the whole Project Summary. To do that, first of all we need a handlebar helper that would truncate and add ellipsis after...
Read more

PnP Modern Search Extensibility

Image
What is it? The PnP Modern Search solution includes a set of open-source web parts for SharePoint Online that allow for a highly customizable search experience. These web parts can be configured to create tailored search results pages, with features like dynamic filters, sorting, and pagination. PNP Modern Search Extensibility refers to the ability to customize and extend the PnP Modern Search webparts. This is achieved through various tools, components, and practices provided by the PnP community. Why do we need it? Before PnP Modern Search Extensibility was introduced, to achieve the desired changes to the search results, a lot of developers would make changes to the PnP Modern Search solution itself, which would result in the solution being detached from the community version, and if there were major releases done on the community version which were now desired on the cloned version, there would be no way to just deploy the new community package without losing the customizatio...
Read more