.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 Tagged ‘error event’

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.

Event ID 5000 occurs when the Exchange IMAP4 worker process crashes intermittently in Exchange Server 2007

Symptoms
The Exchange IMAP4 worker process crashes intermittently on a computer that is running Microsoft Exchange Server 2007. When this problem occurs, an event is logged that resembles the following:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Description: EventType clr20r3, P1 microsoft.exchange.imap4.exe, P2 8.1.278.2, P3 481f7feb, P4 microsoft.exchange.imap4, P5 8.0.0.0, P6 481f7feb, P7 a6, P8 17, P9 system.nullreferenceexception, P10 NIL.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Resolution
To resolve this problem, install Update Rollup 4 for Exchange Server 2007 Service Pack 1 (SP1) on the Exchange server.For more information about Update Rollup 4 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=152556)For more information about how to obtain the latest Exchange service pack or update rollup, see the following Exchange Help topic:
How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007(http://go.microsoft.com/fwlink/?LinkId=152570)

Event 9673 with code 0xc00000fd occurs when the Microsoft Exchange Information Store service crashes on a computer that is running Exchange Server 2007

Symptoms
The Microsoft Exchange Information Store service crashes intermittently with a stack overflow on a computer that is running Exchange Server 2007. This behavior prevents users from accessing their mailboxes.

This behavior may occur approximately every five minutes on a computer that is running Exchange Server 2007
Additionally, event 9673 with code 0xc00000fd is logged in the Application log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9673
Description:
An exception with code 0xc00000fd was thrown in module; some parameters and their values were <Exception address>. A significant section of the call stack is in the data section.For more information, see Help and Support Center at <http://go.microsoft.com/fwlink/events.asp>.Data:00000: 00 00 00 00 00 00 00 00 ……..00008: 00 00 00 00 00 00 00 00 ……..00010: 00 00 00 00 00 00 00 00 ……..00018: 03 00 00 00 00 00 00 00 ……..00020: 04 00 00 00 00 00 00 00 ……..00028: 00 00 00 00 00 00 00 00 ……..00030: 00 00 00 00 00 00 00 00 ……..00038: 00 00 00 00 00 00 00 00 ……..00040: 00 00 00 00 00 00 00 00 ……..00048: 01 00 00 00 00 00 00 00 ……..00050: 72 81 21 54 00 00 00 00 r?!T….00058: 90 40 a3 39 00 00 00 00 ?@£9….00060: 00 00 00 00 00 00 00 00 ……..00068: 00 00 00 00 00 00 00 00 ……..
Resolution
Typically, this problem may be resolved after you install Update Rollup 7 for Exchange Server 2007 SP1. If you have not already installed Update Rollup 7, install the update from the link in the “Install Update Rollup 7″ section. However, in some cases this issue may continue to occur after installation of Update Rollup 7.If this situation occurs, you can resolve the problem by configuring two registry entries that are available after you install Update Rollup 7.To configure these registry entries follow the steps in the “More information about Update Rollup 7” section.
Install Update Rollup 7 To enable the two registry entries that help resolve this problem, install Update Rollup 7 for Exchange 2007 Service Pack 1. For more information about Update Rollup 7 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 7 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=157083)For more information about how to install the latest Exchange service pack or update rollup, see the following Exchange Help topic:
How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007(http://go.microsoft.com/fwlink/?LinkId=152570)
More information about Update Rollup 7By default, after you install Update Rollup 7 for Exchange Server 2007 SP1, the recurrence search for deep folder search is changed from “unlimited” to a limited value of 50,000. In some circumstances, this value may be too high, and you may still experience a Microsoft Exchange Information Store service crash. However, Update Rollup 7 enables you to use two registry entries to manually change the recurrence search parameters. To do this, follow these steps:Start Registry Editor.Locate and then click the following registry subkey:
HKLM\System\CCS\Services\MSExchangeIS\ParametersSystemCreate or change the value for the following registry entry under the registry subkey, as follows:
Name: Validate Search Folder Restriction
Data type: REG_DWORD
Value data: 1After you change the value for the registry entry, verify that the issue is fixed. If you continue to experience the issue, continue with the remaining steps.In Registry Editor, locate and then click the registry subkey that is mentioned in step 2.Create or change the value for the following registry entry under the registry subkey, as follows:
Name: Search Folder Nesting Level
Data type: REG_DWORD
Value data: 500 (decimal)If you continue to experience the same issue even after the change to the Search Folder Nesting Level registry entry, complete the steps in the “UseIsinteg tool” section.
Notes For the registry changes to take effect, you do not have to do the following:Restart the Microsoft Exchange Information Store service.Restart the Exchange server.Fail over the Exchange server in a clustered environment.Use Isinteg toolIf the Microsoft Exchange Information Store service continues to crash even after the change of values for the two registry entries, you must use the Isinteg tool. To do this, follow these steps.
Note You can run the Isinteg tool from the Drive_Letter:\Program Files\Exchsrvr\bin folder.Identify and unmount the Exchange database that has the problem.Run the Isinteg tool against the database by using the following command:
exchsrvr\bin\isinteg -s Server_Name -fix -test alltestsAfter Isinteg finishes running, view the ISINTEG.pri log file that is created in the MDBDATA folder.Verify that the entry for FIXES is equal to zero. If this entry is not equal to zero, run the Isinteg tool against the database again. You may have to run the Isinteg tool several times until you see that the FIXES entry is equal to zero.

An exception error is generated after you run a Set-AttachmentfilterListConfig command together with the ExceptionConnectors option on an Exchange 2007 SP1-based server

Symptoms
When you run the Set-AttachmentfilterListConfig command together with the -ExceptionConnectors option on an Exchange Server 2007-based server, the command doesnot run successfully. Additionally, an exception is generated.
For example, you may run the following command:
Set-AttachmentfilterListConfig -ExceptionConnectors d18f518a-38e3-4349-9697-bc2ac318461f When you run this command, you receive the following error message:

WARNING: An unexpected error has occurred and debug information is being generated: Unable to cast object of type ‘System.Collections.Generic.List`1[Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector]‘ to type ‘Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector[]‘. Set-AttachmentfilterListConfig : Unable to cast object of type ‘System.Collections.Generic.List`1[Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector]‘ to type ‘Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector[]‘. At line:1 char:31 + Set-AttachmentfilterListConfig? <<<< -ExceptionConnectors d18f518a-38e3-4349-9697-bc2ac318461f Additionally, the follow event is logged in the Application log:
Event Type:?Error
Event Source:?MSExchange Common
Event Category:?General
Event ID:?4999
User:??N/A
Computer:?Servername
Description: Watson report about to be sent to dw20.exe for process id: <ID>, with parameters: E12, c-RTL-x86, <version>, powershell, M.E.Management, M.E.M.M.A.SetAttachmentFilterListConfig.InternalProcessRecord, System.InvalidCastException, 4e90, <version>.? ErrorReportingEnabled: False For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Resolution
To resolve this problem, install Update Rollup 2 for Exchange Server 2007 Service Pack 1. For more information about Update Rollup 2 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 2 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=152558)For more information about how to install the latest Exchange service pack or update rollup, see the following Exchange Help topic:
How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007(http://go.microsoft.com/fwlink/?LinkId=152570)