Disp+work.exe Dispatcher Stopped

[joo_migueldimas]

Hi gurus,

System - SAP ECC 5.0

Operation System - Win 2003 Server X32

DataBase - MS SQL 2005

I´m faccing with a problem, after I made a successfull system copy in a sap system with release 6.40, when I start the system the MMC console show me a yellow semaphore, the disp+work.exe has gray color and it status is Stopped!! When I check the dev_disp log I see this: (I will paste that)

DpConvertRequest: net size = 163 bytes

NiBufSend starting

NiIWrite: write 562, 1 packs, MESG_IO, hdl 3, data complete

MsINiWrite: sent 562 bytes

send msg (len 110+452) to name -, type 4, key -

detach from message server

***LOG Q0M=> DpMsDetach, ms_detach ()

NiBufSend starting

NiIWrite: write 110, 1 packs, MESG_IO, hdl 3, data complete

MsINiWrite: sent 110 bytes

MsIDetach: send logout to msg_server

MsIDetach: call exit function

DpMsShutdownHook called

NiSelClear: removed hdl 3 from selectset

MBUF state OFF

AdGetSelfIdentRecord: > <

AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0

AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0

AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0

blks_in_queue/wp_ca_blk_no/wp_max_no = 2/300/8

LOCK WP ca_blk 2

make DISP owner of wp_ca_blk 2

DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 20)

MBUF component DOWN

NiBufClose: clear extensions for hdl 3

NiBufSetStat: bufstat of hdl 3 changed from OK to OFF

NiICloseHandle: shutdown and close hdl 3 / socket 1568

MsIDetach: detach MS-system

EsCleanup ....

***LOG Q05=> DpHalt, DPStop ( 3280)

Good Bye .....

Can you help me please how can I solve this problem?

Best regards

Joao Dimas - Portugal

[Former Member]

Hi,

Can you please check whether your database is running or not.

or else you can check whether LISTENER is running or not.

If not please start LISTENER from SERVICES.MSC from RUN.

or from command prompt

c:\> LSNRCTL

LSNRCTL> start

and check whether database is started or not at this stage.

goto command prompt

c:\> sqlplus "/as sysdba"

sql> startup

then try to restart your SAPMMC and server.

[joo_migueldimas]

I also run this command "R3trans -d" and it create a file with name "trans.log" and this show this:

4 ETW000 33 0.157885

4 ETW000 [dev trc ,00000] Procname: [ExecuteAndFlush - no proc] 6 0.157891

4 ETW000 [dev trc ,00000] setuser 'prt' failed -- connect terminated 11 0.157902

4 ETW000 [dev trc ,00000] Using Provider SQLNCLI 5300 0.163202

4 ETW000 [dev trc ,00000] OpenOledbConnection: MARS property was set successfully.

4 ETW000 85 0.163287

4 ETW000 [dev trc ,00000] ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

4 ETW000 4416 0.167703

4 ETW000 [dev trc ,00000] ExecuteAndFlush: line 5731. hr: 0x80040e14 Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

4 ETW000 30 0.167733

4 ETW000 [dev trc ,00000] sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

4 ETW000 31 0.167764

4 ETW000 [dev trc ,00000] Procname: [ExecuteAndFlush - no proc] 7 0.167771

4 ETW000 [dev trc ,00000] setuser 'prt' failed -- connect terminated 11 0.167782

4 ETW000 [dev trc ,00000] Using Provider SQLNCLI 5168 0.172950

4 ETW000 [dev trc ,00000] OpenOledbConnection: MARS property was set successfully.

4 ETW000 84 0.173034

4 ETW000 [dev trc ,00000] ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

4 ETW000 4366 0.177400

4 ETW000 [dev trc ,00000] ExecuteAndFlush: line 5731. hr: 0x80040e14 Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

4 ETW000 30 0.177430

4 ETW000 [dev trc ,00000] sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

4 ETW000 32 0.177462

4 ETW000 [dev trc ,00000] Procname: [ExecuteAndFlush - no proc] 7 0.177469

4 ETW000 [dev trc ,00000] setuser 'prt' failed -- connect terminated 10 0.177479

4 ETW000 [dev trc ,00000] failed to establish conn. 0 5208 0.182687

4 ETW000 [dblink ,00419] ***LOG BY2=>sql error 0 performing CON [dblink#1 @ 419]

4 ETW000 86615 0.269302

4 ETW000 [dblink ,00419] ***LOG BY0=><message text not available> [dblink#1 @ 419]

4 ETW000 16 0.269318

2EETW169 no connect possible: "DBMS = MSSQL --- SERVER = 'SAPPRDBICAF' DBNAME = 'PRT'"

Kind Regards

Joao Dimas - Portugal

[former_member759680]

Please post the log dev_w0

[joo_migueldimas]

Hi Gautam Poddar, here you have it:

-

---

trc file: "dev_w0", trc level: 1, release: "640"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS all, M

*

B

B Fri Jan 15 19:41:31 2010

B create_con (con_name=R/3)

B Loading DB library 'C:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll' ...

B Library 'C:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll' loaded

B Version of 'C:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.43)

B New connection 0 created

M systemid 560 (PC with Windows NT)

M relno 6400

M patchlevel 0

M patchno 43

M intno 20020600

M make: multithreaded, ASCII

M pid 3588

M

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3588) [dpxxdisp.c 1160]

I MtxInit: -2 0 0

M DpSysAdmExtCreate: ABAP is active

M DpSysAdmExtCreate: JAVA is not active

M DpShMCreate: sizeof(wp_adm) 6624 (828)

M DpShMCreate: sizeof(tm_adm) 2219848 (11044)

M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

M DpShMCreate: sizeof(comm_adm) 192000 (384)

M DpShMCreate: sizeof(vmc_adm) 0 (320)

M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)

M DpShMCreate: SHM_DP_ADM_KEY (addr: 044A0040, size: 2505416)

M DpShMCreate: allocated sys_adm at 044A0040

M DpShMCreate: allocated wp_adm at 044A17A8

M DpShMCreate: allocated tm_adm_list at 044A3188

M DpShMCreate: allocated tm_adm at 044A31B0

M DpShMCreate: allocated wp_ca_adm at 046C10F8

M DpShMCreate: allocated appc_ca_adm at 046C5748

M DpShMCreate: allocated comm_adm_list at 046C6EB8

M DpShMCreate: allocated comm_adm at 046C6ED0

M DpShMCreate: allocated vmc_adm_list at 046F5CD0

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 046F5CF8

M DpShMCreate: allocated wall_adm at 046F5D00

X EmInit: MmSetImplementation( 2 ).

X <ES> client 0 initializing ....

X Using implementation flat

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

M calling db_connect ...

C Thank You for using the SLOLEDB-interface

C Using dynamic link library 'C:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll'

C dbmssslib.dll patch info

C patchlevel 0

C patchno 43

C patchcomment View with literal containing (0x60) (786638)

C np:(local) connection used on SAPPRDBICAF

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C

C Fri Jan 15 19:41:32 2010

C ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

C sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

C Procname: [ExecuteAndFlush - no proc]

C setuser 'prt' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

C sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

C Procname: [ExecuteAndFlush - no proc]

C setuser 'prt' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

C sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

C Procname: [ExecuteAndFlush - no proc]

C setuser 'prt' failed -- connect terminated

C failed to establish conn to np:(local).

C Retrying without protocol specifier: (local)

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

C sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

C Procname: [ExecuteAndFlush - no proc]

C setuser 'prt' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

C sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

C Procname: [ExecuteAndFlush - no proc]

C setuser 'prt' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'prt' setuser 'prt']

C sloledb.cpp [ExecuteAndFlush,line 5731]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'prt' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

C Procname: [ExecuteAndFlush - no proc]

C setuser 'prt' failed -- connect terminated

C failed to establish conn. 0

B ***LOG BY2=> sql error 0 performing CON [dbsh#2 @ 1200] [dbsh 1200 ]

B ***LOG BY0=> <message text not available> [dbsh#2 @ 1200] [dbsh 1200 ]

B ***LOG BY2=> sql error 0 performing CON [dblink#1 @ 419] [dblink 0419 ]

B ***LOG BY0=> <message text not available> [dblink#1 @ 419] [dblink 0419 ]

M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c 1269]

M in_ThErrHandle: 1

M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 9413]

M

M Info for wp 0

M

M stat = 4

M reqtype = 1

M act_reqtype = -1

M rq_info = 0

M tid = -1

M mode = 255

M len = -1

M rq_id = 65535

M rq_source = 255

M last_tid = 0

M last_mode = 0

M int_checked_resource(RFC) = 0

M ext_checked_resource(RFC) = 0

M int_checked_resource(HTTP) = 0

M ext_checked_resource(HTTP) = 0

M report = > <

M action = 0

M tab_name = > <

M

M *****************************************************************************

M *

M * LOCATION SAP-Server SAPPRDBICAF_PRT_00 on host SAPPRDBICAF (wp 0)

M * ERROR tskh_init: db_connect

M *

M * TIME Fri Jan 15 19:41:32 2010

M * RELEASE 640

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 9589

M * COUNTER 1

M *

M *****************************************************************************

M

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 730]

M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 252]

M Entering ThSetStatError

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3588) [dpnttool.c 357]

[former_member759680]

Okay... nothing new. The same lines are repeating

Setuser failed because of one of the following reasons: the database principal 'prt' does not exist

Kindly check parameter - dbs/mss/schema in default.pfl of SAP.

(Open the file /usr/sap/SID/SYS/profile/default.pfl and check)

If it is not set to 'prt', kindly set it and then try.

[joo_migueldimas]

Hello Gautam Poddar,

I already checked what you recommend me to see and as you see in next text (default.pfl) that parameter is there:

SAPSYSTEMNAME=PRT

SAPDBHOST=SAPPRDBICAF

rdisp/mshost=SAPPRDBICAF

rdisp/accept_remote_trace_level=0

rdisp/sna_gateway=SAPPRDBICAF

rdisp/sna_gw_service=sapgw00

rslg/collect_daemon/listen_port=37

rslg/collect_daemon/talk_port=13

rdisp/bufrefmode=sendoff,exeauto

ms/server_port_0=PROT=HTTP, PORT=8100

dbms/type=mss

dbs/mss/server=SAPPRDBICAF

dbs/mss/schema=prt

dbs/mss/dbname=PRT

Best regards,

João Dimas - Portugal

[peter_dzurov]

Kindly check Note 683447 - SAP Tools for MS SQL Server and run SAP Tools provided there.

Probably you will find also Note 551915 - R/3 won't start after database restore or database copy helpful.

[joo_migueldimas]

Hi Peter Dzurov,

First at all, I didn´t made it through SAP Tools for MS SQL Server I did it by sapinst because this was a system copy in a target server without having an installed system there! It was a copy system with sapinst.exe so I didn´t need to do that copy with SAP Tools for MS SQL Server!

Second, you mentioned the note 551915, in fact I´d already read that note but unfortunately I don´t understand some things that is mentioned in there, for instance how can I know if the original (source) system was running as a non-MCOD system... and if I installed the target system with profile parameters which indicate an MCOD system... I Don´t Know!! Can you tell how can I know this specifics parameters...!?

Best regards,

Joao Dimas - Portugal

[peter_dzurov]

Hi,

please check again that note carefully, specially:

Database Copy
Use the Database Copy option of the SAP Tools for MS SQL Server 
to set up an ABAP system with a basis lower 
or equal to 6.40 "AFTER" you have performed an MS SQL Server database copy 
with the detach/attach and backup/restore method.

You need to run SAP Tools AFTER you did a system copy not FOR system copy...

Please keep in mind also some kind of prereq for running SAP Tools in that note.

btw. check Step 8: Follow-up procedure in Note 151603 - Copying an SQL Server database

[joo_migueldimas]

Hi Peter Dzurov,

I already solve this question... You´re right, this is related with sap tools from MS SQL but now I´ll try to describe what I did wrong and what I did and in fact what I should have done so that problems didn´t appear.

The system know looks fine without any problem.The main problem one more time was my lack of attention, this is, when I returned to the main note of system copy with an upgrade at SQL Server (2000 to 2005) - 799058 - I noticed two mistakes that I had not done correctly which was first in point III.8 - in fact what I have done here was ran the sapinst.exe and do a system copy from that wizard, and now I think what I should have done here was install a normal sap instance as I always do when I install a new sap system (correct me if I am wrong.) because this was a migration to a new physical server which didn´t have any sap instance installed.

The second mistake was in point III.11 - I thought the "SAP Tools for MS SQL Server" was exclusively used when we have to do a system copy on a server that already have an installed sap instance (for instance, in those situation that we want to have a Quality system with a same data of Production system and so we use that tool for that system copy in Quality system!)(correct me if I am wrong.) and so for that reason I didn´t made that phase/point eleven...

it were my two mistakes, but the mistakes in this situations teach us to a near future, we learned with them!

Besides those mistakes at all process, the system seems me OK without errors in SICK or SM21...

Thanks for your help Peter Dzurov,

Kind regards,

João Dimas - Portugal

[Former Member]

Hi jmgmad,

I have the same error, It happens after I applied the restore in MS SQL Server, as the database, hostname & SID are the same,

Can you please inform what did you do because I think the error is the smae case here.

Thank you in advance.

Regards,

[joo_migueldimas]

Hello gastadron,

I´m not sure if your problem is exactly the same as mine but nevertheless the solution for my problem is described in my last message (Posted: Jan 22, 2010 7:15 PM) and besides other things I read the post of Peter Dzurov (Posted: Jan 16, 2010 10:30 PM) it gave me a light so I could find the solution!!

So what I recommend you is read with attention the posts/messages that I mentioned above I besides that you must to describe better what is your problem...!!

Ahh other thing, my scenario wasn´t exactly as your actual scenario, in my case I used the method detach/attach of SQL Server platform... the management studio feature of SQL Server DB!!

Best regards,

João Dimas - Portugal