NSP start app server then disp+work.EXE problem

[Former Member]

Hi all,

I've installed the Netweaver 7.0 ABAP trial version recently on a laptop with XP Home Edition. I've also installed MS loopback adaptor as instructed.

Start -> ... NSP -> Start app server

Initially the command window shows up and then turns green. Then a popup shows me disp+work.EXE crashing (ind typical WinXP fashion) then the start app server timing out and the command window turning yellow.

I have included the windows Event Viewer log description from that incident below:

Faulting application dispwork.EXE, version 7000.95.13.34297, faulting module dispwork.EXE, version 7000.95.13.34297, fault address 0x0002a299.

So when trying to logon, I get Connection Refused. I was told the above problem is the main culprit ... not knowing what to do here.

Does anybody know what is going on? I'm a total newbie at this.

Thanks in advance,

Kelvin

[vincentlim826 · Accepted solution]

typically see the trace files:

- sapstart.log

- sapstartsrv.log

- stderr* files

- dev_ms, dev_disp, dev_w*

cheer,

Vincent

[Former Member · Accepted solution]

Hi,

From the 2 log files below, I'm guessing that I should shorten my computer name and I have (including a restart). But the problem remains. The C:\SAP\NSP\SYS\profile dir still has many references to my old computer name. Should I just change all those references to the new (shorter) computer name?? I don't want to risk screwing things up more than it already is.

thanks and regards,

Kelvin

sapstart.log gives:

SAP-R/3-Startup Program

Starting at 2008/02/20 14:30:00

Startup Profile: "C:\SAP\NSP\SYS\profile\START_DVEBMGS00_your-8545fb4e07"

Starting Programs

(2668) Execute: C:\SAP\NSP\SYS\exe\run\strdbs.cmd NSP

(2684) CreateProcess: C:\SAP\NSP\SYS\exe\run\msg_server.EXE pf=C:\SAP\NSP\SYS\profile\NSP_DVEBMGS00_your-8545fb4e07

(1260) CreateProcess: C:\SAP\NSP\SYS\exe\run\disp+work.EXE pf=C:\SAP\NSP\SYS\profile\NSP_DVEBMGS00_your-8545fb4e07

trusted named pipe user is stopping R/3 System at 2008/02/20 14:33:10

(616) Parent Shutdown at 2008/02/20 14:33:10

(616) kill(SIGINT 1260) failed.

stderr2 gives:

Wed Feb 20 14:30:26 2008

• DP_FATAL_ERROR => main: rdisp/myname=your-8545fb4e07_NSP_00 exceeds 20 characters

• DISPATCHER EMERGENCY SHUTDOWN ***

***

• DISPATCHER EMERGENCY SHUTDOWN => main: rdisp/myname=your-8545fb4e07_NSP_00 exceeds 20 characters

NiWait: sleep (5000ms) ...

NiISelect: timeout 5000ms

NiISelect: maximum fd=1

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Wed Feb 20 14:30:31 2008

NiISelect: TIMEOUT occured (5000ms)

DpHalt: shutdown server >< (normal)

DpJ2eeDisableRestart

Switch off Shared memory profiling

ShmProtect( 57, 3 )

ShmProtect(SHM_PROFILE, SHM_PROT_RW

ShmProtect( 57, 1 )

ShmProtect(SHM_PROFILE, SHM_PROT_RD

call semaphore clean-up function ...

***LOG Q0E=> DpSigGenHandler, Exception (c0000005) [dpnttool.c 432]

-

---

C-STACK -

---

SAP (R) - R/3(TM) Callstack, Version 1.0

Copyright (C) SAP AG. All rights reserved.

-

---

Application exception occurred:

Exception : c0000005 (Access Violation)

App : disp+work.EXE (pid=1260)

When : 2/20/2008 14:30:31.968

Threads : 1

-

---

Computer Name : MY-8545FB4E07

User Name : SYSTEM

. . .

[Former Member · Accepted solution]

Your system name should be >=13 character .. After installing just changeing the system name ( to less than 13 ) wont work , you have to change the name in all the places where ever the old system name is specified ( eg> in profile name , profile parameterer etc ) . I think it would be much easy if you do a reinstallation

Thanks

Prince Jose

[Former Member · Accepted solution]

Hi,

You need to modify all the profiles and also make the entry in hosts file with new name.Then try R3trans -d check the error log in trans.log in the directory where you have executed R3trans.

Thanks,

Sagar.

[Former Member]

Your SAP is not up thats why you cant login .. Check disp+work logs in work directory

Thanks

Prince Jose