cancel
Showing results for 
Search instead for 
Did you mean: 

*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

0 Kudos

Dear All,

Not able to start SAP Instance

dev_disp.trc

*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

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

some other trc file .

*** ERROR => FiRemove() failed. [emxx.c      1093]

--------------------------------------

OS:Windows Server 2008 R2

SAP 605 NW 702

-------------------------------

SAP Basis System: Message server disconnected

netstat -a

TCP    172.25.1.50:3300      SNPLIDES:59988        CLOSE_WAIT

TCP    172.25.1.50:59988      SNPLIDES:sapgw00      FIN_WAIT_2

VMC (JAVA VM in WP) is not active

Activate VM.

Please guide

Regrds

Momin

Accepted Solutions (0)

Answers (2)

Answers (2)

kaus19d
Active Contributor
0 Kudos

Hi ,

Then you should have kept my content here too instead of archiving. After my moderation alert creation, only because of your post reply only my moderation alert got rejected. We could have let other people also see the same matter so that this matters do not happen again in future by anyone. Keeping old posts available & able to reply is for the general people to see & understand those scenarios, is not is it such?

Thanks,

Kaushik

former_member189546
Active Contributor
0 Kudos

Hello,

1 possible network problems detected is not significent just a self test at the start.

Open command prompt

Please try r3trans -d from kernel directory check the trans.log produced can you connect ok

to database?

Check also Windows eventviewer do you get errors?

Can the sap services start ok?

Also check dev_w0 are there errors there memory, db  etc

regards,

John Feely

0 Kudos

Dear John

R3trans -d is successful.

dev_w0,dev_disp,dev_ms,dev_rd attached for your refrence.

rgds

momin

former_member189546
Active Contributor
0 Kudos

hello,

Work process seems to be fails with programme buffer

Pxa initialisation

Please set abap/buffersize to 800000 in instance profile and try to start system

Also check note 88416 set PHYS_MEMSIZE correctly

if the problem persists do you get any errors in windows event viewer

regards,

John Feely