Analysis and Solution for customErrors Configuration Errors in ASP.NET Website Deployment

Problem Background and Error Symptoms

During ASP.NET website deployment, developers often encounter customErrors-related runtime errors when accessing the site remotely. According to user reports, the website runs normally in the local development environment but produces the following error when deployed to a remote server:

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

Error Configuration Analysis

The user's provided web.config file contains serious configuration errors:

<?xml version="1.0"?>
<configuration>
  <system.web>
    <customErrors mode="Off"/>
  </system.web>

  <system.web>
    <compilation debug="true"/>
    <authentication mode="None"/>
  </system.web>
</configuration>

This configuration file contains two separate <system.web> configuration sections, which is the root cause of the problem. The ASP.NET configuration system requires that each configuration section appear only once in the configuration file. Duplicate sections cause parsing errors.

Solution and Correct Configuration

The correct approach is to consolidate all configuration elements under <system.web> into a single section:

<?xml version="1.0"?>
<configuration>
  <system.web>
    <customErrors mode="Off"/>
    <compilation debug="true"/>
    <authentication mode="None"/>
  </system.web>
</configuration>

This configuration approach ensures the integrity and correctness of the configuration file, avoiding runtime errors caused by duplicate configuration sections.

customErrors Mode Detailed Explanation

The mode attribute of the <customErrors> element controls how error information is displayed:

• On: Always display custom error pages
• Off: Always display detailed error information
• RemoteOnly: Display detailed errors locally and custom errors remotely (default value)

During development, it is recommended to set mode to "Off" to view detailed error information. In production environments, it should be set to "RemoteOnly" or "On" to hide sensitive information.

Other Common Deployment Issues

The GoDaddy deployment case mentioned in the reference article reveals other potential deployment problems:

Framework Version Compatibility

If the server does not support the project's target framework version, runtime errors will occur. For example, projects developed using .NET Framework 4.0 deployed to servers that only support .NET Framework 3.5 will experience compatibility issues. Solutions include:

• Changing the target framework version in project properties
• Ensuring the server environment supports the required framework version
• Using appropriate publishing tools and configurations

Server Permission Issues

The "Server cannot access application directory" error appearing in the reference article indicates that the server process lacks sufficient access permissions to the application directory. Resolution methods include:

• Checking permission settings for IIS application pool identities
• Ensuring website directories have appropriate read/write permissions
• Verifying the correctness of file upload paths

Best Practice Recommendations

Based on problem analysis and solutions, the following best practices are recommended:

1. Configuration File Validation: Use XML validation tools to check web.config file syntax correctness before deployment
2. Environment Adaptation: Create different configuration files for different environments (development, testing, production)
3. Error Handling Strategy: Properly configure customErrors mode to balance security and debugging needs
4. Deployment Checklist: Establish standard deployment check procedures including key items like framework version and permission settings

Conclusion

customErrors configuration errors during ASP.NET website deployment typically stem from structural issues in configuration files. By correctly consolidating <system.web> configuration sections, most such problems can be resolved. Additionally, developers need to pay attention to potential issues like framework version compatibility and server permissions, establishing comprehensive deployment and quality assurance processes to ensure smooth website operation.