Could not find key data. Cannot continue

Technical Articles ID: KB67044
Last Modified: 2021-02-23 17:41:14 Etc/GMT

Environment

McAfee Agent (MA) 5.x - supported non-Windows systems

For environment information, see KB51573 - Supported platforms for McAfee Agent 5.x.

Problem 1

If you install MA for non-Windows using the install.sh command, you see the following error:

root# ./install.sh -i
space required to copy archive is 10696 bytes
space available at mfe1530415304 is 212053873 bytes
extracting archive to mfe1530415304... please wait
151216+0 records in
151216+0 records out
10786745+0 records in
10786745+0 records out
Illegal Instruction - core dumped
cp: cannot access mfe1530415304/sitelist.xml
cp: cannot access mfe1530415304/srpubkey.bin
cp: cannot access mfe1530415304/reqseckey.bin
Could not find key data.Cannot continue
root# ls -l
total 43554
-rw-r--r-- 1 root sysadmin 10864027 Sept 26 10:03 MA400P1SOL.zip
-rw-r--r-- 1 root sysadmin 1388 Sept 26 10:03 PkgCatalog.z
-rw-r--r-- 1 root sysadmin 295 Sept 26 10:03 Replica.log
-rw------- 1 root root 445305 Sept 26 10:07 core
-rwxr-xr-x 1 root sysadmin 10942682 Sept 26 10:03 install.sh
drwxr-xr-x 2 root root 512 Sept 26 10:07 mfe1530415304
-rw-r--r-- 1 root sysadmin 4042Sept 26 10:03 setup

Problem 2

The Install.sh command on a Linux system records the following error:

Space required to copy archive is 39139924 bytes
space available at Delilah is 22750142464 bytes
extracting archive to Delilah... please wait
Archive: Delilah/package
inflating: Delilah/Mecum inflating: Delilah/presence. Failed to extract contexts of install package. Installer cannot continue

The following error can also be seen:

invalid compressed data to inflate

Cause

Text-only files are American Standard Code for Information Interchange (ASCII), whereas word-processing documents, image files, and data files are binary files.

Every byte is eight bits. In ASCII, a byte is made up of seven significant bits and an eighth, the insignificant bit is used for error control. Binary uses all eight bits as significant bits.

When a binary file is transferred in ASCII mode, every eighth bit can become corrupted and the file rendered unusable after the transfer. The following results apply:

When the operating systems on both ends of the file copy are using the same convention for the eighth error-checking bit, sending an ASCII file as binary works correctly most of the time
When there are different operating systems at either end of the file copy, the conventions can be mismatched and file corruption can occur.

Solution

Copy the file in binary mode to the affected computer. For more information about how to do this action, see your operating system documentation.

NOTE: The text of the error can vary based on the platform the installation is being installed on. The errors stated above are current samples.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Could not find key data. Cannot continue

Environment

Problem 1

Problem 2

Cause

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

Could not find key data. Cannot continue

Environment

Problem 1

Problem 2

Cause

Solution

Affected Products

Languages:

Choose your region

Title

Title