An application error occurred on the server.

Question

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.

Answer 1

Hello Evelyn Hernandez,

This issue is not related to Windows for Business or Windows 365 Enterprise. What you are seeing is a classic ASP.NET application error message. By default, ASP.NET hides detailed error information from remote clients for security reasons. The message “The current custom error settings for this application prevent the details of the application error from being viewed remotely” is controlled by the <customErrors> section in the web.config file of the application.

To view the actual error details remotely, you would need to modify the configuration. On the server hosting the application, open the web.config file located in the root directory of the web application. Inside the <system.web> section, you will find or need to add <customErrors mode="RemoteOnly" />. Changing this to <customErrors mode="Off" /> will allow detailed error messages to be displayed to remote clients. For example:

<configuration>
  <system.web>
    <customErrors mode="Off"/>
  </system.web>
</configuration>

Be aware that this should only be done temporarily for troubleshooting, because exposing detailed error information to remote users can reveal sensitive application internals. The recommended approach is to keep mode="On" or mode="RemoteOnly" in production and instead capture detailed error logs locally using tools such as Event Viewer, IIS logs, or application-level logging frameworks like Serilog or NLog.

In short, the error is not a Windows licensing or enterprise issue, but an ASP.NET configuration matter. Adjusting the web.config customErrors setting will let you see the full stack trace and pinpoint the root cause of the application error.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.

Answer 2

The error message you are encountering indicates that the application is configured to prevent detailed error information from being displayed remotely for security reasons. To view the actual error details, you can modify the Web.config file of your application. Here are the steps to do so:

1. Open the Web.config file located in the root directory of your application.
2. Look for the customErrors element within the <system.web> section. If it exists, change the mode attribute to off. If it does not exist, you can add the following code:

      <configuration>
        <system.web>
          <customErrors mode="off"/>
        </system.web>
      </configuration>
   

3. Save the changes and redeploy the application.
4. After redeploying, access the application again to reproduce the error. This time, you should see the detailed error message.
5. Once you have resolved the issue, remember to change the customErrors setting back to its original state to maintain security.

By following these steps, you should be able to view the specific error that is occurring on the server.