« Previous Next »

Thread: Error 500.19 IIS7 on one server not on other identical server.

Last post 05-23-2008 4:04 PM by sfawcett2. 1 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (2 items)

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

  • 05-23-2008, 10:26 AM

    • sfawcett2
    • Not Ranked
    • Joined on 05-23-2008, 10:08 AM
    • Posts 2

    Error 500.19 IIS7 on one server not on other identical server.

    Reply Contact

    I have set up two 2008 servers with IIS7 and as far as I can see identical set up of the IIS7.

    The second server errors with...

     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 InformationModule IIS Web Core
    Notification BeginRequest
    Handler Not yet determined
    Error Code 0x80070005
    Config Error Cannot read configuration file due to insufficient permissions 
    Config File \\?\UNC\pupils\Pupils Shared Documents\web.config
    Requested URL https://wwwnet:443/pupilsshared
    Physical Path \\pupils\Pupils Shared Documents
    Logon Method Not yet determined
    Logon User Not yet determined

    Both servers logged on as system administrator on the domain. I copied the applicationhost.config from good server and restarted iis7 and no change. Same error when running from browse within iis7 and XP pro on another machine. I can fix error by adding "everyone" read permissions to the remote share. last line "logon user not yet determined" seems to be the problem. The "basic authentication" does not throw up a password box like the firtst server does. Both set to basic authentication. I do not use webconfig.cfg.

    Thanks

    steve

     

     

     

     

     

     
    Tags:

  • 05-23-2008, 4:04 PM In reply to

    • sfawcett2
    • Not Ranked
    • Joined on 05-23-2008, 10:08 AM
    • Posts 2

    Re: Error 500.19 IIS7 on one server not on other identical server.

    Reply Contact

     I saw this from Bill staples..

    "The ApplicationPool identity also needs access to the share, so it can read any web.config files that might be there.  This is a change from IIS6 where all configuration was in the metabase and the worker process did not require access to the share.

    If your Web server and file servers are in a domain, you can grant machine$ read access and the default AppPool (which runs as NetworkService) should be able to conntect.  If you have a customer AppPool identity (domain user or sync'd account), grant that user read access."

    I removed everyone permissions and added a machine$ account for the webservers. The error has gone. Why one web server was ok and one was not I dont know. Both were looking at the same share. same user , same web page!

    What security implications (read only) has adding the machine account got?  
Page 1 of 1 (2 items)
Microsoft Communities