Hi,
Thanks for your suggestion, I have followed following steps from provided link.
1) In the connections tree (in IIS), go to your server node and then to your website.
2) For the website, in the right window you will see configuration editor under Management.
3) Double click on the configuration editor.
4) In the window that opens, on top you will find a drop down for sections. Choose "system.webServer/handlers" from the drop down.
5) On the right side, there is another drop down. Choose "ApplicationHost.Config "
6) On the right most pane, you will find "Unlock Section" under "Section" heading. Click on that.
7) Once the handlers at the applicationHost is unlocked, your website should run fine.
Now, the following error started…
1016: <modules runAllManagedModulesForAllRequests="true">
I made it as ‘false’ under web.config at line 1016 but still same error exists
So repeated above steps and unlocked modules and set value to true
Here, I tried both the ways by setting value to false as well as true but error is same
Also tried as
<modules runAllManagedModulesForAllRequests="true" runManagedModulesForWebDavRequests="true">
Identity: ApplicationPoolIdentity
Identity: NetworkService
Now the error is as follows…
HTTP Error 500.21 - Internal Server Error
Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list
- As stated in below link - 500.21 - Module not recognized.
But when i changed to Managaged Pipeline Mode to Clasic, in .Net Ver 4.0, the error is as
HTTP Error 404.3 - Not Found
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.
_________________________________________________________________________________________________________________________
When I changed dot net version to .Net 2
Error is as follows (Both in Integrated and Classic in Managed Pipeline)
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Config Error
The configuration section 'system.web.extensions' cannot be read because it is missing a section declaration
Kindly help me out..