What does this mean, and does that implied that some parts of the archive file cannot be extracted?
I use 7z 9.22 beta on Windows 7 SP1 x64 Ultimate.
Best Answer
I've just had this error message with an UpdraftPlus database backup file. My fix was to open up the .gz file in Notepad++. Delete the last word 'null' from the file, save it, then reopen it in 7-Zip and extract the file. Tested on two different .gz files. The extracted sql file looks good and imports into MySQL OK.
You will need to download the LMZA SDK from 7-Zip. The "installer.txt" file contains documentation:
7zSD.sfx is SFX module for installers. 7zSD.sfx uses msvcrt.dll.
SFX modules for installers allow to create installation program. Such module extracts archive to temp folder and then runs specified program and removes temp files after program finishing. Self-extract archive for installers must be created as joining 3 files: SFX_Module, Installer_Config, 7z_Archive.
Installer_Config is optional file. You can use the following command to create installer self-extract archive:
Config file contains commands for Installer. File begins from string
;!@Install@!UTF-8! and ends with ;!@InstallEnd@!. File must be written
in UTF-8 encoding. File contains string pairs:
ID_String="Value"
Title Title for messages
BeginPrompt Begin Prompt message
Progress Value can be "yes" or "no". Default value is "yes".
RunProgram Command for executing. Default value is "setup.exe". Substring %%T will be replaced with path to temporary folder, where files were extracted
Directory Directory prefix for "RunProgram". Default value is ".\"
ExecuteFile Name of file for executing
ExecuteParameters Parameters for "ExecuteFile"
For example:
;!@Install@!UTF-8!
Title="7-Zip 4.00"
BeginPrompt="Do you want to install the 7-Zip 4.00?"
RunProgram="setup.exe"
;!@InstallEnd@!
Best Answer
I've just had this error message with an UpdraftPlus database backup file. My fix was to open up the .gz file in Notepad++. Delete the last word 'null' from the file, save it, then reopen it in 7-Zip and extract the file. Tested on two different .gz files. The extracted sql file looks good and imports into MySQL OK.