.NET Questions and Solutions

Symptoms
Consider the following scenario:
You install the Terminal Services role on a computer that is running Windows Server 2008.You connect to this terminal server, and then you perform some window-related operations in a terminal server session.
For example, you open and then close some windows in the terminal server session.In this scenario, the computer may restart unexpectedly. Additionally, you receive a Stop error message that resembles the following:

STOP 0×0000003B (parameter1, parameter2, parameter3, parameter4)
SYSTEM_SERVICE_EXCEPTION
Notes
The parameters in this Stop error message may vary, depending on the configuration of the computer.Not all the “Stop 0×0000003B” Stop errors are caused by this issue.

Resolution
This issue occurs because the Rdpwd.sys driver does not check whether a returned list is NULL or not.
When the returned list is NULL, the Rdpwd.sys driver accesses the wrong memory location. Therefore, an access violation exception occurs.

Symptoms
The SQL Server may encounter an access violation exception during normalization. The following or similar stack track is generated in the SQL Server error log indicating you have encountered the failure condition:

CGroupProperties::FTableGroup() line 52 + 18 bytesCOpArg::DeriveNormalizedGroupProperties(CTreeHandle * 0×26d1ac28) line 1250 + 8 bytesCOptExpr::DeriveGroupProperties(unsigned long 0) line 2714 + 25 bytesCImpRuleBaseJoinToIdxLookup::BuildSubstitutes(COptExpr * 0×1c933b2c, CRuleContext * 0×26d1b590, CRuleReturn * 0×26d1b5fc) line 1428CTask_ApplyRule::Perform(int 5799) line 1692 + 46 bytesCMemo::ExecuteTasks(COptTask * 0×1c90b3ac, int 0, int 0) line 3453 + 20 bytesCMemo::OptimizeQuery(CQuery * 0×1c6da8bc, COptExpr * 0×1c8ca63c, double * 0×1c6d430c, int 0, int 0, s_OptimPlans * 0×26d1baf4) line 3779COptContext::PexprSearchPlan(COptExpr * 0×1c8ca63c) line 1809 + 227 bytesCOptContext::PcxteOptimizeQuery(COptExpr * 0×1c8ca63c, DRgCId * 0×26d1df24) line 1337 + 15 bytesCQuery::Optimize() line 576 + 16 bytesCQuery::Optimize(unsigned long 1) line 1101CCvtTree::PqryFromTree(TREE * 0×1c740c9c, IMemObj * 0×1c6da030, CRangeCollection * 0×1c6da85c, unsigned long 0, CCompPlan * 0×1c6da2bc {CCompPlan}) line 1056 + 25 bytesBuildQueryFromTree(TREE * 0×1c740c9c, IMemObj * 0×1c6da030, IMemObj * 0×1c6e0020, IQueryObj * * 0×1c6da800, CRangeCollection * 0×1c6da85c, unsigned long 0, CCompPlan * 0×1c6da2bc {CCompPlan}) line 521 + 31 bytes
Resolution
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:

File namePlatform———————-s80222i.exeIntel NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

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.

Symptoms
An illegal instruction (C00000FD) exception or an access violation (C0000005) exception occurs in the Intersite Messaging service (ismserv.exe). The exception causes ismserv.exe to crash.
Resolution
This problem occurs if a function in the Adsiis.dll component leaves a released cache item in the server cache when a remote procedure call (RPC) error occurs. When a subsequent client request tries to use the released cache item, the illegal instruction exception or the access violation exception occurs.

Symptoms
The Microsoft Operations Manager (MOM) OnePointService stop working because there is an access violation in the Performance Manager (PerfMgr) thread on MOM agents. The service attempts to restart but it may or may not succeed. The following two events are typically logged in the Application event log if you experience this problem:

Event ID: 9015Event Type: ErrorEvent Source: OnePoint OperationsDescription:The Microsoft Operations Manager 2000 service (OnePointService.exe) received an unexpected exception. Thread Name: PerfMgr Exception code: 0xc0000005 Exception description: Access Violation Exception address: 77DF7D88

Event ID: 9014Event Type: ErrorEvent Source: OnePoint OperationsUser:NT AUTHORITY\SYSTEMDescription:The Microsoft Operations Manager 2000 service (OnePointService.exe) terminated due to an unhandled exception.It will attempt to restart itself.If the “Thread Name”, “Exception code”, and the “Exception address” match these errors, you are most likely affected by this issue. Also, the OnePointService log file may log entries that are similar to the following entries:

“12015“`0`3044`39`1`PerfMgr`PerformanceManager::execute`236775672`29425836“Event logging is disabled (this is normal for GUIs).Suppressed logging of event 9015(Error) args = “0xbe4″ “0×00000000c0000005″ “Access Violation” “77DF7D88″ “0×0″ “PerfMgr” “12016“`0`3044`39`1`PerfMgr`PerformanceManager::execute`236775672`29425836“Event logging is disabled (this is normal for GUIs).Suppressed logging of event 9014(Error) args = “12017“`0`3044`39`0`PerfMgr`PerformanceManager::execute`236931925`29425836“}PerformanceManager::execute: exiting.“12018“`0`3044`39`0`PerfMgr“239275720`29425836“VERIFY FAILURE:T:\Dev\EEM\V3\Ship\Providers\PerfProvider\PerformanceManager.cpp(51): Destroying mutex locked at this location!After you receive these errors, the OnePointService service may appear to be running when it stops responding (hangs). To recover from this, you must restart the computer.
Resolution
This problem occurs because there is a timeout issue when the PerfMgr thread requests performance data from the computer.