on 11-29-2012 7:14 PM
Hello communities,
We are in the step to upgrade our SRM System 5.5 to SRM 7.0 EHP2
We did the following :
1. Generate the XML via the MOPZ (Option Upgrade with Enhancement Package Installation)
2. Download all the files links to this XML stacks
The current release and the target release were well regognize. by the MOPZ
3. Put all the files in a download directory with the XML
4. Start the SUM (Software Update Manager 1.6)
5. Pass all the preparation steps
6. The source release and the target relese were well detected byt SUM
But in the phase PREP_INPUT/SELSTACKXML_ASK
I've got the following error :
ETQ373 parameter "EV_MESSAGE" = "The stack configuration is not valid for the system XXX, inst.-no. XXXXXXX"
In the log SELSTACKXMLA.LOG (I can see)
1 ETQ359 RFC Login to: System="XXX", AsHost="XXXX" Nr="00", GwHost="XXXXX", GwService="sapgw00"
2 ETQ232 RFC Login succeeded
4 ETQ010 Date & Time: 20121129154338
1 ETQ233 Calling function module "OCS_API_GET_STACK_INFO" by RFC
2 ETQ373 parameter "IV_STACK_GUID" = ""
2 ETQ373 parameter "IV_STACK_FILE" = "/usr/sap/XXX/SUM/abap/tmp/SMSDXML_XXX_20121128121003.255.xml"
1 ETQ234 Call of function module "OCS_API_GET_STACK_INFO" by RFC succeeded
4 ETQ010 Date & Time: 20121129154338
2 ETQ399 Table ET_CVERS_INITIAL (#0):
2 ETQ399 Table ET_CVERS_EXPORT (#0):
2 ETQ399 Table ET_CVERS_TARGET (#0):
2 ETQ374 parameter "EV_RC" = "8"
2 ETQ373 parameter "EV_MESSAGE" = "The stack configuration is not valid for the system XXX , inst.-no. XXXXXX"
4 ETQ399 ... Error reading stack info (rc = 8, reason = "The stack configuration is not valid for the system XXX , inst.-no. XXXXX")
4EETQ399 Stack configuration not useable: The stack configuration is not valid for the system XXX , inst.-no. XXXXX
So I'm wondering if it is really the good way to upgrade our SRM system ?
I used the upgrade guide for SRM 7.0 EHP2 Abap + upgrade guide for SRM 7.0 EHP2 Java + SUM Update Guide (+ some OSS notes) and I've found no trace about the "Export DVD", "Java DVD" etc...all set of DVD that I've used in the past for upgrading our ECC system (1 year ago).
Is that really the path to upgrade our SRM System ???
This sound strange for me that my system could be upgraded with so less bunch of files (93 files were downloaded with the XML), I have the feeling that it looks more the files needed for an EHP update but not for an update !
But then why in the "SUM" it's recommended to follow this path ???
Anyone has already use the "SUM" to do this kind or upgrade ?
Thanks a lot for your input 🙂
Dom./
Hello Dom,
I would first recommend you to check note 1134872.
Then, since the message error states that the configuration stack is not valid for system XXX, check if the SMSY informations is incorrect. Check in SMSY the installation number for that system. If this is not correct then you have to fix it and regenerated the XML filein MOPZ.
Best regards,
Blanca
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
First of all thank you Blanca for your answer !
Indeed I've already check this note.
But finally I've managed to find the root cause.
Here the solution
There was an issue in the XML file generated in DSM, I've found an inconsistency concerning the "System Number" that was assigned to "**** Not Yet***" in the *.txt & *.XML file.
I've found and fixed the inconsistency in the LMDB related to my system then I've regenerate the "XML" in my Solman.
I've restart from scratch the "SUM" and now the phase PREP_INPUT/SELSTACKXML_ASK passed successfully.
Kr,
Dom./
HI Dom,
I am facing similar issue while i am updating ECC6.0 to EHP5.I am getting same error as
ETQ373 parameter "EV_MESSAGE" = "The stack configuration is not valid for the system XXX, inst.-no. XXXXXXX"
Could you please more specific on *.XMl files that i need to look inot and in which system i can find these XML file ? is it in Solman ?
What is DSM and LMDB .please explain in detail regarding the files o look into.
Thanks,
Krishna
Hello Krishna,
DSM = My solution Manager (so don't be pertub by this).
You should do the following :
1. In your solution manager --> Start the TCODE LMDB
2. Then select the name of your system --> Edit
3. Check if the system number is correct otherwise correct it
Then regenerate a new XML (via the MOPZ) and restart from scratch the SUM.
At least this was solving my issue.
Dom
Hi Dom,
Can I ask you a question please regarding this upgrade?
I am currently completing the same upgrade and I have also generated the XML via the MOPZ (Option Upgrade with Enhancement Package Installation)
I’m in the process of downloading all the files for the XML stacks but I’m having some issues identifying the correct upgrade dvds. SUM will not recognised the kernel dvd from
the SRM 7.0 swdc.
By any chance do you still have a record of the upgrade DVD’s you used?
Can you advise me on the ID for the Kernel DVD. (win_x86_64, oracle)
thanks in advance,
colm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.