Skip to Content
0

jstart.exe status info unavailable color yellow

Oct 17, 2017 at 06:57 PM

202

avatar image
Former Member

Hi all,

I made an upgrade from SAP Kernel 711 to SAP Kernel 721 ext.

In the SAP MMC console I get the jstart.exe process with the status "info unavailable" and color is yellow, reviewing the developer trace it appears that the instance is "All processes running" and to enter the console of SAP MII and NWA all is working without problems.

so, the unique problem is the color yellow is not updating the status and color to green

Please your help in resolving this case.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Manuel Garcia
Oct 18, 2017 at 07:40 AM
0

Hi Diego,

Java instance status is read by sapstartsrv.exe (in SAP service SAP<SID>_<inst. nr> from shared memory.

You can check that all executables for the instance have the same version with OS command :

sapcontrol -nr XX -function GetVersionInfo

If this is not the problem and all executables have the same version then you can try to check if a restart of the service helps. You can restart the service at OS level or running the OS command:

sapcontrol -nr XX -function RestartService.

This will restart only the sapstartsrv, not the whole system.

Best regards,

Manuel

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

I have executed the command "sapcontrol -nr XX -function GetVersionInfo" and found that sapstartsrv.exe has a higher version than the others. The problem will be by the version of sapstartsrv.exe?

<>:\usr\sap\<>\<>\exe\sapstartsrv.exe, 721, patch 913, changelist 1776967, opt, NTAMD64, 2017 07 26

<>:\usr\sap\<>\<>\exe\gwrd.exe, 721, patch 801, changelist 1730403, optU (EXT), NTAMD64, 2017 01 04

<>:\usr\sap\<>\<>\exe\icman.exe, 721, patch 801, changelist 1730403, optU (EXT) , NTAMD64, 2017 01 04

<>:\usr\sap\<>\<>\exe\sapwebdisp.exe, 721, patch 801, changelist 1730403, optU (EXT), NTAMD64, 2017 01 04

<>:\usr\sap\<>\<>\exe\jcontrol.exe, 721, patch 801, changelist 1730403, optU (E XT), NTAMD64, 2017 01 04

<>:\usr\sap\<>\<>\exe\jlaunch.exe, 721, patch 801, changelist 1730403, optU (EX T), NTAMD64, 2017 01 04

<>:\usr\sap\<>\<>\exe\jstart.exe, 721, patch 801, changelist 1730403, optU (EXT ), NTAMD64, 2017 01 04

Regards,

Diego.

0
Manuel Garcia
Oct 18, 2017 at 02:16 PM
0

Hi Diego,

Yes, it is different and it can be the cause of the problem.

You can check if sapstartsrv.exe included in the kernel package SAPEXE.SAR for kernel upgrade is different from the sapstartsrv.exe shown in the kernel directory.

Regards,

Manuel

Share
10 |10000 characters needed characters left characters exceeded