cancel
Showing results for 
Search instead for 
Did you mean: 

SUM Javaonly update on Dual Stack

Former Member
0 Kudos


I have a ticket open with SAP but I wanted to get other peoples advice?

Background:

Windows\oracle

NW 731

SUM 1.0 SP09, PL4

Trying to update from SP00 to SP10

History of events:

Installed fresh 731.

Created Stack with MOPZ from source 731sp00 to 731SP10 dual stack

I dislike SUM so this is why the following, trying to be old school but now realize, SAP has us.

Implemented SP10 in ABAP via SPAM (completed)

Launched JSPM, it complained about the XML not matching installed components, found SLD sycn issues,resolved issue and generated a new XML&STACK.

Launched JSPM with new Stack/XML, I updated the JSPM tool from SP00 to SP10, reloaded it and found out SAP disabled the tool for no longer able to use.

Launch SUM(with great regret)

SUM Detects dual stack, complains the XML only contains JAVA update info and not ABAP. Of course, ABAP was at SP10(latest) when I recreated the new XML.

CLosed SUM and launched with with SUM\startup.bat javaonly switch

SUM moved on, did notice still dual stack but only cared to update the JAVA stack.

I was able to make it to phase 5.6 Execution, system hangs on running Step RESTART SYSTEM FOR JAVA-ONLY.

The timeout is 7200, so after it, message I get is SUM cannot restarts instance 02.

Stuck here, options is to ignore but need a password from SAP.

Log looks like this.

Jan 16, 2014 11:49:40 AM [Info  ]: Stopping instance number 0 on host SD01XXXXXX with timeout of 7200 seconds.

Jan 16, 2014 11:49:42 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:42 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:42 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:49:42 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:49:42 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:49:42 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:49:42 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:49:42 AM [Info  ]: Instance 0 on host SD01XXXXXX already stopped.

Jan 16, 2014 11:49:42 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:49:42 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:49:42 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:49:42 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:49:42 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:49:42 AM [Info  ]: The instance with number 0 on hostSD01XXXXXX was stopped after 1 seconds.

Jan 16, 2014 11:49:42 AM [Info  ]: Stop service for instance 0 on host SD01XXXXXX...

Jan 16, 2014 11:49:43 AM [Info  ]: Setting the credentials for userABC\JLBadm and a password.

Jan 16, 2014 11:49:43 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:43 AM [Info  ]: Wait for service for instance 0 on host SD01XXXXXX to stop...

Jan 16, 2014 11:49:44 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:44 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:46 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:46 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:47 AM [Info  ]: Service for instance 0 on host SD01XXXXXX has been stopped.

Jan 16, 2014 11:49:47 AM [Info  ]: Disable service for instance 0 on host SD01XXXXXX...

Jan 16, 2014 11:49:47 AM [Info  ]: Process ID 125, name sc.exe has been started.

Jan 16, 2014 11:49:47 AM [Info  ]:   Command line: sc.exe config SAPJLB_00 start= disabled

Jan 16, 2014 11:49:47 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\DISABLE_SERVICE_00_02.OUT

Jan 16, 2014 11:49:47 AM [Info  ]: Process ID 125 has been started.

Jan 16, 2014 11:49:47 AM [Info  ]: Waiting for process ID 125, name sc.exe to finish.

Jan 16, 2014 11:49:47 AM [Info  ]: Process ID 125, name sc.exe has been finished, exit code 0.

Jan 16, 2014 11:49:47 AM [Info  ]: Service for instance 0 on host SD01XXXXXX has been disabled.

Jan 16, 2014 11:49:47 AM [Info  ]: Enable service for instance 0 on host SD01XXXXXX...

Jan 16, 2014 11:49:47 AM [Info  ]: Process ID 126, name sc.exe has been started.

Jan 16, 2014 11:49:47 AM [Info  ]:   Command line: sc.exe config SAPJLB_00 start= auto

Jan 16, 2014 11:49:47 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\ENABLE_SERVICE_00_02.OUT

Jan 16, 2014 11:49:47 AM [Info  ]: Process ID 126 has been started.

Jan 16, 2014 11:49:47 AM [Info  ]: Waiting for process ID 126, name sc.exe to finish.

Jan 16, 2014 11:49:47 AM [Info  ]: Process ID 126, name sc.exe has been finished, exit code 0.

Jan 16, 2014 11:49:47 AM [Info  ]: Service for instance 0 on host SD01XXXXXX has been enabled.

Jan 16, 2014 11:49:47 AM [Info  ]: Restart service for instance 0 on host SD01XXXXXX...

Jan 16, 2014 11:49:49 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:49 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:50 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:50 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:51 AM [Info  ]: Start service for instance 0 on host SD01XXXXXX...

Jan 16, 2014 11:49:51 AM [Info  ]: Process ID 127, name sapcontrol.exe has been started.

Jan 16, 2014 11:49:51 AM [Info  ]:   Command line: H:\usr\sap\JLB\DVEBMGS00\exe\sapcontrol.exe -nr 0 -user ABC\JLBadm <SecureField> -function StartService JLB

Jan 16, 2014 11:49:51 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\SAPCONTROL_STARTSERVICE_00_02.OUT

Jan 16, 2014 11:49:51 AM [Info  ]: Process ID 127 has been started.

Jan 16, 2014 11:49:51 AM [Info  ]: Waiting for process ID 127, name sapcontrol.exe to finish.

Jan 16, 2014 11:49:52 AM [Info  ]: Process ID 127, name sapcontrol.exe has been finished, exit code 0.

Jan 16, 2014 11:49:52 AM [Info  ]: Wait for service for instance 0 on host SD01XXXXXX to start...

Jan 16, 2014 11:49:53 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:53 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:53 AM [Info  ]: Service for instance 0 on host SD01XXXXXX has been started.

Jan 16, 2014 11:49:53 AM [Info  ]: Wait for service for instance 0 on host SD01XXXXXX to start...

Jan 16, 2014 11:49:54 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:54 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:54 AM [Info  ]: Service for instance 0 on host SD01XXXXXX has been restarted.

Jan 16, 2014 11:49:54 AM [Info  ]: Stopping instance number 2 on host SD01XXXXXX with timeout of 7200 seconds.

Jan 16, 2014 11:49:55 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:55 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:55 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:49:55 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:49:55 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:49:55 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:49:55 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:49:55 AM [Info  ]: Instance 2 on host SD01XXXXXX already stopped.

Jan 16, 2014 11:49:55 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:49:55 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:49:55 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:49:55 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:49:55 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:49:55 AM [Info  ]: The instance with number 2 on host SD01XXXXXX was stopped after 1 seconds.

Jan 16, 2014 11:49:55 AM [Info  ]: Stop service for instance 2 on host SD01XXXXXX...

Jan 16, 2014 11:49:56 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:56 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:56 AM [Info  ]: Wait for service for instance 2 on host SD01XXXXXX to stop...

Jan 16, 2014 11:49:57 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:57 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:49:59 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:49:59 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:50:00 AM [Info  ]: Service for instance 2 on host SD01XXXXXX has been stopped.

Jan 16, 2014 11:50:00 AM [Info  ]: Disable service for instance 2 on host SD01XXXXXX...

Jan 16, 2014 11:50:00 AM [Info  ]: Process ID 128, name sc.exe has been started.

Jan 16, 2014 11:50:00 AM [Info  ]:   Command line: sc.exe config SAPJLB_02 start= disabled

Jan 16, 2014 11:50:00 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\DISABLE_SERVICE_02_02.OUT

Jan 16, 2014 11:50:00 AM [Info  ]: Process ID 128 has been started.

Jan 16, 2014 11:50:00 AM [Info  ]: Waiting for process ID 128, name sc.exe to finish.

Jan 16, 2014 11:50:00 AM [Info  ]: Process ID 128, name sc.exe has been finished, exit code 0.

Jan 16, 2014 11:50:00 AM [Info  ]: Service for instance 2 on host SD01XXXXXX has been disabled.

Jan 16, 2014 11:50:00 AM [Info  ]: Enable service for instance 2 on host SD01XXXXXX...

Jan 16, 2014 11:50:00 AM [Info  ]: Process ID 129, name sc.exe has been started.

Jan 16, 2014 11:50:00 AM [Info  ]:   Command line: sc.exe config SAPJLB_02 start= auto

Jan 16, 2014 11:50:00 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\ENABLE_SERVICE_02_03.OUT

Jan 16, 2014 11:50:00 AM [Info  ]: Process ID 129 has been started.

Jan 16, 2014 11:50:00 AM [Info  ]: Waiting for process ID 129, name sc.exe to finish.

Jan 16, 2014 11:50:00 AM [Info  ]: Process ID 129, name sc.exe has been finished, exit code 0.

Jan 16, 2014 11:50:00 AM [Info  ]: Service for instance 2 on host SD01XXXXXX has been enabled.

Jan 16, 2014 11:50:00 AM [Info  ]: Restart service for instance 2 on host SD01XXXXXX...

Jan 16, 2014 11:50:01 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:50:01 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:50:02 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:50:02 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:50:03 AM [Info  ]: Start service for instance 2 on host SD01XXXXXX...

Jan 16, 2014 11:50:03 AM [Info  ]: Process ID 130, name sapcontrol.exe has been started.

Jan 16, 2014 11:50:03 AM [Info  ]:   Command line: H:\usr\sap\JLB\DVEBMGS00\exe\sapcontrol.exe -nr 2 -user ABC\JLBadm <SecureField> -function StartService JLB

Jan 16, 2014 11:50:03 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\SAPCONTROL_STARTSERVICE_02_03.OUT

Jan 16, 2014 11:50:03 AM [Info  ]: Process ID 130 has been started.

Jan 16, 2014 11:50:03 AM [Info  ]: Waiting for process ID 130, name sapcontrol.exe to finish.

Jan 16, 2014 11:50:04 AM [Info  ]: Process ID 130, name sapcontrol.exe has been finished, exit code 0.

Jan 16, 2014 11:50:04 AM [Info  ]: Wait for service for instance 2 on host SD01XXXXXX to start...

Jan 16, 2014 11:50:05 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:50:05 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:50:05 AM [Info  ]: Service for instance 2 on host SD01XXXXXX has been started.

Jan 16, 2014 11:50:05 AM [Info  ]: Wait for service for instance 2 on host SD01XXXXXX to start...

Jan 16, 2014 11:50:07 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:50:07 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:50:07 AM [Info  ]: Service for instance 2 on host SD01XXXXXX has been restarted.

Jan 16, 2014 11:56:07 AM [Info  ]: Enable service for instance 2 on host SD01XXXXXX...

Jan 16, 2014 11:56:07 AM [Info  ]: Process ID 131, name sc.exe has been started.

Jan 16, 2014 11:56:07 AM [Info  ]:   Command line: sc.exe config SAPJLB_02 start= auto

Jan 16, 2014 11:56:07 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\ENABLE_SERVICE_02_04.OUT

Jan 16, 2014 11:56:07 AM [Info  ]: Process ID 131 has been started.

Jan 16, 2014 11:56:07 AM [Info  ]: Waiting for process ID 131, name sc.exe to finish.

Jan 16, 2014 11:56:07 AM [Info  ]: Process ID 131, name sc.exe has been finished, exit code 0.

Jan 16, 2014 11:56:07 AM [Info  ]: Service for instance 2 on host SD01XXXXXX has been enabled.

Jan 16, 2014 11:56:07 AM [Info  ]: Start service for instance 2 on host SD01XXXXXX...

Jan 16, 2014 11:56:07 AM [Info  ]: Process ID 132, name sapcontrol.exe has been started.

Jan 16, 2014 11:56:07 AM [Info  ]:   Command line: H:\usr\sap\JLB\DVEBMGS00\exe\sapcontrol.exe -nr 2 -user ABC\JLBadm <SecureField> -function StartService JLB

Jan 16, 2014 11:56:07 AM [Info  ]:   Standard out: H:\usr\sap\JLB\SUM\sdt\log\SUM\SAPCONTROL_STARTSERVICE_02_04.OUT

Jan 16, 2014 11:56:07 AM [Info  ]: Process ID 132 has been started.

Jan 16, 2014 11:56:07 AM [Info  ]: Waiting for process ID 132, name sapcontrol.exe to finish.

Jan 16, 2014 11:56:07 AM [Info  ]: Process ID 132, name sapcontrol.exe has been finished, exit code 0.

Jan 16, 2014 11:56:07 AM [Info  ]: Wait for service for instance 2 on host SD01XXXXXX to start...

Jan 16, 2014 11:56:08 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:56:08 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:56:08 AM [Info  ]: Service for instance 2 on host SD01XXXXXX has been started.

Jan 16, 2014 11:56:08 AM [Info  ]: Starting instance number 2 on host SD01XXXXXX with timeout of 7200 seconds.

Jan 16, 2014 11:56:09 AM [Info  ]: Setting the credentials for user ABC\JLBadm and a password.

Jan 16, 2014 11:56:09 AM [Info  ]: Setting the service timeout to 300 s.

Jan 16, 2014 11:56:09 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:09 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:09 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:09 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:09 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:09 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:09 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:09 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:09 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:09 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:09 AM [Info  ]: Starting instance number 2 on host SD01XXXXXX with timeout of 7200 seconds.

Jan 16, 2014 11:56:09 AM [Warning]: The instance could not be started. Will retry after a pause of 15 seconds.

Jan 16, 2014 11:56:24 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:24 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:24 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:24 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:24 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:24 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:24 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:24 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:24 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:24 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:24 AM [Info  ]: Starting instance number 2 on host SD01XXXXXX with timeout of 7200 seconds.

Jan 16, 2014 11:56:24 AM [Warning]: The instance could not be started. Will retry after a pause of 15 seconds.

Jan 16, 2014 11:56:40 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:40 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:40 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:40 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:40 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:40 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:40 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:40 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:40 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:40 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:40 AM [Info  ]: Starting instance number 2 on host SD01XXXXXX with timeout of 7200 seconds.

Jan 16, 2014 11:56:40 AM [Warning]: The instance could not be started. Will retry after a pause of 15 seconds.

Jan 16, 2014 11:56:55 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:55 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:55 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:55 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:55 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:55 AM [Info  ]: All retrieved instances : 3

Jan 16, 2014 11:56:55 AM [Info  ]: Correctly detected instance: 1 on host SD01XXXXXX

Jan 16, 2014 11:56:55 AM [Info  ]: Correctly detected instance: 2 on host SD01XXXXXX

Jan 16, 2014 11:56:55 AM [Info  ]: Correctly detected instance: 0 on host SD01XXXXXX

Jan 16, 2014 11:56:55 AM [Info  ]: Instance has status STOPPED.

Jan 16, 2014 11:56:55 AM [Info  ]: Starting instance number 2 on host SD01XXXXXX with timeout of 7200 seconds.

Jan 16, 2014 11:56:55 AM [Warning]: The instance could not be started. Will retry after a pause of 15 seconds.

Jan 16, 2014 2:00:32 PM [Info  ]: The status of instance 2 on host SD01XXXXXX is STOPPED.

Jan 16, 2014 2:00:32 PM [Error ]: Start of instances exceeded the timeout of 7200s.

Jan 16, 2014 2:00:32 PM [Warning]: The instance could not be started. Will retry after a pause of 15 seconds.

Jan 16, 2014 2:00:47 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number 2.

The instance with number 2 on host SD01XXXXXX could not be started within the specified timeout.

.

Questions:

1-Anyone see anything?

2- I have manually restarted the instances several times during this process just to see if the system would catch it but not sure if its in the shadow instance at this time.

3- During Step2, enter credentials for SIDADM, if at this point I put in the wrong password, when clicking next, would it verify then? Im almost concerned maybe its a password for the service?

4- Because its a dual Stack, and I ran SUM with javaonly switch, could this be causing the issue? I did read the switch was only supported for SOLMAN, but common, other systems like this require it also.

Any feedback?

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Advisor
Advisor
0 Kudos

Jan 16, 2014 2:00:32 PM [Warning]: The instance could not be started. Will retry after a pause of 15 seconds.

Jan 16, 2014 2:00:47 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number 2.

What is instance number 2 ?

What system is this ?

If the system number is 2 for the Java stack then check the trace files in the work directory why the system fails to start.

Regards

RB

Former Member
0 Kudos

I forgot to mention, yes its started and running, yet SUM won't detect it? im really leaning towards the ABAP only switch

Former Member
0 Kudos
Reagan
Advisor
Advisor
0 Kudos

If the system is running the I would restart SUM and see if that helps.

Unfortunately as there is no indication to what the system is, I cannot be precise here.

As far as I know Dual stacks are no longer supported (apart from Solution Manager and SAP PI).

Regards

RB

Former Member
0 Kudos

I rebooted the entire server, started everything over again and its continuing to hang.

Look for other options? Can i clean and stop SUM at this point? Or am I too far in?

I did a backup fo the DB prior, but would that be enough? I have a good notion to restore the entire server prior to installing ABAP SP10 stack and doing it all via SUM, but if I land at the same point again i might go crazy.

SAP only stopped dual stack support as of NW 7.4 I believe.

Reagan
Advisor
Advisor
0 Kudos

Hello Joshua

I wouldn't reset the upgrade and start it all over again.

If the SAP system is running and the SUM tool is not able to detect it then I would check the logs for the SUM on top of the upgrade logs. I would also check the event viewer logs.

Raise an OSS message under BC-UPG-TLS and get the support guys involved.

Also check the solution for the "second error" mentioned in this thread

Upgrade Portal from NW 7.0 to NW 7.31 | SCN

Regards

RB

Former Member
0 Kudos

RB, You are thinking this might help?

The second error

Error: Could not start SAP instance with number 79. Could not send the command to start the instance with number 79 on host fmgepx. No instance was found in the system instances list with number 79 and host name fmgepx

The solution is to add the following rows:

SAPLOCALHOST = fmgepx

SAPLOCALHOSTFULL = fmgepx.munich-airport.de

in

/SUM/sdt/EPX/SYS/profile/EPX_JC78_fmgepx

and

/SUM/sdt/EPX/SYS/profile/EPX_SCS79_fmgepx

Then restart sapstartsrv

sapcontrol -nr 78 -function RestartService

sapcontrol -nr 79 -function RestartService

Check if the correct host is in the list.

sapcontrol -nr 78 -function GetSystemInstanceList

sapcontrol -nr 79 -function GetSystemInstanceList

Then repeat the failed step in SUM.

Reagan
Advisor
Advisor
0 Kudos

I would consider that suggestion and see if that helps.

Regards

RB

Former Member
0 Kudos

Odd, I dont have a shadow instance under SUM.

I thought at step 5.6 execution it did downtime to merge the shadow instance with the real instance.

How Can I not have a shadow instance at this point? OMG SUM is such a brutal tool.

Reagan
Advisor
Advisor
0 Kudos

If you are in the downtime phase then the SUM tool does the switch of the shadow instance with the main instance.

Have you checked the upgrade logs to know what phase you are on and the error you are getting ?

Regards

RB

Former Member
0 Kudos

Could it be a kernel issue maybe? When I built the system and downloaded all the packages, SAP gave me Kernel 720 and I had allot of issues, it wasn't till i read the PAM of 731 and as of 731, they dropped support for 720 and only support 720_ext. I downloaded it and installed it and my problem went away, but could I maybe have old files existing of 720? I mean i always do a copy over top, maybe either a file is missing or wrong version.

Any quick way to verify each file quickly?

Reagan
Advisor
Advisor
0 Kudos

sapcontrol -nr 00 -function GetVersionInfo

Run this as sidadm and check the output.

Replace 00 with the right system number.

Regards

RB

Former Member
0 Kudos

INTERESTING...

Logged in as SIDADM

Reagan
Advisor
Advisor
0 Kudos

This is due to problem with the sapstarsrv.

Restart the sapstartsrv service and see if that helps.

Also search for HTTP/1.1 401 on SMP and you will see few SAP note addressing this issue.

1563660 - sapcontrol, <sid>adm authorization issues (SUM)

1664214 - Upgrade is not able to start or stop an instance because of an "HTTP error 401 Unauthorize...

1361528 - Error Message - FAIL: HTTP error, HTTP/1.1 401 Unauthorized

Regards

RB

Former Member
0 Kudos

I'm digging but I believe this might be my issue

service/protectedwebmethods = DEFAULT

Mine was set to =ALL, just changed and restarting instance

Reagan
Advisor
Advisor
0 Kudos

Cool. Let us see how it goes.

Regards

RB

Former Member
0 Kudos

No that didnt work, let me dig into your OSS notes you posted.


Former Member
0 Kudos

service/protectedwebmethods = NONE

This seems to allow me now to use sapcontrol now./

I will try SUM AGain.

Former Member
0 Kudos

thank you for sharing, it fixed my problem

Answers (2)

Answers (2)

Former Member
0 Kudos

RB, let me know if you go to teched, i owe ya a beer.

Reagan
Advisor
Advisor
0 Kudos

What is the version of kernel you are using ?

Regards

RB

Former Member
0 Kudos

GOT IT!

Its currently deploying software components.

Kernel 720_ext PL 500