cancel
Showing results for 
Search instead for 
Did you mean: 

SDM Gui does not respone after input password problem.

Former Member
0 Kudos

Hi all,

I have a trouble of deploy SDA file use SDM GUI, After input password and click "Login" button, the Repository/Deployment/Undeployment menu bar never display back now and the cursor just in busy mode forever.

By the way , the port and account/pwd was correct, i deploy SDA File success several days ago.

If some give some advise? Or someone has other way to depoly SDA file to my server?

the SDM log

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7185 - 630]/>

<!NAME[C:\usr\sap\J2E\JC01\SDM\program\log\sdmlog20100915.log]/>

<!PATTERN[sdmlog20100915.log]/>

<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>

<!ENCODING[Cp1252]/>

<!LOGHEADER[END]/>

Sep 15, 2010 12:10:04... Info:

Sep 15, 2010 12:10:04... Info: ============================================

Sep 15, 2010 12:10:04... Info: = Starting to execute command 'server' =

Sep 15, 2010 12:10:04... Info: ============================================

Sep 15, 2010 12:10:04... Info: Starting SDM - Software Deployment Manager...

Sep 15, 2010 12:10:05... Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0009.20060817110748.0000

Sep 15, 2010 12:10:08... Info: SDM operation mode successfully set to: Integrated

Sep 15, 2010 12:10:10... Info: JStartupFramework is requesting to start the SDM Server.

Sep 15, 2010 12:10:10... Info: Start the SDM Server integrated in the JStartupFramework.

Sep 15, 2010 12:10:11... Info: Initializing Network Manager (50117)

Sep 15, 2010 12:10:11... Info: Starting SDM Server listening on port 50118

Sep 15, 2010 12:10:11... Info: SDM started successfully.

Sep 15, 2010 12:32:29... Info: Opened client connection to lenovo (IP address lenovo/192.168.0.150, remote port 1291)

Sep 15, 2010 12:32:30... Info: Request for Logon as admin accepted

Sep 15, 2010 3:30:47 AM Info: ====================================

Sep 15, 2010 3:30:47 AM Info: JControl is shutting SDM Server down

Sep 15, 2010 3:30:47 AM Info: ====================================

Sep 15, 2010 3:30:47 AM Info: Server finished sending back the answer of the ShutdownRequest.

Sep 15, 2010 3:30:47 AM Info: Shutting dispatcher down

and SDM GUI log:

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7185 - 630]/>

<!NAME[C:\usr\sap\J2E\JC01\SDM\program\log\sdmgui20100915.log]/>

<!PATTERN[sdmgui20100915.log]/>

<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>

<!ENCODING[Cp1252]/>

<!LOGHEADER[END]/>

Sep 15, 2010 12:31:55... Info: SDM-Gui is started

Sep 15, 2010 12:31:55... Info: Gui is remote - have to connect to server

Sep 15, 2010 12:32:29... Info: Attempting to logon from Host "0.0.0.0", Port "0" to Host "LENOVO", Port "50118", Role "admin"

Sep 15, 2010 12:32:37... Info: Logon to host "LENOVO" was successful

Sep 15, 2010 12:32:37... Info: Repository data loaded successfully

Sep 15, 2010 12:55:21... Info: SDM-GUI is exited

thanks

Accepted Solutions (1)

Accepted Solutions (1)

desiree_matas
Contributor
0 Kudos

Hi,

A duplicated entry in the SDM repository may be the reason why the SDM gui is hanging. Check SAP note 824357, which provides some instructions on how to check and correct the repository.

Regards,

Désiré

Jozsó
Explorer
0 Kudos

Hi,

another option is to set the SDM to standalone mode and try again

OR

use the command sdm.sh deploy file=<filename>

For the second option the SDM needs to be set to standalone mode too and it is convenient to copy the archive you need to deploy into the ...SDM/program folder.

Regards,

Jozsef

Former Member
0 Kudos

Hi Jozsef Bola ,

I try the proccess:

1.shut down sdm in SAPMMC console

2.sdm jstartup "mode=standalone"

3.sdm deploy "file=%path%\my.ear"

4.sdm jstartup "mode=integrated"

I am not sure all the steps are correct. But the ear was deployed.

Thanks a lot.

reefish

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

paste few more logs.

if possible restart the j2ee engine and try again to deploy.

Regards,

Mahendra