SUM fails in Phase 5.2 with task VALIDATE_MSS_PORT for NW 7.30 ?

[Former Member]

Hi everybody,

During patch preparation phase 5.2 - Configuration SUM tries to read the Profiles and fails to find a task in the ReadProfiles.xml:

Details from UseCaseExec.log:

Mar 17, 2014 7:39:41 PM [Info]: Evaluation pre-condition SourceVersion == "700" || SourceVersion == "630" of step detect

-high-availability-system.

Mar 17, 2014 7:39:41 PM [Info]: Pre-condition SourceVersion == "700" || SourceVersion == "630" of step detect-high-avail

ability-system resulted in true.

Mar 17, 2014 7:39:41 PM [Info]: Step Detect HA system started.

Mar 17, 2014 7:39:41 PM [Info]:  Step type is com.sap.sdt.executor.step.StepExecutor.

Mar 17, 2014 7:39:41 PM [Info]: Changed the execution state of Step detect-high-availability-system from INITIAL to RUNN

ING.

Mar 17, 2014 7:39:41 PM [Info]: Service log file is /usr/sap/L2P/SUM/sdt/log/SWITCH/DETECT-HIGH-AVAILABILITY-SYSTEM_01.L

OG

Mar 17, 2014 7:39:41 PM [Info]: Starting execution of Step Step ID: detect-high-availability-system

Service Ref: com.sap.sdt.j2ee.services.servicesimpl.EngineInfoService

Operation: detectHighAvailabilitySystem

Can Revoke: true

Display Name: Detect HA system

Can Reset: false

Step Parameters Map: {}

.

Mar 17, 2014 7:39:41 PM [Info]: Loaded parameters for operation detectHighAvailabilitySystem.

Mar 17, 2014 7:39:41 PM [Info]: Successfully executed operation detectHighAvailabilitySystem.

Mar 17, 2014 7:39:41 PM [Info]: Start handling of result from operation detectHighAvailabilitySystem.

Mar 17, 2014 7:39:41 PM [Info]: Result from operation detectHighAvailabilitySystem successfully stored to data repositor

y.

Mar 17, 2014 7:39:41 PM [Info]: Changed the execution state of Step detect-high-availability-system from RUNNING to COMP

LETED.

Mar 17, 2014 7:39:41 PM [Info]: Finished execution of step detect-high-availability-system.

Mar 17, 2014 7:39:41 PM [Info]: Evaluation pre-condition Scenario == "SWITCH_UPGRADE" of step validate-ms-port.

Mar 17, 2014 7:39:41 PM [Info]: Pre-condition Scenario == "SWITCH_UPGRADE" of step validate-ms-port resulted in true.

Mar 17, 2014 7:39:41 PM [Info]: Step Validate message server port started.

Mar 17, 2014 7:39:41 PM [Info]:  Step type is com.sap.sdt.executor.step.StepExecutor.

Mar 17, 2014 7:39:41 PM [Info]: Changed the execution state of Step validate-ms-port from INITIAL to RUNNING.

Mar 17, 2014 7:39:41 PM [Info]: Service log file is /usr/sap/L2P/SUM/sdt/log/SWITCH/VALIDATE-MS-PORT_01.LOG

Mar 17, 2014 7:39:41 PM [Info]: Starting execution of Step Step ID: validate-ms-port

Service Ref: com.sap.sdt.j2ee.services.servicesimpl.TaskExecutorService

Operation: executeTask

Can Revoke: true

Display Name: Validate message server port

Can Reset: false

Step Parameters Map: {0=Parameter

Type: in

Index: 0

Reference: null

Value Type: string

Value: ReadProfiles.xml

Is password: false

dataModelStorage: false

Entries: []

, 1=Parameter

Type: in

Index: 1

Reference: null

Value Type: string

Value: VALIDATE_MSS_PORT

Is password: false

dataModelStorage: false

Entries: []

}

.

Mar 17, 2014 7:39:41 PM [Info]: Loaded parameters for operation executeTask.

Mar 17, 2014 7:39:41 PM [Info]: Changed the execution state of Step validate-ms-port from RUNNING to ABORTED.

Mar 17, 2014 7:39:41 PM [Error]: The following problem has occurred during step execution: java.lang.reflect.InvocationT

argetException.

Mar 17, 2014 7:39:41 PM [Info]: Changed the execution state of Module detect-system from RUNNING to ABORTED.

Mar 17, 2014 7:39:41 PM [Error]: A problem has occurred: com.sap.sdt.executor.exception.StepExecutionException: Problem

while trying to execute operation on service  validate-ms-port. The following problem has occurred java.lang.reflect.Inv

ocationTargetException. CSN Component BC-UPG-TLS-TLJ.

Error while executing Task with input file ReadProfiles.xml and task VALIDATE_MSS_PORT.

Task VALIDATE_MSS_PORT not found in configuration file ReadProfiles.xml.

.

Mar 17, 2014 7:39:43 PM [Info]: Zip file /usr/sap/L2P/SUM/sdt/log/errorReport.zip with collected logs created succesfull

y.

---------

and this ist the logfile VALIDATE-MS-PORT_01.LOG:

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

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

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

<!--NAME[/usr/sap/L2P/SUM/sdt/log/SWITCH/VALIDATE-MS-PORT_01.LOG]/-->

<!--PATTERN[VALIDATE-MS-PORT_01.LOG]/-->

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

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

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

Mar 17, 2014 7:39:41 PM [Info  ]: Configuration has been built from input file /usr/sap/L2P/SUM/sdt/config/ReadProfiles.

xml.

Mar 17, 2014 7:39:41 PM [Info  ]: Global configuration has been built from input file /usr/sap/L2P/SUM/sdt/config/ReadPr

ofiles.xml.

Mar 17, 2014 7:39:41 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagEx

ception: Error while executing Task with input file ReadProfiles.xml and task VALIDATE_MSS_PORT.

Task VALIDATE_MSS_PORT not found in configuration file ReadProfiles.xml.

.

As far as I know, this task should try to read rdisp/msserv from the instance profile. This parameter is set in the SCS profile

But according to the process report this task should only be performed when the system is 700.

In the SUM directory there exist several versions of ReadProfiles.xml depending on basis release. The valid copy in the working directory ./sdt/config/ReadProfiles.xml is a copy from the file ./sdt/patch/source/71x,72x,73x,74x/config/ReadProfiles.xml for releases >700, but the check procedure VALIDATE_MSS_PORT is only contained in the 700 version stored in ./sdt/patch/source/70x/config/ReadProfiles.xml

So why tries SUM to check the configuration needed for 700, but takes the correct ReadProfiles.xml? Ever met this error before?

Regards Ralf

[Former Member · Accepted solution]

So to give you the final soultion:

These errors were caused by the use of an old XML-file. There had been an upgrade from 7.00 to 7.30 in January, and now we should apply the newest patches to fix some errors.

But someone deleted the XML File, and we accidentally picked the old one for the upgrade.

Despite of complaining that the XML did not fit to the current System release, SUM mixed everything up and tried checksw for 7.0 on a 7.3 System.

So we used a "plain directory" instead of an XML-File patching, and everything was fine...

[Former Member]

Current status is: I used SUM 1.0 SP10 and got different errors:

1. In "Specify credentials" the sapcontrol service certificate was not trusted.Since the SUM documentation here is somehow obscure I failed in locating and ex/importing the correct certificate. Therefore I disabled secure connection in /usr/sap/<SID>/SUM/sdt/param/jump_config.txt
2. Afterwards I got until 5.3 where READ_INSTANCE_PROPS failed. Looks like SUM still tries to check "old" parameter values that don't exist in 7.30 any more.

So: Until now just "new" error messages for the old problem.

[former_member185239]

Hi Ralf,

What is the version SUM you are using.

With Regards

Ashutosh Chaturvedi

[Former Member]

Sorry, forgotten this detail 1.0_09 Patch 8

So it's rather new ...

[former_member185239]

Hi Ralf,

Can you please give a try SUM 1.0 SP 8.

and in the mean time please attached the default profile and ReadProfiles.xml

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi Ralf Schulz,

             I am facing the same issue while i am upgrading the patches for NW731.Please let me know you have any solution for this problem.

Regards,

Jeevanandan

[former_member187565]

Hi Joshi, Ralf,

Try to use SUM 1.0 SP10 and check whether you pass these phase or not.

Regards,

Rafikul