Hi Jonathan,
Thread ID: 11
System Thread ID: c70
Kernel Time: 0:0:4.953
User Time: 0:1:28.250
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for -
Other information: Thread is waiting for a lock to be released.
Looking for lock owner.
Owning thread System ID: ccc
Thread Type: Other
# ChildEBP RetAddr
00 018cf538 77f23741 SharedUserData!SystemCallStub+0x4
01 018cf53c 77f3d64e ntdll!ZwWaitForSingleObject+0xc
02 018cf578 77f22044 ntdll!RtlpWaitForCriticalSection+0x126
03 018cf580 7ad603a9 ntdll!RtlEnterCriticalSection+0x46
WARNING: Stack unwind information not available. Following frames may
be wrong.
04 018cf590 7ad6b384 msolap80!Ordinal98+0x203a9
05 018cf5c8 084a1344 msolap80!PrivateConnectionDialogSetDB+0x4867
06 51e30a5c 0844cb2c 0x84a1344
07 00000000 00000000 0x844cb2c
...
Thread ID: 17
System Thread ID: ccc
Kernel Time: 0:0:0.15
User Time: 1:15:34.359
Thread Type: Other
# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may
be wrong.
00 7afdfe5c 7ae26dd4 msolap80!DllRegisterServer+0xb7bcc
01 7afdfe6c 7ae26aed msolap80!DllRegisterServer+0xb77bc
02 7afdfe84 7adacc13 msolap80!DllRegisterServer+0xb74d5
03 7afdfea4 7adaccb3 msolap80!DllRegisterServer+0x3d5fb
04 7afdfec8 7ad69ed5 msolap80!DllRegisterServer+0x3d69b
05 7afdfef8 7ad7dd78 msolap80!PrivateConnectionDialogSetDB+0x33b8
06 7afdff20 7ad7dc7b msolap80!DllRegisterServer+0xe760
07 7afdff7c 7ad7dba9 msolap80!DllRegisterServer+0xe663
08 7afdff84 77b690a2 msolap80!DllRegisterServer+0xe591
09 7afdffb8 77dea990 msvcrt!_endthread+0xa6
0a 7afdffec 00000000 kernel32!BaseThreadStart+0x34
The dealock of msolap80.dll is obvious, there are a batch of threads
waiting for it to release the lock. However, the DllRegisterServer
function call in the log is masked and useless. This is because
Symbols doesn't match and so iisstate use the exposed function name
DllRegisterServer and an offset to represent the actual function
call. Therefore from the log we cannot determine what the thread was
doing at that time.
I saw an exactly similar SQL2K/OLAP/ASP case with this kind of call
stack is currently opened in PSS. I recommend you also report an
incident to PSS for debugging. A SQL engineer who has the internal
Symbols of msolap80.dll can help you find out the root cause. Also,
if the issue is finally confirmed being caused by a bug, the case
charge will be refunded or waived. You can find your local PSS phone
number from the following link:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
Best regards,
WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! -
www.microsoft.com/security