Finally after a long beta phase the final version of DebugDiag 1.2 has been released.
The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any user-mode process. The tool includes additional debugging scripts focused on Internet Information Services (IIS) applications, SharePoint, web data access components, COM+ and related Microsoft technologies.
I'm especially proud as the SharePoint analysis script is based on a debugger extension (SharePointExt.dll) I have developed in the last couple of years and which is included in this version of DebugDiag as well.
Here are some highlights of the new version:
DebugDiag 1.2 does not allow side-by-side installation with DebugDiag 1.1. You have to uninstall DebugDiag 1.1 before installing version 1.2
Looks like you forgot to mention the link
thanks for the hint!
You were right. I added the link.
Hi, i get an error during installation.
I'm using portuguese (PT-BR) OS Version, the error was:
"Users is not a valid user group."
In my case there is a (local) group called "Usuários".
I think it is just a language issue.
If you would like get more details, mail me at:
sanguedemonstro gmail com
the issue you raised has been confirmed.
Currently you can use the following workaround:
- Install on an English OS to get the binaries
- Copy all the binaries to \Debugdiag on the non english machine
- Run register.bat
An additional hint: you would also have to perform the following actions which are not don by register.bat:
- add Read and Execute permissions for “Users” on the installation directory of DebugDiag
- add Full Control permissions for “Administrator” on the installation directory of DebugDiag
Don't you know, when this issue with "Users is not a valid user group" will be fixed?
I want to recomend to install 1.2 version in production environment but support team woun't be glad to see this error.
I think, I have the same situation as sanguedemonstro.
I've failed to install DebugDiag 1.2 x64 on russian Win7 x64.
On stage Creating Folders I have a dialog box "An error occured while applying security settings. User is not a valid user or group. This could be a problem with the package, or a problem connecting to a domain controller on the network. Check your network settings and click Retry, or Cancel to end the installation."
My Local\Users group name is "Пользоваители".
I've found a little workaround:
1) Create local group named "Users"
2) Add yourself to this group
3) Grand full access to this group to DebugDiag installation folder
4) Install DebugDiag
5) Run Register.bat from the installation folder
That's it, now I have 1.2 on non english machine.
sorry I don't have a timeframe.
Nice workaround btw.
Same install issue happens on a Spanish OS, the lack of a group called "Users" causes the install to halt. Many thanks to Stefan for a workaround!
I can confirm the problem described above for the German version of Win7 x64, and the solution helped to solve this problem - but in one of the next steps (status message "Removing backup files") I got an error saying somthing like an other program required for the install...
To workaround this I...
1) accessed the install directory (as administrator) while the installation was running and the error was shown,
2) copied the files to another directory,
3) completed the registration (failed - files deleted),
4) copied the files back to the installation directory,
5) and run the installation once again.
On X64 French W2008 servers, got successively both installation issues reported above by sanguedemonstro and Ziegenberg.
Thanks to previous contributors, the "local group" workaround then the "save-backup files and reinstall" workaround both described above were both hits.
The workaround posted by Dronkoff 08-08-2011 12:31 PM works fine for a German environment.
Thx a lot.
I confirm that workaround posted by Dronkoff Mon, Aug 8 2011 11:31 AM works also on a french W2K3 IIS 6 system. большое спасибо !
Don't put the blame on Microsoft US developers to ignore foreign OSes, Oracle 11g database suffers from the same kind of problems... :-)
Dronkoff, thx for your solution!