Dispatcher stopped and not able to connect with sq...

Former Member · ‎01-05-2012

Hi ,

In one of test system disp+work is started and then within no time its stopped.

I am able to connect with sql server 2005 database but while starting sap dispatcher is stopping.

Here is the log of dev_wo

-

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

-

*

ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ

*

B

B Thu Jan 05 07:24:02 2012

B create_con (con_name=R/3)

B Loading DB library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' ...

B Library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' loaded

B Version of 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' is "700.08", patchlevel (0.72)

B New connection 0 created

M sysno 11

M sid DE1

M systemid 560 (PC with Windows NT)

M relno 7000

M patchlevel 0

M patchno 75

M intno 20050900

M make: multithreaded, Unicode, optimized

M pid 988

M

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

M length of sys_adm_ext is 572 bytes

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

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) 23936 (1408)

M DpShMCreate: sizeof(tm_adm) 3994272 (19872)

M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

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

M DpShMCreate: sizeof(comm_adm) 528064 (1048)

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

M DpShMCreate: sizeof(file_adm) 0 (72)

M DpShMCreate: sizeof(vmc_adm) 0 (1440)

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

M DpShMCreate: sizeof(gw_adm) 48

M DpShMCreate: SHM_DP_ADM_KEY (addr: 07F90040, size: 4659000)

M DpShMCreate: allocated sys_adm at 07F90040

M DpShMCreate: allocated wp_adm at 07F91E40

M DpShMCreate: allocated tm_adm_list at 07F97BC0

M DpShMCreate: allocated tm_adm at 07F97BF0

M DpShMCreate: allocated wp_ca_adm at 08366E90

M DpShMCreate: allocated appc_ca_adm at 0836CC50

M DpShMCreate: allocated comm_adm at 0836EB90

M DpShMCreate: system runs without file table

M DpShMCreate: allocated vmc_adm_list at 083EFA50

M DpShMCreate: allocated gw_adm at 083EFA90

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 083EFAC0

M DpShMCreate: allocated wall_adm at 083EFAC8

X EmInit: MmSetImplementation( 2 ).

X MM global 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 Thu Jan 05 07:24:03 2012

M ThInit: running on host sugarland

M

M Thu Jan 05 07:24:04 2012

M calling db_connect ...

C Warning: Env(MSSQL_SERVER) [SUGARLAND\DE1] <> Prof(dbs/mss/server) [SUGARLAND]. Profile value will be used.

C Thread ID:708

C Thank You for using the SLOLEDB-interface

C Using dynamic link library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll'

C dbmssslib.dll patch info

C patchlevel 0

C patchno 72

C patchcomment MSSQL: Thread check in DbSlDisconnect (969143)

C np:(local) connection used on SUGARLAND

C CopyLocalParameters: dbuser is 'de1'

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C

C Thu Jan 05 07:24:19 2012

C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C

C Thu Jan 05 07:24:34 2012

C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C

C Thu Jan 05 07:24:49 2012

C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

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

C Thu Jan 05 07:25:05 2012

C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C

C Thu Jan 05 07:25:21 2012

C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C

C Thu Jan 05 07:25:37 2012

C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

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

M in_ThErrHandle: 1

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

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 sugarland_DE1_11 on host sugarland (wp 0)

M * ERROR ThInit: db_connect

M *

M * TIME Thu Jan 05 07:25:37 2012

M * RELEASE 700

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 13

M * MODULE thxxhead.c

M * LINE 10354

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 ***LOG Q02=> wp_halt, WPStop (Workproc 0 988) [dpnttool.c 327]

Please help me on this

Thanks

Srikanth

Former Member · ‎01-05-2012

Hello Srikanth,

Can you please let us know which OS is it?

1)If its windows, I will suggest you to stop every services of sap and SQL in services and then restart it.

After that try to start your SAP system.

2)IF its AIX or LINUX, I will suggest you to kill every process running leaving behing only root processes, ie kill processes running with id <sid>adm and database id.

After that try to restart the SAP system.

Hope it helps..

Regards,

Amit Barnawal

Dispatcher stopped and not able to connect with sql server

Accepted Solutions (0)

Answers (1)

Answers (1)

Re: Dynamic SemanticObject for Intent Based Naviga...

Re: I have a similar issue.I started using a repor...

Re: Validation during Create - Similar to Side eff...

Master Data Replication From S/4HANA Core to S/4HA...

Re: I have a similar issue.I started using a repor...