Debugging a .NET crash with rules in Debug Diag

re: Debugging a .NET crash with rules in Debug Diag

Walter — Fri, 20 Mar 2009 18:47:53 GMT

Hey Tess,

You have a deep understanding of IIS!

What are your thoughts on upgrading to 64 bit IIS servers?

Good idea? Bad idea?

Debugging a .NET crash with rules in Debug Diag

What's New — Fri, 20 Mar 2009 22:50:24 GMT

During mine and Micke’s presentation at TechDays this week I showed a demo of setting up rules with Debug

re: Debugging a .NET crash with rules in Debug Diag

Anthony Sciuto — Sat, 21 Mar 2009 02:17:14 GMT

Could you tell me how to debug this problem please

Anthony

ajracer01@gmail.com

Server Error in '/' Application.

--------------------------------------------------------------------------------

Authentication failed. Restarting authentication process.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: DotNetOpenMail.SmtpException: Authentication failed. Restarting authentication process.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SmtpException: Authentication failed. Restarting authentication process.

]

DotNetOpenMail.SmtpServer.Send(ISendableMessage emailMessage, EmailAddressCollection rcpttocollection, EmailAddress mailfrom) +812

DotNetOpenMail.EmailMessage.Send(SmtpServer smtpserver) +88

Radactive.Projects.Arbseek.Core.Utils.SendMail(String fromAddress, String fromName, String toAddress, String toName, String subject, String bodyText, String bodyHTML, String[] attachments) in C:\Documents and Settings\mfabbian\Documenti\Visual Studio Projects\Radactive.Projects.Arbseek\Core\Utils.cs:310

Radactive.Projects.Arbseek.WWW.Controls.Contact.sendContactMail(String firstName, String lastName, String email, String message) in C:\Documents and Settings\mfabbian\Documenti\Visual Studio 2005\Projects\MGS\ASPNET\Radactive\Projects\Arbseek\WWW\Controls\Contact.ascx.cs:69

Radactive.Projects.Arbseek.WWW.Controls.Contact.Page_Load(Object sender, EventArgs e) in C:\Documents and Settings\mfabbian\Documenti\Visual Studio 2005\Projects\MGS\ASPNET\Radactive\Projects\Arbseek\WWW\Controls\Contact.ascx.cs:82

System.Web.UI.Control.OnLoad(EventArgs e) +67

System.Web.UI.Control.LoadRecursive() +35

System.Web.UI.Control.LoadRecursive() +98

System.Web.UI.Page.ProcessRequestMain() +739

--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

Debugging a .NET crash with rules in Debug Diag - Tess Ferrandez

DotNetShoutout — Sat, 21 Mar 2009 08:35:01 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout

Interesting Finds: 2009 03.20~03.22

gOODiDEA.NET — Sun, 22 Mar 2009 06:06:29 GMT

Web Writing IE8 accelerator in 15 minutes (bookmark on Delicious) Constructing Web Interfaces on the

Interesting Finds: 2009 03.20~03.22

gOODiDEA — Sun, 22 Mar 2009 06:09:20 GMT

WebWritingIE8acceleratorin15minutes(bookmarkonDelicious)ConstructingWebInterface...

re: Debugging a .NET crash with rules in Debug Diag

dreamzgj — Mon, 23 Mar 2009 13:28:27 GMT

Thank you very much!

It's a powerfull tool!

re: Debugging a .NET crash with rules in Debug Diag

Tess — Mon, 23 Mar 2009 16:19:40 GMT

walter, i dont have a stron opinion on that. If you need the extra memory then go for it.

I woud say though that it shouldnt be used to cover up for a memory issue that you dont know the cause of, since runnng asp.net on 64 bit means a lot larger segments, and thus that you dont collect a often. IN other words you need to make sure that you have enough RAM to back your mem usage up if you run 64 bit.

re: Debugging a .NET crash with rules in Debug Diag

AaronS — Fri, 27 Mar 2009 02:35:10 GMT

The problem with 64bit is that Debug Diag doesn't work.

Whenever you pull up a list of processes, it only displays the ones running in x86 mode, and none that are running in x64 mode (including IIS).

I wish there was a work around for this.

re: Debugging a .NET crash with rules in Debug Diag

Pure Krome — Thu, 02 Apr 2009 06:50:32 GMT

@AaronS: SAME!!! I just downloaded this to debug a memory leak and i noticed it only installs an (x86) version. So of course no x64bit version dll's can be attached. I also couldn't find any info about an x64 bit version on the MS download site.

:( Unusable, but potentially kewl, product :(

re: Debugging a .NET crash with rules in Debug Diag

Tess — Thu, 02 Apr 2009 10:29:07 GMT

There is a 64 bit version in the works.

If you work with support or with your TAM/ADC if your company has one, you can get the 64 bit version, but it is not public yet as it hasn't gone through rigorous testing.

Debug Diagnostic Tool v1.1

RedCrystal — Mon, 13 Apr 2009 02:32:57 GMT

Here’s a nifty tool that every enterprise ASP.NET programmer and ops person should know about: Download

Unable to load DLL ‘dllname.dll’: A dynamic link library (DLL) initialization routine failed. 0x8007045A

If broken it is, fix it you should — Wed, 29 Apr 2009 14:33:59 GMT

I recently got an email with the following question: “Can you give me some very helpful hints with this

503 Service unavailable,Fatal Execution Engine Error,Faulting application w3wp.exe,.NET crash

dudu's 镜像 — Thu, 07 May 2009 09:42:09 GMT

最近博客园被HTTP Error 503 Service unavailable的问题困扰，博客(http://www.cnblogs.com/)与社区(http://space.cnblogs.com

re: Debugging a .NET crash with rules in Debug Diag

mga — Mon, 03 Aug 2009 20:35:21 GMT

Tess - this tutorial was invaluable in helping me solve a problem. Thank you!

re: Debugging a .NET crash with rules in Debug Diag

Walter — Tue, 29 Sep 2009 01:17:31 GMT

Hi Tess,

great article, thanks.

I don't even know what the acronyms TAM/ADC mean.

I am an independant web software developer who could really do with a version of debugdiag to debug a server crash on Windows 2008 64 bit.

Can you advise me of how I can get a copy please.

Thanks.

Walter

walterlockhart at gmail dot com

re: Debugging a .NET crash with rules in Debug Diag

Tess — Tue, 29 Sep 2009 10:08:44 GMT

TAM/ADC means Technical Account Manager or Application Development Consultant, you have one if you have a premier contract with MS.

Unfortunately the 64bit version is not publicly available yet but as soon as it is released it will be available for download on the MS download site. If you need one before, create a support case with MS, or try pining the guys at http://blogs.msdn.com/debugdiag/

re: Debugging a .NET crash with rules in Debug Diag

Gavi Narra — Mon, 23 Nov 2009 19:30:14 GMT

Thank you for the excellent article.

Looks like there is a typo in this command

.loadby sos mscorkws

it should be

.loadby sos mscorwks

re: Debugging a .NET crash with rules in Debug Diag

Tess — Tue, 24 Nov 2009 07:04:21 GMT

Thanks Gavi, corrected it in the post