Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

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


  • kristian schneider 190 posts 351 karma points
    Nov 16, 2012 @ 11:08
    kristian schneider
    0

    500.19 - Internal Server Error from one deployment location and not another

    Courier

    Hi.

    We have two developement enviroments that deploy to a staging server.

    One of them deploys without any problems, while the other one runs into a persmission error.

    The error stems from the staging enviroment, which is weird since it works from the other development machine.

    The error we get on one of the development machines is shown below.

    web.config on the staging server has modify access to everyone

    Any sugestions?

     

    /Kristian

     

    Error Summary

    HTTP Error 500.19 - Internal Server Error

    The requested page cannot be accessed because the related configuration data for the page is invalid.

    Detailed Error Information
    Module CustomErrorModule
    Notification SendResponse
    Handler Not yet determined
    Error Code 0x80070003
    Config Error Cannot read configuration file
    Config File \\?\C:\Staging\web.config
    Requested URL http://staging.XXXXXX.com:80/umbraco/plugins/courier/webservices/repository.asmx
    Physical Path C:\Staging\umbraco\plugins\courier\webservices\repository.asmx
    Logon Method Not yet determined
    Logon User Not yet determined
    Config Source

     

    Copy Link
  • Jan Skovgaard 11280 posts 23678 karma points MVP 10x admin c-trib
    Nov 17, 2012 @ 03:56
    Jan Skovgaard
    0

    Hi Kristian

    Are you 100% certain that both environments have been setup the same way?

    Have you tried resetting permissions on the development environemetn to ensure that this is absolutely not the issue? Is there any difference in the servers being used? In example IIS, app pools etc.?

    I suspect something must differ at some point.

    /Jan

    Copy Link
  • Ed Knight 16 posts 99 karma points
    Nov 17, 2012 @ 06:43
    Ed Knight
    0

    When we've encountered the 500.19 error before on local dev machines it was always corrected by making sure URL Rewriter is installed. I would start there.

    Copy Link
  • kristian schneider 190 posts 351 karma points
    Nov 20, 2012 @ 11:31
    kristian schneider
    0

    #h5is 

    Turned out one of the deployment machines had the DNS pointing to the wrong machine. so when it tried to resolve the staging server it got something wrong

     

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft