Debug Diagnostic Tool - All Comments

re: Welcome back to the Debug Diagnostics Blog.

Daniel — Fri, 23 Nov 2012 06:38:56 GMT

So, I decided to uninstall the Debug Diagnostics Tool (doing maintenance), and during uninstall (from control panel) I was presented with an error

"Failed to create 32 bit dbghost error 0x80040154"

I looked into the error, not being able to find the root of the problem - I'm guessing that a service is still trying to call the dbghost. What I found was the register.bat and unregister.bat seems to be very different (this being a 64-bit server)

The register.bat performs the following commands:

dbgsvc /service

dbghost /regserver

regsvr32 /s exts\ComplusDDExt.dll

regsvr32 /s exts\ CrashHangExt.dll

regsvr32 /s exts\IISInfo.dll

regsvr32 /s exts\MemoryExt.dll

regsvr32 /s exts\SharePointExt.dll

x86support\dbghost /regserver

regsvr32 /s x86support\exts\ComplusDDExt.dll

regsvr32 /s x86support\exts\CrashHangExt.dll

regsvr32 /s x86support\exts\IISInfo.dll

regsvr32 /s x86support\exts\MemoryExt.dll

regsvr32 /s x86support\exts\SharePointExt.dll

While the unregister.bat performs these commands:

net stop dbgsvc

dbgsvc /unregserver

dbghost /unregserver

regsvr32 /s /u exts\ComplusDDExt.dll

regsvr32 /s /u exts\CrashHangExt.dll

regsvr32 /s /u exts\IISInfo.dll

regsvr32 /s /u exts\MemoryExt.dll

regsvr32 /s /u exts\SharePointExt.dll

Now I can't be the only one that noticed some commands missing here?

Should the unregister.bat not unregister every instance of the x86support services and dll's?

Like this:

net stop dbgsvc

dbgsvc /unregserver

dbghost /unregserver

regsvr32 /s /u exts\ComplusDDExt.dll

regsvr32 /s /u exts\CrashHangExt.dll

regsvr32 /s /u exts\IISInfo.dll

regsvr32 /s /u exts\MemoryExt.dll

regsvr32 /s /u exts\SharePointExt.dll

x86support\dbghost /unregserver

regsvr32 /s /u x86support\exts\ComplusDDExt.dll

regsvr32 /s /u x86support\exts\CrashHangExt.dll

regsvr32 /s /u x86support\exts\IISInfo.dll

regsvr32 /s /u x86support\exts\MemoryExt.dll

regsvr32 /s /u x86support\exts\SharePointExt.dll

Anyways, I tried running my own script before uninstalling - but I still end up getting the error message.

Please advise, asap, on how to uninstall properly. These kind of deployment errors are so f-ing annoying!

re: Welcome back to the Debug Diagnostics Blog.

Moshe — Tue, 28 Aug 2012 12:52:01 GMT

I am using this grate tool for years. waiting for new version and options.

re: DebugDiag v1.1 Available!

Mick — Fri, 08 Jun 2012 12:00:17 GMT

Link is dead try this Debug Diagnostic Tool v1.2

www.microsoft.com/.../details.aspx

Memory increasing even when in debug-break | keyongtech

Memory increasing even when in debug-break | keyongtech — Thu, 22 Jan 2009 11:15:06 GMT

PingBack from http://www.keyongtech.com/2391074-memory-increasing-even-when-in

re: DebugDiag v1.1 Available!

jformacek — Thu, 26 Jul 2007 16:58:02 GMT

Hello,

I got into situation, where I needed to dump worker process reported unhealthy, as described in KB article

http://support.microsoft.com/default.aspx/kb/828222/en-us

I had debugdiag already installed on web server and I didn't want to install another debugger on production machine, so I was finding a way how to use debugdiag to dump such a process.

Didn't find a lot in the documentation, so after looking into debugdiag TLBs for a while, I created the following vbscript, that should do the job:

'-------------

Dim pid

Dim controller

Dim process

If Not wscript.arguments.named.exists("PID") Then

wscript.quit

End If

pid=CInt(wscript.arguments.named("PID"))

Set controller=CreateObject("dbgsvc.controller")

For Each process In controller.processes

If process.ProcessID=pid Then

dumpname=process.createdump("Deadlock_Dump","I:\DebugDiag")

process.terminateprocess

Exit For

End If

Set controller=Nothing

'--------------------

Script is supposed to be a batch file to be executed when process orphans.

Seems to be working on my test machine, now I'm going to use it on server I'm troubleshooting.

Is this type of use of debugdiag supported?

Will the debugdiag documentation be enhanced to cover this type of use?

thanks,

Jiri