Problem with .aspx pages on IIS 5.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • maikl
    New Member
    • Jan 2007
    • 3

    Problem with .aspx pages on IIS 5.0

    I can`t browse .aspx pages on my w2k adv. server with IIS 5. Other types (.asp and .html ...) have no problem.

    In the browser:

    (Server Application Unavailable
    The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

    Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.)

    In the application log:

    (Failed to execute request because the App-Domain could not be created. Error: 0x80004005 Unspecified error.)
  • radcaesar
    Recognized Expert Contributor
    • Sep 2006
    • 759

    #2
    Originally posted by maikl
    I can`t browse .aspx pages on my w2k adv. server with IIS 5. Other types (.asp and .html ...) have no problem.

    In the browser:

    (Server Application Unavailable
    The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

    Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.)

    In the application log:

    (Failed to execute request because the App-Domain could not be created. Error: 0x80004005 Unspecified error.)

    Let's run through some and you check them out.

    1. indexing is turned on.
    The fix is to turn indexing off for the application's directories.

    Not too common, but sometimes happens.

    2. file system encryption is enabled.
    The IIS/ASP.NET accounts can't access file system.
    Unencrypt that part of the file system and all is well.

    Again, not too common, but worth checking.

    3. file permissions, either direct or as a result of impersonation

    If you are *not* impersonating, make sure that the NETWORK SERVICE
    account has at least Read permission to your application's directory and
    to all subdirectories below it.

    You may need to assign Modify and/or Write permissions, too,
    depending on whether your application creates/modifies files or not.

    If you *are* impersonating, make sure that whatever account
    is being impersonated by ASP.NET has the same permissions
    outlined for the NETWORK SERVICE account.

    Also check with the .net version the server using (If u have 1.1 and 2.0 installed)

    :)

    Comment

    Working...