disp+work.exe dont start

[former_member716643]

After a power failure in the server room, I can not start the SAP GUI program. After starting SAP in SAPMMC, msg_server changes to green, and disp + work.exe remains gray.
When I try to connect, the following message appears: "<server address>: sapdp00 not reached; CONNECTIONREFUSED".

ping 127.0.0.1 is ok

ping <serveraddress> from other PC is ok

Please help

[stefan_schnell]

Hello Rafal,
welcome in the SAP Community.
I changed you primary tag from SAP GUI for Windows to SAP NetWeaver Application Server.
Best regards
Stefan

[oppancs]

Dear Rafal,

This error usually comes, if the message server is not up and running or not reachable due to some network issue. Please try the followings one by one:

1. Check that the relevant message server is up and running. Its log file (dev_ms) can be found in the following path: "LocalDrive\usr\sap\<SID>\SCS<XX>\work".

2. Otherwise it can be a firewall issue. Try to telnet to port <potrnr> from your network and from the external app location.

3. Please check following note and test message server conenction: 1341701 - partner 'hostname:service' not reached

4. Check the message server settings using note: 52959 - sapms..., sapdp.., sapgw.. unknown (or not found)

5. Verify if the AS Java is able to reach the hostname using OS commands (i.e. ping, traceroute, nslookup) from the affected system. If not, please ask for internal IT team assistance to verify the resolution for the hostname issue at OS level.

Best Regards,

Barnabás Paksi

[oppancs]

In case the gateway is not reachable, the same steps should be checked. Its path is te same as message server and the file is dev_rd, as well as its port should be checked.

[raquel_gomez]

Hi Rafal,

As Dispatcher is not started, you're unable to logon into the system, getting error:
"<server address>: sapdp00 not reached; CONNECTIONREFUSED"

Please provide Dispatcher (dev_disp) trace, it should show us why Dispatcher did not start correctly when application server was started.

Regards,
Raquel

[m_25032016]

trc file: "dev_disp", trc level: 1, release: "745"

sysno 00

sid ER1

systemid 562 (PC with Windows NT)

relno 7450 patchlevel 0

patchno 800

intno 20151301

make multithreaded, Unicode, 64 bit, optimized

profile \\LRPSAP\sapmnt\ER1\SYS\profile\ER1_D00_LRPSAP pid 3768

please help

[raquel_gomez]

Hi Mahmoud,
For the analysis, I'd need complete Dispatcher trace filde (dev_disp).
Please upload it here.
Thanks!
Raquel

[isaias_freitas]

Hello Rafal,

Please attach the following files to this thread:

• dev_disp
• dev_w0
• dev_rd
• dev_icm

They can be found at the "work" folder of the instance (/usr/sap/<SID>/<instance>/work).

Depending on what we find, we might need additional files.

Regards,

Isaías

[former_member383442]

Hi. I started to experience similar issue recently and it has to do with shared memory not releasing properly. - Windows 2008 Server I did not have this issue before until about few weeks ago. Typically, cleanicp command could've used in linux/unix environment, but windows does not offer this feature. Instead, shutting down SAP services and starting was done as well in windows. However, this time, it's did not work.

My speculation is that windows OS patch may have affected the how kernel is behaving and prevented SHM to be released after shutting down the system. I'm looking for if there's any SAP note or support message for this but i could not find any. only way is re-starting the server but this is becoming very painful.

i'm thinking to upgrade kernel to latest version which i hadn't done yet.

[santanu034]

Hi,

Please check the dev_disp logs.

Parallel to this please check the message server is reachable and entry for the host is defined in /etc/hosts file.