We have an error that we can't seem to find and don't have the need/resources to try and track it down. What we do need to do is just keep the freaking "Please tell Microsoft about this problem" dialog boxes from cluttering up the server.

It is from an MS-Access error (we think) but I can't find where Access is installed (I don't think it is); there is no MS Office directory on any of the drives.

If we could just stop the dialog boxes from appearing that would be great.


Spec: Window Server 2003 sp2

+4  A: 

Well, I would try and figure out what application is using Access. Not knowing what is running is a real issue, especially when it is having unhandled exceptions!

As far as just disabling? Try:

Right click 'My Computer'

left click 'Properties'

left click 'Advanced' tab

left click 'Error Reporting' (near bottom)

left click 'Disable error reporting'

Geoffrey Chetwood
+9  A: 


If you also want to disable the Windows “Send Error Report” dialog on your computer, right-click on the “My Computer” icon, select “Properties”, switch to the “Advanced” tab, and click on the “Error Reporting” button. In the Options dialog, select the “Disable error reporting” radio button:

Compare also for general .NET Exception Handling sanity.

Jared Updike
They don't want to run that on their customer's machines, because that will disable _any_ application from using the dialog. They just want to prevent _their_ application from sending it.
Joel Coehoorn
+2  A: 

It's called the Windows Error Reporting Dialog. You can disable it by following these instructions:

However, I would be concerned with why you are getting those error messages. You are just concealing a problem which could be very bad.

Cory Foy
+1 because the link explains how to disable it for a single app
Lars D
+2  A: 

Since I see three different people posted instructions on how to disable the dialog on their own machine, I'll post this again as an answer instead of just a comment:

They don't want to do that on their customer's machines, because that will disable any application from using the dialog. They just want to prevent it from coming up for their application.

Joel Coehoorn
Very good point and thanks for the comment/answer transition. The server is ours and it is limited to our apps. The fact that something is crashing somewhere outside of our core apps bothers us but it's too expensive to try to track down to find out it's some bizarre minesweeper function. 80)
@Joel: I really don't understand where you got any of your assumptions from here. I don't read any of that in his question.
Geoffrey Chetwood
+7  A: 

I don't think you realize jusy how serious this error might be. These errors pop up under severe conditions like buffer overflows, null pointer dereferences, division by zero errors, etc. Given that you mentioned that this runs on a server, you potentially (depending on your situation) have a network facing, easily exploitable program!

As others have suggested, you can turn off error-reporting system wide, or you can use the SetErrorMode API to disable it for just your application, but again I would strongly advise to investigate and fix the problem at its root!


I have a question for the original poster:

What, exactly, leads you to think that MS Access is causing the issue?

the dialog box actually says, "MS Access" crashed do you want to send info to MS?
Have you searched for MSACCESS.EXE on the PC where this is happening? Perhaps some application is using the Access runtime behind the scenes.
+1  A: 

It's not concealing anything, if a program crashes windows will still tell you. The difference is that it won't compile a core dump and try to send it to microsoft for you. It's very useful to disable this garbage.

Sam Watkins

When working in .net, you can catch all unhandled exceptions (which is what causes this message). But I'm not aware of a way to do the same in Access.