Question:
hello
I am getting the error message "System Lock. Please contact your system administrator" when trying to create a new user by copying the account of another user.
I looked in the system Log and found these messages:
QUESTION is how do I start the messge server and how do i release this lock and what is the enqueue server!??
Basically HELP!!!
|11:07:18|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:07:18|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:07:18|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:07:18|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:07:48|RD | | | | |S30|SAP gateway was closed
|11:07:50|DIA| 2| | | |Q02|Stop Workproc 2, PID 2280
|11:07:50|DIA| 5| | | |Q02|Stop Workproc 5, PID 2304
|11:07:50|UPD| 7| | | |Q02|Stop Workproc 7, PID 2320
|11:07:50|UPD| 6| | | |Q02|Stop Workproc 6, PID 2312
|11:07:50|DIA| 4| | | |Q02|Stop Workproc 4, PID 2296
|11:07:50|SPO|11| | | |Q02|Stop Workproc11, PID 2352
|11:07:51|DIA| 0| | | |Q02|Stop Workproc 0, PID 2264
|11:07:51|DIA| 3| | | |Q02|Stop Workproc 3, PID 2288
|11:07:51|BTC| 9| | | |Q02|Stop Workproc 9, PID 2336
|11:07:51|ENQ| 8| | | |Q02|Stop Workproc 8, PID 2328
|11:07:52|BTC|10| | | |Q02|Stop Workproc10, PID 2344
|11:07:52|UP2|12| | | |Q02|Stop Workproc12, PID 2360
|11:07:56|DIA| 1| | | |Q02|Stop Workproc 1, PID 2272
|11:07:57|DP | | | | |Q0M|Message server disconnected
|11:07:57|DP | | | | |Q05|R/3 System stop, dispatcher PID 21
|11:07:58|MS | | | | |Q02|Stop Msg Server, PID 2160
|11:41:58|MS | | | | |E10|Buffer SCSA Generated with Length 4096
|11:41:58|MS | | | | |Q01|Start Msg Server, 1 times since system startup. PID 1560
|11:42:02|DP | | | | |Q00|R/3 System start, SAPSYSTEM 00, dispatcher PID 2128
|11:42:07|DP | | | | |GZZ|> 1 possible network problems detected - check tracefile and adjus
|11:42:09|DP | | | | |Q0K|Connection to message server (on athsw2k006) established
|11:42:09|RD | | | | |S00|SAP Gateway Started (PID: 2196)
|11:42:09|DP | | | | |Q1C|MsgServer Hardware ID Was Determined
|11:42:16|WRK| 0| | | |Q0Q|Start Workproc 4, Pid 2248
|11:42:16|WRK| 0| | | |Q0Q|Start Workproc 2, Pid 2232
|11:42:17|WRK| 0| | | |Q0Q|Start Workproc 7, Pid 2272
|11:42:17|WRK| 0| | | |Q0Q|Start Workproc 3, Pid 2240
|11:42:17|WRK| 0| | | |Q0Q|Start Workproc 5, Pid 2256
|11:42:18|WRK| 0| | | |Q0Q|Start Workproc10, Pid 2296
|11:42:19|WRK| 0| | | |Q0Q|Start Workproc 8, Pid 2280
|11:42:20|WRK| 0| | | |Q0Q|Start Workproc12, Pid 2312
|11:42:21|WRK| 0| | | |Q0Q|Start Workproc 0, Pid 2216
|11:42:21|WRK| 0| | | |Q0Q|Start Workproc 6, Pid 2264
|11:42:26|WRK| 0| | | |Q0Q|Start Workproc 1, Pid 2224
|11:42:26|WRK| 0| | | |Q0Q|Start Workproc 9, Pid 2288
|11:42:30|WRK| 0| | | |Q0Q|Start Workproc11, Pid 2304
|11:42:35|SPO|11| | | |BB0|Buffer TABL started with 30000000 bytes
|11:42:35|SPO|11| | | |BB0|Buffer TABLP started with 10240000 bytes
|11:42:36|SPO|11| | | |BB0|Buffer EIBUF started with 4096k bytes
|11:42:36|SPO|11| | | |BB0|Buffer ESM started with 4096k bytes
|11:42:36|SPO|11| | | |BB0|Buffer CUA started with 3000k bytes
|11:42:36|SPO|11| | | |BB0|Buffer OTR started with 4096k bytes
|11:42:36|SPO|11| | | |BB0|Buffer CALE started with 500000 bytes
|11:42:39|SPO|11| | | |AV6|Initialization SCSA for Security Audit completed, number of selections 02
|11:42:42|SPO|11| | | |CP2|In table TCPDB, there are 0 entries
|11:42:42|SPO|11| | | |E10|Buffer RSCPCCC Generated with Length 6000000
|11:42:46|DIA| 0| | | |GJ0|Incorrect lock handler configuration
|11:42:46|DIA| 0| | | |GJ2|> No. of enqueue processes in non-lock servers must be 0
|11:42:46|DIA| 0| | | |GZZ|> rdisp/myname=ATHSW2K006_Y11_00 enxxhead1260
|11:42:46|DIA| 0| | | |GZZ|> rdisp/enqname=athsw2k006_Y11_00 enxxhead1261
|11:42:46|DIA| 0| | | |GZZ|> rdisp/wp_no_enq=1 enxxhead1262
|11:42:46|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:42:46|DIA| 0| | | |GI0|Error calling the central lock handler
|11:42:46|DIA| 0| | | |GI2|> Unable to reach central lock handler
|11:42:47|SPO|11|000|SAPSYS | |GJ0|Incorrect lock handler configuration
|11:42:47|SPO|11|000|SAPSYS | |GJ2|> No. of enqueue processes in non-lock servers must be 0
|11:42:47|SPO|11|000|SAPSYS | |GZZ|> rdisp/myname=ATHSW2K006_Y11_00 enxxhead1260
|11:42:47|SPO|11|000|SAPSYS | |GZZ|> rdisp/enqname=athsw2k006_Y11_00 enxxhead1261
|11:42:47|SPO|11|000|SAPSYS | |GZZ|> rdisp/wp_no_enq=1 enxxhead1262
|11:42:47|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:42:47|SPO|11|000|SAPSYS | |GI0|Error calling the central lock handler
|11:42:47|SPO|11|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:42:47|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:42:47|SPO|11|000|SAPSYS | |GI0|Error calling the central lock handler
|11:42:47|SPO|11|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:42:47|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:42:47|SPO|11|000|SAPSYS | |GI0|Error calling the central lock handler
|11:42:47|SPO|11|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:42:49|DIA| 4|000|SAPSYS | |GJ0|Incorrect lock handler configuration
|11:42:49|DIA| 4|000|SAPSYS | |GJ2|> No. of enqueue processes in non-lock servers must be 0
|11:42:49|DIA| 4|000|SAPSYS | |GZZ|> rdisp/myname=ATHSW2K006_Y11_00 enxxhead1260
|11:42:49|DIA| 4|000|SAPSYS | |GZZ|> rdisp/enqname=athsw2k006_Y11_00 enxxhead1261
|11:42:49|DIA| 4|000|SAPSYS | |GZZ|> rdisp/wp_no_enq=1 enxxhead1262
|11:42:49|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:42:49|DIA| 2|000|SAPSYS | |GJ0|Incorrect lock handler configuration
|11:42:49|DIA| 2|000|SAPSYS | |GJ2|> No. of enqueue processes in non-lock servers must be 0
|11:42:49|DIA| 2|000|SAPSYS | |GZZ|> rdisp/myname=ATHSW2K006_Y11_00 enxxhead1260
|11:42:49|DIA| 2|000|SAPSYS | |GZZ|> rdisp/enqname=athsw2k006_Y11_00 enxxhead1261
|11:42:49|DIA| 2|000|SAPSYS | |GZZ|> rdisp/wp_no_enq=1 enxxhead1262
|11:42:49|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:42:49|DIA| 2|000|SAPSYS | |GI0|Error calling the central lock handler
|11:42:49|DIA| 2|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:20|DIA| 0|000| | |A10|Initialization complete
|11:43:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:29|SPO|11|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:29|DIA| 1|000|SAPSYS | |GJ0|Incorrect lock handler configuration
|11:43:29|DIA| 1|000|SAPSYS | |GJ2|> No. of enqueue processes in non-lock servers must be 0
|11:43:29|DIA| 1|000|SAPSYS | |GZZ|> rdisp/myname=ATHSW2K006_Y11_00 enxxhead1260
|11:43:29|DIA| 1|000|SAPSYS | |GZZ|> rdisp/enqname=athsw2k006_Y11_00 enxxhead1261
|11:43:29|DIA| 1|000|SAPSYS | |GZZ|> rdisp/wp_no_enq=1 enxxhead1262
|11:43:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:29|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:29|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:29|SPO|11|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:29|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:29|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWDHEX
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWDHEX
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job RFKGEN
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job UPDATE_IDES_REORG_DATE_(14_DAYS)
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job Z_PROJCASH_ON_CL800_COCODE1000
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job PERIODENVERSCHIEBER_800
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job ZIDSDATA
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |GI0|Error calling the central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job ZID_KREDI
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job PERIODEN-VERSCHIEBER-ATLANTIK
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job ZID_CREDIT_NOTE
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job ZIDSCHCK
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job ZCONN
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWERRE
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWCOND
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWERRE
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWCOND
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWUR3FS
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWCLEAR
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SWWCLEAR
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job RSBTCDEL
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SAP_REORG_SPOOL
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SAP_REORG_JOBS
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SAP_REORG_BATCHINPUT
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:30|DIA| 1|000|SAPSYS | |ECP|Background scheduler: 26 . Error message with delay level 5
|11:43:30|DIA| 1|000|SAPSYS | |EB9|Batch scheduler: Unable to perform job SAP_REORG_ABAPDUMPS
|11:43:30|DIA| 1|000|SAPSYS | |EB7|> Cause: Error within the lock operation
|11:43:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language 1 Code Page 8400 Locale Chinese_CHN.936
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language 3 Code Page 8500 Locale Korean_Korea.949
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language C Code Page 1401 Locale Czech_Czech.28592
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language J Code Page 8000 Locale Japanese_Japan.932
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language L Code Page 1401 Locale Polish_Poland.28592
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language M Code Page 8300 Locale CHT_TWN.950
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language Q Code Page 1401 Locale Slovak_Slovak.28592
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language R Code Page 1500 Locale Russian_Russia.28595
|11:43:37|DIA| 1|000| |SESS|CPG|Failed to Set Environment for Language T Code Page 1610 Locale Turkish_Turkey.28599
|11:43:38|DIA| 1|800|DTHAKRAR |SESS|R68|Perform rollback
|11:43:41|DIA| 1|800|DTHAKRAR |SESS|AB0|Run-time error "START_CALL_SICK" occurred
|11:43:42|DIA| 1|800|DTHAKRAR |SESS|AB1|> Short dump "030806 114341 ATHSW2K0 DTHAKRAR " generated
|11:44:29|DIA| 3|000|SAPSYS | |GJ0|Incorrect lock handler configuration
|11:44:29|DIA| 3|000|SAPSYS | |GJ2|> No. of enqueue processes in non-lock servers must be 0
|11:44:29|DIA| 3|000|SAPSYS | |GZZ|> rdisp/myname=ATHSW2K006_Y11_00 enxxhead1260
|11:44:29|DIA| 3|000|SAPSYS | |GZZ|> rdisp/enqname=athsw2k006_Y11_00 enxxhead1261
|11:44:29|DIA| 3|000|SAPSYS | |GZZ|> rdisp/wp_no_enq=1 enxxhead1262
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|DIA| 3|000|SAPSYS | |GI0|Error calling the central lock handler
|11:44:29|DIA| 3|000|SAPSYS | |GI2|> Unable to reach central lock handler
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:44:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:45:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:45:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:45:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|11:45:30|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|12:29:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|12:30:21|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|12:30:21|DIA| 0|800|PBAILEY | |GI0|Error calling the central lock handler
|12:30:21|DIA| 0|800|PBAILEY | |GI2|> Unable to reach central lock handler
|12:30:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|12:30:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
|12:30:29|MS | | | | |Q0U|Client athsw2k006_Y11_00 is not known to the message server
Answer:
I had a similar problem on a Win2k box. RZ10 would not run either. Turned out it was a upper/lower case problem between my hostname and Sap profiles. I think it all started when somehow the operating system host file was overwritten with a blank file so there were no references to Sap. Just go through the default, instance, start profiles and the system host file and use Notepad to replace the case with the right one. First you should back these files up. You can get the hostname from a command prompt with "hostname". If it's lower case then make sure it is the same in the files mentioned above.
Answer:
hi!
i had the same problem before.if the host file entry is ok then just install the NT patch which comes with the installation master CD.