OLE error code 0x80040154: Class not registered.

[Amedee Van Gasse]

Hello,

I am supporting (not programming) a Foxpro 7 application. On one of the
forms there is a datepicker control. Iirc, this is in the mscomct2.ocx.
The software was installed under an administrator account.
Now, when a regular user opens the form, he gets an error:

OLE error code 0x80040154: Class not registered.
OLE object is being ignored.
Record number: 156.

After cancelling the error, the forms opens normally. It's difficult to
ask the user if he sees the calender control and if he is able to use
it, because of language issues and user experience. And because
actually almost none of our users use that control so they don't know
where it is or how to use it...

[Eric den Doop]

Hello, Amedee!
You wrote on Wed, 08 Sep 2004 06:40:38 -0700:

AVG> I am supporting (not programming) a Foxpro 7 application. On one of
AVG> the forms there is a datepicker control. Iirc, this is in the
AVG> mscomct2.ocx.

Correct.

AVG> The software was installed under an administrator account. Now, when a
AVG> regular user opens the form, he gets an error:
AVG> OLE error code 0x80040154: Class not registered.
AVG> OLE object is being ignored.
AVG> Record number: 156.

You did't tell us if the file exists and if it's registered correctly. Try
to register it again:
REGSVR32 mscomct2.ocx

[Amedee Van Gasse]

Post by Eric den Doop
AVG> The software was installed under an administrator account. Now,
AVG> OLE error code 0x80040154: Class not registered.
AVG> OLE object is being ignored.
AVG> Record number: 156.
You did't tell us if the file exists and if it's registered
REGSVR32 mscomct2.ocx

and my reaction is:

Ooops.. indeed I should have mentioned.

The file exists, is the correct version, and should be registered.
I say "should be" because it is installed by an installshield installer
that contains it. Our installation specialist says that he is 100% sure
that running the setup registers the ocx (or fails with an error if it
can't).
The setup was done under the administrator account.

When the user runs the program as a regular user, he gets the error.
I don't know what happens when he runs as administrator, but in
previous cases with other clients (that we have not been able to solve,
we just told them always run as admin) the program doesn't give an
error.

When the normal user registers the ocx, he gets an error. I don't
remember the exact wording (and iirc it was in french anyway - user is
in Luxemburg) but it was something concerning not having enough rights
to do this or that.

[Eric den Doop]

Hello, Amedee!

OK, I'd try to run the program as admin to see if it 'fixes' the error. If
it does, then you are sure it's a security issue. If it doesn't, then the
OCX is not registered properly, or you get this error because of a different
active x class.

[Amedee Van Gasse]

Post by Eric den Doop
Hello, Amedee!
OK, I'd try to run the program as admin to see if it 'fixes' the
error. If it does, then you are sure it's a security issue. If it
doesn't, then the OCX is not registered properly, or you get this
error because of a different active x class.

and my reaction is:

Eric,

I agree with you it is most probably a security issue, but how to fix
it... ???
I'll ask the client to try this anyway. I'll keep you informed.

Also I am 100% sure the datepicker is the only activex on the form (or
even in the entire program)