cancel
Showing results for 
Search instead for 
Did you mean: 

JSPM could not stop system

Former Member
0 Kudos

We have upgraded NW CE7.2 kernel to SP100(7.20.3710.69682.20090922144234)

and JSPM to SP 06 (1000.7.20.6.0.20110921183200) in win 2008 R2 (Oracle 11g)

After this upgrade we are getting the below error while upgrading other

components through JSPM,

"Cannot stop system. Could not stop system ECQ. Could not execute

operating system process for action check stopped on instance 00. Process

ID is 41, process name is sapcontrol. Return code condition success

evaluated to false for process sapcontrol for action check stopped."

Please provide us some help.

Regards,

Raja

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Please check if the following thread helps.

Regards,

Varun

Former Member
0 Kudos

Hi Varun,

Thanks for the reference.

I have referred the thread and provided access to startsapsrv file.

But while executing the below command, it is not giving out any message like OK or Action Failed. It is totally wierd.

sapcontrol -host <shorthostname> -nr <instancenumber> -user <sidadm> <password> -function AccessCheck Stop

Please let me know if there is any other changes required in Windows 2008 server.

Thanks.

Warm Regards,

Raja

pushkar_dhale
Participant
0 Kudos

We have HA setup I had the exact problem.

I resolved issue by following steps:

1. updated the scs instance profile with parameter "service/hostname=hostname or packacge" e.g jdbciDSU

2. updated application/dialog instance profile with parameter "service/hostname=hostname or packacge" e.g jd64DSU

3.After kernel upgrade ensure file permission for sapuxuserchk and sapstartsrv in three places especially in HA environment like Please note sapcpe cannot set the s-bit automatically after upgrade for sapuxuserchk. Please ensure Sapuxuserchk is owned by root to prevent overwriting:

Example:

a.Sapuxuserchk:

i./usr/sap/DSU/J64/exe/sapuxuserchk (shared with JC64)

ii./usr/sap/DSU/JC64/exe/sapuxuserchk

iii./usr/sap/DSU/SCS61/exe/sapuxuserchk

b.Sapstartsrv:

i./usr/sap/DSU/J64/exe/sapstartsrv

ii./usr/sap/DSU/JC64/exe/sapstartsrv

iii./usr/sap/DSU/SCS61/exe/sapstartsrv

As root change ownership and set S-bit permissions as show below in both instance exe and SCS exe:

#-> chown root:sapsys sapuxuserchk

root@jd64DSU:/usr/sap/DSU/J64/exe#

#-> chmod u+s,o-rwx sapuxuserchk

root@jd64DSU:/usr/sap/DSU/J64/exe#

#-> chown root:sapsys sapuxuserchk

root@jdbciDSU:/usr/sap/DSU/SCS61/exe#

#-> chmod u+s,o-rwx sapuxuserchk

root@jdbciDSU:/usr/sap/DSU/SCS61/exe#

Test SAPCONTROL program by executing below command as sidadm:

/usr/sap/dSU/SCS61/exe/sapcontrol -nr 61 -host <ip address> -user dsuadm <passwd> -function Stop

It should return OK.

I also had problem with sidadm password it had special character '@' which was also contributing to the problem.

All the best!

Answers (0)