EHP1 Installation - error during the XML stack file check.

Question

Hello SAP fans and gurus.
I'm updating CRM with EHP1 and I'm stuck at the phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML. Something wrong with the XML stack file. I get this error:
Severe error(s) occured in phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML!
Last error code set: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
The trouble ticket isn't saying much, but I'll post it anyway:
This trouble ticket was created by SAPehpi on 20110520102342
SAPehpi broke during phase SUBMOD_EXTENSION_NEW/SELSTACKXML in module PREP_EXTENSION / Extension module for start release >= 40B
Error Message: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
Summary of SAPehpi:
SAPehpi Release:     lmt_001
SAPehpi Version:     40.005
Start Release:          701
Target Release:          701
Summary of host system details:
SID:               CRM
Host:               sapvmcrm
MS Host:          sapvmcrm
GW Host:          sapvmcrm
Start Path:          /usr/sap/CRM/DVEBMGS00/exe     
Kernel Path:          /usr/sap/CRM/DVEBMGS00/exe
Summary of operating system details:
OS Type:          Linux X86_64
OS Version:          2.4
Summary of database details:
Database Type:          ada
Database Version:     7.7.07.014
Summary of RFC details:
Host:               sapvmcrm
GW Host:          sapvmcrm
Client:               000
Destination:          CRM
Language:          
System No.:          00
There's one problem with the file SAPEXEDB_82-10007250.SAR, which was in the download basket, but is not available for download. I deleted the record in the XML stack file and tried the phase again... with no success. Going through the XML file and checking if the packages have been downloaded is a real pain in the ***.
Anyway, can I somewhere download this file SAPEXEDB_82-10007250.SAR?
Or can anyone help me, how solve this issue different way?
Thanks a lot in advance.
-Stefan

Answer 1

OK, I got it. Wrong installation number. We had to change the installation number in the stack file according the system in the Solution Manager via transaction SMSY. Then it worked like a charm.