Problem to create a MapPoint instance

[Chris_B]

Whenever I am connected to internet using a modem, I cannot create the
mappoint object in my .Net application. The catched exception "Cannot create
ActiveX component" is raised after a couple of minutes (probably a timeout).
I have no problem at all, as soon as I connect to internet via my LAN or
disable my modem connection which means no connection at all to internet. I
have the following syntax which states that the object is created locally as
wanted.
CreateObject(classID,"").
Does anyone has a clue what may cause the problem and how to solve it?
--
/embe

[Gilles Kohl [MVP]]

Not really, this sounds pretty strange.

Anything in the event log?

Are you familiar with SysInternals TcpView or tools like WireShark?
You could try and monitor what type of network activity goes on during
those timeout minutes.

Hmm, can you show a bit more of your code - ideally, create a new
MapPoint application and ONLY create the instance, and post that code
- i.o.w, the smallest _standalone_ app that still exhibits the
problem.

Does the behaviour change if you use the direct "new" syntax instead
of trying to instantiate via classID? I.e. something along these
lines:

(with a reference set to the "Microsoft MapPoint 13.0 Object Library
(North America)")

// member that holds a reference to the MapPoint instance
MapPoint.Application m_MapPointApplication = null;

// Later, e.g. in Form_Load
m_MapPointApplication = new MapPoint.ApplicationClass();

Same problem?

Regards,
Gilles [MVP].

(Please reply to the group, not via email.
Find my MVP profile with past articles / downloads here:
http://www.gilleskohl.de/mvpprofile.htm)

[Chris_B]

Thanks for your tips Gilles, it helped me to localize the problem.
It has nothing to do with the code, but when I use early binding to create
the object, I recieve a more detailed exception message as follows.
"Retrieving the COM class factory for component with CLSID
{15A40122-24D2-4FDB-8155-5F65FCE7017F} failed due to the following error:
80080005."
Searching on this message gives many leads even to MapPoint. Most of them
indicates that it is an security issue. I havent solved the problem yet, but
a funny thing is that if I close my modem connection while wating for the
object to be created (2 min timeout), the object will be nicely created every
time. Any clue?
--
/embe

[Gilles Kohl [MVP]]

Chris,

On Sat, 5 Jan 2008 09:00:00 -0800, Chris_B
<Chr...@discussions.microsoft.com> wrote:

>Thanks for your tips Gilles, it helped me to localize the problem.
>It has nothing to do with the code, but when I use early binding to create
>the object, I recieve a more detailed exception message as follows.
>"Retrieving the COM class factory for component with CLSID
>{15A40122-24D2-4FDB-8155-5F65FCE7017F} failed due to the following error:
>80080005."
>Searching on this message gives many leads even to MapPoint. Most of them
>indicates that it is an security issue. I havent solved the problem yet, but
>a funny thing is that if I close my modem connection while wating for the
>object to be created (2 min timeout), the object will be nicely created every
>time. Any clue?

Have you seen this discussion? Is your context comparable?

http://www.mapforums.com/mappoint-2006-object-initialization-fails-asp-net-2-0-a-6174.html

[Chris_B]

Yes I have seen it, but I think I have found what causes the problem thanks
to your info. I downloaded TCPview and could see that MapPoint establish a
TCP connection to my LAN. When I connect my broadband modem it also connects
(netbios) to my LAN server. Somehow this causes the problem when starting
MapPoint after disabling the LAN, it tries to connect (thats probably the
timeout).
Whats happening at a more detailed level and how to get around the problem I
have no answer to at the moment. I am not an network expert.
But many thanks for your tips that helpmed to find the cause.
--
/embe

[D'Errico@discussions.microsoft.com Sebastien D'Errico]

Hi Chris,

I have the same problem for a different object. I am creating an instance on
Microsoft Windows 2003. After waiting a minute, I get error 80080005.

Did you find a way to solve your problem?

Your comment are appreciated,

Thanks,
Have a nice day!
Sebastien