File Exception Error Victoria 2

 admin

-->

  1. File Exception Error Victoria 2018
  2. Exception Error Java
  3. File Exception Error Victoria 277

This article helps you resolve the problem where unhandled exceptions cause ASP.NET-based applications to quit unexpectedly in the .NET Framework.

Original product version: .NET Framework 4.5
Original KB number: 911816

Note

This article applies to the Microsoft .NET Framework 2.0 and all later versions.

Symptoms

When an unhandled exception is thrown in a ASP.NET-based application that is built on the .NET Framework 2.0 and later versions, the application unexpectedly quits. When this problem occurs, no exception information that you must have to understanding the issue is logged in the application log.

Ultimate is an ambitious mod for Paradox Interactive's outstanding grand strategy game Victoria II, it has an expansive feature list with multiple new start dates, from 1604 to 2023. This is a list of what the files and folders inside the main Victoria 2 folder mean, knowing what files go where, and where to make changes is the most important part of modding, as something in the wrong place can easily lead to a fatal crash.

However, an event message that is similar to the following example may be logged in the System log. Additionally, an event message that is similar to the following example may be logged in the application log.

Cause

This problem occurs because the default policy for unhandled exceptions has changed in the .NET Framework 2.0 and later versions. By default, the policy for unhandled exceptions is to end the worker process.

In the .NET Framework 1.1 and in the .NET Framework 1.0, unhandled exceptions on managed threads were ignored. Unless you attached a debugger to catch the exception, you wouldn't realize that anything was wrong.

ASP.NET uses the default policy for unhandled exceptions in the .NET Framework 2.0 and later versions. When an unhandled exception is thrown, the ASP.NET-based application unexpectedly quits.

This behavior doesn't apply to exceptions that occur in the context of a request. These kinds of exceptions are still handled and wrapped by an HttpException object. Exceptions that occur in the context of a request don't cause the worker process to end. However, unhandled exceptions outside the context of a request, such as exceptions on a timer thread or in a callback function, cause the worker process to end.

Resolution 1

Modify the source code for the IHttpModule object so that it will log exception information to the application log. The information that is logged will include the following:

  • The virtual directory path in which the exception occurred
  • The exception name
  • The message
  • The stack trace
Victoria

To modify the IHttpModule object, follow these steps.

Note

This code will log a message that has the Event Type of Error and the Event Source of ASP.NET 2.0.50727.0 in the application log. To test the module, request an ASP.NET page that uses the ThreadPool.QueueUserWorkItem method to call a method that throws an unhandled exception.

  1. Put the following code in a file that is named UnhandledExceptionModule.cs.

  2. Save the UnhandledExceptionModule.cs file to the C:Program FilesMicrosoft Visual Studio 8VC folder.

  3. Open the Visual Studio Command Prompt.

  4. Type sn.exe -k key.snk, and then press ENTER.

  5. Type csc /t:library /r:system.web.dll,system.dll /keyfile:key.snk UnhandledExceptionModule.cs, and then press ENTER.

  6. Type gacutil.exe /if UnhandledExceptionModule.dll, and then press ENTER.

  7. Type ngen install UnhandledExceptionModule.dll, and then press ENTER.

  8. Type gacutil /l UnhandledExceptionModule, and then press ENTER to display the strong name for the UnhandledExceptionModule file.

  9. Add the following code to the Web.config file of your ASP.NET-based application.

Resolution 2

Change the unhandled exception policy back to the default behavior that occurs in the .NET Framework 1.1 and in the .NET Framework 1.0.

Note

We do not recommend that you change the default behavior. If you ignore exceptions, the application may leak resources and abandon locks.

File Exception Error Victoria 2018

To enable this default behavior, add the following code to the Aspnet.config file that is located in the following folder:
%WINDIR%Microsoft.NETFrameworkv2.0.50727

Status

This behavior is by design.

Exception Error Java

Victoria

More information

File Exception Error Victoria 277

For more information about changes in the .NET Framework 2.0, visit Breaking Changes in .NET Framework 2.0.