cancel
Showing results for 
Search instead for 
Did you mean: 

Disp+work.exe Dispatcher Running but Dialog Queue standstill

former_member229542
Active Participant
0 Kudos

Hi Guys,

This issue is related to my previous post where the system just hang after increasing the buffers.

Now it got worse, since after returing the abap/buffersize to original value, the system does not start

How a system can work with a set of memory parameters one day and not the other day.

I have performed a few changes to profile memory values, but after those changes did not work, i reverted them back to the original, and SAP does not start

The WP starts, and they all suddenly dies.

The disp+work process ends saying Dialog Queue Standstill, J2EE: Stopping the proceess

My main concern is why the system was working with these same values, and now is not starting up?

Is it possible to refresh/reset SAP shared memory, if this is causing the issue.

I have trying restarting the server and still same error.

On Dev_w0 there is no much info

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP

M TrThHookFunc: called for WP dump

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

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

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

M ThCallHooks: call hook >BtcCallLgCl< for event BEFORE_DUMP

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 10932) [dpnttool.c 334]

The MSSQLSERVER log is not full.

R3trans -d is returing code 0

Upgrading the Kernel is a last resort, since the system was working just yesterday with this same Kernel Version?

Any ideas?

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member229542
Active Participant
0 Kudos

Somehow this was causing the issue

The internal Adapter for the loaded GSS-API mechanism identifies as:

N Internal SNC-Adapter (Rev 1.0) to SECUDE 5/GSS-API v2

N SncInit(): found snc/identity/as=p:CN=BID, OU=PG, O=BOBJ, C=CA

N *** ERROR => SncPAcquireCred()==SNCERR_GSSAPI [sncxxall.c 1439]

N GSS-API(maj): No credentials were supplied

N GSS-API(min): File is not existing

N Could't acquire ACCEPTING credentials for

N

N name="p:CN=BID, OU=PG, O=BOBJ, C=CA"

N SncInit(): Fatal -- Accepting Credentials not available!

I had to put parameter snc/enable = 0 in order to allow WP start.

Any ideas how to fix that?