cancel
Showing results for 
Search instead for 
Did you mean: 

Stack error using SUM Tool

Former Member
0 Kudos

Hi,


We are trying to update the SP stack for our CRM Java system (CRM 7.0 EHP3). After generating a stack (SPS04) via maintenance optimizer and using with SUM, we encounter the following error:


Error: The system description in the provided stack.xml does not match

your system. In the stack, the described release 740 is different from

release 731, which is detected in your system. Generate a new stack.xml

that matches your system


We are indeed on 740 release for Basis, and stack too generated for the same, but SUM tool sees a different version 731. Any advice on this would be helpful.


Regards,

Naga


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All,

Issue has been resolved.

As expected, issue isn't with the Stack.

The folder structure at OS isn't correct under '..\j2ee\cluster\bootstrap\'. Had to patch SERVERCORE component in accordance with KB article 1794179, and Voila!

Naga

Former Member
0 Kudos

Hi All,

Please help me with exactly the same error.

I have read SAP Note 1794179 and copy CORETTOLS, BASETABLES and all other components described in this note to new folder. Restart SUM and say 'Manually prepared durectory' and select directory with Java Core components. But SUM says me ' Component sap.com/CORE-TOOLS cannot be updated to higher SP level, Components sap.com/CORE-TOOLS is part of SAP stack definition file'.

How you update your CORETOOLS step-by-step? Does I need to generate new stack for this components only?

Former Member
0 Kudos

Hi Alexander,

Since the issue occurred at the stack selection screen for me, after checking the note, i just selected the 'Manually Prepared Directory' option and pointed to the directory where the SCAs are downloaded as described in the note. And SUM tool completed the process.

Checking the current component version for the mentioned components in the note, and downloading the patches to the same version might help.

Former Member
0 Kudos

Hi all,

We have similar problem about the differents releases:

Error:

The system description in the provided stack.xml does not match your system. In the stack, the described release 702 is different from release 701, which is detected in your system. Generate a new stack.xml that matches your system.


I had checked the versions and the versions below are in release 702:

  • BASETABLES
  • J2EEFRMW
  • ENGINEAPI
  • SERVERCORE
  • CORETOOLS
  • J2EE-APPS*

Anybody how to solve this problem?

Thanks in advance,

Cheung

former_member185239
Active Contributor
0 Kudos

Hi Cheung,

Follow the below steps:

- You need to push the data from java system to SLD

-  resync the LMDB with SLD.

- Genarate the stack.xml again.

In the meantime , Paste the component version of the java system.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ashutosh,

Hereby the component version of the Java system:

sap.com ADSSAP 7.02 SP13 (1000.7.02.13.2.20130321191503) SAP AG SAP AG 20140319110328
sap.com BASETABLES 7.02 SP13 (1000.7.02.13.0.20130124091700) SAP AG SAP AG 20140319095655
sap.com BI_MMR 7.02 SP13 (1000.7.02.13.0.20130124103738) SAP AG SAP AG 20140319110408
sap.com BI_UDI 7.02 SP13 (1000.7.02.13.1.20130520115616) SAP AG SAP AG 20140319110528
sap.com CAF 7.02 SP13 (1000.7.02.13.0.20130129044842) SAP AG MAIN_NW702P13_C 20140319111040
sap.com CAF-KM 7.02 SP13 (1000.7.02.13.0.20130129042818) SAP AG MAIN_NW702P13_C 20140319121221
sap.com CAF-UM 7.02 SP13 (1000.7.02.13.0.20130129044847) SAP AG MAIN_NW702P13_C 20140319111114
sap.com CORE-TOOLS 7.02 SP13 (1000.7.02.13.2.20130301051449) SAP AG SAP AG 20140319100116
sap.com EP-PSERV 7.02 SP13 (1000.7.02.13.16.20131028092534) SAP AG SAP AG 20140319193141
sap.com EP-WDC 7.02 SP13 (1000.7.02.13.0.20130128092520) SAP AG SAP AG 20140319115641
sap.com EPBC 7.02 SP13 (1000.7.02.13.0.20130128092218) SAP AG SAP AG 20140319112719
sap.com EPBC2 7.02 SP13 (1000.7.02.13.6.20130826104639) SAP AG SAP AG 20140319193151
sap.com ETPRJSCHEDULER 8.00 SP33 (1000.8.00.33.58.20120516131700) SAP AG SAP AG 20130727101927
sap.com JLOGVIEW 7.02 SP13 (1000.7.02.13.0.20130124091800) SAP AG SAP AG 20140319100305
sap.com JSPM 7.02 SP13 (1000.7.02.13.0.20130124091800) SAP AG SAP AG 20140319114726
sap.com KM-KW_JIKS 7.02 SP13 (1000.7.02.13.0.20130124104105) SAP AG SAP AG 20140319112740
sap.com KMC-BC 7.02 SP13 (1000.7.02.13.4.20130903124502) SAP AG SAP AG 20140319193218
sap.com KMC-CM 7.02 SP13 (1000.7.02.13.5.20131007060748) SAP AG SAP AG 20140319193306
sap.com KMC-COLL 7.02 SP13 (1000.7.02.13.3.20130926083803) SAP AG SAP AG 20140319193358
sap.com LM-PORTAL 7.02 SP13 (1000.7.02.13.0.20130129043328) SAP AG MAIN_NW702P13_C 20140319120140
sap.com LM-TOOLS 7.02 SP13 (1000.7.02.13.3.20131121075130) SAP AG MAIN_NW702P13_C 20140319200321
sap.com NET-PDK 7.02 SP13 (1000.7.02.13.0.20130128085100) SAP AG SAP AG 20140319114945
sap.com RTC 7.02 SP13 (1000.7.02.13.1.20130305183700) SAP AG SAP AG 20140319114948
sap.com RTC-STREAM 7.02 SP13 (1000.7.02.13.0.20130121220300) SAP AG SAP AG 20140319120144
sap.com SAP-EU 7.02 SP13 (1000.7.02.13.0.20130129043431) SAP AG MAIN_NW702P13_C 20140319121128
sap.com SAP-JEE 7.02 SP13 (1000.7.02.13.4.20130913132242) SAP AG SAP AG 20140319174331
sap.com SAP-JEECOR 7.02 SP13 (1000.7.02.13.13.20131017104229) SAP AG SAP AG 20140319175150
sap.com SAP_JTECHF 7.02 SP13 (1000.7.02.13.7.20131015082335) SAP AG SAP AG 20140319175449
sap.com SAP_JTECHS 7.02 SP13 (1000.7.02.13.13.20131106103907) SAP AG SAP AG 20140319190745
sap.com SWLIFECYCL 7.02 SP13 (1000.7.02.13.1.20130926110920) SAP AG MAIN_NW702P13_C 20140319200707
sap.com UMEADMIN 7.02 SP13 (1000.7.02.13.2.20130412072801) SAP AG MAIN_NW702P13_C 20140319113727
sap.com UWLJWF 7.02 SP13 (1000.7.02.13.12.20131031092216) SAP AG SAP AG 20140319200853
sap.com VCBASE 7.02 SP13 (1000.7.02.13.0.20130128092742) SAP AG SAP AG 20140319121310
sap.com VCFLEX 7.02 SP13 (1000.7.02.13.0.20130128092805) SAP AG SAP AG 20140319121223
sap.com VCFRAMEWORK 7.02 SP13 (1000.7.02.13.0.20130128092810) SAP AG SAP AG 20140319121228
sap.com VCKITGP 7.02 SP13 (1000.7.02.13.0.20130128092811) SAP AG SAP AG 20140319121312
sap.com VCKITXX 7.02 SP13 (1000.7.02.13.0.20130128092811) SAP AG SAP AG 20140319121314
sap.com WDEXTENSIONS 7.02 SP13 (1000.7.02.13.0.20130129043535) SAP AG MAIN_NW702P13_C 20140319121424
former_member185239
Active Contributor
0 Kudos

Hi Cheung,

- Run the transaction LMDB

- Enter the java system SID

- Click on the software and check the software component list and also do paste the screenshot.

Also do attach the stack.xml file

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Thanks Ashutosh for your help!

The transaction LMDB is in Solution Manager?

The stackfile i attached

former_member185239
Active Contributor
0 Kudos

Hi CF,

You need to run the transaction in solman. Whats your solman version?

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ashutosh,


The Solman is on 3rd-party its not on our site.

I'll pass.


Thanks Ashutosh!

Former Member
0 Kudos

Hi Ashutosh,


The synchronization is done and stackfile is create it again, but still error in SUM.


In de SUM-folder in log DETERMINE-ENGINE-RELEASE_02.LOG, we can see "AS Java release is 701" but we don't know which component(s) is 701, how too find that?


<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/P11/SUM/sdt/log/SUM/DETERMINE-ENGINE-RELEASE_02.LOG]/-->

<!--PATTERN[DETERMINE-ENGINE-RELEASE_02.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Nov 20, 2014 7:00:33 PM [Info  ]: Checking AS Java release using version command.

Nov 20, 2014 7:00:33 PM [Info  ]: The tool has not been found in location: /usr/sap/P11/DVEBMGS11/j2ee/cluster/bootstrap/scripts/version.sh.

Nov 20, 2014 7:00:33 PM [Info  ]: Checking AS Java release using jspm tool.

Nov 20, 2014 7:00:33 PM [Info  ]: The tool have been found in location /usr/sap/P11/DVEBMGS11/j2ee/JSPM.

Nov 20, 2014 7:00:33 PM [Info  ]: AS Java process ID 15, name com.sap.sdt.jspm.main.Jspm has been started.

Nov 20, 2014 7:00:33 PM [Info  ]:   Command line: /usr/sap/P11/SUM/jvm/jre/bin/java -cp .:/usr/sap/P11/DVEBMGS11/j2ee/JSPM/lib/sdt_jspm.jar com.sap.sdt.jspm.main.Jspm -rootdir=/usr/sap/P11/DVEBMGS11/j2ee/JSPM -logdir=/usr/sap/P11/DVEBMGS11/j2ee/JSPM -v

Nov 20, 2014 7:00:33 PM [Info  ]:   Standard out: /usr/sap/P11/SUM/sdt/log/SUM/JSPM_ACTION_VERSION_NULL_02.OUT

Nov 20, 2014 7:00:33 PM [Info  ]: Process ID 15 has been started.

Nov 20, 2014 7:00:33 PM [Info  ]: Waiting for process ID 15, name java to finish.

Nov 20, 2014 7:00:43 PM [Info  ]: Process ID 15, name java has been finished, exit code 0.

Nov 20, 2014 7:00:43 PM [Info  ]: Process ID 15, name java has been terminated.

Nov 20, 2014 7:00:43 PM [Info  ]: AS Java release is 701.

Nov 20, 2014 7:00:43 PM [Info  ]: Saving data model JUP.J2EE.DataModel.xml ...

Nov 20, 2014 7:00:49 PM [Info  ]: Data model JUP.J2EE.DataModel.xml saved.

Nov 20, 2014 7:00:49 PM [Info  ]: Java upgrade product name detected:A1S.

Nov 20, 2014 7:00:49 PM [Info  ]: Java upgrade product version detected:SP0.

Nov 20, 2014 7:00:50 PM [Info  ]: Saving data model JUP.J2EE.DataModel.xml ...

Nov 20, 2014 7:00:53 PM [Info  ]: Data model JUP.J2EE.DataModel.xml saved.

Nov 20, 2014 7:00:53 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/AppSnapshotSupport.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:54 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/CleanupFilesystem.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:55 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/ComponentPredecessors.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:55 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/DetectionTasks.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:56 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/ExecuteTasksDepl.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:56 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/ExecuteTasksDepl_OS4.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:57 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/InitParameters.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:57 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/readme.txt has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:58 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/ReadSecureStore.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:58 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/SAPJVMTasks.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:59 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/SAPJVMTasksSequence.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:00:59 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/SecStoreSuperUser.properties has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:00 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/SecStoreTasks.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:00 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/templates/AppSnapshotExport.xml has been copied to directory /usr/sap/P11/SUM/sdt/config/templates.

Nov 20, 2014 7:01:01 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/630,70x/config/templates/AppSnapshotImport.xml has been copied to directory /usr/sap/P11/SUM/sdt/config/templates.

Nov 20, 2014 7:01:01 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/ComponentSlots.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:01 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/ComponentsToKeep.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:02 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/ComponentsToUndeploy.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:02 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/readme.txt has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:02 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/ReadProfiles.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:03 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/SourceProductDefinition.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:03 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/SourceUsageDefinition.xml has been copied to directory /usr/sap/P11/SUM/sdt/config.

Nov 20, 2014 7:01:04 PM [Info  ]: File /usr/sap/P11/SUM/sdt/patch/source/70x/config/templates/Profile_J2ee_Addin_Start has been copied to directory /usr/sap/P11/SUM/sdt/config/templates.

Nov 20, 2014 7:01:04 PM [Info  ]: Bootstrapping configuration for 700 has been completed.

Nov 20, 2014 7:01:04 PM [Info  ]: Bootstrapping for release 700 has been completed.

Answers (4)

Answers (4)

MKI
Explorer
0 Kudos

Hello,

check your J2EE licenses in the Visual Admin.

Regards,

Mohamed

former_member182657
Active Contributor
0 Kudos

Hi Naga,

I suggest you to delete the system from the solution manager and re sync it again,but before resync try to first execute report AI_LMDB_EXTSID_CONSISTENCY under SE38 to resolve any inconsistencies and orphans.

Second execute report RLMDB_SYNC_TECHNICAL_SYSTEM to sync your technical systems with detailed trace.If possible share the trace with us.

Last need to generate the stack.xml again.

Hope this will help you.

Regards,

Gaurav

v_veeramalla
Active Participant
0 Kudos

Are planning update from CRM7.0 EHP3 (SP1/SP2/SP3) to SP4 ? or looking for upgrade to version CRM7.0 EHP3 ?

Provide your source and target component versions and also check your LMDB/SMYS/SLD for component information and check whether it's having same levels as your system(consistancy)

//Venkat V

Former Member
0 Kudos

Hi Venkat,

Yes, from SPS03 to SPS04.

LMDB is in sysn with the actual components:

Component LocationComponent NameVendorVersion
SAP AGADSSAPsap.com1000.7.40.5.0.20131201164500
SAP AGAJAX-RUNTIMEsap.com1000.7.40.5.0.20131201164500
SAP AGBASETABLESsap.com1000.7.40.5.0.20131201164500
SAP AGBI-WDALVsap.com1000.7.40.5.0.20131201182100
SAP AGBI_UDIsap.com1000.7.40.5.0.20131201194200
MAIN_CRMX73V_CBPCRMAPPsap.com1000.733.0.0.0.20130507154415
MAIN_CRMX73V_CBPCRMFNDsap.com1000.733.0.0.0.20130507154424
SAP AGCFG_ZAsap.com1000.7.40.5.0.20131201164500
SAP AGCFG_ZA_CEsap.com1000.7.40.5.0.20131201164500
SAP AGCOMP_BUILDTsap.com1000.7.40.5.0.20131201193300
SAP AGCORE-TOOLSsap.com1000.7.40.5.0.20131201164500
MAIN_CRMX73V_CCRMAPPsap.com1000.733.0.0.0.20130507154426
MAIN_CRMX73V_CCRMFNDsap.com1000.733.0.0.0.20130507154416
SAP AGCU-BASE-JAVAsap.com1000.7.40.5.0.20131201193500
SAP AGCU-BASE-WDsap.com1000.7.40.5.0.20131201224100
SAP AGDATA-MAPPINGsap.com1000.7.40.5.0.20131201193500
SAP AGDI_CLIENTSsap.com1000.7.40.5.0.20131201164500
SAP AGECM-ADMINsap.com1000.7.40.5.0.20131201180500
SAP AGECM-APPSsap.com1000.7.40.5.0.20131201180500
SAP AGECM-COREsap.com1000.7.40.5.0.20131201180500
SAP AGECM-JEE-COMPsap.com1000.7.40.5.0.20131201180500
SAP AGECM-STOREsap.com1000.7.40.5.0.20131201180500
SAP AGENGFACADEsap.com1000.7.40.5.0.20131129220200
SAP AGENGINEAPIsap.com1000.7.40.5.0.20131201164500
SAP AGEP-ADMINsap.com1000.7.40.5.0.20131201194300
SAP AGEP-APPS-EXTsap.com1000.7.40.5.0.20131201194300
SAP AGEP-BASISsap.com1000.7.40.5.0.20131201194300
SAP AGEP-BASIS-APIsap.com1000.7.40.5.0.20131201194300
SAP AGEP-CONNECTIVITYsap.com1000.7.40.5.0.20131201194300
SAP AGEP-CONNECTIVITY-EXTsap.com1000.7.40.5.0.20131201194300
SAP AGEP-RUNTIMEsap.com1000.7.40.5.0.20131201194300
SAP AGEP-WPCsap.com1000.7.40.5.0.20131201194300
SAP AGEP_BUILDTsap.com1000.7.40.5.0.20131201193300
SAP AGESCONF_BUILDTsap.com1000.7.40.5.0.20131201193300
SAP AGESI-UIsap.com1000.7.40.5.0.20131201221700
SAP AGESMP_BUILDTsap.com1000.7.40.5.0.20131201193500
SAP AGESP_FRAMEWORKsap.com1000.7.40.5.0.20131201193300
SAP AGESREG-BASICsap.com1000.7.40.5.0.20131201193300
SAP AGESREG-SERVICESsap.com1000.7.40.5.0.20131201193300
SAP AGFRAMEWORKsap.com1000.7.40.5.0.20131201164500
SAP AGFRAMEWORK-EXTsap.com1000.7.40.5.0.20131201194200
SAP AGGROUPWAREsap.com1000.7.40.5.0.20131201194700
SAP AGJ2EE-APPSsap.com1000.7.40.5.0.20131201164500
SAP AGJ2EE-FRMWsap.com1000.7.40.5.0.20131201164500
SAP AGJSPMsap.com1000.7.40.5.0.20131201164500
SAP AGJWFsap.com1000.7.40.5.0.20131201194700
SAP AGKM-KW_JIKSsap.com1000.7.40.5.0.20131201194200
SAP AGKMC-BCsap.com1000.7.40.5.0.20131201194700
SAP AGKMC-CMsap.com1000.7.40.5.0.20131201194700
SAP AGKMC-COLLsap.com1000.7.40.5.0.20131201194700
SAP AGKMC-WPCsap.com1000.7.40.5.0.20131201194700
SAP AGLM-COREsap.com1000.7.40.5.0.20131201164500
SAP AGLM-CTSsap.com1000.7.40.5.0.20131201182100
SAP AGLM-CTS-UIsap.com1000.7.40.5.0.20131201164500
SAP AGLM-MODEL-BASEsap.com1000.7.40.5.0.20131201182100
SAP AGLM-MODEL-NWsap.com1000.7.40.5.0.20131201182100
SAP AGLM-PORTALsap.com1000.7.40.5.0.20131201222500
SAP AGLM-SLDsap.com1000.7.40.5.0.20131201182100
SAP AGLM-TOOLSsap.com1000.7.40.5.0.20131201222500
SAP AGLMCFGsap.com1000.7.40.5.0.20131201182100
SAP AGLMCTCsap.com1000.7.40.5.0.20131201182100
SAP AGLMNWABASICAPPSsap.com1000.7.40.5.0.20131201182100
SAP AGLMNWABASICCOMPsap.com1000.7.40.5.0.20131201182100
SAP AGLMNWABASICMBEANsap.com1000.7.40.5.0.20131201182100
SAP AGLMNWACDPsap.com1000.7.40.5.0.20131201182100
SAP AGLMNWATOOLSsap.com1000.7.40.5.0.20131201222500
SAP AGLMNWAUIFRMRKsap.com1000.7.40.5.0.20131201182100
SAP AGMESSAGINGsap.com1000.7.40.5.0.20131201193300
SAP AGMMR_SERVERsap.com1000.7.40.5.0.20131201194200
SAP AGMOIN_BUILDTsap.com1000.7.40.5.0.20131201164500
SAP AGNET-PDKsap.com1000.7.40.5.0.20131201194300
SAP AGNWTECsap.com1000.7.40.5.0.20131201182100
SAP AGODATA-CXF-EXTsap.com1000.7.40.5.0.20131201182100
SAP AGRTCsap.com1000.7.40.5.0.20131201194700
SAP AGRTC-STREAMsap.com1000.7.40.5.0.20131201194700
MAIN_CRMX73V_CSAP-CRMAPPsap.com1000.733.0.0.0.20130507154419
MAIN_CRMX73V_CSAP-CRMDICsap.com1000.733.0.0.0.20130507154421
MAIN_CRMX73V_CSAP-SHRAPPsap.com1000.733.0.0.0.20130507154422
SAP AGSAP-XI3RDPARTYsap.com1000.7.40.5.0.20131201193300
SAP AGSAP_BUILDTsap.com1000.7.40.5.0.20131201164500
SAP AGSECURITY-EXTsap.com1000.7.40.5.0.20131201164500
SAP AGSERVERCOREsap.com1000.7.40.5.0.20131201164500
SAP AGSERVICE-COMPsap.com1000.7.40.5.0.20131201193500
SAP AGSOAMONBASICsap.com1000.7.40.5.0.20131201221700
SAP AGSR-UIsap.com1000.7.40.5.0.20131201221700
SAP AGSUPPORTTOOLSsap.com1000.7.40.5.0.20131201164500
SAP AGSWLIFECYCLsap.com1000.7.40.5.0.20131201222500
SAP AGUDDIsap.com1000.7.40.5.0.20131201193300
SAP AGUISAPUI5_JAVAsap.com1000.7.40.5.0.20131201164500
SAP AGUKMS_JAVAsap.com1000.7.40.5.0.20131201221700
SAP AGUMEADMINsap.com1000.7.40.5.0.20131201182100
SAP AGUWLJWFsap.com1000.7.40.5.0.20131201194700
SAP AGVC70RUNTIMEsap.com1000.7.40.5.0.20131201194600
SAP AGWD-ADOBEsap.com1000.7.40.5.0.20131201164500
SAP AGWD-APPSsap.com1000.7.40.5.0.20131201193500
SAP AGWD-RUNTIMEsap.com1000.7.40.5.0.20131201164500
SAP AGWD-RUNTIME-EXTsap.com1000.7.40.5.0.20131201193500
SAP AGWSRMsap.com1000.7.40.5.0.20131201193300

Issue here is with the SUM tool, as far i can say.

Stack generated fine, and is in sync with the installed components. Any advice?

Regards,

Naga

v_veeramalla
Active Participant
0 Kudos

Can you also check in Solman , whether it is maintained ans SIDECAR or HUB system

  • Hub: Technical systems that you have assigned to the Hub landscape pattern are used by multiple product systems. During upgrades, the Maintenance Optimizer handles the system as a shared system and only application updates are installed, while the underlying SAP NetWeaver platform is upgraded to the minimum version required.

Technical system is a sidecar, although more than one product sy - SAP Solution Manager - SAP Librar...

1620472 - MOpz: Different results over time in stack XML calculation

//Venkat V

Former Member
0 Kudos

Hi Venkat,


Our Java CRM system is added as 'sidecar' to the ABAP CRM system in LMDB, so stack generation part was correct.

Naga

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Naga,

Have you tried using latest SUM version ?

Was you system upgraded to EHP3 CRM 7 ? If yes, what was the process ?

Do you have a JAVA stack ? Can you share the components list and SP level ?

Regards,

Divyanshu

Former Member
0 Kudos

Hi Divyanshu,

We are using the latest SUM tool, version 1.0.11.3.

Ours is a new installation, Java system, EHP3 for CRM 7.0. Now we are updating it to SPS04. (Currently it is on SPS03 stack).

Regards,

Naga

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Naga,

I need one more info:

goto below URL and open

http://<host>:<http_port>/utl/UsageTypesInfo

Are the usage type correct ?

Former Member
0 Kudos

Hi Divyanshu,

Active Usage Types  :

Product Code  UT Code  Short Name  Description 

CRM  BP-CRM-FND  BP CRM FND  Business Packages Foundation (Portal Content) 

CRM  BP-CRM  BP CRM  Business Packages (Portal Content) 

CRM  JCRM  JCRM  CRM Application Server Java 

NetWeaver  AS  Application Server Java Extensions  Application Server Java Extensions 

NetWeaver  EP  Enterprise Portal  Enterprise Portal 

NetWeaver  EPC  EP Core - Application Portal  EP Core - Application Portal 

NetWeaver  BASIC  Application Server Java  Application Server Java 

NetWeaver  ADOBE  Adobe Document Services  Adobe Document Services 

NetWeaver  NW-MODEL  NW-MODEL  NW Product Description 

Regards,

Naga