ASP Net Application on IIS 7 and Windows Server 2008 does not run
-
Dear All, I have an Asp.Net application, which is run correctly in windows 2003, and also is run correctly when I run this application using Visual Studio 2008 through VS 2008 IIS. But when I tried to run this application using windows 2008 IIS.7 , it gives me an error: HTTP Error 500.22 - Internal Server Error and guided me to change the application pool from DefaultAppPool to Classic .NET AppPool I then changed the application pool as I've been guided, but another error appear is: HTTP Error 403.18 - Forbidden Links and More Information: This error occurs if the application pool for the request does not exist, or if an ISAPI filter, ISAPI extension or HTTP module calls the ExecuteURL server support function (or ExecuteRequest) with a URL that is configured in a different application pool. Due to security reasons, a Web site in one application pool cannot make ExecuteURL requests against a URL in another application pool. If you have an application that is trying to process a URL in another application pool, ensure that they both run in the same application pool if appropriate. I do not know what to do now, I looked for something talks about custome error pages and its application pool in the IIS.7, but I found nothing. please help :(
Kind Regards OBarahmeh
-
Dear All, I have an Asp.Net application, which is run correctly in windows 2003, and also is run correctly when I run this application using Visual Studio 2008 through VS 2008 IIS. But when I tried to run this application using windows 2008 IIS.7 , it gives me an error: HTTP Error 500.22 - Internal Server Error and guided me to change the application pool from DefaultAppPool to Classic .NET AppPool I then changed the application pool as I've been guided, but another error appear is: HTTP Error 403.18 - Forbidden Links and More Information: This error occurs if the application pool for the request does not exist, or if an ISAPI filter, ISAPI extension or HTTP module calls the ExecuteURL server support function (or ExecuteRequest) with a URL that is configured in a different application pool. Due to security reasons, a Web site in one application pool cannot make ExecuteURL requests against a URL in another application pool. If you have an application that is trying to process a URL in another application pool, ensure that they both run in the same application pool if appropriate. I do not know what to do now, I looked for something talks about custome error pages and its application pool in the IIS.7, but I found nothing. please help :(
Kind Regards OBarahmeh
Create your own Application pool and assign it to the web application. I have written a complete article on IIS 7. Hope this will helps you Deploying Web sites on IIS 7 and Windows server 2008[^]
cheers, Abhijit
-
Create your own Application pool and assign it to the web application. I have written a complete article on IIS 7. Hope this will helps you Deploying Web sites on IIS 7 and Windows server 2008[^]
cheers, Abhijit
I've created my own Application pool and assigned it to my application, but the problem still appear: HTTP Error 500.22 - Internal Server Error Things you can try: As the error message says: 1: Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS. 2: If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. 3: Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application. (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)
Kind Regards OBarahmeh
-
I've created my own Application pool and assigned it to my application, but the problem still appear: HTTP Error 500.22 - Internal Server Error Things you can try: As the error message says: 1: Migrate the configuration to the system.webServer/modules section. You can do so manually or by using AppCmd from the command line - for example, %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/". Using AppCmd to migrate your application will enable it to work in Integrated mode, and continue to work in Classic mode and on previous versions of IIS. 2: If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false. 3: Alternatively, switch the application to a Classic mode application pool - for example, %SystemRoot%\system32\inetsrv\appcmd set app "Default Web Site/" /applicationPool:"Classic .NET AppPool". Only do this if you are unable to migrate your application. (Set "Default Web Site" and "Classic .NET AppPool" to your application path and application pool name)
Kind Regards OBarahmeh
Did you install IIS 7.0 after .NET Framework ?
cheers, Abhijit
-
Did you install IIS 7.0 after .NET Framework ?
cheers, Abhijit
-
No, because IIS.7 is contained in windows 2008 by default...and so, I've installed .Net framework after IIS.7 is installed
Kind Regards OBarahmeh
Did you try the suggestion that are given in with the error message ?
cheers, Abhijit
-
Did you try the suggestion that are given in with the error message ?
cheers, Abhijit