Getting /_ovrly: cannot execute binary file trying in install client 9.2 on linux

P

paabrennan

New Member
I am trying to install progress cleint 9.2 32 bit on a linux red hat server which is 64 bit intel.
When I try to install I abend with the following message.
/_ovrly: cannot execute binary file/_ovrly: cannot execute binary file

Linux is : 2.6.18-238.9.1.el5 #1 SMP Fri Mar 18 12:42:39 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

I did a file command on the file above and get
_ovrly: ELF 32-bit MSB executable, SPARC, version 1 (SYSV), dynamically linked (uses shared libs), not stripped

The install I did before on Solaris 5.8 32 bit worked.

Is there any way to get this to work.

Any help would be greatly appreciated.
 
The final release of Progress version 9 was 9.1E service pack 4.

Thus "client 9.2" makes no sense and may be an indication of why you are having problems.

Or it might be that you are trying to install a Sparc binary on an Intel platform ;)

BTW, version 9 is ancient, obsolete and unsupported. You shouldn't be trying to install it. You should be installing a current release such as 10.2B. And unless you are installing a Windows GUI client you should only be installing 64 bit executables.
 
9.1D is the client. It was thought that the client I had would work on either. Do you know if there is a 64 client that can be downloaded for 9.1D database. Sorry if I am not stating this correctly.
 
There are no clients which can be installed on both Sparc and Intel.

"r-code" is portable between platforms so long as the same "display type" and bitness are used. In other words 32 bit character r-code is portable to all UNIX systems but will not run in a Windows GUI session.

But the client executable that runs the r-code is specific to the platform.
 
Also, all clients are 32 bit, regardless of OS. Only server components are 64 bit.
 
TomBascom said:
"r-code" is portable between platforms so long as the same "display type" and bitness are used. In other words 32 bit character r-code is portable to all UNIX systems but will not run in a Windows GUI session.
Click to expand...

Character r-code actually runs fine in a Windows GUI session as long as there is no display tomfoolery going on.

We compile everything that has no display handling with _progres on Windows and force recognizable compile errors if gui r-code is required. The result is that of our 600 or so megabyes of r-code, only 3 mb or so (our display renderer) is compiled with prowin32.

Also, 32 bit r-code compiled prior to 10.1 will run fine on 64 bit and vice versa. This was 'feature fixed' in 10.1A or so to allow correct byte alignment for the target bits. Portable bits r-code should be back in OpenEdge 11.
 
You must log in or register to reply here.
Back
Top