PY7333 Server Full Package build fails on CDBASE DLL file

I recently refreshed my PY7333 development objects with those from PD7333. I then copied the PD7333 packages over to PY7333 and modified them correctly to change them to PY7333 packages. The Client Full package built and deployed fine. The Server Full package errored out with various errors. I then decided to build the PY7333 Server Full package from scratch. It errored out on the CDBASE dll file. I searched all of the appropriate log files on both my Deployment Server and my Enterprise Server. The only errors I could find were in the jde.log file on the Deployment Server. Package name is PYA_SF. DEPSVR is the Deployment Server and ENTSVR is the Enterprise Server. Here are the error messages near the end of the log file:

<font class="small">Code:</font><hr /><pre>2180/1988 Thu Apr 28 12:50:08 2005 spkgclnt1670
PKG0005205 - JDENET_AddFileToMsgX failed with JDENET Error: File open error.
Unable to transfer \\DEPSVR\B7333\PY7333\package\PYA_SF\include\allitems.h to ENTSVR

2180/1988 Thu Apr 28 12:50:08 2005 spkgclnt859
PKG0005100 - Unable to transfer table header file ALLITEMS

2180/1988 Thu Apr 28 12:50:08 2005 spkgutil1060
PKG0010001 - Unable to transfer object ddtabl to server ENTSVR. Package Error: Network error.

2180/1988 Thu Apr 28 12:53:28 2005 spkgclnt1670
PKG0005205 - JDENET_AddFileToMsgX failed with JDENET Error: File open error.
Unable to transfer \\DEPSVR\B7333\PY7333\package\PYA_SF\source\x0010.c to ENTSVR

2180/1988 Thu Apr 28 13:24:45 2005 spkgclnt1692
PKG0005207 - JDENET_ReceiveMsg failed with JDENET error: Timeout.

2180/1988 Thu Apr 28 13:24:45 2005 spkgclnt1393
PKG0005000 - Creation of detail file for CDBASE on ENTSVR failed!
Unable to create a network message. JDENET error: Connection closed.

2180/1988 Thu Apr 28 13:24:45 2005 spkgutil1106
PKG0010003 - Unable to create detail file on server for CDBASE on ENTSVR.Package Error: Network error.

2180/1988 Thu Apr 28 13:24:45 2005 spkgclnt1748
PKG0005300 - Status retrieval of asvrhdr on ENTSVR failed!
Unable to create a network message. JDENET error: Connection closed..

2180/1988 Thu Apr 28 13:24:45 2005 spkgutil837
PKG0000702 - Unable to retrieve status for package PYA_SF on ENTSVR.
Server returned: Network error.

2180/1988 Thu Apr 28 13:24:46 2005 spkgclnt1938
PKG0005300 - Freeing structures on ENTSVR failed!
Unable to create a network message. JDENET error: Connection closed.</pre><hr />

After you did this copy did you recycle jour JDE services, it seems that there is a communication issue between the dep. server and ent. server.

[ QUOTE ]
After you did this copy did you recycle jour JDE services, it seems that there is a communication issue between the dep. server and ent. server.

[/ QUOTE ]

I rebooted my Deployment Server and then rebooted my Enterprise Server.

Do you have enough space on the server?

Manoj

Hi,

I have run into this same problem a few times before in ERP8. Usually when refreshing environments. The problem has to do with the x0010.c file. You should check to make sure it does exist in your PY source directories. I was told by JDE at the time I had this problem to just copy the file to the 'source' directories and then rebuild the package. This fix worked for me. You may have to copy it from another environment to your \\DEPSVR\B7333\PY7333\Source directory and to your \\DEPSVR\B7333\PY7333\package\PYA_SF\source directory if you are going to resubmit the same build again. If you do a new package build you will only need to copy the file to your \\DEPSVR\B7333\PY7333\Source directory.

I hope this helps.

KD.

Thanks. I don't have the X0010.c file anywhere. The x0010.h file is where it should be, but it is completely empty. I checked each path code on all client machines, and none of them have the x0010.c file. Any other suggestions? Thanks, Jeremy.

You may need to go into the Object Librarian and mark the object to be excluded from the package builds. My understanding is that the object is obsolete(used to be used for next numbers), but was not completely removed from the object librarian. If you go into OMW and add the object x0010 to a project at status 21, check it out, then open the design, go to 'Install/Merge codes' and see if you have 'Global build option' set to 'Not used in JDEGLOBAL' You will have to promote the checked in object to PY and then try your package.

KD

I did the above recommendation, and it was already marked in that manner. I'm just wondering why it is looking for this file now, but never was before. When I rebuilt the package from the Package History screen, I did get a specific error regarding not being able to find the x0010.c file in my PY7333 pathcode directory. As a temporary solution, I've created a blank file called x0010.c and placed it in both my path code and my package source directories. I kicked off another rebuild, so we will see if it works. I don't think it is actually trying to find the function inside the file, just trying to make sure the file exists (for some odd reason). Thanks, Jeremy.

Did you mention before that you had the x0010.h file? Perhaps it finds the .h file and then looks for the .c file. Perhaps the existance of the .h is causing the build to look for the .c ?

KD

According to PeopleSoft, the errors regarding the x0010.c file can be ignored. The real problem is actually related to the network communications, but I will keep looking into it and post my findings. Thanks for all of the help, Jeremy.

The x0010 is a red herring and can be ignored. There also used to be an x0005 error of the same type.

I have most often seen this caused by a port on a switch or a NIC that was set to autosense instead of full-duplex.

I noticed that my C drive on my Enterprise Server was out of space. That is most likely the problem. I got rid of 1.88 GB on there and rebuilt the package. It is not done yet, but I will post when it has completed. Thanks, Jeremy.

BUILD SUCCESSFUL! Insufficient drive space on my enterprise server was the culprit. Thanks for all of your advice and help. Jeremy.