Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. A Dllhost.exe process may stop responding when it is associated with a package that contains a COM Transaction Integrator component

A Dllhost.exe process may stop responding when it is associated with a package that contains a COM Transaction Integrator component

View products that this article applies to.

Symptoms

A Dllhost.exe process that is associated with a Microsoft COM+ application package that contains a Component Object Model (COM) Transaction Integrator (COMTI) component may stop responding. The problem occurs intermittently, but it may occur more frequently on systems that have fast or multiple processors.

An application dump file of the unresponsive Dllhost.exe process shows a thread that is blocking on a critical section and the owner of this critical section has been orphaned.

↑ Back to the top

Workaround

To work around this problem, rename Snasii.dll. Snasii.dll is used for the Single Sign-On (SSO) service.

If the COMTI Remote Environment is configured to use SSO, do not rename Snasii.dll.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

The following code is an excerpt from an AutoDump+ (ADPlus) dump file that was created after the Dllhost.exe process stopped responding because of the problem that is described in the "Symptoms" section.

This code is the stack trace of the thread that is waiting for a Microsoft Foundation Classes (MFC)-specific critical section to be released:
ChildEBP RetAddr Args to Child
00cafca8 77f85c55 0000002c 00000000 00000000 NTDLL!ZwWaitForSingleObject+0xb
00cafd1c 77f85bd1 6c440000 6c375f3e 6c440024 NTDLL!RtlpWaitForCriticalSection+0x9e
00cafd24 6c375f3e 6c440024 6c440000 000a08c0 NTDLL!RtlEnterCriticalSection+0x46
00cafd40 6c37107b 00000001 000a08c0 00000000 mfc42!CThreadSlotData::SetValue+0x60
00cafd54 6c371092 6c375e77 6c37110e 6c3729e2 mfc42!CThreadLocalObject::GetData+0x70
00cafd5c 6c37110e 6c3729e2 6c38028f 00000000 mfc42!AfxGetModuleState+0xf
00cafd60 6c3729e2 6c38028f 00000000 00000003 mfc42!AfxGetModuleThreadState+0x5
00cafd64 6c38028f 00000000 00000003 00000000 mfc42!AfxLockTempMaps+0x5
00cafd8c 6c376174 00000000 00000000 00000003 mfc42!AfxTermThread+0x1c
00cafeb8 6c375d6e 6c370000 00000003 00000000 mfc42!DllMain+0x173
00cafed8 77f85058 6c370000 00000003 00000000 mfc42!_DllMainCRTStartup+0x50
00cafef8 77f852cb 6c375d23 6c370000 00000003 NTDLL!LdrpCallInitRoutine+0x14
00caff4c 77e8887f 00000000 00000008 78866e40 NTDLL!LdrShutdownThread+0xa3
00caffb4 77e887e3 00000000 00000000 00000008 KERNEL32!ExitThread+0x53
00caffec 00000000 787f2190 78866e40 00000000 KERNEL32!BaseThreadStart+0x81

CritSec NTDLL!LoaderLock+0 at 77FCF348
LockCount 7
RecursionCount 1
OwningThread d88
EntryCount 49
ContentionCount 49
*** Locked

CritSec mfc42!__afxThreadData+1c at 6C440024
LockCount 1
RecursionCount 1
OwningThread ed0
EntryCount 1
ContentionCount 1
*** Locked

↑ Back to the top

Keywords: KB838003, kbbug, kbfix, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 838003
Revision : 4
Created on : 1/26/2009
Published on : 1/26/2009
Exists online : False
Views : 298