Full Server packages

[recker5]

We are running B7332 and Xe on the same box(only PY7333 environment
upgraded). Xe has update 3 and latest planner ESU along with SP 17 with all
One-Off's. We are on NT 4.0/SQL Server 2000 with 2 GB of RAM on Enterprise
Server and 1 GB on deployment server. For some reason, full server packages
fail to build. If we build specs and BSFN together, it unpacks till GBRSPEC
and then everything errors out including BSFN (include directory does not
have all header files only 1000 compared to 7000+ in pathcode). When we
build specs and BSFN seperately, we run into similar issues. We have tried
building it from NT 4.0 deployment server as well as Windows 2000 Client.
Any help is appreciated. Thanks.

Errors are similar to:

466/374 Mon Nov 12 18:59:37 2001 spkgstatus.c746
PKG0007011 - fwrite of 0 bytes failed in WriteStringToStatus (errno = 17)

466/374 Mon Nov 12 18:59:37 2001 spkgstatus.c1664
PKG0007029 - SetStatusOfBuildDLLProcess failed in
jdeSetStatusOfBuildDLLProcess

 

[NoSleep]

Did you check the "text" folder for any of the DLLs in the jdedwardsoneworld/ddp/B7332/packages/*.* folder for the particular package you are building? see if the log file for any of the DLLs are there and open them to see if there are any weird messages. there might be something wrong with SP17 (Since it is the most latest SP with the latests jdekrnl.lib).

The two errors along with your description sounds like there is a) a linking issues amongst the DLL's, including JDE DLLs and Windows DLLS or b)Your NER specs might be corrupt. When the build occurs, it might not be converting the NER BSFN's to C incorrectly, hence, when you do a build, there are errors.

 

[StewartSchatz]

We are having the same issue. We are trying to add an additional Win2K logic server. Could you post how/if you fixed this issue?

Thanks.

OneWorld Xe
1 AS/400 Model 730 Enterprise Server
1 Compaq ML370 W2K Deployment Server
1 Compaq ML570 W2K Citrix Server

 

[dan_richards]

Hello,

This may be a dumb question, but I didn't see you reference anything to a C Compiler. Is it installed? Does it have SP3 or higher (For C++)?

[blue line]
Dan Richards
Xe, SP15, XU1, RS6000, Oracle 8.1.7, Metaframe XP

 

[timhui]

Here are my two cents.

At first, the Tech support at JDE told us that the package building process would not work well or correctly if the deployment server was Windows NT 4.0 and the client was Windows 2000. Any other combinations would be fine.

We had problems at building the full server packages the same as you encountered (GBRSPEC). We found that any backup processes, such as system backup or SQL server backup, would interrupt the full package building process. As well, some Anti-Virus programs, such as Norton Anti-Virus, would interrupt the full package building process. Try to avoid any scheduled backup processes and disable Anti-Virus program file checking functions for those JDE related directories/extensions on all servers and the building client.

No matter what, even both PDF files show the build completed successfully, the errors you mentioned in the JDE_xxx.LOG files on the enterprise server will show up. That's built-in bugs in JDE and JDE does not know how to solve them (or does not want to solve them). That's why you need to change the "DeploymentStatus" in the package INF file from "No Status Defined" to "Approved" to make the full package available for the client installation.

There are lots of .TXT and .LOG files on the deployment server that you should check for the real result of your build as well as the SVRBUILD.LOG in the package directory on the enterprise server. In addition, The .STS and .TXT files in the TEXT direcotry under the package on the enterprise server may give you some clues.

Good luck!


Tsunghan Tim Hui
[email protected]
Xe SP16.1 Update 3, SQL 7 SP2, Windows 2000 SP 2, ES=NT 4.0 SP6.1a, DS=NT 4.0 SP 6.1a

 

[husni]

We had the same problem due to the incorrect environment variable setup for C++ in deployment and enterprise server.
You must have the same values in system variables (include, lib, path) as it is in the user variable.
example;
include = C:\Program Files\Microsoft Visual Studio\VC98\atl\include;C:\Program Files\Microsoft Visual Studio\VC98\mfc\include;C:\Program Files\Microsoft Visual Studio\VC98\include;C:\msdev\vc98\atl\include;C:\msdev\vc98\mfc\include;C:\msdev\vc98\include;

lib = C:\Program Files\Microsoft Visual Studio\VC98\mfc\lib;C:\Program Files\Microsoft Visual Studio\VC98\lib;C:\msdev\vc98\mfc\lib;c:\msdev\vc98\lib;

path = D:\ORANT\bin;%SystemRoot%\system32;%SystemRoot%;C:\SNA\system;d:\MSSQL7\BINN;d:\B7\PY7333\bin32;d:\B7\system\bin32;C:\Program Files\MicroSoft Visual Studio\Common\Tools\WinNT;C:\Program Files\MicroSoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\MicroSoft Visual Studio\Common\Tools;C:\Program Files\MicroSoft Visual Studio\vc98\bin

Usually we run the full server package builds from the deployment server.

Good luck

Husni
Xe, Update 3, SP17
Win2000, SQL2000

 

[imedlatrech]

what a bout partial and update packages

 

[Darren_Evans]

We have experienced a similar issue.
Upon submitting a FULL Build from a Win 2000 client to a Win NT4.0 enterprise server, the client part of the build completes successfully whereas the BSFN options and the Objects section of the Server Side produce errors.
The logs also throw out error messages of the type:
SetStatusOfBuildDLLProcess failed in jdeSetStatusOfBuildDLLProcess

As a result we are not submitting the build from the Win2000 client anymore, although it is the more powerful machine.

Any feedback about the incompatibility of NT4.0 and Win 2000 in a Client/Server relationship would be appreciated.

Regards

Darren Evans
B733.1, SP11.3, Oracle 8.1.5, WINNT4.0 SP6, Citrix Metaframe 1.8

OneWorld CNC Technical Administrator
More Group UK
2nd Floor Meirion House
18 - 28 Guildford Road
Woking
Surrey
GU22 7QF

 

[imedlatrech]

HI
our case is that when we submit a FULL or PARTIAL from a DEPLOYEMENT SERVER (WIN NT 4.0) we receive the same error message
but building update package it's fine

thinks in advance



XE
WIN NT 4.0
SQL 7.0