The server was upgraded from Windows Server 2003 to Windows Server 2008 in the past few days. The corresponding IIS is also upgraded from 6.0 to 7.0. magicajax error is found after the previous service is deployed:
Magicajax. magicajaxexception
The magicajax httpmodule is not supported in Web. config. Add [ < Httpmodules > < Add Name = "Magicajax" Type = "Magicajax. magicajaxmodule, magicajax" /> </ Httpmodules > ] Inside < System . Web > Section.
Note: An unhandled exception occurs during the execution of the current Web request. Check the stack trace information to learn about this error and Code Detailed information about the cause of the error.
Exception details: magicajax. magicajaxexception: The magicajax httpmodule is not supported in Web. config. Add [<Httpmodules> <AddName= "Magicajax"Type= "Magicajax. magicajaxmodule, magicajax" /> </Httpmodules>] Inside<System. Web>Section.
Source error:
An unhandled exception is generated during the execution of the current Web request. You can use the following exception stack trace information to determine the cause and location of the exception.
Stack trace:
[Magicajaxexception: The magicajax httpmodule is not supported in Web. config. Add [ < Httpmodules > < Add Name = "Magicajax" Type = "Magicajax. magicajaxmodule, magicajax" /> </ Httpmodules > ] Inside < System . Web > Section.]
Magicajax. magicajaxcontext. get_current () ++ 125
Magicajax. UI. ajaxcontrol. setajaxintrinsics () + 18
Magicajax. UI. ajaxcontrol. onload (eventargs e) + 18
Magicajax. UI. Controls. AjaxPanel. onload (eventargs e) + 14
System. Web. UI. Control. loadrecursive () + 50
System. Web. UI. Control. loadrecursive () + 141
System. Web. UI. Control. loadrecursive () + 141
System. Web. UI. Page. processrequestmain (Boolean includestagesbeforeasyncpoint, Boolean includestagesafterasyncpoint) + 627
________________________________________
Version: Microsoft. NET Framework Version: 2.0.50727.3053; ASP. NET version: 2.0.50727.3053
Search for the Web. config file and find that there is no exception. You have already placed the corresponding httpmodules in the corresponding location according to the instructions, and there is no problem in IIS6. Why? It may be an iis7.0 problem. No clear answers can be found in the online search, so you have to redeploy and check the errors. After deployment, the following prompt appears:
Code
Application Program Server Error in "TTT"
Internet Information Service 7.0
Error Summary
HTTP 500.22-Internal Server Error
Detected ASP. net settings that are not applicable in integrated managed pipeline mode.
Detailed error message
Module configurationvalidationmodule
Notification beginrequest
Handler staticfile
Error code 0x80070032
Request URL http: // localhost: 81/
Physical path E: \ ttt
Logon method not determined
Login User not determined
The most likely cause is:
• This application defines the configuration in the system. Web/httpmodules section.
Possible operations:
• Migrate configurations to the system. webserver/modules section. You can also do this manually or by using appcmd in the command line-for example, % SystemRoot % \ system32 \ inetsrv \ appcmd migrate config "Default web site /". Migrating an application using appcmd will enable it to work in integrated mode and continue to work in Classic mode and earlier versions of IIS.
• If you are sure you can ignore this error, you can disable it by setting system. webserver/validation @ validateintegratedmodeconfiguration to false.
• You can also switch an application to an application pool in Classic Mode-for example, % SystemRoot % \ system32 \ inetsrv \ appcmd set app "Default web site/"/applicationpool: "classic. net apppool ". This is done only when the application cannot be migrated.
(Set "Default web site" and "Classic. Net apppool" to your application path and application pool name)
Connection and more information integration modes are the preferred mode for running ASP. NET Applications on IIS 7.0.
Run: % SystemRoot % \ system32 \ inetsrv \ appcmd migrate config "TTT/" to solve the problem