BUSBUILD Errors

We loaded some ESU's in Pristine and when I build an update package in the BUSBUILD we are getting the following message:
sCPAY.lib(N0700300.obj) : error LNK2001: unresolved external symbol __imp___calloc_dbg

This error gets repeated over and over again. I have tried just building an object and still getting the error. I have even backed out the ESU's and we still get the problem.

I have a call open to JDE but they have not been any help.

I was wondering if anyone has seen this error before and what they have done to fix it.

This is our config:
ERP8.0 SP19
ES - AS/400 V5R1M0
Citrix
Many ESU's

Thank You
Ellen

Ellen :

Have you applied the same ESUs on Pristine than on the rest of the
environments?
Perhaps you've applied some ESUs on the other environments and
Pristine was left 'incomplete'.

Sebastian (JDELIST)

Check to see if you have BusObj folder in your Path Code and delete it, then try re-building your package.

Did you select to do a backup before applying the ESU? If so, after backing out the ESU, did you restore from your backup?

I checked the deployment server and BusObj was not on the system.

Ellen

Yes, I restored the ESU from the backup.

Ellen

Ellen,

are you able to build in another pathcode and what was the ESU you applied.

Hi Ellen,

My first question is to everyone... Does anyone else apply ESU's and fixes
to the Pristine environment? If so... how can you call it pristine? I
leave the Pristine environment alone so that if somethng goes wrong in the
other environments I can test the function in Pristine and find out if it
was an ESU that broke the function or if it's a shipped JDE issue. The
only things I would consider applying to Pristine would be Updates and SP's
and only after they have been fully tested in the other env's. Even then I
may leave Prist alone.

Having said that...

Does the N0700300.obj exist in the path code on your deployment server?
Does the N0700300.H file exist in ...\JD7333\include?
Does the N0700300.c file exist in ...\JD7333\source?
Do those include and source files exist on your JD7333\package\package
name\include and source directories respectively?
Are these the same files that came with your ESU? (date/time stamp, file
size, etc.)
Were there any errors during your Merge process?

It almost sounds like there was an issue updating the existing source and
you are trying to compile old code but the system requires new references
from the new code.

Verify the merge process and that you have all of your peices where they
need to be for the compile to work.

You can also try to build this function by itself with debug turned on to
see if that tells you any more.

Regards,
Gerald.





ellendavis
<ellen.davis@manp To: Gerald Kastanek/Toronto/IBM@IBMCA
ower.com> cc:
Sent by: Subject: BUSBUILD Errors
owner-jdelist@jde
list.com


08/21/2002 12:48
PM
Please respond to
jdelist





We loaded some ESU's in Pristine and when I build an update package in the
BUSBUILD we are getting the following message:sCPAY.lib(N0700300.obj) :
error LNK2001: unresolved external symbol __imp___calloc_dbgThis error gets
repeated over and over again. I have tried just building an object and
still getting the error. I have even backed out the ESU's and we still get
the problem.I have a call open to JDE but they have not been any help.I was
wondering if anyone has seen this error before and what they have done to
fix it.This is our config:ERP8.0 SP19ES - AS/400 V5R1M0CitrixMany ESU's
Thank You Ellen
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=40317
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+

Re: RE: BUSBUILD Errors

Yes, we have put the ESU's on our development environment and am seeing the same problem. We even did a full build and the errors still come up.

Ellen