PD7333 Package Build Fail

Recently we reinstalled our JDE servers(Deployment, Enterprise and SQL). We applied all our Updates and ESUs on PY7333 and copied the environment to PD7333.

However, now we cannot seem to build a Full Package on PD7333. The build will end up in error and the Enterprise Server's networking will die off. We cannot even ping it. We have to restart the Enterprise Server. It takes around 16 hours to build.

The JDE consultant suspects it is due to our network, and advised us to isolate our servers and do a build again. We did it but to the same result. Also 16 hours even with antivirus switched off. All the Business Functions ended up in error.

I'm attaching the log files here. Please help!

Can you do a full package build in PY? Looking at your logs, you have many corrupted Central Objects records. That's why the business functions never build, because it can't generate the C code from the Named Event Rules. (BSFN usually begin with "B," but NER BSFN begin with "N.") Without the NER, most of the DLLs cannot compile. All the NER are stored in F98741, which also generates the GBRSPEC file. You've got "corrupted" messages all the way down your GBRSPEC generation.

If you can build a full package in PY, then you've just got a bad set of PD Central Objects, and you should be able to rebuild them from PY. If you cannot, then you've got other problems.

Anyway ...

Some things to make sure about:

1) When you "copied the environment to PD7333," did you remember to copy the INCLUDE and SOURCE directories on the Deployment Server?
2) Did you remember to run R989861 to transfer Object Librarian records from PY to PD?
3) Did you remember to check F983051 and see if the VRENHV field says "PD7333" in the JDE_PD7333 database?

Either the compiler is not installed correctly (or at all) or the environment variables for VC++ are associated with the NT user that installed VC++ and not set as system variables.

Try building an update package with a single UBE in it. If that works build one with a single BSFN in it. If that doesn't work, the problem is likely in the compliler (Visual C++)