E1: PKG: Troubleshooting Package Build Compression - Information, FAQ and Common Errors about Package Compression (Doc ID 626327.1)

Last updated on JULY 16, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.

Purpose

This document provides detailed information, Frequently Asked Questions and describes common errors found when compressing a package. It was created to assist customers on troubleshooting the different scenarios, causes and resolutions for Package Build Compression Issues.
This information pertains to customers on EnterpriseOne Xe to 9.2.x applications release levels.

In addition, information about Package Compression is available in the Package Management Guide - Chapter 6 - Building Packages >> 6.1.5 Package Compression
Use this link here for the latest Package Management Guide, or refer to Oracle JD Edwards EnterpriseOne Tools Documentation - Release 9.1.x > Administration > Change Management Administration tab.

This document is part of an Information Center - to see other documents related to Package Management, please refer to the follwoing document:
Doc ID 1369078.2 - Information Center: Package Management in the JD Edwards EnterpriseOne Tools and Technology Product

Troubleshooting Steps

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Troubleshooting Steps

Information on Compressing Server Packages

How to Recompress Parent Packages

1 - Purpose of Recompressing the Full Parent Package

2A - Steps to Re-compress the Full Parent Package (E1 Applications Releases 8.12, and 9.x)

2B - Steps to Re-compress the Full Parent Package (E1 Applications Releases XE, ERP8.0, 8.9, 8.10 and 8.11x)

Frequently Asked Questions in Package Compression

General Questions

Question 1 - Where can I find a Log file when I have any Compression Errors?

Question 2: Parent Package Compression - Which Parent Package to Recompress for Update Packages?

Questions on Compression of Update/Full Server Packages

Question 1: Can user deploy COMPRESSED update server packages to server? Or should compression be done only for full server package?

Question 2: If user has 2 logic servers: SVR1 and SVR2. User build a full package on only Server 1 with "DoCompression=1" set in the jde.ini of the build machine (Deployment Server). User did not build this full package on SVR2. Then, user deployed the compressed full server package to both SVR1 and SVR2. Do user need to make sure that the full package needs to be built on both SVR1 and SVR2 before they can deploy the full package to both servers?

Question 3: If user has 2 logic servers: SVR1 and SVR2. User build a full package on only SVR1 with "DoCompression=1 " and had deployed this full package to both SVR1and SVR2. Then, users went ahead to build an update server package on only SVR1 without compression. Can they deploy this update server package to both servers SVR1 and SVR2 even though the update package was not built on SVR2?

Question 4: How does the server package build process determine the machine type (INTEL 5.2 or INTEL 6.1) when creating the directory where it will store the Compress.inf file and the servername.inf file?

Package Build Compression Errors on Specs Caused by Third Party Software

Package Compression Process Creating Multiple Spec.cab Files - Deployment of Those Files Not Expanding

Compress Error Message In Package Build CompressError.txt Log File - No Space Left On Device

Troubleshooting Package Compression

Issues on Package Compression Related to Client Packages

Scenario 1A - Client Full Package Build Fails with Compression errors - PKGCMP0013 ERROR: Failed to compress / PKGCMP0016 ERROR: Unknown error / PKGCMP0001 ERROR: Compression failed.

Scenario 1C - Client Package Build Fails to Compress System Foundation - Logs Generated Under System Folder Structure - PKGCMP0013 ERROR: Failed to compress / PKGCMP0016 ERROR: Unknown error / PKGCMP0001 ERROR: Compression failed.

Scenario 1D - Client Full Package Build Compression Errors on Include and Source folders - PKGCMP0013 ERROR: Failed to compress / PKGCMP0016 ERROR: Unknown error / PKGCMP0001 ERROR: Compression failed.

Scenario 2 - Compression Error in ClientPkgBuild.log for \java\sbf Folder - PKGCMP0013 ERROR: Failed to compress \\DEPSVR\E900\PY900\package\PY900FB\java\sbf.

Scenario 3 - Error on Compression during Client Full Package Build - FCIFlushCabinet() failed: code 4 [Could not create a temporary file]

Scenario 4A - Client Package Build Error On Compressing "OBJ" Directory - ERROR: Could not compress directory

Scenario 4B - After Updated Service Pack - Package Compression Error on System Folder - ERROR: Could not compress directory

Issues on Package Compression Related to Server Packages

Scenario 1 - Errors Compressing a Server Package - AS400 iSeries Platform

Other Available Solutions Related to Server Package Compression

Issues on Package Compression Related to Update Packages

Scenario 1 - Package Compression for Update Package Deployment Issues - Old TR Releases until TR 8.98

Scenario 2 - Update Package Build Error on HELPS Folder Compression - ERROR: Could not compress directory

Issues on Compression Related to Package Deployment and Client Install

Scenario 1 - Update Package Not Bringing Specs Down to Client Workstation - Update Package Built with Compression Option Checked

Scenario 2 - Problem with Local Databases Having Incorrect Pathcode Names

Scenario 3 - Server package deployment fails with DoCompression=1. Deploy fails to copy multiple bin32.cab files to Enterprise Server.

Other Available Solutions On Compression Issues Related to Package Deployment and Client Install

Issues Related to Packages Re-compression

Errors when Recompressing Parent Package - Could Not Create Cabinet File - [Windows] Delayed Write Failed

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.