on 10-26-2007 11:40 AM
Hi,
I found this logs in the SM21.
Please find the error check it and suggest me.
ECF Failed to create log for job Z6UMM0002
ECF Failed to create log for job Z6UMM0002
F20 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
F20 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
R47 Delete session 001 after error 023
R47 Delete session 001 after error 023
Q0E Signal 11 received by operating system
Q0E Signal 11 received by operating system
Q01 Start Workproc48, 11 times since system startup. PID 4509
Q01 Start Workproc49, 10 times since system startup. PID 4510
F3T Invalid object name for TemSe object: " "
F3T Invalid object name for TemSe object: " "
ECF Failed to create log for job Z6UMM0002
ECF Failed to create log for job Z6UMM0002
F20 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
F20 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
Please check it ASAP.
Regards
S.Prasad
Hi,
We are installed the CROClink in the server. After that there is no problem.
Regards
S.Prasad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prasad,
The
Calling program reports invalid handle ...
message is usually only a follow up error. As mentioned above, the root cause is that in some kernel layer, a signal was caught.
First of all, you should check the dev_w<xx> file to which the
Signal 11 received by operating system
message belongs. This dev file contains the C-Stack of the SAP kernel that will show us the kernel function that actually caused this exception.
It would be best to open a customer messages with this information, since, especially in case the signal was caused by DB client library functions, further analysis can be very difficult.
Best Regards,
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Signal 11 is "SIGSEGV" - the program is terminating due to a null pointer access.
Which kernel version and patchlevel are you using?
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.