ProfileTool doesn't work on half the machines I try it on. I get an error like:<\/p>\n
Profiletool.exe Common Language Runtime Debugging Services Click OK to terminate the application. There's no point searching Google for the process ID and thread number; they're unique to your instance.<\/p>\n What can you do here? You get an error suggesting that 'debugging failed' if you hit Cancel - this is correct, because you don't have a debugger installed!<\/p>\n First step, if you're running your .NET application off the network, stop, move it to your local disk, and try again. The default security policy doesn't let you do this - you can edit it in the Administrative Tools if you need to.<\/p>\n Now, if you still get the error, drop to a command line, and run the following:<\/p>\n This redirects the standard error output<\/a> to error.log, which you can then read. Linux\/UNIX outputs this to the terminal by default; Windows hides it.<\/p>\n Thanks to Frank Racis<\/a>, by way of Mohamed Yehia<\/a>.<\/p>\n
\nApplication has generated an exception that could not be handled.
\nProcess ID=0x14 (1300), Thread Id=0xe8(232)<\/font><\/p>\n
\nClick CANCEL to debug the application.<\/font><\/p>\n\r\nProfileTool 2>error.log<\/pre>\n