cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Dispatcher getting stopped after successful DB restore

Former Member
0 Kudos

Dear Experts,

I have installed Solution Manger 7 with MSS 2005 on Windows 2003 x64. MSS DB and thereafter

SAP installtion was successful. I also logged on the system and checked a few things. Then we

performed a DB restore using MSS Management Studio and DB restore completed successfully.

I also logged on the DB and checked a few table like sm1.USR01, sm1.PAT03 etc. and found the

restore was successful.

Then we take a restart and tried to start SAP. Primaryly I found it is starting and then when it come

binary sychronization for JAVA stack it is stopping and gradually killed the dispatcher too. I checked

in log file it is showing DB connetion failure.

I tried with r3trans -d and it gives me

This is r3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).
unicode enabled version
2EETW169 no connect possible: "DBMS = MSSQL                            ---  SER
ER = 'SAPSM' DBNAME = 'SM1'"
r3trans finished (0012).

I checked the environmental variable as mentioned in few therads and found in my system it is

completely maintained.

Please help me in this regard.

Regards,

Partha

Accepted Solutions (1)

Accepted Solutions (1)

former_member524429
Active Contributor
0 Kudos

Hi,

Please analyze dev_w0, dev_w1, dev_server0 logs to get possible causes and post the same.

Have you referred this SAP Note 151603 - Copying an SQL Server database, for DB restore ? Refer Step 8.

Have you used STM (SAP Tool for MS SQL) after DB restore as a Post Processing activity? Please refer SAP Note 683447 to get more information.

If you are not able to download and apply STM, then run the Scripts (as manual method same as STM) which is attached to this SAP Note 551915 - R/3 won't start after database restore or database copy.

Please read SAP Note 551915 - R/3 won't start after database restore or database copy carefully apply the suggestions.

Regards,

Bhavik G. Shroff

Answers (4)

Answers (4)

Former Member
0 Kudos

Just simply run STM tools --> Database Copy Completion.

Former Member
0 Kudos

Thank you all. Resolved

Former Member
0 Kudos

Dear Ray,

Can you tell us how did you resolve this issue.. ? .as I am facing the same issue after database restore..

former_member204746
Active Contributor
0 Kudos

also check contents of file trans.log to view SAP's connenction status to the database. You will see error messages that will help you track this problem.

Former Member
0 Kudos

Dear Experts,

One thing I want to mention that

1. I did not take up backup of master and msdb backup of old Database. So I have just restore*d

Full DB and transaction log backup in the newly installed DB.

Though the DB restore was successful yet as no restore of old master and MSDB performed,

Is that may create this problem ???

2. Please find the dev_w0

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-


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

-


*

  • ACTIVE TRACE LEVEL 1

  • ACTIVE TRACE COMPONENTS all, MJ

*

B

B Tue Feb 09 14:32:35 2010

B create_con (con_name=R/3)

B Loading DB library 'D:\usr\sap\SM1\DVEBMGS01\exe\dbmssslib.dll' ...

B Library 'D:\usr\sap\SM1\DVEBMGS01\exe\dbmssslib.dll' loaded

B Version of 'D:\usr\sap\SM1\DVEBMGS01\exe\dbmssslib.dll' is "700.08", patchlevel (0.52)

B New connection 0 created

M sysno 01

M sid SM1

M systemid 562 (PC with Windows NT)

M relno 7000

M patchlevel 0

M patchno 52

M intno 20050900

M make: multithreaded, Unicode, 64 bit, optimized

M pid 2208

M

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

M length of sys_adm_ext is 572 bytes

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

I MtxInit: 30000 0 0

M DpSysAdmExtCreate: ABAP is active

M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M DpShMCreate: sizeof(wp_adm) 12816 (1424)

M DpShMCreate: sizeof(tm_adm) 5217968 (25960)

M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

M DpShMCreate: sizeof(comm_adm) 552080 (1088)

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

M DpShMCreate: sizeof(file_adm) 0 (72)

M DpShMCreate: sizeof(vmc_adm) 0 (1760)

M DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)

M DpShMCreate: sizeof(gw_adm) 48

M DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000ECC0050, size: 5901456)

M DpShMCreate: allocated sys_adm at 000000000ECC0050

M DpShMCreate: allocated wp_adm at 000000000ECC1EE0

M DpShMCreate: allocated tm_adm_list at 000000000ECC50F0

M DpShMCreate: allocated tm_adm at 000000000ECC5150

M DpShMCreate: allocated wp_ca_adm at 000000000F1BF000

M DpShMCreate: allocated appc_ca_adm at 000000000F1C4DC0

M DpShMCreate: allocated comm_adm at 000000000F1C6D00

M DpShMCreate: system runs without file table

M DpShMCreate: allocated vmc_adm_list at 000000000F24D990

M DpShMCreate: allocated gw_adm at 000000000F24DA10

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 000000000F24DA40

M DpShMCreate: allocated wall_adm at 000000000F24DA50

X EmInit: MmSetImplementation( 2 ).

X MM diagnostic options set: 0

X <ES> client 0 initializing ....

X Using implementation flat

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

M

M Tue Feb 09 14:32:36 2010

M ThInit: running on host sapsm

M

M Tue Feb 09 14:32:37 2010

M calling db_connect ...

C Thank You for using the SLOLEDB-interface

C Using dynamic link library 'D:\usr\sap\SM1\DVEBMGS01\exe\dbmssslib.dll'

C dbmssslib.dll patch info

C patchlevel 0

C patchno 52

C patchcomment MSSQL: Avoid cursor on sap_ procs, ABINDEX (935477)

C np:(local) connection used on SAPSM

C CopyLocalParameters: dbuser is 'sm1'

C

C Tue Feb 09 14:32:38 2010

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C

C Tue Feb 09 14:32:39 2010

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

C sloledb.cpp [ExecuteAndFlush,line 6277]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'sm1' 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 'sm1' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

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

C sloledb.cpp [ExecuteAndFlush,line 6277]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'sm1' 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 'sm1' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

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

C sloledb.cpp [ExecuteAndFlush,line 6277]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'sm1' 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 'sm1' 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() != 'sm1' setuser 'sm1']

C sloledb.cpp [ExecuteAndFlush,line 6277]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'sm1' 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 'sm1' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

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

C sloledb.cpp [ExecuteAndFlush,line 6277]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'sm1' 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 'sm1' failed -- connect terminated

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

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

C sloledb.cpp [ExecuteAndFlush,line 6277]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'sm1' 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 'sm1' failed -- connect terminated

C failed to establish conn. 0

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

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

B ***LOG BY2=> sql error 0 performing CON [dblink#3 @ 431] [dblink 0431 ]

B ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink 0431 ]

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

M in_ThErrHandle: 1

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

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 semaphore = 0

M act_cs_count = 0

M control_flag = 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 vm = V-1

M

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

M *

M * LOCATION SAP-Server sapsm_SM1_01 on host sapsm (wp 0)

M * ERROR ThInit: db_connect

M *

M * TIME Tue Feb 09 14:32:39 2010

M * RELEASE 700

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 10204

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 720]

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

M Entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M

M Tue Feb 09 14:32:40 2010

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

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Reagards,

Partha

former_member524429
Active Contributor
0 Kudos

Hi,

Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'sm1' 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.

Have you executed STM (SAP Tool for MS SQL) after DB restore, as Post Processing activity ?

Have you referred suggested SAP Notes as mentioned in my last post ?

Regards,

Bhavik G. Shroff