cancel
Showing results for 
Search instead for 
Did you mean: 

SUM Error Could not detect AS Java release

Former Member
0 Kudos

Hi

We are upgrading Enterprise Portal from 7.02 to 7.40 using latest SUM
(1.0 SP12) and getting error right in the beginning "Specify Credentials" phase when we start SUM
tool:

   


      Could not detect AS Java release. Return
      code condition success evaluated to false for process
      e:\usr\sap\DP2\JC01\j2ee\cluster\bootstrap\scripts\version.bat for
      action ACTION_VERSION.

   

   


      DETECT  input_credentials  input-credentials-dialog  determine-engine-release  com.sap.sdt.j2ee.services.servicesimpl.EngineInfoService  class
      com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetectionException

   

 

We have already tried the below:


- 1681776 - Update fails with - Could not detect AS Java release.
- 2084188 - Could not detect AS Java release
- Set service/protectedwebmethods = DEFAULT in default profile
- Rebooted Entire server (Sapstartsrv processes also restarted
obviously)

- Gave full Permission to cluster/bootstrap/scripts folder
- Checked JVM version in configtool, ENV JAVA_HOME, command prompt,
Java System Info, Instance Profile. JVM version looks good in all
aspects
- We do NOT have have SERVERCORE component installed as we are on 702. We also did not
have ..cluster/bootstrap/scripts folder earlier. So we created the "scripts"
folder manually under bootstrap and put the contents of attachment from OSS Note 1681776 inside
the scrips folder. Did not help before or after
- We are not able to apply SERVERCORE as we are on 7.02 and the minimum
I see in Marketplace is 710 and it is not accepted with SDM, JSPM or
Deploytool

Below is the content of DETERMINE-ENGINE-RELEASE_10.LOG

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


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


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


<!--NAME[J:\CDs\SUM\SUM\sdt\log\SUM\DETERMINE-ENGINE-RELEASE_10.LOG]/-->


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


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


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


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


Dec 17, 2014 4:38:34 PM [Info  ]: Checking AS Java release using version command.


Dec 17, 2014 4:38:34 PM [Info  ]: The tool have been found in location e:\usr\sap\DP2\JC01\j2ee\cluster\bootstrap\scripts\version.bat.


Dec 17, 2014 4:38:34 PM [Info  ]: Process ID 12, name e:\usr\sap\DP2\JC01\j2ee\cluster\bootstrap\scripts\version.bat has been started.


Dec 17, 2014 4:38:34 PM [Info  ]:   Command line: e:\usr\sap\DP2\JC01\j2ee\cluster\bootstrap\scripts\version.bat


Dec 17, 2014 4:38:34 PM [Info  ]:   Standard out: J:\CDs\SUM\SUM\sdt\log\SUM\VERSION_ACTION_VERSION_NULL_10.OUT


Dec 17, 2014 4:38:34 PM [Info  ]: Process ID 12 has been started.


Dec 17, 2014 4:38:34 PM [Info  ]: Waiting for process ID 12, name e:\usr\sap\DP2\JC01\j2ee\cluster\bootstrap\scripts\version.bat to finish.


Dec 17, 2014 4:38:36 PM [Info  ]: Process ID 12, name e:\usr\sap\DP2\JC01\j2ee\cluster\bootstrap\scripts\version.bat has been finished, exit code 2.


Dec 17, 2014 4:38:36 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetectionException: Could not detect AS Java release.


Return code condition success evaluated to false for process e:\usr\sap\DP2\JC01\j2ee\cluster\bootstrap\scripts\version.bat for action ACTION_VERSION.


.


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi this was resolved after upgrading SAP JVM to the latest patch.

Answers (0)