.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 ‘unexpected exception’

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.

Error message when you use a map to transform messages in a BizTalk Server orchestration: “Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service”

Symptoms
Consider the following scenario:You create a map in a Microsoft BizTalk Server project. The map uses an XSL for Transformations (XSLT) file that is defined inthe Custom XSL Path Grid Properties. The map uses the XSLT fileto transformmessages. You use the map in an orchestration to process messages.In this scenario, messages may be suspended. Additionally, you may receive an error message that resembles the following in the Application log:

Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10030
Description:Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘BizTalk orchestration’.The service instance will remain suspended until administratively resumed or terminated. If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.InstanceId: instance id
Shape name: shape name
ShapeId: shape id
Exception thrown from: segment number, progress number
Inner exception: Error encountered while executing the transform project name.map name. Error:Unable to create the transform.The “Additional error information” section of the error message contains error information that resembles the following:

Resolving of external URIs was prohibited.
Resolution
This issue can occur if the XSLT file that is definedin the Custom XSL Path Grid Properties uses the<xsl:import> element or the <xsl:include> element to import or to include an external XSLT file.