Introduction:
The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map. Detailed Error InformationModule StaticFileModule.
In this article I will explain how to solve The page you are requesting cannot be served because of the extension configuration problem in IIS7.
Description:
In previous post I explained clearly about what WCF is and I explain how to create WCF sample and how to consume WCF service in our application. After completion creation of WCF service I tried to host my application on my local system during that time I got error like
HTTP Error 404.3 – Not FoundIn previous post I explained clearly about what WCF is and I explain how to create WCF sample and how to consume WCF service in our application. After completion creation of WCF service I tried to host my application on my local system during that time I got error like
The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map. Detailed Error InformationModule StaticFileModule.
To solve this error I run some of command after that my problem solved easily. To run commands just follow below instructions.
Start --> All Programs --> Microsoft Visual Studio 2008 --> Visual Studio Tools --> Open Visual Studio Command Prompt
Run Visual Studio 2008 Command Prompt as “Administrator” if you are using Windows7.
After that navigate to
C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation
After that Run this command servicemodelreg -i
After run servicemodelreg -i all components will install successfully now run your hosted WCF service will work perfectly.
After install these commands run your application during that time if you are getting any error like
There
is no compatible TransportManager found for URI
‘http://localhost/WCFSample/Service.svc’. This may because that you have
used an absolute address which points outside of the virtual
application. Please use relative address instead.
Check this post to solve this error There is no compatible TransportManager found for URI
No comments:
Post a Comment