Running ASPX after installing IIS displays the "Server Application Unavailable" workaround

The reason for this is probably that the. NET Framework is now installed, and the post-loaded IIS causes. NET not to be registered in IIS.

Also, it is possible that the ASPNET account does not have permission to the server directory specified by IIS. Find "Tools-Folder Options-view-Using simple folder sharing (recommended)" In Explorer, remove the previous tick, then right-click on the server-specific directory, properties-security-add-advanced-Find Now, add the ASPNET account to it and give it full access permissions. Doing so will find that there is no error, but if access to the database may prompt the ASPNET account does not have permission to access the database. This hint is much clearer, the account in the database to add the appropriate permissions on it.

Workaround One Re-registration. Net 2.0: 
C:windowsmicrosoft.netframeworkv2.0.50727as.net_regiis.exe–i

Workaround Two Create a new application pool:
Steps to create a new application pool
1. Click Start, point to Programs, and then click Control Panel.
2. Double-click Administrative Tools, and then double-click Inte.net Information Services (IIS).
3. Right-click Application Pools, point to New, and then click Application Pools.
4. Type AppPool1 in the application pool ID text box.
5. Click OK.

assigning an application to an application pool
1. Click Start, point to Programs, and then click Control Panel.
2. Double-click Administrative Tools, and then double-click Inte.net Information Services (IIS).
3. Double-click "Web site".
4. Double-click Default Web site.
5. Right-click DebugApp1, and then click Properties.
6. In the Home Directory tab, in the Application Pool list box, select AppPool1, and then click OK.

Workaround three,Modify access permissions for the folder where the site directory resides:

Locate the current Site directory, right--Properties---security--Add, advanced--Quick Find, select users, OK.

Workaround:
1. Create a new application pool, point properties, identify, select the security account for the application pool, local system, ok!
2. Add the Network Service account permissions to the permissions in the Web folder properties.
At this point, the site can function properly. NET program.

3. Check the settings in the home directory to see if there is an. aspx entry, no add a file type, point to C:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll