cancel
Showing results for 
Search instead for 
Did you mean: 

How to reset SLS and start with Initialization again

Colt
Active Contributor
0 Kudos

Hi Folks,

just deployed SLS 3.0 SP1 on a multi instance AS Java and finished Initialization with Automatic PKI generation.

After click on Finish i received a timeout some minutes later.

Now SLS is showing issues:

If i click on Certificate Management Tab i receive the following exception:

Already tried following steps:

list_app | grep ecure

stop_app sap.com/SecureLoginServer

undeploy name=securelogin.ui vendor=sap.com

undeploy name=securelogin.ui.alias vendor=sap.com

undeploy name=securelogin.umep vendor=sap.com

undeploy name=SecureLoginServer vendor=sap.com

Checked D:\usr\sap\<SID>\J<xx>\j2ee\cluster\apps\sap.com for SecureLoginServer, nothing.

Then deployed again. The previous information still available and the Initialization doesn't occur - still same issue.

The system keeps the configuration data in the database of the SAP NetWeaver Application Server

Question: how can I completely remove SLS from the system and start from scratch?

Thanks,

Carsten

Accepted Solutions (1)

Accepted Solutions (1)

kuhnen
Explorer
0 Kudos

Hi Carsten,

the problem that you might be facing here is that Secure Login Server Admin Console is not being able to access its own Secure Login Server  key storage view (there is a key storage permission bug in some NW AS versions). Therefore, try to do the following:

1. Open Netweaver Administration console

2. Goto Configuration -> certificates and keys

3. On the upper side tab, choose security

4. Goto the "permission per domain" tab

5. type in "securelogin.ui"

6. choose "sap.com/securelogin.ui"

7. Press the button modify below, then "grant new permission"

8. A pop up window will appear, press here the "All Actions" checkbox.

9. Choose the "SecureLoginServer" View in the drop box below and press ok.

10. Press the save button (Important!)

This is grant all permission to the SLAC to read the key storage view. It that does not solve the problem, you can try to install it again and do the same procedure above before starting the init wizard again.

To initilize from scratch, you need to delete the SecureLoginServer node from the ConfigDB tool. If Secure Login Server does not find his configuration, it starts again the Initial Wizard.

By the way, what is the system version of you Java AS?

Hope this helps

Marcus

Colt
Active Contributor
0 Kudos

Thanks Marcus,

using the ConfigDB i was able to remove everything and solve the issue!!



Carsten

Answers (0)