2615828 - Archive file '(...).SAR' did not match

During SAP system installation following warning appears:

Archive file '<path/to/archive/name.SAR' did not match. See info file.

You cannot continue with the selected service.

sapinst.log and ArchiveScanResults.[n].html under sapinst_instdir folder (default location on Windows: C:\Program Files\sapinst_instdir on UNIX: /tmp/sapinst_instdir) provides further details:

sapinst_log

Checking archive 'SAPEXEDB.SAR, part of the Kernel' ('SAPEXEDBMSS'): Not found
 Manifest Content
 -- '<path>\SAPEXEDB_300-70001663.SAR': Content of manifest file 'sapmanifestdb.mf' does not match requirement.
 Requirement: @keyname='SAP_KERNEL' and @kernel_os='NTAMD64' and @compilation_mode='UNICODE' and @kernel_db='MSS' and @kernel_release=//SAPEXE/@kernel_release and @kernel_patch_number>=//SAPEXE/@kernel_patch_number and @make_variant=//SAPEXE/@make_variant and ((@kernel_release=749 and @kernel_patch_number>=313) or (@kernel_release!=749)) and ((@kernel_release=753 and @kernel_patch_number>=15) or (@kernel_release!=753)) and ((@kernel_release=745 and @kernel_patch_number>=600) or (@kernel_release!=745))
 Manifest: keyvendor=sap.com; Manifest-Version=1.0; kernel_os=NTAMD64; kernel_release=749; keylocation=SAP AG; kernel_dbslversion=749.05; kernel_db=mss; compiled_for=64 BIT; compilation_mode=UNICODE; keyname=SAP_KERNEL; kernel_patch_number=300; make_variant=749_REL; downward-compatible_to=740 750 751 765
 Manifest File
 ok '<path>\SAPEXEDB_300-70001663.SAR': Archive contains manifest file 'sapmanifestdb.mf'.
 Dependency Check
 ok 'SAPEXE.SAR (any version supporting your release)' ('SAPEXE'): Dependency is available.

********************************
Automatically found Archives: -

ArchiveScanResults.[n].html

FileManifest FileManifest ContentResultD:\Install\Java Components\SAPEXEDB_300-70001663.SARoknot okContent of manifest file 'sapmanifestdb.mf' does not match requirement.

keyvendor=sap.com

Manifest-Version=1.0

kernel_os=NTAMD64

kernel_release=749

keylocation=SAP AG

kernel_dbslversion=749.05

kernel_db=mss

compiled_for=64 BIT

compilation_mode=UNICODE

keyname=SAP_KERNEL

kernel_patch_number=300

make_variant=749_REL

downward-compatible_to=740 750 751 765

@keyname='SAP_KERNEL' and

@kernel_os='NTAMD64' and

@compilation_mode='UNICODE' and

@kernel_db='MSS' and

@kernel_release=//SAPEXE/@kernel_release and

@kernel_patch_number>=//SAPEXE/@kernel_patch_number and

@make_variant=//SAPEXE/@make_variant and

((@kernel_release=749 and @kernel_patch_number>=313) or (@kernel_release!=749)) and

((@kernel_release=753 and @kernel_patch_number>=15) or (@kernel_release!=753)) and

((@kernel_release=745 and @kernel_patch_number>=600) or (@kernel_release!=745))

In the above example, kernel_patch_number=300 but kernel_patch_number>=313 is required; other requirements could be affected as well like kernel_os, compilation_mode, kernel_db, kernel_release, make_variant, etc.

Archive-Based SAP system installation using Software Provisioning Manager

SWPM, sapinst , KBA , BC-INS-SWPM , Installation with Software Provisioning Manager , BC-INS , Installation Tools (SAP Note 1669327) , Problem