on 09-26-2007 8:24 PM
We are upgrading our BI environment from 2004s SP-STACK 09 to 12. During the upgrade of kernel the JSPM crashed and system is not able to start after that. This is a ABAP+J2EE addin system. Whenever we are trying to start the system, dispatcher greys out. Following are the log file details.
-
trc file: "dev_ms", trc level: 1, release: "700"
-
[Thr 448] Wed Sep 26 13:55:34 2007
[Thr 448] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 562 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 73
intno 20050900
make: multithreaded, Unicode, 64 bit, optimized
pid 3684
[Thr 448] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 3684) [msxxserv.c 1824]
[Thr 448] load acl file = E:\usr\sap\SID\SYS\global\ms_acl_info.DAT
[Thr 448] MsGetOwnIpAddr: my host addresses are :
[Thr 448] 1 : [139.51.77.153] a.b.c.com (HOSTNAME)
[Thr 448] 2 : [127.0.0.1] a.b.c.com(LOCALHOST)
[Thr 448] MsHttpInit: full qualified hostname = a.b.c.com
[Thr 448] HTTP logging is switch off
[Thr 448] set HTTP state to LISTEN
[Thr 448] MsHttpOwnDomain: own domain[1] = a.b.c.com
[Thr 448] ms/icf_info_server : deleted
[Thr 448] *** I listen to port sapmsDB1 (3601) ***
[Thr 448] *** I listen to internal port 3901 (3901) ***
[Thr 448] *** HTTP port 8101 state LISTEN ***
[Thr 448] CUSTOMER KEY: >T1519191498<
-
trc file: "sapstartsrv.log", trc level: 0, release: "700"
-
pid 1476
Wed Sep 26 14:20:40 2007
SAP HA Trace: Build in SAP Microsoft Cluster library '700, patch 102, changelist 896495' initialized
Initializing SAPControl Webservice
SapSSLInit failed => https support disabled
Starting WebService Named Pipe thread
Starting WebService thread
Webservice named pipe thread started, listening on port
.\pipe\sapcontrol_01
Webservice thread started, listening on port 50113
Please suggest some solutiopn
Kevin,
If you haven't done so, please check the following files:
the dev_dispatcher from work directory and defaultTrace.trc file from "Drive:\usr\sap\<SID>\DVEBMGS<no>\j2ee\cluster\dispatcher\log" these files should point out the issue.
Thanks,
Kalyan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Navin,
Here are the steps to come out of safe mode:
Start the configtool script file from the /usr/sap/<SID>/<instance name>/j2ee/configtool directory.
Choose File -> Safe Mode. A dialog box appears.
From the Safe Mode Enabled drop-down list, choose:
Yes to enable safe mode.
No to disable safe mode.
Choose OK.
Save the settings and confirm all the messages that are displayed.
Restart the J2EE Engine.
Hope this helps, points are welcome.
-Kalyan.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.