Server Error in '/BugNET' Application. when running Install.aspx

Topics: Installing BugNET
Aug 26, 2013 at 2:40 PM
Figured out my last issue (I hope--I've learned a bit about server management, as our backend guy has been rather busy to look into things himself and is really more of a programmer--hooray small company)

This is what Install.aspx does

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Install.aspx.cs" Inherits="BugNET.Install.Install" Theme="" %>

Based on my searching for what CodeBehind does in .NET applications, is refers to another file (in this case Install.aspx.cs) and runs the code that that file contains.

As far as I have been able to determine, this file does not exist.
Aug 26, 2013 at 2:46 PM
You are correct, but this file gets compiled into the BugNET.dll assembly and is executed by IIS and .NET. This is the first thing that gets executed (roughly) when you try to install so any errors in execution would happen here.
Aug 26, 2013 at 2:49 PM
Thank you for the...correct, but unhelpful reply.

How does I feex eet?
Aug 26, 2013 at 2:56 PM
Set <customErrors mode="Off"/> in the web.config (edit in a text editor and save) then run the install again , this will should a more detailed error page.
Aug 26, 2013 at 3:00 PM

Server Error in '/BugNET' Application.

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

Source Error:


Line 72: </controls>
Line 73: </pages>
Line 74: <compilation debug="false" targetFramework="4.0" batch="false">
Line 75: <assemblies>
Line 76: <add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>


Source File: C:\Inetpub\vhosts[site].com\httpdocs\BugNET\web.config Line: 74
Aug 26, 2013 at 4:05 PM
In IIS , make sure the application pool is set to .net 4.0
Aug 26, 2013 at 4:29 PM
Had to create a new application pool, as I don't want to fuck with one that's being used for 9 applications and have one (or more) of them stop working (this physical server manages 5 separate websites, four of which belong to clients). And now I get this:

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: IIS Web Core
Notification: Unknown
Handler: Not yet determined
Error Code: 0x80070005
Config Error: Cannot read configuration file due to insufficient permissions
Config File: \?\C:\Inetpub\vhosts[site].com\httpdocs\web.config

I set the application pool to use the NetworkService identity (the identity associated with the other application pool has a password and I don't know it), which has full control over the related files.
Sep 3, 2013 at 7:53 PM
Changed the Application Pool that was already set up using IWAM_plesk over to version 4.0 (our server guy said that shouldn't break anything) and tried again. Got this:



HTTP Error 404.17 - Not Found
The requested content appears to be script and will not be served by the static file handler.

Detailed Error Information

Module: StaticFileModule

Notification: ExecuteRequestHandler

Handler: StaticFile
Error Code: 0x80070032

Requested URL: http://www.[site].com:80/BugNet/Install/Install.aspx
Physical Path: C:\Inetpub\vhosts[site].com\httpdocs\BugNET\Install\Install.aspx

Logon Method: Anonymous
Logon User: Anonymous
Sep 4, 2013 at 5:05 PM
You can try running the iisreg tool to properly setup the script mappings for asp.net to execute pages again. Looks like the asp.net engine is not even being invoked and its treated the files as static content.

http://stackoverflow.com/a/3763400
Sep 4, 2013 at 5:29 PM
Yeah, none of the solutions there worked for me.
I'm already set as 4.0, I ran aspnet_regiis.exe -i, I checked the other things people had pointed out and either it didn't help or I was unable to find the setting because the layout of menus and such were different.