Preventing the Microsoft Application Error Reporting (DW20.exe)

[DJackman]

I'm trying to set up an automated process that runs as a service on my
Windows 2000 server. However, occasionally one of these processes
(Visual Studio 2005) crashes and fires off DW20.exe in an attempt to
send an error report back to Microsoft. The problem is, there is no
user to click on the button, so all it does is hang my automated build.
Is there any way to turn this error reporting off so the process can
just log the error and continue?

I tried following the instructions given on
http://www.pulpfusion1.com/demotech/....cfm?x=b11,0,w
but this had no effect.

Thanks,
...David..

[Jabez Gan [MVP]]

Right click My Computer > properties > Advanced > Error reporting.

Select Disable Error reporting. Uncheck "But notify me when critical errors
occur".

If this doesn't work, select Enable Error reporting and only select Windows
Operating System. Uncheck "Programs".

Hope this works.



--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net


"DJackman" <david.jackman@fastsearch.com> wrote in message
news:1137618389.860443.245320@g47g2000cwa.googlegroups.com...
> I'm trying to set up an automated process that runs as a service on my
> Windows 2000 server. However, occasionally one of these processes
> (Visual Studio 2005) crashes and fires off DW20.exe in an attempt to
> send an error report back to Microsoft. The problem is, there is no
> user to click on the button, so all it does is hang my automated build.
> Is there any way to turn this error reporting off so the process can
> just log the error and continue?
>
> I tried following the instructions given on
> http://www.pulpfusion1.com/demotech/....cfm?x=b11,0,w
> but this had no effect.
>
> Thanks,
> ..David..
>

[DJackman]

These were the instructions given on the web page I mentioned before.
This has no effect (I didn't try enabling error reporting and
unchecking "programs", but don't see how that would be any better--I've
changed to that configuration now, but can't cause the problem to
happen so it's just wait and see until the next crash).

This is a server machine. If anything ever crashes on it there should
never be any kind of user prompt for action. It really ought to be
easier to make this possible.