Hello everyone,
When using !threads command to monitor thread status (for a dump), there is an error message. Does anyone meet this before? What is wrong?
0:001> !threads
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
??? 2) the file mscordacwks.dll that matches your version of mscorwks.dll is
??? in the version directory
??? 3) or, if you are debugging a dump file, verify that the file
??? mscordacwks_.dll is on your symbol path.
??? 4) you are debugging on the same architecture as the dump file.
??? For example, an IA64 dump file must be debugged on an IA64
??? machine.
You can also run the debugger command .cordll to control the debugger’s
load of mscordacwks.dll.? .cordll -ve -u -l will do a verbose reload.
If that succeeds, the SOS command should work on retry.
If you are debugging a minidump, you need to make sure that your executable
path is pointing to mscorwks.dll as well.
thanks in advance,
George
Is this a full dump?
–
Steve Johnson
On Tue, Jul 15, 2008 at 2:54 AM, Lin George
wrote:
> Hello everyone,
> When using !threads command to monitor thread status (for a dump), there is
> an error message. Does anyone meet this before? What is wrong?
> 0:001> !threads
> Failed to load data access DLL, 0x80004005
> Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
> 2) the file mscordacwks.dll that matches your version of
> mscorwks.dll is
> in the version directory
> 3) or, if you are debugging a dump file, verify that the file
> mscordacwks_.dll is on your symbol
> path.
> 4) you are debugging on the same architecture as the dump file.
> For example, an IA64 dump file must be debugged on an IA64
> machine.
> You can also run the debugger command .cordll to control the debugger’s
> load of mscordacwks.dll. .cordll -ve -u -l will do a verbose reload.
> If that succeeds, the SOS command should work on retry.
> If you are debugging a minidump, you need to make sure that your executable
> path is pointing to mscorwks.dll as well.
> thanks in advance,
> George
>
Thanks Steve!
Yes, it is a full dump. You are so cool and could find some information which is not mentioned in my email! 
Any ideas to my question?
regards,
George
----- Original Message ----
From: Steve Johnson
To: Kernel Debugging Interest List
Sent: Thursday, July 17, 2008 6:18:55 PM
Subject: Re: [windbg] error monitoring thread status
Is this a full dump?
–
Steve Johnson
On Tue, Jul 15, 2008 at 2:54 AM, Lin George wrote:
Hello everyone,
When using !threads command to monitor thread status (for a dump), there is an error message. Does anyone meet this before? What is wrong?
0:001> !threads
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
??? 2) the file mscordacwks.dll that matches your version of mscorwks.dll is
??? in the version directory
??? 3) or, if you are debugging a dump file, verify that the file
??? mscordacwks_.dll is on your symbol path.
??? 4) you are debugging on the same architecture as the dump file.
??? For example, an IA64 dump file must be debugged on an IA64
??? machine.
You can also run the debugger command .cordll to control the debugger’s
load of mscordacwks.dll.? .cordll -ve -u -l will do a verbose reload.
If that succeeds, the SOS command should work on retry.
If you are debugging a minidump, you need to make sure that your executable
path is pointing to mscorwks.dll as well.
thanks in advance,
George
— You are currently subscribed to windbg as: xxxxx@yahoo.com To unsubscribe send a blank email to xxxxx@lists.osr.com