cancel
Showing results for 
Search instead for 
Did you mean: 

Dispatcher not running

Former Member
0 Kudos

Hello everybody I installed SAP Netweaver 2004s ABAP+JAVA in Microsoft SQL 2005 on Windows Server 2003 SP1, and the dispatcher is not running correctly the status is this:

disp+work.EXE Dispatcher Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE: status info unavailable

in the developer trace shown below indicates that :

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

can anybody point me in the right direction to solve this problem, the developer trace is below:

-


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

-


sysno 00

sid XID

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 83

intno 20050900

make: multithreaded, Unicode, optimized

pid 2796

Thu Feb 08 13:58:20 2007

kernel runs with dp version 218000(ext=109000) (@(#) DPLIB-INT-VERSION-218000-UC)

length of sys_adm_ext is 572 bytes

      • SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 2796) [dpxxdisp.c 1239]

shared lib "dw_xml.dll" version 83 successfully loaded

shared lib "dw_xtc.dll" version 83 successfully loaded

shared lib "dw_stl.dll" version 83 successfully loaded

shared lib "dw_gui.dll" version 83 successfully loaded

shared lib "dw_mdm.dll" version 83 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

Thu Feb 08 13:58:25 2007

      • WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0168.qqq.nxst) took 4 seconds

Thu Feb 08 13:58:35 2007

      • WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 10 seconds

***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5277]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >svrvirintel_XID_00 <

DpShMCreate: sizeof(wp_adm) 18304 (1408)

DpShMCreate: sizeof(tm_adm) 3994272 (19872)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

DpShMCreate: sizeof(comm_adm) 528064 (1048)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1440)

DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 06E80040, size: 4653368)

DpShMCreate: allocated sys_adm at 06E80040

DpShMCreate: allocated wp_adm at 06E81E40

DpShMCreate: allocated tm_adm_list at 06E865C0

DpShMCreate: allocated tm_adm at 06E865F0

DpShMCreate: allocated wp_ca_adm at 07255890

DpShMCreate: allocated appc_ca_adm at 0725B650

DpShMCreate: allocated comm_adm at 0725D590

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 072DE450

DpShMCreate: allocated gw_adm at 072DE490

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 072DE4C0

DpShMCreate: allocated wall_adm at 072DE4C8

MBUF state OFF

DpCommInitTable: init table for 500 entries

Thu Feb 08 13:58:36 2007

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 511 blocks reserved for free list.

Thu Feb 08 13:58:37 2007

ES initialized.

Thu Feb 08 13:58:47 2007

J2EE server info

start = TRUE

state = STARTED

pid = 240

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1040

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Feb 08 13:58:48 2007

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1625]

Thu Feb 08 13:58:52 2007

***LOG Q0K=> DpMsAttach, mscon ( svrvirintel) [dpxxdisp.c 11644]

DpStartStopMsg: send start message (myname is >svrvirintel_XID_00 <)

DpStartStopMsg: start msg sent

Thu Feb 08 13:58:54 2007

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

Thu Feb 08 13:58:56 2007

CCMS: start to initalize 3.X shared alert area (first segment).

DpJ2eeLogin: j2ee state = CONNECTED

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 83

Release check o.K.

Thu Feb 08 14:00:01 2007

MBUF state ACTIVE

Thu Feb 08 14:00:02 2007

DpModState: change server state from STARTING to ACTIVE

Thu Feb 08 14:03:10 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1520

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1051) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=240)

      • ERROR => DpProcKill: kill failed [dpntdisp.c 371]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:03:12 2007

J2EE server info

start = TRUE

state = STARTED

pid = 3652

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1142

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Thu Feb 08 14:03:17 2007

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:04:54 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1468

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1146) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3652)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:05:12 2007

J2EE server info

start = TRUE

state = STARTED

pid = 544

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1169

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:05:21 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1508

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1170) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=544)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:05:32 2007

J2EE server info

start = TRUE

state = STARTED

pid = 3956

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1178

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:05:40 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1464

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1179) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3956)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:05:52 2007

J2EE server info

start = TRUE

state = STARTED

pid = 3288

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1186

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:06:00 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1460

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1187) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3288)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:06:12 2007

J2EE server info

start = TRUE

state = STARTED

pid = 3092

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1190

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:06:20 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1456

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1191) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3092)

      • ERROR => DpProcKill: kill failed [dpntdisp.c 371]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:06:32 2007

J2EE server info

start = TRUE

state = STARTED

pid = 3332

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1199

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:06:40 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1452

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1200) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3332)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:06:52 2007

J2EE server info

start = TRUE

state = STARTED

pid = 3712

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1203

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:07:00 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1448

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1204) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3712)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:07:12 2007

J2EE server info

start = TRUE

state = STARTED

pid = 2696

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1211

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:07:20 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1212) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=2696)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:07:32 2007

J2EE server info

start = TRUE

state = STARTED

pid = 792

argv[0] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[1] = E:\usr\sap\XID\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1219

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=XID

argv[7] = -DSAPMYNAME=svrvirintel_XID_00

argv[8] = -DSAPPROFILE=E:\usr\sap\XID\SYS\profile\XID_DVEBMGS00_svrvirintel

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

DpJ2eeLogin: j2ee state = CONNECTED

Thu Feb 08 14:07:40 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4242]

      • ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1440

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1220) [nixxi.cpp 4242]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=792)

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Thu Feb 08 14:07:52 2007

DpEnvCheckJ2ee: switch off j2ee start flag

Thanks in advance.

Regards

Julio Cesar

Accepted Solutions (1)

Accepted Solutions (1)

tim_buchholz
Active Participant
0 Kudos

Dear Julio Cesar,

the dispatcher starts the J2EE engine, but this engine crashes after a minute or so. You should look for anything in the J2EE log files in order to track this down. This is NOT a problem in the network. It manifests with a network error, since the J2EE ungracefully closes the network connection, which is seen as a network error by the dispatcher.

Best Regards,

Tim

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Julio

It looks as if there is already a server running. Please make sure

no disp+work with the same instance-number is running on this box

(it could also bee that there is an old instance of dpmon or MMC

is running).

Please check it.You should call sopsap or 'cleanipc <instnr>' in order to remove

any old shared memory segment.

Reward suitable points

Former Member
0 Kudos

Hi Rajat,

I'm having the same problem. I found out that there are two instances are running in my SAPMMC. How do I find out which is the active one? How do I remove the old instance? Please advise. Thanks

Regards,

Lisan

Former Member
0 Kudos

Hello,

you can add/modify the services using "sapstartsrv" program.

Cheers,

-Sunil

Former Member
0 Kudos

Hi Sunil,

Thanks for the reply. I'm actually having two database instance (the blue colour storage), which contains the SQL Server logs, running on my SAPMMC. Any idea how can I remove one of the database instance?

Regards,

Lisan

Former Member
0 Kudos

Hi rajat,

i wanted to clear the old shared memory segment. how can i do so?

I have a windows based OS with 2004s installed.

Former Member
0 Kudos

Hello,

Can you try to clean shared memory using cleanipc command?

cleanipc <SAPSYSTEM> remove

Cheers,

-Sunil

Former Member
0 Kudos

hi Julio,

It is network related issue, better ask your network team to help you out

To find out, whether DNS is the cause for your problem, disable it on your application server. The procedure for this is operating system specific. NT uses the "Network" control panel, UNIX uses the files "/etc/resolv.conf", "/etc/nsswitch.conf", "/etc/netsvc.conf", the environment variable "NSORDER" or others. Please consult your operating system documentation. Now the other application servers and the database server have to be entered into /etc/hosts manually for the R/3 system to function.

Another clear indication of DNS problems is given, when the command "netstat -i" hangs, but "netstat -in" completes fast. The only difference between these two commands is, that "netstat -i" tries to resolve IP-addresses into network and host names. (On Windows you may use the commands: "netstat -a" and "netstat -an")

If you have identified your DNS server as the cause of the problems, some of your options are:

Configure your DNS correctly. This means that all your internal networks have to be represented as a so called "zone" in your DNS server. Now the name server knows that it is responsible for these networks and will answer all queries to the best of its knowledge.

Mostly the system does not rely on the result of client IP-address resolutions. The functionality is not affected if the resolution fails. Thus it is not necessary to enter all computers into the zone files - if they are not present the name server will return an error message to the caller immediately.

Check all name server configuration files for references to Internet name servers. The so called "Root Cache Data" may have the Internet root name servers configured by default (this is the case with the Microsoft DNS server that comes with Windows NT Server). Remove all references to unreachable or inappropriate external name servers.

Disable DNS lookups on your application servers. The system needs only the addresses of all other application servers and the database server of the same system in order to run. This information can easily be kept in the static file /etc/hosts.

Refer note 525900

Cheers,

Shyam