cancel
Showing results for 
Search instead for 
Did you mean: 

GetProcesslist failed: 80040154(Cannot connect to SAP service on IDES)

Former Member
0 Kudos

Hi All,

Our IDES system cannot be accesed after a process of shutdown and restarting. Below is the procedures tried out:

1) Solution Manager - Started but IGSWD.EXE not running

2) IDES - In Ides there appears to be a no entry sign. Subsequent effort of trying to start Ides leads to error message "GetProcesslist failed: 80040154"

FYI, our IDES and Solution Manager are all in one System Instance. Previous shutdown and restarting has been done without any error encountered. Is there any cause and solution. Please reply ASAP. Thanks.

Best Regards,

Sam

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Can you please check the file \windows\system32\drivers\etc\services whether you the following type of entry. If not please add in that file.

sapdp<your instanceno> 36<instanceno>

e.t.

sapdp23 3623 (where 23 is instance no). add this correspondingly to your workstation and server.

regards

Anand.M

Former Member
0 Kudos

HI Anand.M

Already one line as below was within the file.

"sapdp00 3200/tcp" (SID is 00)

By the way, one service "SAPOSCOL" was not activated when we started the windows. We tried to avtivate manully & download lastest version from Service Marketplace of SAP then restart. It's still not ativated at Service Manager but in console mode it's starting in the command "saposcol -l".

Best regards,

Sam

Former Member
0 Kudos

Hi,

Have you checked the trace files in /usr/sap/../work directory. After you try to start the instance and if that fails, take a look at dev_disp, and dev_w0 files and see if there are any errors listed in there.

Regards

Shehryar

ps: SAPOSCOL is not requird to startup SAP instance. The service named SAP<sid>_<instance no> should start automatically or when you start the SAP instance from MMC.

Message was edited by: Shehryar Khan

Former Member
0 Kudos

Hi Shehryar Khan

I checked the 2 files and it seems to be fine. It only recorded the info to the date before we are not able to restart SAP.

BTY, SAPIDS_00 & SAPSMR_02 services are avtivated automatically after system resatrt.

Thanks

Former Member
0 Kudos

The files should be updated every time you try to start SAP from MMC.

Do you receive this error when you open MMC or after you try to start SAP system from inside MMC? Please also check the Syslog node in MMC for latest errors in the startup process.

Regards

Former Member
0 Kudos

Hi

If you want to regenerate service and MMC configuration, use: sapstartsrv.exe (uninstall and then install)

in path usr/sap/<SID>/SYS/exe/run

Regards,