More in this section

Forums / General Discussions / wcf services not working under IIS 5.1

wcf services not working under IIS 5.1

4 posts, 0 answered
  1. Jeroen
    Jeroen avatar
    3 posts
    Registered:
    26 Nov 2008
    25 Nov 2010
    Link to this post
    I have created a new Sitefinity project under IIS 5.1 (Windows XP). But a lot of functions don't work when administering my website under IIS. However, they work fine when using the build-in developer server of the Sitefinity project manager.

    After digging into this I found out that none of the WCF services work and return the error: "The resource cannot be found" (like http://localhost/MySite/Sitefinity/Services/Pages/PagesService.svc/). Even my own WCF (non-REST)service is not working under Sitefinity, but works fine in a separate non-Sitefinity project under IIS.

    In IIS I checked the application extension mappings for wildcard (*) and added mapping for .svc (as I did for non-Sitefinity project), but this didn't solve the problem here. How can i get the wcf services to work, so I can administer it under IIS 5.1 (6.0)?
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    12 Sep 2017
    26 Nov 2010
    Link to this post
    Hi Jeroen ,

    Try creating a  script map for .svc manually through IIS. Make sure your script mapping for .svc is using aspnet_isapi.dll from .net 2.0 folder (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll). Add svc extension, for all verbs. IIS-hosted services can only use the HTTP transport. Its implementation in IIS 5.1 has introduced some limitations in Windows XP. The message-based activation provided for an WCF service by IIS 5.1 on Windows XP blocks any other self-hosted WCF service on the same computer from using port 80 to communicate. IIS 6.0 can share port 80 with other self-hosted WCF services running on the same machine, unlike IIS 5.1.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Jeroen
    Jeroen avatar
    3 posts
    Registered:
    26 Nov 2008
    26 Nov 2010
    Link to this post
    Hi Ivan,

    I've already mapped .svc (as described in my first post), but this doesn't make a difference. But when I remove the wildcard script map (.* extension mapped to aspnet_isapi.dll on all verbs), the .svc files work perfect, but this stops the "virtual" pages created with Sitefinity (like http://localhost/MySite/Home) from working.
  4. Radoslav Georgiev
    Radoslav Georgiev avatar
    3370 posts
    Registered:
    01 Feb 2016
    01 Dec 2010
    Link to this post
    Hi Jeroen,

    It seems to be a problem with IIS 5.1itself. It looks like if you have a wildcard script map to the Isapi Module it messes up mappings to extensions such as .svc and does not serve them properly. I have been able to reproduce this problem in a project which is not Sitefinity based. On Windows XP you have to use the integrated development server of Sitefinity's project manager or VS's development server. You can also check our system requirements page. IIS 5.1 is not supported officially.

    Regards,
    Radoslav Georgiev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
4 posts, 0 answered