MapPoint object crashed with an internal error (6-40028--1073741819)

This is a discussion on MapPoint object crashed with an internal error (6-40028--1073741819) within the Development forums, part of the MapPoint Desktop Discussion category; Hi all,
We have a C# project that use MapPoint 2006 as object to display vehicle locations. The application crashed ...

MapPoint object crashed with an internal error (6-40028--1073741819)

Hi all,

We have a C# project that use MapPoint 2006 as object to display vehicle locations. The application crashed on some Win XP machines after running a while. The error message is follwoing: This program has encountered an error and will close. The error details says: This application is unable to continue running due to an internal error. (6-40028--1073741819)

I googled the error. Microsoft knowledgebase has to articles addressing this error. It suggests either the MDAC is broken or the user has an uncompatible network printer driver. In our case, we ruled out the broken MDAC and believe it's probably a printer driver issue. But Micorsoft did not give a real fix or work around to get rid of this problem. As a product, we cannot limit the user not to use network printer. We are at the dead end now.

Does anybody encounter the same problem? Any solutions or suggestion? Thanks.

Wilfried, thanks for asking. The bad thing is, we never call the printer or try to print anything from our code. The Microsoft knowledge base suggests this error could be a printer driver issue. We donot know how this issue is related to printer driver. Maybe MapPoint object by default will try to do something with printer, but definitely not from our code.

To confirm this, we ran a test on 4 identical machines with fresh installed Win XP, MapPoint 2006 and our application. When no printer is installed, our application could continuously run for days without crashing. But after we installed a HP network printer, the application will eventually crash after running a period time, time range from several minutes to 8 hours. Some our clients also complain the same error.

When checking for details error messages, I found the ModName of error sigature is different with what's described in Microsoft's KB310596. So it may not be the printer at all but the VC++ run time library!!!??? Then, how to explain when no printer installed, the application never crash?

Thanks Wilfried for the reply. Managed code ususally does not introduce this kind of errors, unless we did a very poor job . If this is what you suspect, it must be in the C# InteropServices calls to the MapPoint control. It's difficult to debug since the error cannot be trapped, when it happens, the MapPoint object just simply crashes. Does anybody have some ideas how to debug MapPoint?

Still, the printer does not look like a coincidence, since we can always reproduce the error. When no printer is installed, the error is gone.

In Delphi it is possible to pause a running program in IDE and then view cpu / call stack and so. I see the latter are also possible in VS2005, but I cannot see how to pause a program. Maybe it is possible ? If you can pause at the moment of the crash then the call stack maybe get you further.

Has Microsoft ever come up with a valid solution for this problem? I have an app where I'm using the active x control in vb.net 2003. (I'm using Mappoint 2004). The application can work great 9 times out of 10, but it does crash for no reason. The Mappoint control just seems to shut down for no reason. I've tried many of the Microsoft suggestions, but nothing has worked.

Has anybody had this problem and been able to find a solution where it no longer crashes?? If so, I would like to hear how you solved this problem.

If upgrading to a higher version of vb.net and/or mappoint will solve this let me know. Given the current economic situation, I need to be sure purchasing something is a guarenteed fix before we buy it.