Clicking on "Pages" generates "IIS 7.5 Detailed Error - 404.0 - Not Found" in IIS 7.5 / Windows Server 2008 R2 - General Discussions - General Discussions - Progress Community

Clicking on "Pages" generates "IIS 7.5 Detailed Error - 404.0 - Not Found" in IIS 7.5 / Windows Server 2008 R2

 General Discussions

Clicking on "Pages" generates "IIS 7.5 Detailed Error - 404.0 - Not Found" in IIS 7.5 / Windows Server 2008 R2

  • Clicking on "Pages" generates "IIS 7.5 Detailed Error - 404.0 - Not Found" in IIS 7.5 / Windows Server 2008 R2
  • Has anyone received this error?

    I've gone through all of the installs, videos, blogs, re-installs, and I'm basically stuck here...

    Environment:
    - IIS 7.5 / WIndows Server 2008 R2
    - SQL Server 2008 R2

    I'm able to create a project, setup the admin user, login, and see the dashboard.

    It's when I click on "Pages" where I get this.

    Anyone who has an idea or has run into this already, feedback would be extremely appreciated.

    Thanks.

    Dave
  • Hi David Hahn,

    It seems that you have problems with WCF services. There two most common issues that can cause this:

    1) WCF is not enabled for your website (please consult this configuration article).
    2) The second cause for this issue is related to the one described in this article.

    All the best,
    Radoslav Georgiev
    the Telerik team
  • I had the same error, even though I had *.svc registered in handler mappings in IIS (7.5 under Windows7). Turned out it was because it was pointing to the dot net 2.0 isapimodule instead of the 4.0 version. Looking closer, I realized dot net 4.0 was not fully set up under IIS (only 2 app pools - classic and integrated version 2, etc). Running "aspnet_regiis -i" per:
    http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx 
    fixed everything up

    Cheers

    Jonathan
  • I had the same error, even though I had *.svc registered in handler mappings in IIS (7.5 under Windows7). Turned out it was because it was pointing to the dot net 2.0 isapimodule instead of the 4.0 version. Looking closer, I realized dot net 4.0 was not fully set up under IIS (only 2 app pools - classic and integrated version 2, etc). Running "aspnet_regiis -i" per:
    http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx 
    fixed everything up

    Cheers

    Jonathan
  • I was also having the same issue on IIS 8.5 . it was because we have not added the handler mapping for sitefinity services, check out the following link to know how to add handler mapping for this purpose. 

    https://theprogressiveviews.blogspot.com/2015/10/sitefinity-backend-issue-after-hosting.html