RE: Business Function Load Failed


Active Member
RE: Business Function Load Failed

Do you have install ESU or the euro cum on your system, and do you have
crate a full package after that ?

There was a problem like this in B732 when you install the MFG cum. The
error message was the same with copbase.dll because it was a new dll
retrofiting from a further oneworld version.
To avoid this error, you could try to create the CRACAL in OL if it don't
exist. You must after recompile the business function. If it works on the
workstation, you must create a full package and deploy it on all workstation
and server.

Perhaps it exists a better solution...

Service Informatique RAVATE
Tel : 02 62 90 40 63
E-mail : [email protected]

Current Version : OneWorld B7332 Oracle, RS600
Work on :
Oneworld B7321, B7331, B7332, XE
Platform, UNIX, AS400, NT
Database : Oracle, SQL, DB2

-----Message d'origine-----
De : [email protected]
[mailto:eek:[email protected]]De la part de ste_baxter
Envoyé : mercredi 27 juin 2001 10:15
À : [email protected]
Objet : Business Function Load Failed

I wonder if anyone can shed any light on this error message:

"Business Function Load Failed - CRACAL.DLL -
[email protected]"

I have checked the Business Function out and rebuilt it but this has not

One point that is confusing me a little is that the Business Function is
defined in OL with parent dll of CALLBSFN (not the CRACAL mentioned in the
error message).

Any ideas


Visit the forum to view this thread at:

Service Informatique RAVATE
Tel : 02 62 90 40 48
E-mail : [email protected]


Active Member

If this is a client problem you could try running Busbuild from you b7\system\bin32 directory and choose Tools / Sychronize JDEBLC. This will tell OneWorld which DLL functions should be run from. i.e. CALLBSFN not CRACAL.

B7332 SP15.1. NT/AIX. Oracle 8.1.6


Thanks for the tip on JDEBLC.

A developer who had previously worked on this site told me to change the parent dll definition in OL to CRACAL and re-build the BSFN then copy the CRACAL.dll across onto the Terminal Server and change the parent dll back to CALLBSFN in OL.

This seemed to do the trick.