Exception EOleSysError - Class not registered????

Arie van Leyen

unread,

Jan 31, 1997, 3:00:00 AM1/31/97

to

Hello,

I'm currently developing an application that should be installed on another
computer than the one I'm developing it on.

The application is a database application that uses BDE.

I've use InstallShield Express to make the install-disks. I've also
included BDE in the installer.

When I run setup from the disks I've created in the remote machine it
installes perfectly (I think).
The moment when I start the application I get an error message
(EOleSysError) and the program quits:

Application Error
Exception EOleSysError in module EGOS.EXE at 00053412
Class not Registered

If I install Delphi on the remote system the program works fine. So I think
there must be something I forgot while making the install disks with
InstallShield. I've checked everything, but can't figure out what is wrong
with the installation diskettes. I guess I have forgotten to include some
kind of registry entry in InstallShield, but I can't find any help on this.

Does the problem sound familiar and does anyone have a suggestion on this?

Many thanks,

Arie

Stephen Meeke

unread,

Jan 31, 1997, 3:00:00 AM1/31/97

to

Arie van Leyen <ae...@xs4all.nl> wrote in article
<01bc0f82$faf5a920$ec266dc2@aevl>...

> Hello,
>
> I'm currently developing an application that should be installed on
another
> computer than the one I'm developing it on.
>
> The application is a database application that uses BDE.
>

>...

> The moment when I start the application I get an error message
> (EOleSysError) and the program quits:
>
> Application Error
> Exception EOleSysError in module EGOS.EXE at 00053412
> Class not Registered
>
>
> If I install Delphi on the remote system the program works fine.

>....

> Does the problem sound familiar and does anyone have a suggestion on
this?

Hello,

Yup, the problem sounds familiar.

I've had this problem when I use any OCX's in my project. In particular
the FTP component supplied with Dephi. The only way around this that I
have found (although I am sure I am missing something) is to export the
appropriate keys from the registry (Search for the name of the ocx) and set
these up in InstallShield or import them manually on the target machine.

Are you using any OCX's ? Let me know what the outcome is as I have to do
the same thing very soon myself but haven't got around to dragging out my
old machine to test things out yet.

Stephen Meeke
Online Software & Services Limited
Prestwick, Scotland, UK

Brad Aisa

unread,

Feb 9, 1997, 3:00:00 AM2/9/97

to

In article <01bc0fb9$72ee0860$7e98...@pwick.demon.co.uk>,
"Stephen Meeke" <ste...@pwick.demon.co.uk> wrote:

>>...
>> The moment when I start the application I get an error message
>> (EOleSysError) and the program quits:
>>
>> Application Error
>> Exception EOleSysError in module EGOS.EXE at 00053412
>> Class not Registered

>I've had this problem when I use any OCX's in my project. In particular

>the FTP component supplied with Dephi. The only way around this that I
>have found (although I am sure I am missing something) is to export the
>appropriate keys from the registry (Search for the name of the ocx) and
>set these up in InstallShield or import them manually on the target
>machine.
>
>Are you using any OCX's ? Let me know what the outcome is as I have to do
>the same thing very soon myself but haven't got around to dragging out my
>old machine to test things out yet.

We are using an OCX, and the programmer using it found that simply
including it in the InstallShield setup (to the Windows system
directory) caused it to get registered properly. Have you tried this?

--
Brad Aisa <ba...@tor.hookup.net> http://www.hookup.net/~baisa/

"The highest responsibility of philosophers is to serve as the
guardians and integrators of human knowledge." -- Ayn Rand

Marcus Monnig

unread,

Feb 9, 1997, 3:00:00 AM2/9/97

to

On Sun, 09 Feb 97 00:50:58 GMT, see.s...@email.com (Brad Aisa)
wrote:

>We are using an OCX, and the programmer using it found that simply
>including it in the InstallShield setup (to the Windows system
>directory) caused it to get registered properly. Have you tried this?

I used OCX before and never had problems, but now in my current
project it seems that InstallShield fails to automatically register
the OCX. This problem with IS has been reported from other users
before. Where can I find the keys in the registry that I should set in
IS?

Marcus

*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
Marcus Monnig - mini...@cs.tu-berlin.de - PGP Public Key on request
*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~

Bart Davis

unread,

Feb 9, 1997, 3:00:00 AM2/9/97

to

another trick for most ocx's (those that are self-registering) is to simply
double click on the offending ocx from within explorer....

Brad Aisa <see.s...@email.com> wrote in article
<5dj6th$6be$2...@loki.tor.hookup.net>...

> In article <01bc0fb9$72ee0860$7e98...@pwick.demon.co.uk>,
> "Stephen Meeke" <ste...@pwick.demon.co.uk> wrote:
>
> >>...
> >> The moment when I start the application I get an error message
> >> (EOleSysError) and the program quits:
> >>
> >> Application Error
> >> Exception EOleSysError in module EGOS.EXE at 00053412
> >> Class not Registered
>
> >I've had this problem when I use any OCX's in my project. In particular
> >the FTP component supplied with Dephi. The only way around this that I
> >have found (although I am sure I am missing something) is to export the
> >appropriate keys from the registry (Search for the name of the ocx) and
> >set these up in InstallShield or import them manually on the target
> >machine.
> >
> >Are you using any OCX's ? Let me know what the outcome is as I have to
do
> >the same thing very soon myself but haven't got around to dragging out
my
> >old machine to test things out yet.
>

> We are using an OCX, and the programmer using it found that simply
> including it in the InstallShield setup (to the Windows system
> directory) caused it to get registered properly. Have you tried this?
>

Brian Sweeney

unread,

Feb 10, 1997, 3:00:00 AM2/10/97

to

In article <32fd331...@news.cs.tu-berlin.de>,
mini...@cs.tu-berlin.de wrote:

> On Sun, 09 Feb 97 00:50:58 GMT, see.s...@email.com (Brad Aisa)
> wrote:
>

> >We are using an OCX, and the programmer using it found that simply
> >including it in the InstallShield setup (to the Windows system
> >directory) caused it to get registered properly. Have you tried this?
>

> I used OCX before and never had problems, but now in my current
> project it seems that InstallShield fails to automatically register
> the OCX. This problem with IS has been reported from other users
> before. Where can I find the keys in the registry that I should set in
> IS?
>
> Marcus
>
>
> *~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
> Marcus Monnig - mini...@cs.tu-berlin.de - PGP Public Key on request
> *~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~

I think that I could have been the programmer that originally started this
thread.
The answer to my problem was the ORDER in which my dlls and ocxs are installed.
I did not have my OLEPRO32.DLL before the OCXs in my list in InstallShield.
If you do not have OLEPRO32.dll first Installshield will not give you an error
message when it cannot register the OCXs.
I would recommend copying ALL necessary DLLs before installing the necessary
OCXs

Brian Sweeney
Bre...@twics.com

Marcus Monnig

unread,

Feb 10, 1997, 3:00:00 AM2/10/97

to

On 10 Feb 1997 16:15:18 GMT, Bre...@twics.com (Brian Sweeney) wrote:

>The answer to my problem was the ORDER in which my dlls and ocxs are installed.
>I did not have my OLEPRO32.DLL before the OCXs in my list in InstallShield.
>If you do not have OLEPRO32.dll first Installshield will not give you an error
>message when it cannot register the OCXs.
>I would recommend copying ALL necessary DLLs before installing the necessary
>OCXs

Oh boy... is that true? IS should really be clever enough to handle
this...
I looked it up and in fact had my ocx as the second system file.

Stefan Paetow (remove * to mail me)

unread,

Feb 12, 1997, 3:00:00 AM2/12/97

to

On Mon, 10 Feb 1997 21:07:43 GMT, mini...@cs.tu-berlin.de (Marcus Monnig)
wrote:

>>If you do not have OLEPRO32.dll first Installshield will not give you an error
>>message when it cannot register the OCXs.
>>I would recommend copying ALL necessary DLLs before installing the necessary
>>OCXs
>
>Oh boy... is that true? IS should really be clever enough to handle
>this...
>I looked it up and in fact had my ocx as the second system file.

Markus and others....

It has nothing to do with InstallShield. The problem lies with the way
WINDOWS installs the OCX/OLE server.

InstallShield is Windows95/WindowsNT guidelined and uses the proper ways to
install OLE servers. Don't blame it on InstallShield, blame it on
Microsoft.

I have used InstallShield for a long time now and am very happy. The fact
is that InstallShield is very popular because it uses the Windows95
guidelines. It will do everything possible to make your installation
conform to that guideline spec, but if Microsoft screws up, it is NOT the
third-party vendor's (in this case InstallShield) fault.

Happy coding

Stefan Paetow
CEO - ellipse data systems

-
=========================================================================
= Any opinions here are my personal opinions, not those of my company =
= Home on the web: http://www.ellipse-data.com/ =
= Delphi Super Page: http://minnie.iafrica.com/~delphi/ =
= Delphi User Groups in South Africa: http://www.delphi.co.za/dugg/ =
=========================================================================