Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Carlos 338 posts 472 karma points
    Aug 07, 2012 @ 00:24

    MiniProfiler Version for 4.7 version broke site

    We downloaded the Package for 4.7 and tried to install the .zip file to our site. When we installed it, it completely broke our website.  we got a 500 server error. We took out the .dll's and what references we could find to them in the web.config. Could there be anything else we are missing that it installed or changed?



  • Carlos 338 posts 472 karma points
    Aug 07, 2012 @ 00:31


    Umbraco 4.7.1.

    IIS 7.5


    Just getting a 500 internal Server Error.

    we just need to know what we need to do to remove it for now.  

    Then if you have a fix or suggestion that would be awesome.



  • Carlos 338 posts 472 karma points
    Aug 07, 2012 @ 00:32

    We are using not 4.7.1.

     And we don't have server tracing on so we don't know of any of the errors that are thrown.



  • Carlos 338 posts 472 karma points
    Aug 07, 2012 @ 00:36

    We turned the error tracing on. This is what we got.



    HTTP Error 500.22 - Internal Server Error

    An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

    Detailed Error Information
    Module ConfigurationValidationModule
    Notification BeginRequest
    Handler ExtensionlessUrlHandler-Integrated-4.0
    Error Code 0x80070032
    Requested URL
    Physical Path D:\WebSites\
    Logon Method Not yet determined
    Logon User Not yet determined
    Most likely causes:
    • This application defines configuration in the system.web/httpModules section.
    Things you can try:
    • 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.
    • If you are certain that it is OK to ignore this error, it can be disabled by setting system.webServer/validation@validateIntegratedModeConfiguration to false.
    • 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)
    Links and More InformationIntegrated mode is the preferred mode for running ASP.NET applications on IIS 7.0 and above.

    View more information ยป

  • Carlos 338 posts 472 karma points
    Aug 07, 2012 @ 01:04

    Ok we backed out our web.config file to an earlier version we had from a week ago and now the site came back up.  I saw on your other forum you tested it on 4.7.2, but not 4.7.1 or  Do you plan to?  

    Thanks, the package looks very promising. We plan, on upgrading our Umbraco version at the end of the year.  We are a large organization and can only upgrade at certain times as not to bring down our public site.


Please Sign in or register to post replies

Write your reply to: