503 Service Unavailable after solution manager upgrade from 7.0 to 7.1

[Former Member]

Hi,

I have upgraded solman production system 7.0 to 7.1 with patch level 13 upgrade completed succuss fully, after upgrade ABAP+JAVA all work process are showing green, when i try the web url http:/host:<port> , i am getting "503 Service Unavailable" and " You have requested an application that is currently stopped" I try to start the application from Visual admin
tool i am getting the warning " The J2ee Engine is running in safe mode and may not be fully operational to swith safe mode off, use the config tool and restart the J2ee Engine." but the config toll is not set as safemode."in the config tool safemode is already set to NO"

If i change the configtool setting to safe mode is "YES" it is working fine, and i am able to acess the all the web links web url http:/host:<port>,if i change it to back safemode setting to "NO" i am getting same issue.

Please let me know if anymore information.

Thanks,

Ramakrishna.

[Reagan · Accepted solution]

Hello

Check these first.

1267123 - System remains in SAFE mode after update

https://help.sap.com/saphelp_nw04/helpdata/en/43/1c3e6811a52d23e10000000a1553f7/content.htm

Could you provide the latest trace files (dev_server, std_server) from the work directory and also the latest default traces ?

Regards

RB

[Former Member · Accepted solution]

i have created  a OSS message immediatly i got the below reply from sap

During an update/upgrade operation the safe mode (and action mode) is

set

directly in the nodes, and not only globally. Probably the tool

responsible for the upgrade operation had some issue and did not turn

it off in the

particular nodes.

Open the Configtool and go to cluster-data ->

instance. There look

into server, you will still see the parameters

"-Dstartup.mode=SAFE"

and "-Dstartup.action=UPGRADE". The nodes from the

instance still

"think" they are in the middle of an upgrade operation. You can remove

this parameters, Save, and restart the cluster.

Do the same

for the Dispatcher node under Configtool -> cluster-data

-> instance

-> dispatcher.

I did the same changes in config tool it is working