.NET Questions and Solutions

Symptoms
In Microsoft BizTalk Server 2004, you may receive the following error message when you try to compile a large map:

Exception Caught: Object reference not set to an instance of an object.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751?(http://support.microsoft.com/kb/888751/) How to obtain the latest BizTalk Server 2004 service pack
Hotfix informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

DateTimeVersionSizeFile name——————————————————————————————01-Apr-200402:313.0.5267.0676,864Btsxmltools.dll01-Apr-200402:573.0.5267.0274,432Microsoft.biztalk.basefunctoids.dll01-Apr-200402:573.0.5267.045,056Microsoft.biztalk.crossreferencing.dll01-Apr-200402:573.0.5267.040,960Microsoft.biztalk.crossreferencingfunctoids.dll01-Apr-200402:573.0.5267.0249,856Microsoft.biztalk.mapper.dll01-Apr-200402:573.0.5267.01,114,112Microsoft.biztalk.tom.dll
NoteBecause of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Symptoms
Any or all of the following symptoms may occur:When you attempt to open or close Control Panel, or when you removenetwork components in Network properties and then restart Windows, you receive one of the following error messages:

A fatal exception 0E has occurred at 0028:xxxxxxxx in VXD IFSMGR(04)+ 0000D4F1.
The current application will be terminated.
-or-

A fatal exception 0E has occurred at 0028:xxxxxxxx in VXD IFSMGR(03) + 000CF7C.
The current application will be terminated.
The <0028:xxxxxxxx> value represents the enhancedinstruction pointer to the code segment; the 32-bit address is the actualaddress where the exception occurred and can vary from computer to computer.After you receive one of these error messages, you can still use Control Panel, but the Speaker icon may no longer appear on the taskbar. This behavior may also occur in Safe mode.
When you start Windows, you receive the following error message:

A fatal exception 0E has occurred at 028:C0282dB0 in VxD IFSMGR(03) + 0000 CF7C
The current application will be terminated.Windows 95 or Windows 98 Setup stops responding (hangs) while Control Panel is being configured.
Resolution
This behavior can occur if a scanner is installed in your computer, and the Vhpscand.vxd file is located in the Windows\System folder instead of the Windows\System\Iosubsys folder.

Symptoms
When you upgrade to Windows 98, or after you install Cordes Comspeedversion 2.14, you may receive a fatal exception error message on a bluescreen. This behavior may be repeated when you restart your computer.
Resolution
This behavior can occur if you are running Cordes Comspeed version 2.14.Windows 98 is not compatible with the type of .vxd file used by thisprogram.

Symptoms
When you attempt to open a file or folder on Windows NT shared networkdrive that is on a NTFS partition, you may receive the following errormessage:

A Fatal Exception 0E has occurred at 0028:C0231810 in VXD VMM(0D) +00001810.
The current Application will be terminated.
Resolution
This behavior can occur if both of the following conditions exist:The file or folder you are attempting to open has a long file name.You have disabled short file name (standard 8.3 naming) creation on theWindows NT computer.

Symptoms
If the last two or more components in a path match MS-DOS device names, you may receive an error message on a blue screen similar to the following example:

A fatal exception 0E has occurred at (address) in VXD (FSD) + (address). The current application will be terminated.
* Press any key to terminate the current application. * Press CTRL+ALT+DEL to restart your computer. You will lose any unsaved information in all applications.
Press any key to continue NOTE: The VXD in question is a File System Driver (FSD) from the list in the “More Information” section of this article.
If you do not restart your computer at this point, subsequent blue screen error messages occur and the computer does not shut down properly. It may be necessary to interrupt power to the computer to reset it successfully.
Alternatively, if your computer has a large amount of memory (for example, 192 MB), the mouse pointer may be displayed as an hourglass over the taskbar and you may be unable to run additional programs. The computer eventually becomes unresponsive to mouse and keyboard input.
Resolution
MS-DOS device names are reserved words and cannot be used as folder or file names. When parsing a reference to a file or folder, Windows correctly checks for the case in which a single MS-DOS device name is used in the path, and treats it as invalid. However, Windows does not check for the case in which the path includes multiple MS-DOS device names. When Windows attempts to interpret the device name as a file resource, it performs an illegal resource access operation that usually results in the computer becoming unresponsive.
Because you cannot create files or folders that contain MS-DOS device names, it is unusual for a user to try to gain access to one under normal circumstances. The chief threat posed by this vulnerability is that a malicious user can entice a user to attempt such an access. For example, if a Web site operator hosts a hyperlink that references such a path, when the user clicks the link, the computer may hang. Likewise, a Web page or HTML e-mail message that specifies a local file as the source of rendering information can cause the user’s computer to hang when it is displayed. If this happens, you can put the computer back into normal service by restarting it.

Symptoms
When you attempt to shut down or restart your computer, you may receive the following error message:

A Fatal Exception 0E has occurred at 0028:C00082CD in VxD VMM(01) +000072CD
Resolution
This issue can occur if you have an incompatible or early version of a Matrox video driver installed on your computer.