.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries for June, 2010

Exception in DbgBreakPoint with TN5250 Service

Symptoms
An application exception (trap) may occur on the SNA Server computer when you use the Rumba 5.2 TN5250 client to connect to the TN5250 Service. If you have Dr. Watson (Drwtsn32.exe) configured as the default debugger, a Drwtsn32.log file is created in the [NTROOT] directory. The following events are created in the Application event log of the Event Viewer:

Event ID: 5
Source : SNA TN5250 ServerDescription:
The SNA TN5250 Service detected an internal error.
File = ..\shared\tn5tnspm.c
Line = 3477
Fail = ((NB_IPS *)dsi5_data)->buf_size >= ((NB_IPS *)dsi5_data)->ips_length
Parm = 0×0
Event ID: 4097
Source: DrWatson
The application, exe\tn5250.dbg, generated an application error The error occurred on1/25/2000 @ 20:58: 3.406.
The exception generated was 80000003 at address 77f76274 (DbgBreakPoint).The following is an example of the exception in DbgBreakPoint:

Application exception occurred:App: exe\tn5250.dbg (pid=326)When: 1/25/2000 @ 20:58:3.406Exception number: 80000003 (hardcoded breakpoint)function: DbgBreakPointFAULT ->77f76274 ccint377f76275 c3ret77f76276 8bc0moveax,eax
Resolution
To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
215838?(http://support.microsoft.com/kb/215838/EN-US/) How to Obtain the Latest SNA Server Version 4.0 Service Pack

Exception Error in Nwconv.exe During Migration

Symptoms
When you attempt to migrate user accounts and data from Novell NetWare3.1x servers to Windows NT 3.5, 3.51, or 4.0 servers using the MigrationTool for Netware (Nwconv.exe), the Migration Tool for NetWare may stopresponding with an exception error 0xc0000005 in Nwconv.exe and generatea Drwtsn32.log file.
Resolution
During migration, the Migration Tool for NetWare builds a PrinterOperators member list. It enumerates all the print servers on the NetWareserver and then builds the user list of who is in the Printer Operatorgroup associated with the respective print server. The Migration Tool forNetWare sets a buffer size to hold a print server name less than or equalto 20 characters, including the null character. NetWare allows less thanor equal to 47 characters for the print server name. Unexpected resultsmay occur when you read a string into the buffer of a smaller size. Inthis case, the result is an exception error in Nwconv.exe.

Exception configured in Outlook rule does not prevent move of received message to folder

Symptoms
After you create a rule in Microsoft Outlook to move received e-mail messages to afolder, if the rule contains an exception that prevents the message from moving to thefolder if the message is from a specified user, the message is still transferred to the specified folder.
Resolution
This problem occurs because the user that you specified as an exception is contained in the Global Address List (GAL).

Exception 0E in Vredir.vxd during CoCreateInstanceEx() on remote DCOM server

Symptoms
If your network is set up as a workgroup, you have a drive mapped to a Microsoft Windows NT-based server, and you run a Distributed Component Object Model (DCOM) program that attempts to start a remote server component on the Windows NT-based server, you may receive one of the following error messages on a blue screen.
Windows 95, Windows 98, Windows 98 Second Edition:

Windows
A fatal exception 0E has occurred at 0028:???????? in VXD VREDIR(??)+ ????????. The current application will be terminated.
* Press any key to terminate the current application.
* Press CTRL+ALT+DEL again to restart your computer. You will lose any unsaved information on all applications.
Press any key to continue.Windows Millennium Edition (Me):

Windows
An error has occurred. To continue:
Press Enter to return to Windows, or Press CTRL+ALT+DEL to restart your computer. If you do this, you will lose any unsaved information in all open applications.
File Name: VREDIR(06) + 00006C54 Error: 0E : 0028 : C02D2770
Press any key to continue.If you press ENTER, CoCreateInstanceEx returns RPC_S_CALL_FAILED (0×800706BE). The program may display the following error message:

The remote procedure call failed.See the “More Information” section of this article for the error message values for various versions of the Vredir.vxd file.
Resolution
The redirector (Vredir.vxd) incorrectly references internal resource data for the mapped drive connection while setting up the connection that the DCOM Remote Procedure Call (RPC) traffic will use.

Event IDs 106 and 107 may be logged in the System log on a Windows Server 2003-based computer

Symptoms
When you use Event Viewer to view the System log on a Microsoft Windows Server 2003-based computer, you may see event messages that are similar to the following:
Event ID: 107
Source:WMIxWDM
Description: Machine check event reported is a fatal error.
Event ID: 106
Source: WMIxWDM
Description:Machine check event reported is a corrected error.
MessageId=0×0078 Facility=Mca Severity=Error
SymbolicName=MCA_MEMORYHIERARCHY_ERROR
Language=English
Machine Check Event reported is a fatal memory hierarchy error.%r
Trasaction Type: %1%r
Memory Hierarchy Level: %2%r
Request Type: %3%r
Address: %4
MessageId=0×0079 Facility=Mca Severity=Error
SymbolicName=MCA_TLB_ERROR
Language=English
Machine Check Event reported is a fatal TLB error.%r
Transaction Type: %1%r
Memory Hierarchy Level: %2%r
Address: %3
MessageId=0×007a Facility=Mca Severity=Error
SymbolicName=MCA_BUS_ERROR
Language=English
Machine Check Event reported is a fatal Bus or Interconnect error.%r
Memory Hierarchy Level: %1%r
Participation: %2%r
Request Type: %3%r
Memory/IO: %4%r
Address: %5
MessageId=0×007b Facility=Mca Severity=Error
SymbolicName=MCA_BUS_TIMEOUT_ERROR
Language=English
Machine Check Event reported is a fatal Bus or Interconnect timeout error.%r
Memory Hierarchy Level: %1%r
Participation: %2%r
Request Type: %3%r
Memory/IO: %4%r
Address: %5
MessageId=0×007c Facility=Mca Severity=Error
SymbolicName=MCA_INTERNALTIMER_ERROR
Language=English
Machine Check Event reported is a fatal internal watchdog timer error.
MessageId=0×007e Facility=Mca Severity=Error
SymbolicName=MCA_MICROCODE_ROM_PARITY_ERROR
Language=English
Machine Check Event reported is a fatal microsoft ROM parity error.
MessageId=0×007f Facility=Mca Severity=Error
SymbolicName=MCA_EXTERNAL_ERROR
Language=English
Machine Check Event reported is a fatal condition. A processor received an external signal that an unrecoverable error has occurred.
MessageId=0×0080 Facility=Mca Severity=Error
SymbolicName=MCA_FRC_ERROR
Language=English
Machine Check Event reported is a fatal functional redundancy check error.
Resolution
These event messages may be logged in the System log in response to a Machine Check Architecture exception. A Machine Check Architecture exception is sent by the CPU in the computer in response to a computer error. The computer error may cause the computer to restart. After the computer has restarted, the CPU reports the Machine Check Architecture exception to the hardware abstraction layer (HAL). The HAL uses Windows Management Instrumentation (WMI) to report the Machine Check Architecture exception to the operating system.The operating system then logs the Machine Check Architecture exception in the System log as an event ID.

Event ID 9014 and Event ID 9015 are logged, and MOMservice.exe stops unexpectedly after you configure a Collect Specific Events (Collection) rule in Microsoft Operations Manager 2005

Symptoms
After you configure a Collect Specific Events (Collection) rule in Microsoft Operations Manager (MOM) 2005, the following symptoms occur:The MOM service (MOMservice.exe) stops unexpectedly. If you try to start the MOM service, you receive the following error message:

Could not start the MOM service on Local Computer.Error 1067:The process terminated unexpectedly. The following events are logged in the Application log:
Event Type:Error
Event Source:Microsoft Operations Manager
Event Category: None
Event ID:9014
Date:date
Time:time
User:N/A
Computer: ComputerName
Description: The Microsoft Operations Manager service (MOMService.exe) terminated due to an unhandled exception.Itwill attempt to restart itself.
For more information, see Help and Support Center at<http://go.microsoft.com/fwlink/events.asp>.
Event Type:Error
Event Source:Microsoft Operations Manager
Event Category: None
Event ID:9015
Date:date
Time:time
User:N/A
Computer: ComputerName
Description: The Microsoft Operations Manager service (MOMService.exe) received an unexpected exception.
Thread Id: 0xf40
Thread Name: MSB3904
Exception code: 0×00000000c0000005
Exception description: Access Violation
Exception address: 025EB79C
Exception flags: 0×0
For more information, see Help and Support Center at<http://go.microsoft.com/fwlink/events.asp>.
Resolution
This problem may occur if the Collect Specific Events (Collection) rule is configured to collect security event parameters. In this scenario, the Collect Specific Events (Collection) rule may occasionally collect more parameters than requested. This behavior may cause the MOM service to stop.