Critical shutdown was invoked. Reason is: Enque Server was restarted ...

Question

Hello,
the following Error appears and the Portal restarts automatically. I don't know how do solve this issue.
Critical shutdown was invoked. Reason is: Enque Server was restarted without restarting the J2EE engine.
/usr/sap/<sid>/SCS*/work:
[Thr  1] Mon May  4 21:18:12 2009
[Thr  1] ShadowTable:attach: ShmCreate - pool doesn't exist
[Thr  1] Enqueue: EnqMemStartupAction Utc=1241464692
[Thr  1] Enqueue Info: replication enabled
[Thr  1] Enqueue Info: enque/replication_dll not set
[Thr  1] ShadowTable:attach: ShmCreate - pool doesn't exist
[Thr  1] *** ERROR => EnqRepAttachOldTable: failed to get information on old replication table: rc=-1 [enxxmrdt.h   393]
[Thr  1] EnqRepRestoreFromReplica: failed to attach to old replication table: rc=-1
[Thr  1] enque/backup_file disabled in enserver environment
[Thr  1] Mon May  4 17:04:31 2009
[Thr  1] *** ERROR => MsSRead: NiBufReceive (rc=NIECONN_BROKEN) [msxxserv_mt. 10598]
[Thr  1] *** ERROR => MsSClientHandle: MsSRead C2 (J2EE526266050), MSEINTERN [msxxserv_mt. 4166]
[Thr  1] MsJ2EE_AddDisconnectedNode: add node [526266050] into disconnect list
[Thr  1] *** ERROR => MsSRead: NiBufReceive (rc=NIECONN_BROKEN) [msxxserv_mt. 10598]
[Thr  1] *** ERROR => MsSClientHandle: MsSRead C3 (J2EE548308450), MSEINTERN [msxxserv_mt. 4166]
[Thr  1] MsJ2EE_AddDisconnectedNode: add node [548308450] into disconnect list
regards

Answer 1

Hi Michael,
enqueue server is part of the central services (SCS). If SCS is restarted the J2EE Engine will restart also by automatical process.
The error means enqueue did not find a replication table on the host where it was started - maybe after a failover. So either there was no replication table at all (because the replication server was not started prior to the failover), or the OS did not start the enqueue server on the host the replication server was running on or the replication server was started with a different instance number than the enqueue server.
Check those points of your configuration and review note 1249256.
You may also try changing the following row in the replication start profiles to see if it helps:
eg: Start_Program_01 =local $(_ER) pf=$(DIR_PROFILE)/P01_ERS01_hseep01en NR=00
You can take note 39876 as reference to this string.                     
Hope this helps.
Cheers, Anja