on 02-22-2013 3:43 PM
Hi Folks,
I want to upgrade Solution manager 7.0 EHP 1 SPS 29 to Solution manager 7.1.
I used the maintenance optimizer to calculate the needed files by using calculate automatic option.
Then is error pop up:
ABAP queue check failed
The mandatory SP SAPK-20006INCTSPLUG for component CTS_PLUG rel. 200 is missing in the queue.
Do you know how to solve the issue?
Please shed some light.
Thanks
Hi,
I just checked and found that only till Patch 5 has been released for CTS PLUG 200 .
Since you would require SAPK-20006INCTSPLUG for the upgrade, I would suggest you to raise an OSS Message to SAP and request them on how to fix this.
They might give some corrections that you need to implement the TR in your system ...
Thanks and Regards,
Vimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think SAP is currently having problems calculating the XML stack for Solution Manager 7.1. The reason for it is that CTS Plug-In 2.0 will be standard starting with SP05 and since the plugin is not installed in the system it doesn't know how to handle it. I would expect SAP to provide a correction shortly. Meanwhile you could upgrade to SP04, install the plugin and update to SP07. It should work, I haven't tested it.
Hello,
We can't help with customer messages right now, the reason being, there is no code correction or workaround we can provide for individual customers.
Development Support is looking into the issue by debugging in the so-called SAP Service Backbone (the backend systems to which Maintenance Optimizer connects).
I will try to keep you updated.
Best regards,
Miguel Ariño
Hi,
The original error now is solved but then i encounter other error.
When i rerun the calculation, i got new error after select add on
products
ABAP queue check failed
The Installation/Upgrade Package for Add-on SAPTM rel. 101 is not
available
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
The issue is now solved, please try again with a new Maintenance Optimizer transaction.
Best regards,
Miguel Ariño
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
- When did you last download the note? The solution consisting in downloading the note again was communicated by development support at 16:38. The fact is, the note version was changed around that time, because the note's attributes clashed with the Maintenance Optimizer check for notes. So potentially anything before that would not change anything.
- Have you tried with a new Maintenance Optimizer transaction ? Even solving the issue, if you got the error in a transaction, it will still be there when you change it.
Best regards,
Miguel Ariño
Yes the problem still exists. I just re-downloaded, re-applied the note (this time version 3) and created a new MOPZ transaction. MOPZ is still complaining. Interresting that MOPZ is complaining of not having version 2, version 3 should make MOPZ happy. Maybe the note attributes are still off (equal instead of equal or higher). See the attached screenshot.
Hi,
Just had a reply from SAP, they have confirmed there is an issue with the SAP service backend systems. If you have an existing stack XML and the source and target systems to be upgraded are exactly identical then use report RPT_MOPZ_COPY_STACK_XML. This will copy the source xml to a target xml. See notes 1600302 & 1711612.
Didnt work for me unfortunately because my source and target systems have different components.
Good luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.