JD13750

jgersic93

Active Member
A question regarding busbuild. I went and copied the problem files (.c,
.obj, .h) from the planner pathcode over to the dev pathcode on the
deployment server. I then ran busbuild seperately (in dev on the deployment
server). I re-linked, and then recompiled the problem .dll (cinstall), it
compiled this time without errors.
I then thought it would be ok to try a full client build. I kicked off a
full client build, in the dep7333 pathcode on the deployment server, and the
problem is back, same .dll, same business functions. How is this possible?
How does the busbuild act differently when it is run alone, versus when it
is kicked off from a full build?
And the reason for the full build is not the ESU, but we have had extensive
development in the DEV pathcode and we thought it would be nice to pull it
all together in one package again..

Regards,
John

----------------------------------------------------------
OneWorld Xe (B733.3)
Update 2, SP 16
Oneoffs: SP16_011, _018, _019
Running on: WIN2K/SP2, SQL2k/SP2
Metaframe 1.8a
----------------------------------------------------------

-----------------------------------------------------------------------
John Gersic
Financial Systems DBA
PH: 703.744-6057
1861 International Drive
McLean, Virginia 22102
Microstrategy - Best in Business Intelligence
http://www.microstrategy.com/ <http://www.microstrategy.com/>
-----------------------------------------------------------------------
 
Do you have a busobj folder in the planner pathcode? If so delete it and
resubmit the build. This would explain the problems in the dep7333
environment and not in dev.
Regards
Kieran Fitzgerald
 
Just curious, but are you trying to build a package for DEP7333?

If you are, you can stop. The DEP7333 isn't capable of having packages built for it. Same with the JDEPLAN environment. Howeverm if your issue is with building packages for other environments on the deployment server. Let me know, I would be glad to help you. Some additional info that would help in finding a solution would be the log files from the package build. Also, the jde.log file.

Thanks!

Dan Richards
Plexus Corp.
Xe, SP16.1, XU3, RS6000, Oracle 8.1.7, Metaframe XPe
 
Back
Top