We are working on getting a DR (Disaster recovery) instance of EP6.0 started up after a restore from an offline backup of our Production Portal. This is on a separate piece of hardware. This is the J2EE version 6.2 and Ep 6.0 Sp2 Patch 37. This version is working fine on the Production Portal. When we start up the J2EE (using go.bat or the framework) we get the following error-
[OS: SunOS] [VM vendor: Sun Microsystems Inc.] [VM version: 1.3.1_11-b02] [VM type: Java HotSpot(TM) Client VM]
SAP J2EE Engine Version 6.20 PatchLevel 78993.20 is starting...
Loading: LogManager ...
Loading: SystemThreadManager ...
Loading: ThreadManager ...
Loading: TimeoutManager ...
Loading: MemoryManager ...
Loading: PoolManager ...
Loading: PolicyManager ...
Loading: IpVerificationManager ...
Loading: ClusterManager ...
Loading: ClassLoaderManager ...
Loading: SwapManager ...
Loading: LockManager ...
Loading: R3StartupManager ...
Loading: ServiceManager ...
Loading core services:
Starting core service monitor ... done. (215 ms)
Starting core service p4 ... done. (310 ms)
Starting core service log ... done. (447 ms)
Starting core service dbms ... done. (1145 ms)
Starting core service security ... done. (3008 ms)
Starting core service naming ... done. (5369 ms)
Starting core service admin ... done. (5616 ms)
Timeout starting core services. Kernel not started.
[ServiceManager]: * Timeout starting core services. Kernel not started.
Timeout starting core services.
****************************************************************************
Not started services:
-
deploy
file
[ServiceManager]:
Timeout starting core services.
****************************************************************************
Not started services:
-
deploy
file
Loading: ServiceManager returned false!
Kernel not loaded. System halted.
[Framework -> criticalShutdown] Kernel startup failed.
We need assistance as soon as possible.
Any pointers would help and will be greatly appreciated!
S. Rao