E1: PKG: With Tools Releases 126.96.36.199 and Above, File Transfers to Server Require that Allowed File Extension Types Be Specified in JDE.INI
Last updated on JULY 17, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
Scenario 1: Building iSeries Server Packages with Compression Requires Allowed File Extension "NONE"
When using compression with a package build on an iSeries server, there is a need to transfer files that do not have any file extensions. In order to accommodate this requirement, the value "NONE" should be added to the allowedFileExtensions setting in the JDE.INI file.
Messages in the jde.log:
[PKGBLD] - Wed Aug 17 01:39:56 - spkgclnt.c:1989 PKGCLT0071 ERROR: Failed to compress. Error Server error..
4276/4424 FOREIGN_THREAD Wed Aug 17 01:41:59.573000 Netrcv.c868
Missing file extension for file in net message is not allowed.
4276/4424 FOREIGN_THREAD Wed Aug 17 01:41:59.573001 Netrcv.c885
Valid file extensions must be specified in the 'allowedFileExtensions' parameter in the JDE.INI. If files with no extention should be allowed, use the keyword 'NONE' within the extension list. If this parameter is changed, the system must be restarted for the new values to take effect.
4276/4424 FOREIGN_THREAD Wed Aug 17 01:41:59.573002 Netrcv.c1101
File '\\DENSVR\E900\DV900\package\DV900FE\obj\MODULE' will not be saved.
4276/4424 FOREIGN_THREAD Wed Aug 17 01:41:59.573003 Netrcv.c549
xx Bad packet header, bytes-1077952576, packet#-16448, type-64, flags-64
Scenario 2: Server Update Packages Containing UBE Changes Requires Allowed File Extension ".txt"
This issue is only for server update packages containing UBE changes. (The issue is not seen with full packages.) When submitting the package build, the process transfers files to the server, then when it attempts to transfer the UBEFile.txt to the server the connection is dropped. A message is sent to start the DLL build process, but no further build activities are carried out and a timeout message is received in the jde.log. The problem is with transferring the UBEText.txt file for the update package because the .txt file extension was not specified as being allowed. For the file to be transferred, the value ".txt" must be added to the allowedFileExtensions setting in the JDE.INI file.
Messages from the jde log:
\\DENSVR\E900\PY900\package\PYUP262D\UBEFile.txt to the server /slot/ems4776/appmgr/jdedwards/ow6081/packages/PYUP262D/text/UBEFile.txt.
Mon Sep 19 12:32:21 - spkgclnt.c:731 PKGCLT0032 ERROR: Failed to receive message. Error Timeout.
Mon Sep 19 12:32:21 - spkgutil.c:4373 WARNING: Failed to transfer UBEtext file
\\DENSVR\E900\PY900\package\PYUP262D\UBEFile.txt to the server. Spec cache not refreshed.
Messages from the SvrPkgBuild.log on the Deployment Server:
\\DENSVR\E900\PY900\package\PYUP9\UBEFile.txt to the server Z:\JDEdwards\E900\DDP\packages\PYUP9\text\UBEFile.txt.
spkgutil.c:4373 WARNING: Failed to transfer UBEtext file
\\DENSVR\E900\PY900\package\PYUP9\UBEFile.txt to the server. Spec cache not
Messages from the SvrPkgBuild.log on the Enterprise Server:
Fri Sep 16 14:01:52 - Detail file created successfully.
(...then nothing else is in the file after these messages)
Scenario 3: Full Packages for 8.11 or 8.11 SP1 Require Allowed File Extension ".pak"
Full packages for 8.11/8.11SP1 use pak files to transfer specs to the server during the build process. This will require the .pak file extension to be included in the allowed file extension types.
Scenario 4: UBE Submission Causes UBE Kernel to Zombie on Server: Requires Allowed File Extension ".spc"
This issue is only applicable to pre-8.12 application releases (i.e. those using non-xml specs) with Tools Release 188.8.131.52 or higher. When submitting a UBE from a fat client to a server, the process attempts to transfer specs to the server with file extension .spc. Because the file is blocked, the UBE causes the UBE kernel to zombie on the server. For the specification files to transfer successfully and allow the UBE to process, the value '.spc' must be added to the allowedFileExtensions setting in the JDE.INI file.
Messages from the associated jde_PID.log:
File extension '.spc' in net message is not allowed.
23122/1 MAIN_THREAD Thu Aug 4 02:55:02.738222 netrcv.c885
Valid file extensions must be specified in the
'allowedFileExtensions' parameter in the JDE.INI. If files with no extention
should be allowed, use the keyword 'NONE' within the extension list. If this
parameter is changed, the system must be restarted for the new values to take
23122/1 MAIN_THREAD Thu Aug 4 02:55:02.738733 netrcv.c1100
File 'Packed.spc' will not be saved.
23122/1 MAIN_THREAD Thu Aug 4 02:55:02.739503
xx Bad packet header, bytes-1694524416, packet#-11776, type-115,
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms