cancel
Showing results for 
Search instead for 
Did you mean: 

EHP5 Upgrade error during Extraction Phase

Former Member
0 Kudos

SAP ECC 6.0 EHP5 PRD system installed on MSCS.

OS: Windows 2008 R2 Bit Ent Ed.

DB: MS SQL Server 2008 R2 SP1

Now Planned for EHP5 Upgrade,

1. Downloaded Latest Kernel and Updated.

2. Latest EHPi installer download,

3. uncared and EHPi installer started,

In Extraction Phase, getting the error message,

Your message server host SAPR3P differs from your upgrade host R3PRD1.

Therefore you have to install a temporary license valid for the hardware key of host R3PRD1.

This is required for the shadow system and also for the system during the downtime where a temporary message server on R3PRD1 is run.

R3PRD1 is Node A host name

R3PRD2 is Node B host name

SAPR3P is Virtual host name.

License applied for both the node, as per hardware key and installation number.

Given full rights for the EHPi folder

Solution is apprieciated.

Thanks in advance,

Rajan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Rajan,

Takes into account the Thomas Fleer Post. I had a similar error and I aborted the upgrade with SAPehpi and used SUM (Software Update Manager).

You can easly reset the upgrade at this phase.

Regards,

Serafim Carvalho

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Rajan,

I had the same problem with SAPehpi patch 128 (and 129).

Afterwards I performed a reset of the upgrade and used the latest SUM 1.0 SP04 instead of the SAPehpi and it worked.

Regards

Thomas

0 Kudos

Hi Rajan,

This note could help you

96317   Hostnames during R/3 upgrade, tips & tricks

Regards,

Sriram

nicholas_chang
Active Contributor
0 Kudos

Hi Rajan,

I believe this is just a warning message and not error. You can ignore the message but ensure all instances are move to one single node before downtime.

Hope it helps,

Nicholas Chang

Former Member
0 Kudos

Hi Nicholas,

This is during Extraction Phase of EHP5 installer,

Error message displayed as:

Need write permission for the script file MSSUPGGETREL.SQL

Personalization failed for MSSUPGGETREL

Option: Continue or cancel

When Continue select and clicked ok,

Repeat Phase PREP_INPUT/INITPUT_PRE to continue at the point of stopped,

and if Cancel is clicked, following error message comes,

Unable to execute the SDT request ABAP operation extract on hostname r3prd1 instance 01 Extraction of the ABAP upgrade request ABAP has failed Error from unit observer Tool died unexpectedly with sapparam: sapargv(argc, argv) has not been called! sapparam(1c): No Profile used. sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline ERROR: File 'F:\EHPI\abap\bin\MSSUPGGETREL.SQL' does not exist: The system cannot find the file specified.

But EHPI installer folder has full rights, and while checking the EHPI/ABAP/LOG/Check, below content is seen,

<p><em>WARNING:</em> Your message server host SAPR3P differs from your upgrade host R3PRD1. Therefore you have to install a temporary license valid for the hardware key of host R3PRD1.</p>

<p>This is required for the shadow system and also for the system during the downtime where a temporary message server on R3PRD1 is run. </p>

Thanks in advance,

Rajan

nicholas_chang
Active Contributor
0 Kudos

Hi,

Is EHPI in your F:\ ? If yes, are you able to find MSSUPGGETREL.SQL in F:\EHPI\abap\bin\k

Is F:\ a cluster disk or local disK?

Former Member
0 Kudos

Hi,

MSSUPGGETREL.SQL not found in F:\EHPI\abap\bin

And F:\ is my Local drive.

naveen_kumar1
Active Participant
0 Kudos

Hi Rajan,

Please check if this note is of some help.

438031 Missing license with switch system upgrade

Regards,

Naveen.

nicholas_chang
Active Contributor
0 Kudos

Hi Naveen,

What user do you use? SIDadm?

Former Member
0 Kudos

Hi Nicholas,

User used is SIDADM (then only the java policy script runs & DServices.bat executed).

ECC 6.0 EHP5 Instance Details

Node A                                             Node B

ERS Instance ERS10                         ERS Instance ERS10

First Cluster Node                              Additional MSCS Node  ASCS00                                   

ABAP Central Instance ASCS00                  

Database Instance DVEBMGS01          Dialog Instance D01

Central Instance 01

Thanks in advance,

Rajan

nicholas_chang
Active Contributor
0 Kudos

Hi Rajan,

Besides the check log, please check last few last modified log in /abap/log

Have your move all resource to one single node? Perhaps you can try to reset the upgrade, delete EHPI folder and extract it again. Rerun EHPI and see how it goes.

Cheers,

Nicholas Chang

Former Member
0 Kudos

Hi Nicholas,

I have tried already the process which you have mentioned, deleted the ehpi folder, uncared newly the ehpi installer and tried the installation process still the same error.

In failover cluster, I have paused the Node 2, and EHPi installer is running from node 1.

Thanks in advance,

Rajan

Former Member
0 Kudos

Hi Naveen,

As per the snote,

saplicense -get gives the harwarekey for the system, but when saplicense -temp is executed, its asks for SID, and says no temp license available

Thanks in advance,

Rajan

Former Member
0 Kudos

Hi Nicholas/ Naveen,

Thanks for your valuable time: EHP5 upgrade started and running, I did following changes,

1. EHPi Installer used for EHP5 Upgrade was latest one downloaded from Service Market Place

SAPehpi_128-10005807.SAR

2. Now I stopped the EHPi Installation, and deleted the EHPI folder.

3. Used the EHPi Installer which was used earlier for DEV & QA EHP5 upgrade

SAPehpi_96-10005807.SAR

4. Given Full Rights for the folder EHPI

5. Paused the Node 2 in Failover Cluster

6. Started the EHPi installation with localhost option, now EHPi installation runs.

Thanks in advance,

Rajan

former_member189797
Active Contributor
0 Kudos

Hello,

Regarding the error :

---------------------------------------------------------------------------------

Need write permission for the script file MSSUPGGETREL.SQL

Personalization failed for MSSUPGGETREL

----------------------------------------------------------------------------------

This was a bug in the EHPI tool SAPehpi_128.SAR  &  SAPehpi_129.SAR . This was fixed in the SAPehpi_130.SAR . So kindly use the latest SAPehpi tool and you will not face the issue.

Hope this helps.

Regards,

Gaurav