Sync centre

I've just spent about a week trying to get my new X61 to talk to my PDA. I've
finally got this Mobile Device Sync Centre running and I get an error message:
Retrieving the COM class factory for component with CLSID..... error 80040154.

This error number seems to be the general M$ number for almost anything. Has
anybody got any ideas?

"Lance Bombardier" <> wrote in
message news:CEFBC725-0137-4B35-AF83-...
> I've just spent about a week trying to get my new X61 to talk to my PDA.
> I've
> finally got this Mobile Device Sync Centre running and I get an error
> message:
> Retrieving the COM class factory for component with CLSID..... error
> 80040154.
>
> This error number seems to be the general M$ number for almost anything.
> Has
> anybody got any ideas?


"almost anything"
Or when a program tries to access a dll that does not exist on the system.

Jay,

So all these "Error opening database", "Class not registered" etc. are all
the same error?

Which .dll is it? Where in the rest of the error message does it tell you?

"Jay" wrote:

> "Lance Bombardier" <> wrote in
> message news:CEFBC725-0137-4B35-AF83-...
> > I've just spent about a week trying to get my new X61 to talk to my PDA.
> > I've
> > finally got this Mobile Device Sync Centre running and I get an error
> > message:
> > Retrieving the COM class factory for component with CLSID..... error
> > 80040154.
> >
> > This error number seems to be the general M$ number for almost anything.
> > Has
> > anybody got any ideas?
>
>
> "almost anything"
> Or when a program tries to access a dll that does not exist on the system.
>
>

"Lance Bombardier" <> wrote in
message news:2B68D61B-1D55-40C4-95BA-...
> Jay,
>
> So all these "Error opening database", "Class not registered" etc. are all
> the same error?
>
> Which .dll is it? Where in the rest of the error message does it tell you?

"Retrieving the COM class factory for component with CLSID."

No idea which dll it is looking for as I don't use the soft/hardware that
you describe.
I just know (as a developer) that I have encountered this problem when I
have tried to access a dll on a machine that I have forgotten to
copy/install/reg the necessary dlls.





>
> "Jay" wrote:
>
>> "Lance Bombardier" <> wrote in
>> message news:CEFBC725-0137-4B35-AF83-...
>> > I've just spent about a week trying to get my new X61 to talk to my
>> > PDA.
>> > I've
>> > finally got this Mobile Device Sync Centre running and I get an error
>> > message:
>> > Retrieving the COM class factory for component with CLSID..... error
>> > 80040154.
>> >
>> > This error number seems to be the general M$ number for almost
>> > anything.
>> > Has
>> > anybody got any ideas?
>>
>>
>> "almost anything"
>> Or when a program tries to access a dll that does not exist on the
>> system.
>>
>>

So what can I do? Uninstall - reinstall? Get the latest updates?

"Jay" wrote:

> "Lance Bombardier" <> wrote in
> message news:2B68D61B-1D55-40C4-95BA-...
> > Jay,
> >
> > So all these "Error opening database", "Class not registered" etc. are all
> > the same error?
> >
> > Which .dll is it? Where in the rest of the error message does it tell you?
>
> "Retrieving the COM class factory for component with CLSID."
>
> No idea which dll it is looking for as I don't use the soft/hardware that
> you describe.
> I just know (as a developer) that I have encountered this problem when I
> have tried to access a dll on a machine that I have forgotten to
> copy/install/reg the necessary dlls.
>
>
>
>
>
> >
> > "Jay" wrote:
> >
> >> "Lance Bombardier" <> wrote in
> >> message news:CEFBC725-0137-4B35-AF83-...
> >> > I've just spent about a week trying to get my new X61 to talk to my
> >> > PDA.
> >> > I've
> >> > finally got this Mobile Device Sync Centre running and I get an error
> >> > message:
> >> > Retrieving the COM class factory for component with CLSID..... error
> >> > 80040154.
> >> >
> >> > This error number seems to be the general M$ number for almost
> >> > anything.
> >> > Has
> >> > anybody got any ideas?
> >>
> >>
> >> "almost anything"
> >> Or when a program tries to access a dll that does not exist on the
> >> system.
> >>
> >>
>
>
>