in some rare cases SDM reports, that another session is running, and after long and deep going analysis and questioning you decide, that actually nobody is connected to SDM really. So SDM is unreacheable to anyone (and a server that cannot be reached is not of much use). After clearing the fact that nobody is connected you come up with the idea, that you are about to “restart” the SDM Server, which can be done thru MMC Plugin (M.. Management Console) on Windows based systems.
But in the end it turns up, that you cannot restart you SDM server as long as a session is still connected to it.
But there is a way using the SDM command line tool.
if you have a look at \usr\sap\SID\INSTANCE\SDM\program\doc, you will find documentation for the SDM there.
One File, called SDMCommandLineDoe_en.pdf is particularly interesting for dealing with our topic because it further explains the uage and parameters of the commandline version.
the command relevant here reads as follows
sdm shutdown sdmhome=<…> sdmguiport=<…> [sdmhostname=<…>] [password=<…>] [shutdownmode=<…>]
- sdmhome: means the directory where SDM is located at (…program)
- sdmguiport: means the portyou would use in order to connect using remoteGui.sh
- sdmhostname: should be “localhost” in our case.
- password: your sdmpassword – eventhough optional needed here.
- shutdownmode: “abort” has to be used when “overriding” a connected session.
so a sample would look s.th. like
Please try every other solution, and make really sure that nobody is using SDM to avoid inconsistencies. !
>sdm shutdown sdmhome=/usr/sap/AB01/AB07/SDM/program sdmguiport=50104 sdmhostname=localhost password=sdmadmin shutdownmode=abort