SPS update via SUM problem.

[Former Member]

Hi,

I am trying to update Solman 7.0 EHP1  SPS 20 to SPS 30 - Dual stack - using SUM.

I am stuck at the step 5.3 Configuration in the Java Stack.

The message states " An error has occurred during the execution of the Validate queue step.  Checking of deployment queue completed with error. java.lang.NullPointerException:"

But there are no further details.

here are the contents of /usr/sap/SPR/SUM/sdt/log/SUM/VALIDATE-QUEUE_04.LOG from my system:

------------------------

# more  /usr/sap/SPR/SUM/sdt/log/SUM/VALIDATE-QUEUE_04.LOG

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

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

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

<!--NAME[/usr/sap/SPR/SUM/sdt/log/SUM/VALIDATE-QUEUE_04.LOG]/-->

<!--PATTERN[VALIDATE-QUEUE_04.LOG]/-->

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

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

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

Dec 6, 2013 8:45:36 PM [Info  ]: Validating Java development components...

Dec 6, 2013 8:46:53 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.Jspm

ServiceException: Checking of deployment queue completed with error.

java.lang.NullPointerException:

.

------------------------

Java Trouble Ticket is:

---------------------------------

[-] Trouble Ticket / CSS Message Text

Expand this section for further troubleshooting details.

The Trouble Ticket (and this Process Report) can be used when creating a customer message.

Trouble Ticket Java

        Trouble Ticket Report

Update to SAP SOLUTION MANAGER 7.0 EHP 1

SID................: SPR

Hostname...........: naksprd1

Install directory..: /usr/sap/SPR

SUM directory......: /usr/sap/SPR/SUM/sdt

Database...........: ORA

Operating System...: UNX

JDK version........: 1.6.0_31 SAP AG

Source release.....: n/a

Target release.....: 7.01

ABAP stack present.: true

An error has occurred during the execution of the Validate queue step with action configure. Service com.sap.sdt.jspm.service.JspmService failed with the following message:

Checking of deployment queue completed with error.

You can find more information in the files /usr/sap/SPR/SUM/sdt/log/SUM/VALIDATE-QUEUE_04.LOG and ProcessOverview.html.

Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:

SUM,configure,create-queue,validate-queue,com.sap.sdt.jspm.service.JspmService,class com.sap.sdt.jspm.service.JspmServiceException

-----------------------------------------

Can someone please advise, where else can I see the error. why the que is not being validating, any other pointers?

Regards,

Yasir.

[Former Member]

This is just to update all of you that the probelm has been resolved.

SAP asked me to increase the trace of the tool by folllowing the below

steps and then repeat the phase and attach the trace file

from SUM/sdt/trc folder and SUM/java/trc folder .

- Stop SUM:

- From Menu select Update -> Stop Update

- Enable full tracing: edit SUM/sdt/prop/logging.properties

/System/Server/Upgrade.severity = INFO ->

/System/Server/Upgrade.severity = DEBUG

com.sap.sdt.severity = ERROR -> com.sap.sdt.severity = DEBUG

and SUM/java/param/logging.properties

com.sap.sdt.severity = ERROR -> com.sap.sdt.severity = DEBUG

and SUM/sdt/param/logging.properties

com.sap.sdt.severity = ERROR -> com.sap.sdt.severity = DEBUG

- Start again SUM and repeat the step

And then, they asked for the latest sdmcl* file from directory: /usr/sap/<SID>/DVEBMGS00/SDM/program/log/

That file showed the error that one of the archive was corrupted. I re-downladed that particular patch file again and the valide queue was successful.

Thanks to all for the help.

Regards,

Yasir.

[former_member45419]

Hi Khan,

Just follow what Ashutosh told ,stop all service of java and rename the server

And refer this links

http://scn.sap.com/docs/DOC-25113

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2012/11/07/software-update-ma...

Regards

Nayeem

[Former Member]

I did that, as mentioned earlier, but its not working.

[Former Member]

do you see same thing in the logs . Can you please post the logs and the STACK file.

Can you also explain what all steps were done.

Thanks

Rishi Abrol

[Former Member]

Logs are exactly the same.

stack.xml is attached.

All the 22 components, that java stack refer to, are present in the stack.xml directory as well.

Any other clue?

Yasir.

[Former Member]

Check free space in /usr/sap/SPR directory. Increase it if required.

[Former Member]

Hi,

This is what i see in the stack file.

So sync the data again with the sld and try to generate the stackfile.

I am sure if you go in SMSY of solution manager and then in your Solman system java then software component you would see these two patch in there.

Thanks

RishI Abrol

[former_member185239]

Hi Yasir,

Paste the logs for jspm and also open the process overview html file and check whether some componenet are getting mismatched.

Also try to open the JSPM and try to logon.

With Regards

Ashutosh Chaturvedi

[Former Member]

I am able to login to JSPM and reading the stack.xlm and the queue seems to be allright from here.

please see the attachment.

Yasir.

[former_member185239]

Hi Yasir,

Follow the steps :

1. stop the java instance.

2. Rename the Server0 file to server0_old (also rename the server<x> folders if you have more server node.

3. Restart the java instance

On restarting the java instance , it will create a new server<x> folder and this time it will create the binaries from the database.

Then resume the SUM tool.

Also follow the sap note

1891477 - PI 7.1X upgrade deployment process fails due to missing ExecutionDetails class

With Regards

Ashutosh Chaturvedi

[Former Member]

Thanks for your advise. I followed the steps that you mentioned; server0 folder has been recreated after the sap instance startup as well.

But, the SUM is giving the exact same error as stated earlier.

any other advise, please.

Yasir.

[Former Member]

Hi,

I can see that the Sum tool is detecting the initial release as n/a.

Source release.....: n/a

Can you please post the below logs.

/usr/sap/SPR/SUM/sdt/log/SUM/VALIDATE-QUEUE_04.LOG and ProcessOverview.html.

Can you also past the latest logs in the JSPM log directory.

Thanks

Rishi Abrol

[Former Member]

Please find attached three files.

Yasir.

ProcessOverview.html.txt.zip

VALIDATE-QUEUE_04.LOG.txt.zip

JSPM.LOG.txt.zip

[Former Member]

Hi,

When i check the Note related to Sum tools.

1790828 - Central Note - Software Update Manager 1.0 SP08 [lmt_004]

Upgrading to SAP Solution Manager 7.1 from the following upgrade paths:

• Upgrading from SAP Solution Manager 7.0
• Upgrading from SAP Solution Manager 7.0 EHP1

I dont see any line that if support pack stack is supported. and below is the message that i see in the logs. So i think this action is not supported.

"All" means that the corresponding upgrade or update path is not supported by this SUM version for all system topology types (ABAP, Java and Dual Stack)

Why dont you update the sp using the normal format ? I could think of using the sum tool if you were going to upgrade the solman 7.1.

Thanks

Rishi Abrol

[Former Member]

Thanks for your advise.

please see extract from note: 1843776 - Central Note - Software Update Manager 1.0 SP09 [lmt_005]

• Applying Support Packages Stacks to the following systems:

  • SAP Solution Manager 7.0 including enhancement package 1

Yes, I could use the normal path, but SUM is the future for all the updates and upgrades. If nothing will work then using spam & jspm would be workaround.

Regards,

Yasir.

[Former Member]

Hi,

Yes i can see in the later release Of Sum tool can patch Solman .

Just checking some more logs and found some file that might not be related to this Stack are in the directory.

Have you got installed the below two product in solution manager.

DICMS14_0-10005896.SCA

SAPBUILDT12_0-10005880.SCA

Thanks

Rishi abrol

[Former Member]

No, they are not there in my Solman.

JSPM was intelligent enough to pick the files whose corresponding components exist in the target ssytem.

Do you think SUM is giving the problem because of this? (Personally, I don't think so. But not sure, using SUM for the first time).

Regards,

Yasir.

[Former Member]

Hi,

In the logs i can see that so try to clean the directory and get the file that are defined in the Stack file. Did you check that are there any reference of these file in the stack file.

If there is no reference in the stack file then try to reset the upgrade and start again.

If you find the reference in the stack file than you need to generate new stack file

Thanks

Rishi abrol