Disp+work.exe is stopped

Question

Hi,
   We installed the solution manager EHP1 (windows 2008 with mssql 2008) on distributed environment successfully i.e. application server and database server are diffrent servers on 2 days back.we logged inthe server and completed sgen and local client copy successfully.
today when iam stop and start the SAP MMC disp+work.exe is not started and it goes grey mode.i upgraded the kernel still same problem.here iam sending the dev_wo log,guide me for the same.
M sysno      01
M sid        MSL
M systemid   562 (PC with Windows NT)
M relno      7010
M patchlevel 0
M patchno    111
M intno      20020600
M make:      multithreaded, Unicode, 64 bit, optimized
M pid        2520
M Tue Jun 28 20:30:07 2011
M  kernel runs with dp version 244000(ext=110000) (@(#) DPLIB-INT-VERSION-244000-UC)
M  length of sys_adm_ext is 576 bytes
M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2520) [dpxxdisp.c   1349]
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)          29792     (1752)
M  DpShMCreate: sizeof(tm_adm)          5912704     (29416)
M  DpShMCreate: sizeof(wp_ca_adm)          24064     (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  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M  DpShMCreate: sizeof(slock_adm)          0     (104)
M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M  DpShMCreate: sizeof(file_adm)          0     (72)
M  DpShMCreate: sizeof(vmc_adm)          0     (1864)
M  DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
M  DpShMCreate: sizeof(gw_adm)     48
M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 000000000A600050, size: 6614144)
M  DpRqQInit: Parameter rdisp/queue_lock_level = 2
M  rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80
M  ThTaskStatus: rdisp/reset_online_during_debug 0
X  EmInit: MmSetImplementation( 2 ).
X  MM global diagnostic options set: 0
X  <ES> client 0 initializing ....
X  Using implementation view
X  <EsNT> Using memory model view.
M  <EsNT> Memory Reset disabled as NT default
X  ES initialized.
X  mm.dump: set maximum dump mem to 96 MB
M  ThInit: rdisp/cleanup_after_crash = 1
M  ThInit: running on host msom1sap04
M  calling db_connect ...
B  Loading DB library 'E:\usr\sap\MSL\DVEBMGS01\exe\dbmssslib.dll' ...
B  Library 'E:\usr\sap\MSL\DVEBMGS01\exe\dbmssslib.dll' loaded
B  Version of 'E:\usr\sap\MSL\DVEBMGS01\exe\dbmssslib.dll' is "700.08", patchlevel (0.105)
C 
C Tue Jun 28 20:30:08 2011
C  Callback functions for dynamic profile parameter registered
C  Thread ID:2848
C  Thank You for using the SLODBC-interface
C  Using dynamic link library 'E:\usr\sap\MSL\DVEBMGS01\exe\dbmssslib.dll'
C  dbmssslib.dll patch info
C    SAP patchlevel  0
C    SAP patchno  111
C    Last MSSQL DBSL patchlevel 0
C    Last MSSQL DBSL patchno         105
C    Last MSSQL DBSL patchcomment MSSQL: Unicode literals and standalone tools (1494847)
C  Network connection used from msom1sap04 to AEOM1SAP04\MSL using tcp:AEOM1SAP04\MSL
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2259]
C  (-2146893020) [HY000] [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: The clocks on the client and server machines are skewed.
C 
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2259]
C  (-2146893020) [HY000] [Microsoft][SQL Server Native Client 10.0]Cannot generate SSPI context
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2259]
C  (-2146893020) [HY000] [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: The clocks on the client and server machines are skewed.
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2259]
C  (-2146893020) [HY000] [Microsoft][SQL Server Native Client 10.0]Cannot generate SSPI context
C  Connection 0 failed using Driver={SQL Server Native Client 10.0};Server=AEOM1SAP04\MSL;AutoTranslate=no;Trusted_Connection=yes;WSID=msom1sap04;APP=R3D00 comm rd ODBC;Database=MSL;
C 
B  ***LOG BY2=> sql error -21468 performing CON [dbsh#2 @ 1208] [dbsh    1208 ]
B  ***LOG BY0=> [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: The clocks on the client and server machines are skewed.
[dbsh#2 @ 1208] [dbsh    1208 ]
B  ***LOG BY2=> sql error -21468 performing CON [dblink#4 @ 433] [dblink  0433 ]
B  ***LOG BY0=> [Microsoft][SQL Server Native Client 10.0]SQL Server Network Interfaces: The clocks on the client and server machines are skewed.

Answer 1

d pavani wrote:
> The clocks on the client and server machines are skewed.
Hi,
Could you please check on below points. This might help you.
1: As mentioned in error message, issue might be in time differences at server level between your CI and app server.
You can check the same by executing 'date' command on CI and app server at the same time. Both the servers should be attached to same NTP server.
2: Try with restarting the sapservices as well. As you have done kernel upgrade. sapservice should be restarted as well.
3: Delete entries from SMLG --> Go to --> system diagnosis --> Message server status area
delete entries from here, and try restarting app server completely using sapservice.
This should help you. Let me know if you identify any other error message.
Cheers !!!!
Ashish