Vista - wmdc.exe Windows Mobile Device Center

I have finally located and installed or placed into their proper directories
all of the WMDC components. I think I may be having conflicts with remnants
of Activesync 4.1 that was never uninstalled (tell me how if you know). This
is what I get when I try to manually start WMDC:

System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM
class factory for component with CLSID {EE05EDE6-97CF-4D00-9B20-AD9EC0B45108}
failed due to the following error: 80040154.
at Microsoft.WindowsMobile.DeviceCenter.Program.Main()

Thanks.

This is the exact error I am getting, and the first time someone else has
actually had the same problem as me. Are you getting this on Vista x64?

It only happens once I add the update that was put out last month.

I tracked it down using Reflector to a call in the WindowsMobileForeman
class.

I have submitted a bug, contacted a few people at Microsoft, but so far no
one has come up with an answer.

This is the original message I sent:

=== Copy of Message =====

I'm hoping you might be able to find out why the Mobile Device Center Update
causes the application to blow up when you attempt to run it on Vista x64.
Below is what I've determined, but I can seem to find out what COM object
it's missing and why.

I've tracked my COMException issue when trying to run WMDC after the sync
upgrade to the WindowsMobileForeman class.

Does anyone know what com object this is referencing or can someone lookup
this class id and see which dll it points to?
EE05EDE6-97CF-4D00-9B20-AD9EC0B45108

Error I Get:
System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM
class factory for component with CLSID
{EE05EDE6-97CF-4D00-9B20-AD9EC0B45108} failed due to the following error:
80040154.
at Microsoft.WindowsMobile.DeviceCenter.Program.Main()

Class definition that points to it.
[ComImport, TypeLibType(TypeLibTypeFlags.FCanCreate),
ClassInterface(ClassInterfaceType.None),
Guid("EE05EDE6-97CF-4d00-9B20-AD9EC0B45108")]
public class WindowsMobileForeman
{
}


"Ted" <Ted@discussions.microsoft.com> wrote in message
news:CF942AC5-B7D3-45ED-9F72-543B286354F9@microsoft.com...
>I have finally located and installed or placed into their proper
>directories
> all of the WMDC components. I think I may be having conflicts with
> remnants
> of Activesync 4.1 that was never uninstalled (tell me how if you know).
> This
> is what I get when I try to manually start WMDC:
>
> System.Runtime.InteropServices.COMException (0x80040154): Retrieving the
> COM
> class factory for component with CLSID
> {EE05EDE6-97CF-4D00-9B20-AD9EC0B45108}
> failed due to the following error: 80040154.
> at Microsoft.WindowsMobile.DeviceCenter.Program.Main()
>
> Thanks.

I am using the 32 bit Vista as I did not want to do a clean install on my
system. (Though I may as well have with all of the issues). I have been
working on this problem since Vista Beta 2 was released. I don't even have a
shortcut to WMDC in my control panel at all and had mistaken Sync Center for
WMDC until just 2 days ago. That is when I began investigating why I had no
way to start WMDC. I found that all of the files are located on my computer
in directory
C:\Windows\System32\DriverStore\FileRepository\winmobil.inf_7e222d87. I was
having issues with rapi.dll and ceutil.dll which were causing wmdc to stop
and report errors. Now it just stops and gives me the error I posted below.
In one conversation with another user having similar issues, it seemed to
point to maybe conflicts with Activesync as I was never able to uninstall
that program.

"Scott Glasgow" wrote:

> This is the exact error I am getting, and the first time someone else has
> actually had the same problem as me. Are you getting this on Vista x64?
>
> It only happens once I add the update that was put out last month.
>
> I tracked it down using Reflector to a call in the WindowsMobileForeman
> class.
>
> I have submitted a bug, contacted a few people at Microsoft, but so far no
> one has come up with an answer.
>
> This is the original message I sent:
>
> === Copy of Message =====
>
> I'm hoping you might be able to find out why the Mobile Device Center Update
> causes the application to blow up when you attempt to run it on Vista x64.
> Below is what I've determined, but I can seem to find out what COM object
> it's missing and why.
>
> I've tracked my COMException issue when trying to run WMDC after the sync
> upgrade to the WindowsMobileForeman class.
>
> Does anyone know what com object this is referencing or can someone lookup
> this class id and see which dll it points to?
> EE05EDE6-97CF-4D00-9B20-AD9EC0B45108
>
> Error I Get:
> System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM
> class factory for component with CLSID
> {EE05EDE6-97CF-4D00-9B20-AD9EC0B45108} failed due to the following error:
> 80040154.
> at Microsoft.WindowsMobile.DeviceCenter.Program.Main()
>
> Class definition that points to it.
> [ComImport, TypeLibType(TypeLibTypeFlags.FCanCreate),
> ClassInterface(ClassInterfaceType.None),
> Guid("EE05EDE6-97CF-4d00-9B20-AD9EC0B45108")]
> public class WindowsMobileForeman
> {
> }
>
>
> "Ted" <Ted@discussions.microsoft.com> wrote in message
> news:CF942AC5-B7D3-45ED-9F72-543B286354F9@microsoft.com...
> >I have finally located and installed or placed into their proper
> >directories
> > all of the WMDC components. I think I may be having conflicts with
> > remnants
> > of Activesync 4.1 that was never uninstalled (tell me how if you know).
> > This
> > is what I get when I try to manually start WMDC:
> >
> > System.Runtime.InteropServices.COMException (0x80040154): Retrieving the
> > COM
> > class factory for component with CLSID
> > {EE05EDE6-97CF-4D00-9B20-AD9EC0B45108}
> > failed due to the following error: 80040154.
> > at Microsoft.WindowsMobile.DeviceCenter.Program.Main()
> >
> > Thanks.
>

Under Control Panel in the Additional Options is where the Mobile Device
Center lives. You can create a desktop short-cut.

Anyway, I did a clean install (formatted HD and all) and I don't have
ActiveSync installed. I have tried uninstalling and reinstalling Mobile
Device Center and all the updates but that still doesn't do anything. Before
installing any updates, I was able to run the MDC and view files, etc on my
Pocket PC phone. It's only after I installed the updates that it fails.

I have tried to get someone to look up the class id in their registry to see
what COM object it is, and I searched through all of the WDC components
(dll's/exe) to trace through the calls but the COM object is being loaded by
classid instead of name so I couldn't figure out what was missing.

I found it funny (ok not really) that this appears to be the only COM object
where the name doesn't exist in any of the assemblies.

If and when I find a solution, I will be sure to post it. I was starting to
think it was an issue related to the x64 version only.

"Ted" <Ted@discussions.microsoft.com> wrote in message
news:B98737F3-13A4-4581-8128-3708AF3EBD72@microsoft.com...
>I am using the 32 bit Vista as I did not want to do a clean install on my
> system. (Though I may as well have with all of the issues). I have been
> working on this problem since Vista Beta 2 was released. I don't even have
> a
> shortcut to WMDC in my control panel at all and had mistaken Sync Center
> for
> WMDC until just 2 days ago. That is when I began investigating why I had
> no
> way to start WMDC. I found that all of the files are located on my
> computer
> in directory
> C:\Windows\System32\DriverStore\FileRepository\winmobil.inf_7e222d87. I
> was
> having issues with rapi.dll and ceutil.dll which were causing wmdc to stop
> and report errors. Now it just stops and gives me the error I posted
> below.
> In one conversation with another user having similar issues, it seemed to
> point to maybe conflicts with Activesync as I was never able to uninstall
> that program.
>
> "Scott Glasgow" wrote:
>
>> This is the exact error I am getting, and the first time someone else has
>> actually had the same problem as me. Are you getting this on Vista x64?
>>
>> It only happens once I add the update that was put out last month.
>>
>> I tracked it down using Reflector to a call in the WindowsMobileForeman
>> class.
>>
>> I have submitted a bug, contacted a few people at Microsoft, but so far
>> no
>> one has come up with an answer.
>>
>> This is the original message I sent:
>>
>> === Copy of Message =====
>>
>> I'm hoping you might be able to find out why the Mobile Device Center
>> Update
>> causes the application to blow up when you attempt to run it on Vista
>> x64.
>> Below is what I've determined, but I can seem to find out what COM object
>> it's missing and why.
>>
>> I've tracked my COMException issue when trying to run WMDC after the sync
>> upgrade to the WindowsMobileForeman class.
>>
>> Does anyone know what com object this is referencing or can someone
>> lookup
>> this class id and see which dll it points to?
>> EE05EDE6-97CF-4D00-9B20-AD9EC0B45108
>>
>> Error I Get:
>> System.Runtime.InteropServices.COMException (0x80040154): Retrieving the
>> COM
>> class factory for component with CLSID
>> {EE05EDE6-97CF-4D00-9B20-AD9EC0B45108} failed due to the following error:
>> 80040154.
>> at Microsoft.WindowsMobile.DeviceCenter.Program.Main()
>>
>> Class definition that points to it.
>> [ComImport, TypeLibType(TypeLibTypeFlags.FCanCreate),
>> ClassInterface(ClassInterfaceType.None),
>> Guid("EE05EDE6-97CF-4d00-9B20-AD9EC0B45108")]
>> public class WindowsMobileForeman
>> {
>> }
>>
>>
>> "Ted" <Ted@discussions.microsoft.com> wrote in message
>> news:CF942AC5-B7D3-45ED-9F72-543B286354F9@microsoft.com...
>> >I have finally located and installed or placed into their proper
>> >directories
>> > all of the WMDC components. I think I may be having conflicts with
>> > remnants
>> > of Activesync 4.1 that was never uninstalled (tell me how if you know).
>> > This
>> > is what I get when I try to manually start WMDC:
>> >
>> > System.Runtime.InteropServices.COMException (0x80040154): Retrieving
>> > the
>> > COM
>> > class factory for component with CLSID
>> > {EE05EDE6-97CF-4D00-9B20-AD9EC0B45108}
>> > failed due to the following error: 80040154.
>> > at Microsoft.WindowsMobile.DeviceCenter.Program.Main()
>> >
>> > Thanks.
>>