Full Server package build problem

Luca Agosti

Luca Agosti

Active Member
Hi list,
I'm trying to build full package in my new environment (built as JDEdwards document "Creating an Electronic Software Update Path Code and Environment in Oneworld Xe").
Client full package has not problem, but server full package has errors on N6000005 and N7400160 objects.
Logs say "fatal error C1083: cannot open include file b6000008.h and n6000009.h: no such file or directory".
I cannot understand: why server full package cannot find these files? Where it try to find them? Why client package can find them instead?
Any help appreciated.
Thank you.

Oneworld Xe SP23_Q1 / DB Oracle 9.2.0.7 / Deployment Server Win2003 SP2
 
Hi,

unfortunately JDE sometimes does not always do due diligence on some of there updates.

I have seen this before where the client builds OK BUT the server does not.

You need to check the objects it complains about not being there in the F9860 (field SIBFLOCN) to see if the value is a 2 (Server and Client function). If they are then you need to add these objects to your package assembly.

If they do not exist then you need to find out from JDE why they were not included in the ESU, OR if the exist and the value in SIBFLOCN is not 2 then you need to update the value to 2 and include the objects in your package build (if they are not there already) and resubmit your build.

The problem with the second part of this solution is that it could cause a domino effect in that you may then get error messages for other objects called by the two "missing objects" on the server when they now build on the server.

You may need to delete the build records for the package as it sometimes does not recognise that you have added new objects or changed the SIBFLOCN value.
 
Check on the Enterprise server/Application server:

The jde.ini file under the section [JDE_CG], the LIBS, MAKEDIRS and INCLUDE. They cannot use the shorten path name such as the tilde(~), has to be the full path. . Have them look in there for any tilde and have them cut and paste the paths(INCLUDE,LIBS, MAKEDIRS) into explorer and see if they are valid.
In 894 or higher , we now use the jde.ini settings for the variables to compile with.
In 893, we still depend on the environment variables.

The difference between the deployment server and the Enterprise server are they are different programs compiling these BSFN. On the deployment server, we use Busbuild and the jde.ini. On the enterprise server we use a program called, builddll.exe which for 8.93 uses the Environment Variables and for 894 or 895 uses the jde.ini setting.

In the enterprise server jde.ini, the [JDE_CG] INCLUDE, MAKEDIRS, LIBS cannot have the tilde ~ in it such as c:\Progra~1\Micros~1\Vc98\lib... they all have to have a full path name c:\Program Files\Microsoft Visual Studio\Vc98\lib

Once they correct this, to be safe, bring down services of One World and bring it back up . They need to BUILD a NEW package. If they just do a resubmit of the old package, it is still using the old .txt files that have the tildes in the path.
SystemEnvInclude=c:\Progra~1\Micros~1\Vc98\include;c:\Progra~1\Micros~1\Vc98\mfc\include;$(SYSTEM)\INCLUDE;$(SYSTEM)\INCLUDEV;$(SYSTEM)\CG;$(APP)\INCLUDE;
SystemEnvLib=c:\Progra~1\Micros~1\Vc98\lib;c:\Progra~1\Micros~1\Vc98\mfc\lib;$(SYSTEM)\LIB32;$(SYSTEM)\LIBV32;$(APP)\LIB32;
SystemEnvPath=c:\Progra~1\Micros~1\Common\Tools\WinNT;c:\Progra~1\Micros~1\Common\MSDev98\Bin;c:\Progra~1\Micros~1\Common\Tools;c:\Progra~1\Micros~1\VC98\bin

which will cause it to fail again.

If rebuilding a brand new package does not work, then they need to go to one of their .txt files such as CALLBSFN.txt under <packagename>/text/CALLBSFN and look near the bottom for the SystemEnvInclude, SystemEnvLib and SystemEnvPath. Those paths needs to be correct and without tildes.

If the jde.ini is correct, however the CALLBSFN.txt file is not, and and the ~ tildes are in there, they still need to create a NEW server package.
The whole problem is the tildes and then resubmit and use the same .txt file
After correct that, server package build will complete successfully and all BSFN will be complied and built OK for the server side.


Regards
vaibhav
 
If your Enterprise Server is not Windows - then different versions of the objects are built for the Client and Server.

Would suggest doing a GET of the objects in error - and checking the source / include directories to see if the required .h files are being created.
 
Back
Top