PDA

View Full Version : COM Error 80010105 thrown by MapPoint control in VS 2010 (WPF app)



booboobear0523
11-03-2011, 09:35 AM
All--
I have been trying to use the MapPointControl.ocx in a WPF app and have followed the prescribed procedure laid out by Microsoft. Even though I have adhered to their instructions, I still get the dreaded 'MapPoint failed to load. No further information is available' message while debugging. Here is what my programming environment looks like:

WinXP SP3;

VS 2010 Premium, SP1;

MapPoint 2010 North American Maps.

The procedure is as follows:

1. Create a Windows Forms user control in VB 2010 and embed the MapPointControl.ocx in it.

2. Create a simple WPF XAML window app that contains a Grid, which in turn contains a WindowsFormsHost WPF control.

3. Add code to the code-behind for the XAML page that dynamically loads the Windows Forms user control in step 1 into the WindowsFormsHost.

This code *does* work on Windows 7, but not on Windows XP SP3 and it is extremely frustrating to keep getting the 'MapPoint failed to load' error. I know that there are other posters on here who have gotten the same error but I am not sure that they are running the same version of Windows as I.

TIA,

booboo in NY, USA

booboobear0523
11-14-2011, 01:15 PM
All--
After spending some time on the phone with Microsoft Tech Support and having them analyze a ProcessMonitor dump, it turned out that FICO's Blaze Advisor software was causing a problem with MapPoint 2010. After I went ahead and uninstalled Blaze Advisor, I still was not able to host the MapPoint *.ocx in a Windows Forms user control but the COM error I was getting changed to -2147319779 (8002801C hex). This latter error is indicative of 'error accessing OLE registry', which I believe translates to, 'MapPointControl.ocx is not registered properly.' Am now waiting for MS Tech Support to get back to me after I sent them a TTTracer file that they captured while I ran my MapPoint code (TTTracer.exe is a proprietary Microsoft diagnostic tool). To be continued....

booboo in NY, USA

Mattys Consulting
11-14-2011, 09:52 PM
Thanks.

booboobear0523
11-22-2011, 04:07 PM
All--
Correction to my post of a week ago...the COM error I am now getting, in hex, is 8002801D, "Library not registered." Have repeatedly tried to manually unregister and register MapPointControl.ocx to no avail. Had MS Tech Support take another TTTracer dump and ProcessMonitor dump for further analysis after they saw some irregularities in my Registry that they thought they could correct. (Their suggested corrections didn't work but at least they didn't harm my system.) To be continued....

TIA,

booboo in NY

booboobear0523
12-30-2011, 08:23 AM
Hello, all,
It is more than a month after my last post and I have made some slow, painful progress. Never got MapPoint to work with VS.NET 2010 (XAML) on my WinXP machine. Finally used PCMover to move all applications (yes, *applications*, you read that correctly) EXCEPT MapPoint 2010 to a brand-new Windows 7 Professional box. I am now able to host the MapPoint 2010 *.ocx in a XAML page by using the Windows Forms Host control. However, the one catch is that if I don't run my test *.exe as Administrator, the dreaded COM error occurs. When running as Administrator, this does not happen. Am working with MS Tech Support to resolve this, but I am much happier than I was five weeks ago.

Best,

booboo in NYC