package built failed- deployment server can't receive communication from Enterprise server

package built failed- deployment server can\'t receive communication from Enterprise server

JDE: One World XE B7333 SP23_V1

OS of my servers.
Deployement server - Windows Server 2000 std
Enterprise server - Windows Server 2003 enterprise
Enterprise server1 - Windows Server 2003 std
Enterprise server2 - Windows server 2000 std

My deployment server always could not built the update or full package for the Enterprise server, but no problem with other 2 old Enterprise server 1 and Enterprise server 2. (I had test built update package using JDE STD Report but still same problem)

Here is the SvrBuild log:
(I noticed that the deployment server can't receive communication from the new enterprise but can receive communication from other old enterprise server)

Wed Jan 14 08:30:59 2009 spkgclnt.c74 PKG0000020 - Begin communication
with server ENTSVR.
<font color="red"> </font>
Wed Jan 14 08:30:59 2009 spkgclnt.c74 PKG0000020 - Begin
communication with server ENTSVR1.
Wed Jan 14 08:30:59 2009 spkgclnt.c453 PKG0000021 - Receive
communication with server ENTSVR1.
Wed Jan 14 08:30:59 2009 spkginit.c923 PKG0000022 - Validating
deployment server compression directory - ENTSVR1

Here is the extract from jde.log when I do some testing update package.


2876/2748 Wed Jan 14 14:10:56 2009 spkgclnt.c364
PKG0001010 - An error occured on ENTSVR
Server error.

2876/2748 Wed Jan 14 14:10:56 2009 spkginit.c897
PKG0002305 - Unable to load detail structures for package TESTUPDATE

2876/2748 Wed Jan 14 14:10:56 2009 spkgeng.c200
PKG0000022 - Package Build Failed for TESTUPDATE: Unable to create package header structure.

Help, I wonder what happen to the enterprise server.


Note: I'm able to access the Enterprise server from network
My previous experience, only 1 time out of 100 package can built successfully for the new enterprise server.

Re: package built failed- deployment server can\'t receive communication from Enterprise server

I had some problems with Windows 2003 SP2. Mine wasn't quite the same as yours, it was the Deployment\JASGEN servers that were on SP2, and they sent a message to the server, the server responded and the building server never got the response, so it just hung. It turned out to be 2 advanced settings to be switched off on the NIC. Sadly I didn't keep the specific values, as a Windows expert set it up for me and I no longer work for that client.

However a quick google revealed this:

http://support.microsoft.com/kb/948496/en-us

And I'm fairly certain this was the issue.

Read this link as well, it looks very familar:

http://seer.entsupport.symantec.com/docs/304578.htm

Hopefully this will give you a starting point