cancel
Showing results for 
Search instead for 
Did you mean: 

Data unit C:\SAP_DOWNLOADS\51050166_1\DATA_UNITS\EXPORT_1 is not signed.

former_member561179
Discoverer

Dears,

I'm trying to install SAP ERP IDES Ehp7 on DB SYBASE and OS MS Windows Server 2016 using SWPM SP22 latest version.

It comes ti the screen asking for Installation Export 1 ECC 6.0 EhP7 SR2, then I browse to the correct path, it gives the following error.

Data unit C:\SAP_DOWNLOADS\51050166_1\DATA_UNITS\EXPORT_1 is not signed.

DETAILS: The found data unit must not be used.
SOLUTION: Ensure that you use the latest available version of Installation Export 1 ECC 6.0 EhP7 SR2 downloaded from the SAP Service Marketplace and ensure that its content is unchanged.

whatever I did, re-download, re-extract, re-browse, it stuck with the same error.

Please advise.

Thanks & Regards,

Muhammad

Accepted Solutions (1)

Accepted Solutions (1)

manianls10
Discoverer

The problem is within new SWPM since SP22 he needs a signature of the each export files. Please copy from the attachment all signature files to the corresponding folder after extracting than you can go further with installation. Contact SAP they will provide your the signature file for each export or you can direct message me for the same.

Former Member
0 Kudos

There is no file attached for download.

ceddejarme
Explorer
0 Kudos

Can you share with me the signature files? i also have the same issue.

former_member339387
Discoverer
0 Kudos

Can you share with me the signature files? i also have the same issue.

Jose Duarte

former_member44112
Participant
0 Kudos

I'm having the same problem. Which attachment are you referring to for SIGNATURE.SMF ? Can you please elaborate on the solution that works for you? Thanks.

former_member44112
Participant
0 Kudos

Hi all,

We have managed to address this problem.

Raised this issue with SAP as an incident and they've provided SIGNATURE.SMF files for each of the EXPORT_1 to EXPORT_11 dump folders; SAP provides the attachment (referred above) on the incident as a zip file; Just unzip it in a temporary folder and copy the SIGNATURE.SMF files under each of the EXPORT_1 to EXPORT_11 directories, and after doing this, retry sapinst. It will not issue the error highlighted above.

Hope that helps all looking for a solution on this issue.

Regards,

Rakesh Tripathi

former_member339387
Discoverer
0 Kudos

Thank you very much, for your prompt response

Jose Duarte

Former Member
0 Kudos

Hi Rakesh,

Please will you share the signature.smf files. I have already logged an incident with SAP two days ago and still no response.

Regards,

Ashraf

former_member44112
Participant
0 Kudos

Ashraf,

SIGNATURE.SMF files are dependent on the binaries downloaded. Therefore, best approach is to raise this with SAP Support citing the OS/Database you plan to use, and accordingly obtain a set of files that will work on your platform.

Rakesh

Former Member
0 Kudos

Thanks Rakesh

0 Kudos

Hi Can you provide with the

signature files

ERP 6.0 IDES ehp8 linux x86

OS SLES for SAP 15 sp01

DB hana 2.0 sp04 rev46

Regards

jat50b
Discoverer
0 Kudos

Can you share SIGNATURE.SMF for EHP8-HANA-IDES

51052029 (they are 21 files in the RAR).

0 Kudos

Can you share with me the signature files? i also have the same issue.

Thanks.

Answers (7)

Answers (7)

former_member44112
Participant
0 Kudos

You will have to raise an incident via SAP Support portal. Following that, a zip file containing the SIGNATURE.SMF files is provided by SAP Support. You need to copy these SIGNATURE.SMF files under respective folders (EXPORT_1 to EXPORT_11) and then retry installer.

fmilan
Discoverer
0 Kudos

Hello everyone,

The SAP Note 2622019 mentions that from SWPM SP22 each export media needs a separate signature file and to solve this issue an incident has to be submitted to SAP indicating the OS version and Database used for the IDES installation. Does anybody know if the signature files can be downloaded from the SAP Marketplace or any other website?

Thanks a lot,

Francisco.


.

former_member44112
Participant
0 Kudos

I don't think these files are downloadable via SAP Downloads (from where you've downloaded the binaries).

fmilan
Discoverer
0 Kudos

Thanks for your help Rakesh.


Best regards,


Francisco.

epalaf0z
Explorer
0 Kudos

Hey fellows,

Good evening.

I had the same problem.

I'm installing sap ecc 6.0 ehp7 ides on a VM with Oracle 12g.
I have this error:

Data unit XXX\Sap\51050166_Data\51050166_1\DATA_UNITS\EXPORT_1 is not signed.
DETAILS: The found data unit must not be used.
SOLUTION: Ensure that you use the latest available version of Installation Export 1 ECC 6.0 EhP7 SR2 downloaded from the SAP Service Marketplace and ensure that its content is unchanged.

How could i contact SAP or solve this problem ? Sap can provide signature file for each export ?

Thanks

former_member201157
Participant
0 Kudos

Hi All,

the correct answer is asking SAP for the Signature files as Rakesh mentioned .

Thanks & Best Regards,

Satya

alichtenau
Advisor
Advisor
0 Kudos

Hi all,


please check SAP Note 2510478 (Data unit /xx/xx/xx/SWPM is not signed with an official SAP signature) for more Information.


Best,
Andreas

former_member44112
Participant
0 Kudos

The solution suggested in this note doesn't work for the problem listed above.

strakowskik
Explorer
0 Kudos

It's true, solution form the note not resolve this problem.

BR

Krzysztof

former_member44112
Participant
0 Kudos

Hi Krzysztof,

Agree. To fix the issue, we raised an incident on which SAP Support have provided the signature files; these are required to be copied over under the export folders, and then retrying sapinst eliminates the issue.

Regards,

Rakesh

former_member201157
Participant
0 Kudos

Hi Experts,

what has worked here?

we too have same issue.

thanks,

Satya

former_member44112
Participant
0 Kudos

Hi,

Please see my updates above. SAP provides the signature files after raising the incident, that are required to be copied over under the export folders.

Regards,

Rakesh

former_member561179
Discoverer
0 Kudos

Hi Manian,

Thanks for your suggestion.

It works very well.

Thanks

Former Member
0 Kudos

Can you explain more on how it solved for you .. I facing same issue.

former_member339387
Discoverer
0 Kudos

you could be more precise about where the signature files are

Former Member
0 Kudos

how did you managed to solve the issue. you could be more precise about where the signature files are..

even i did not get the signature files in Exports with the latest download too? are you speaking about the signature files from SWPM archive?

former_member44112
Participant
0 Kudos

Hi,

We have managed to address this problem.

Raised this issue with SAP as an incident and they've provided SIGNATURE.SMF files for each of the EXPORT_1 to EXPORT_11 dump folders; SAP provides the attachment (referred above) on the incident as a zip file; Just unzip it in a temporary folder and copy the SIGNATURE.SMF files under each of the EXPORT_1 to EXPORT_11 directories, and after doing this, retry sapinst. It will not issue the error highlighted above.

Hope that helps all looking for a solution on this issue.

Regards,

Rakesh Tripathi