on 01-30-2009 3:34 AM
Dear Friends,
I have one central instance & one dailog instance. I got one error in SM21. In SM21 of central instance there is some errors like..
08:07:30 DIA 05 999 USER01 VF01 Q02 Stop Workproc 5, PID 10418
08:09:32 DIA 12 999 USER02 SESS Q02 Stop Workproc12, PID 10441
08:09:40 DP Q0M Message server disconnected
08:09:46 DP Q0N Failed to send a request to the message server
08:09:46 DP Q0N Failed to send a request to the message server
08:09:46 DP Q0N Failed to send a request to the message server
08:09:46 DP Q0N Failed to send a request to the message server
08:09:46 DP Q0N Failed to send a request to the message server
08:09:46 DP Q0N Failed to send a request to the message server
08:09:46 DIA 02 R0Z The update dispatch info was reset
08:09:46 DP Q0N Failed to send a request to the message server
08:09:46 DIA 02 R0R The update was deactivated after a system error
08:09:47 DP Q0G Request (type DIA) cannot be processed
08:09:47 DP Q0G Request (type DIA) cannot be processed
08:09:47 DP Q0G Request (type DIA) cannot be processed
08:10:46 MS Q0I Operating system call writev failed (error no. 32 )
08:10:46 MS Q0I Operating system call writev failed (error no. 32 )
08:10:47 MS Q0O Multiple Client logon (MSLAPP_PRD_01 ) for message server
08:10:47 RD Q0I Operating system call writev failed (error no. 32 )
08:10:47 RD USER01 Q0I Operating system call writev failed (error no. 32 )
08:10:47 RD USER02 Q0I Operating system call writev failed (error no. 32 )
08:10:49 DP Q0N Failed to send a request to the message server
08:10:51 DIA 12 999 USER02 SESS R47 Delete session 001 after error 050
08:10:57 DP Q0N Failed to send a request to the message server
08:11:00 DP Q0K Connection to message server (on msldbci) established
08:11:00 DP Q1C MsgServer Hardware ID Was Determined
08:11:00 DIA 01 R0T The update was activated
08:12:53 DP Q04 Connection to user 12716 (DHARAMPAL ), terminal 41 (new-lab ) lo
08:40:46 DIA 02 000 SAPSYS #### R2G RFC server deleted after timeout
and on dailog instance error is like..
08:39:44 DP Q0M Message server disconnected
08:39:49 DIA 03 999 USERxx GI0 Error calling the central lock handler
08:39:49 DIA 03 999 USERxx GI2 > Unable to reach central lock handler
08:39:49 DIA 04 999 USERxx GI0 Error calling the central lock handler
08:39:49 DIA 04 999 USERxx GI2 > Unable to reach central lock handler
08:39:49 DIA 04 999 USERxx D01 Transaction Canceled MC 600 ( )
08:39:49 DP Q0N Failed to send a request to the message server
08:39:49 DIA 02 999 USERxx GI0 Error calling the central lock handler
08:39:49 DIA 00 999 USERxx GI0 Error calling the central lock handler
08:39:49 DIA 11 999 USERxx GI0 Error calling the central lock handler
08:39:49 DP Q0N Failed to send a request to the message server
08:39:49 DIA 11 999 USERxx GI2 > Unable to reach central lock handler
08:39:49 DIA 00 999 USERxx GI2 > Unable to reach central lock handler
08:39:49 DIA 02 999 USERxx GI2 > Unable to reach central lock handler
08:39:49 DIA 09 999 USERxx GI0 Error calling the central lock handler
08:39:49 DIA 09 999 USERxx GI2 > Unable to reach central lock handler
08:39:49 SPO 14 000 SAPSYS GI0 Error calling the central lock handler
08:39:49 SPO 14 000 SAPSYS GI2 > Unable to reach central lock handler
08:39:49 DIA 08 R0Z The update dispatch info was reset
08:39:49 SPO 14 000 SAPSYS GI0 Error calling the central lock handler
08:39:49 SPO 14 000 SAPSYS GI2 > Unable to reach central lock handler
08:39:49 SPO 14 000 SAPSYS GI0 Error calling the central lock handler
08:39:49 SPO 14 000 SAPSYS GI4 > Dequeue All call failed
08:39:49 SPO 14 000 SAPSYS GI0 Error calling the central lock handler
08:39:49 SPO 14 000 SAPSYS GI2 > Unable to reach central lock handler
08:39:49 SPO 14 000 SAPSYS GI0 Error calling the central lock handler
08:39:49 SPO 14 000 SAPSYS GI4 > Dequeue All call failed
08:39:49 DIA 07 000 SAPSYS GI0 Error calling the central lock handler
08:39:49 DIA 07 000 SAPSYS GI2 > Unable to reach central lock handler
Plz suggest, what should i check. Now, system is running with no error.
Ankit
Hi Ankit,
The error type DP is due to network problems.May be at that time network is not good.
Regards,
Kalyan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ankit,
This problem usually occurs on Windows-based application servers that have a large number of configured work processes (more than 50). This problem cannot usually be reproduced. This response is caused by a long initialization phase of the work processes in the systems described above. You execute initialization of the work process in a critical section that is protected by a semaphore. If you perform a lock operation shortly after the system starts, the work process that executes this lock operation requests the same semaphore. If many work processes request this semaphore in the initialization, the system cannot perform the lock operation and it terminates with the syslog entry mentioned above. The problem no longer occurs after the work processes are initialized.
Regards,
Sachin Rane.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ankit
Please check the enque,check that all the servers are using the same kernel patch level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please execute sick or SM28 transaction and check whether it reports any error.
Something is wrong with enque process.
In addition also check note 79084.
Regards,
Sachin Rane.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
any suggestions ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.