Problem in starting SAP server.

Currently our production system is down.we see that dispatcher is unable to conenct to the message server.
production is running on cluetr environment. when i login in clusadmin mmc i see saprd cluter group went to offline and unable to bring online.
Also we see sapprd_00 service is stopped and failed to start the service.
The SAPPRD_00 service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Please see last 50 lines of dispatcher log.
Mon Jun 07 13:48:21 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:48:42 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:49:02 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 328
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:49:23 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:49:37 2010
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5011]
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c   5131]
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5011]
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5011]
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c   5131]
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c   5131]
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5011]
Mon Jun 07 13:49:43 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:50:03 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 332
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:50:23 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 328
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:50:44 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:50:52 2010
ERROR => MsISnd2: not_attached [msxxi.c      1321]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c   5011]
Mon Jun 07 13:51:04 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Mon Jun 07 13:51:24 2010
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2823]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 336
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.201.20:3900) [nixxi.cpp    2823]
ERROR => MsIAttachEx: NiBufConnect to sapclusgrp/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
Highly Appreciate your early response on this.
Regards,
Vinod

Dear Vinod,
Just do the below things
-> ask your cluster admn to bring offline SAP instances & then thereafter your database as well.
-> After that goto usr folder where you find to folder namely ASCS** and SCS** ,In each of this folder there is a sapstartsrv.exe & sapstartsrv.exe.new.
-> Rename the sapstartsrv.exe to sapstartsrv.exe.old &
-> Rename the sapstartsrv.exe to sapstartsrv.exe
-> Now ask cluster administrator to bring the database online first then the SAP instances
-> check now whether your SAP will up or not this time.
Let us know if you find any other errors.
Thank You.
Kind Regards,
Rafikul Hussain

Similar Messages

Hiiii.....when i try to start SAP server its not geting start.....

hiiii.....when i try to start SAP server its not geting start.....
may be problem related with dialog work process....
i attached DEV_W0 log file please help mi out
thanks
trc file: "dev_w0", trc level: 1, release: "620"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, M
B
B Sun Feb 05 19:01:08 2012
B create_con (con_name=R/3)
B Loading DB library 'F:\usr\sap\A12\SYS\exe\run\dboraslib.dll' ...
B Library 'F:\usr\sap\A12\SYS\exe\run\dboraslib.dll' loaded
B Version of 'F:\usr\sap\A12\SYS\exe\run\dboraslib.dll' is "620.02", patchlevel (0.549)
B New connection 0 created
M systemid   560 (PC with Windows NT)
M relno      6200
M patchlevel 0
M patchno    674
M intno      20020600
M pid        2172
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2172) [dpxxdisp.c   1028]
I MtxInit: -2 0 0
M DpShMCreate: sizeof(wp_adm)          12784     (752)
M DpShMCreate: sizeof(tm_adm)          1690816     (8412)
M DpShMCreate: sizeof(wp_ca_adm)     18000     (60)
M DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
M DpShMCreate: sizeof(comm_adm)     192000     (384)
M DpShMCreate: sizeof(wall_adm)     (22440/34344/56/100)
M DpShMCreate: SHM_DP_ADM_KEY          (addr: 034E0040, size: 1977824)
M DpShMCreate: allocated sys_adm at 034E0040
M DpShMCreate: allocated wp_adm at 034E0560
M DpShMCreate: allocated tm_adm_list at 034E3750
M DpShMCreate: allocated tm_adm at 034E3778
M DpShMCreate: allocated wp_ca_adm at 03680438
M DpShMCreate: allocated appc_ca_adm at 03684A88
M DpShMCreate: allocated comm_adm_list at 036861F8
M DpShMCreate: allocated comm_adm at 03686210
M DpShMCreate: allocated ca_info at 036B5010
M DpShMCreate: allocated wall_adm at 036B5018
X
X Sun Feb 05 19:01:09 2012
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation std
M <EsNT> Memory Reset enabled as NT default
X ES initialized.
M calling db_connect ...
C Got ORACLE_HOME=F:\oracle\ora92 from environment
C Client NLS settings: AMERICAN_AMERICA.WE8DEC
C Logon as OPS$-user to get SAPA12's password
C Connecting as /@A12 on connection 0 ...
C Attaching to DB Server A12 (con_hdl=0,svchp=075513DC,svrhp=07553644)
C
C Sun Feb 05 19:01:19 2012
C Starting user session (con_hdl=0,svchp=075513DC,srvhp=07553644,usrhp=0755BE24)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1033
[dboci.c      3718]
C *** ERROR => CONNECT failed with sql error '1033'
[dboci.c      9601]
C Try to connect with default password
C Connecting as SAPA12/<pwd>@A12 on connection 0 ...
C Starting user session (con_hdl=0,svchp=075513DC,srvhp=07553644,usrhp=0755BE24)
C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1033
[dboci.c      3718]
C *** ERROR => CONNECT failed with sql error '1033'
[dboci.c      9601]
B ***LOG BV3=> severe db error 1033      ; work process is stopped [dbsh#2 @ 957] [dbsh    0957 ]
B ***LOG BY2=> sql error 1033   performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> ORA-01033: ORACLE initialization or shutdown in progress [dblink#1 @ 419] [dblink 0419 ]
M ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1102]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   8437]
M
M Info for wp 0
M
M    stat = 4
M    reqtype = 1
M    act_reqtype = -1
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = -1
M    rq_source = 255
M    last_tid = 0
M    last_mode = 0
M    rfc_req = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server wagh_A12_00 on host wagh (wp 0)
M * ERROR       tskh_init: db_connect
M *
M * TIME        Sun Feb 05 19:01:19 2012
M * RELEASE     620
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        8569
M * COUNTER     1
M *
M *****************************************************************************
M
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   672]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 237]
M Entering ThSetStatError
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 2172) [dpnttool.c   346]

hiii guys,
My problem still not solve..now paste DEV_disp log file...here show work process died...plz look that n give mi solution..
trc file: "dev_disp", trc level: 1, release: "620"
Wed Feb 08 17:06:12 2012
kernel runs with dp version 3(ext=1) (@(#) DPLIB-INT-VERSION-3)
length of sys_adm_ext is 304 bytes
Wed Feb 08 17:06:13 2012
systemid   560 (PC with Windows NT)
relno      6200
patchlevel 0
patchno    674
intno      20020600
pid        2412
***LOG Q00=> DpSapEnvInit, DPStart (00 2412) [dpxxdisp.c   978]
     shared lib "dw_xml.dll" version 674 successfully loaded
     shared lib "dw_xtc.dll" version 674 successfully loaded
     shared lib "dw_stl.dll" version 674 successfully loaded
Wed Feb 08 17:06:17 2012
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3212]
MtxInit: -2 0 0
DpShMCreate: sizeof(wp_adm)          11280     (752)
DpShMCreate: sizeof(tm_adm)          1690816     (8412)
DpShMCreate: sizeof(wp_ca_adm)     18000     (60)
DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
DpShMCreate: sizeof(comm_adm)     192000     (384)
DpShMCreate: sizeof(wall_adm)     (22440/34344/56/100)
DpShMCreate: SHM_DP_ADM_KEY          (addr: 034E0040, size: 1976320)
DpShMCreate: allocated sys_adm at 034E0040
DpShMCreate: allocated wp_adm at 034E0560
DpShMCreate: allocated tm_adm_list at 034E3170
DpShMCreate: allocated tm_adm at 034E3198
DpShMCreate: allocated wp_ca_adm at 0367FE58
DpShMCreate: allocated appc_ca_adm at 036844A8
DpShMCreate: allocated comm_adm_list at 03685C18
DpShMCreate: allocated comm_adm at 03685C30
DpShMCreate: allocated ca_info at 036B4A30
DpShMCreate: allocated wall_adm at 036B4A38
MBUF state OFF
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation std
<EsNT> Memory Reset enabled as NT default
<EsNT> EsIUnamFileMapInit: Initialize the memory 1207 MB
<ES> 1206 blocks reserved for free list.
ES initialized.
***LOG Q0K=> DpMsAttach, mscon ( wagh) [dpxxdisp.c   9115]
Wed Feb 08 17:06:18 2012
CCMS: Initalizing shared memory of size 20000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6200, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   941]
DpMsgAdmin: Set patchno for this platform to 674
Release check o.K.
Wed Feb 08 17:06:58 2012
ERROR => W5 (pid 2712) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W5
ERROR => W9 (pid 2744) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W9
ERROR => W11 (pid 2760) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W11
my types changed after wp death/restart 0xbf --> 0xbb
Wed Feb 08 17:07:18 2012
ERROR => W0 (pid 2672) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W0
ERROR => W1 (pid 2680) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W1
ERROR => W3 (pid 2696) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W3
ERROR => W4 (pid 2704) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W4
ERROR => W7 (pid 2728) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W7
ERROR => W8 (pid 2736) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W8
ERROR => W10 (pid 2752) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W10
ERROR => W12 (pid 2768) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W12
ERROR => W13 (pid 2776) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W13
my types changed after wp death/restart 0xbb --> 0xa1
Wed Feb 08 17:07:38 2012
ERROR => W2 (pid 2688) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W2
ERROR => W6 (pid 2720) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W6
ERROR => W14 (pid 2784) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W14
my types changed after wp death/restart 0xa1 --> 0x80
DP_FATAL_ERROR => DpEnvCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
DpModState: change server state from STARTING to SHUTDOWN
Wed Feb 08 17:07:45 2012
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   9341]
MBUF state OFF
MBUF component DOWN
***LOG Q05=> DpHalt, DPStop ( 2412) [dpxxdisp.c   7883]

Problem in starting SAP and DB2

Hi ,
I am facing problem in starting SAP,
I have installed the NW7.0 with DB2 trial version on SUSE LINUX Enterprise Server 10 SP2.
When I try start the SAP , It gives me the error
Why do I receive the error, "SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing." ?
Please can any one help me.
Thanks,
Sridhar

Dear Sridhar,
A TCP/IP communication error occurred while the START or STOP DATABASE MANAGER command was trying to establish connection with all the nodes defined in the sqllib/db2nodes.cfg configuration file.
possible solutions to fix SQL6048N:
Ensure that the node has the proper authorization defined in the .rhosts or the host.equiv files.
Ensure that the application is not using more than (500 + (1995 - 2 * total_number_of_nodes)) file descriptors at the same time.
Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
Ensure the profile file is written in the Korn Shell script format.
Ensure that all the host names defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
For my case, itu2019s as simple as updating the hostname information defined in sqllib/db2nodes.cfg configuration file!
The db2start command rocks again after updating the hostname information!
If youu2019ve the same DB2 SQL6048N error code when starting DB2 Instance processes with db2start command, confirm the hostname in sqllib/db2nodes.cfg is correct, especially after changing Linux networking information, such as the server hostname!
Definetely it will work when you update the host information in sqllib/db2nodes.cfg.
Please let me know if you have still issues.
Thanks
Kishore

Problem in starting SAP liveCache server

Hi,
I am getting the following error message when i tried to start SAP liveCache server with LC10.
"Restart of liveCache LC3 on saplc3cache terminated; reason: User LC3RFC has lock"
Message no. LVC072
Does anyone has idea! abt the error? why it comes and how it can be solved?
Thanks,
Venkat

Hi Christiane,
The startup procedure is not even reaching the lcinit script. There are absolutly no logs in knldiag and lcinit.log files. After little bit debugging I found the problem. But don't know how to solve it.
The problem occured when I was doing disrptive testing for the liveCache server.
When I kill ("KILL -9 PID") the liveCache server processes (<b>master first and then child</b>) there are some IPC resources hanging over there. These IPC resources (shared memory segments) holds some locks and are preventing the liveCache server to startup.
The problem is not happening when I kill child first and then master process (all the IPCs are getting removed in this case).
I am wondering whether SAP has any tool to remove these IPC resources for liveCache server uniquely for perticular liveCache server (something similar to cleanipc for SAP systems).
I can't write a script to remove all the IPC resources based on the user name ('sdb') which same for liveCache server and MaxDB. (Imagine a case where MaxDB(APO DB) and liveCache server are running together). Any other solutions?
Any answers/suggestions are most welcome.
Thanks,
Venkat

BASIS : Problem starting SAP Server.

Hi,
I have a IDES 4.7. It was working fine for last couple of months.
Now i have got probelm starting the server. below are my observation :
1. The instance should be green in color but currently it is Yellow in color.
2. Process list node contains MSG_SERVER.exe and DISPWORK.exe. MSG_SERVER is green and DISPWORK.exe is yellow in color.
3. DISP+WORK.exe has status "Running but dialoq queue standstill".
4.WP Table has all the work processes are in status : Run & Start : No.
Can somebody please help here.
Thanks

reinstalled server. closed

Problem in starting SAP

Dear All,
I have a problem during the startup of my Quality server, the Oracle (10.2g) database is mounting, but while I start the SAP it is giving me this error.
hgquasrv:hqsadm 1> startsap
awk: 0602-533 Cannot find or open file /usr/sap/HQS/SYS/profile/HQS_DVEBMGS07_hg
quasrv.
The source line number is 1.
awk: 0602-533 Cannot find or open file /usr/sap/HQS/SYS/profile/HQS_DVEBMGS07_hg
quasrv.
The source line number is 1.
awk: 0602-533 Cannot find or open file /usr/sap/HQS/SYS/profile/HQS_DVEBMGS07_hg
quasrv.
The source line number is 1.
awk: 0602-533 Cannot find or open file /usr/sap/HQS/SYS/profile/HQS_DVEBMGS07_hg
quasrv.
The source line number is 1.
Checking HQS Database
ABAP Database is not available via R3trans
Starting SAP-Collector Daemon
open logfile '/usr/sap/tmp/dev_coll.tmp' failed... use stderri
12:24:12 14.08.2008 ERROR: cannot open log file /usr/sap/tmp/dev_coll.tmp
12:24:12 14.08.2008 ERROR: Make sure directory /usr/sap/tmp exists or specify D
IR_PERF
12:24:12 14.08.2008 ERROR: in profile and run saposcol pf=<profile>
saposcol already running
Running /usr/sap/HQS/SYS/exe/run/startdb
Trying to start HQS database ...
Log file: /home/hqsadm/startdb.log
HQS database started
/usr/sap/HQS/SYS/exe/run/startdb completed successfully
Starting SAP Instance DVEBMGS07
Startup-Log is written to /home/hqsadm/startsap_DVEBMGS07.log
Instance Service on host hgquasrv started
Startup of Instance failed
See /home/hqsadm/startsap_DVEBMGS07.log for details
hgquasrv:hqsadm 2>
Can any body help me in this regards.
Thanks in advance.
Udaya

Hi,
These files I can see in the directory :
ls -l
total 40
-rwxrwxrwx   1 hqsadm   sapsys         2182 Jun 26 2007 DEFAULT.BAK
-rwxrwxrwx   1 hqsadm   sapsys         2300 Jun 26 2007 DEFAULT.PFL
-rw-rw----   1 hqsadm   sapsys         6894 Aug 06 18:03 HQS_DVEBMGS07_hgquasrv.BAK
-rwxrwxrwx   1 hqsadm   sapsys         3829 May 21 2007 START_DVEBMGS07_hgquasrv
drwxrwxrwx   2 hqsadm   sapsys          256 May 20 2007 oracle
Best Regards
Udaya
Edited by: Uday Bhaskar on Aug 14, 2008 9:47 AM

Problems to start SAP instance after reboot

Hello experts,
we are occuring a problem that we are not able to start our SAP instance after we applied some MS patches and rebooted the server. We also deinstalled these patches buzt this also did not help, so I guess the reason somewhere else.
We are running a SQL server 2000 on a Windows 2003 SP2 (32bit)
SAP kernel is 640 PL 304
The SQL server seems to operate normally, however when we try to start SAP via MMC the process disp+work fails (it's green for a few seconds, but then turn so grey).
In dev_w0 I can find this entry
C Mon Feb 22 12:35:18 2010
C OpenOledbConnection: line 23082. hr: 0x8000ffff [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
C sloledb.cpp [OpenOledbConnection,line 23082]: Error/Message: (err 17, sev 10), [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23082]: Error/Message: (err 0, sev 10), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
I hope you have an idea to solve the issue soon.
Thanks a lot
Philipp

Hi,
yes I read this SAP note however when I try to install this patch
It fails with message "installation unsuccessful"
Reason ??
Check the following:
1. Status of SQLServer Service(s)?
2. Windows Event Log Entries?
What is the SP level of SQL Server 2000 ?
Also, Perform the Connectivity Test as per[ this link|http://support.microsoft.com/kb/827422/].
Regards,
Bhavik G. Shroff

Problem in starting HTTP Server (Oracle 9i AS Rel 1 on Solaris 2.8)

Hi All,
I have installed Oracle9i database Rel1 (version 9.0.1) on Sun Solaris2.8) successfully and now, I'm trying to install Oracle 9i Application Server Rel1 (version 1.0.2.2.1) on the same system. I stopped the database before starting installion of AS. My installation is limited to Oracle Forms & Reports Services and Oracle HTTP Server. Installation successfully completed, but, it is failed to start HTTP server. The error I'm getting is:
Syntax error on line 14 of $ORACLE_HOME/Apache/Apache/conf/mod__sse.conf
AuroraService - directive already in effect for this server.
$ORACLE_HOME/Apache/Apache/bin/httpsctl start: httpd could not be started.
Line 14 in mod__sse.conf is:
AuroraService inst1_http
How can I resolve this issue ? Please help.
An early help would be highly appreciated.
Thanks in Advance.
Sajan Thomas

Hi,
I have resolved that issue by commenting that line. Since I'm not using servlets, I hope that wouldn't create any problems !
Sajan

Problem in starting weblogic server as proxy

I am using weblogic server as Proxy to forward the requests to weblogic cluster.
When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
I am Pasting my complete logs below.
Setting JVM memory params for server IRISProxy
Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
WLS Production Mode=true
./startWebLogic.sh[68]: B: not found.
maxfiles=8192
CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.4.1.05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
Starting WLS with line:
/home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
Bad level value for property: com.iplanet.services.debug.level
Bad level value for property: com.sun.identity.agents.logging.level
Bad level value for property: com.sun.am.policy.amFilter.audit.level
<Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
<Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
<Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
     at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
     at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
     at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
     at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
Can someone help me in solving this problem
Thanks
Kris

I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
WebLogic Temporary Patch for CR211812
WebLogic Temporary Patch for CR235145
Once i commented the above patches in the CLASSPATH.
The issue is resolved.

Problem of Starting the Server

I just downloaded
j2eesdk-1_4_02_2005Q2-windows.exe
to my windows machine and insatlled it.
When I started the verifying of Server by going to "Start menu, choose Programs -> Sun Microsystems -> Application Server PE-> Start Default Server", I did get the message as follows:
"Domain domain1 is ready to receive client requests. Additional services are being started in the background.....Press any key to continue"
But when I ran "http://localhost:8080", I got an error page with something like "can't find the web site".
I even tried to use "http://my real IP address here:8080", and I got the same error.
Could anyone tell me what might be the problem? Do I need to set up something somewhere else?
Thanks a lot

BTW, the server.log file gives me these messages:
[#|2005-10-13T11:24:12.828-0500|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-10-13T11:24:12.828-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Sun/AppServer/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\jdk\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\j2re1.4.2_09\bin;C:\Program Files\Java\j2re1.4.2_09\javaws;C:\Program Files\ATI Technologies\ATI Control Panel;C:\putty;C:\Sun\AppServer\bin;.
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Sun/AppServer/jdk/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-10-13T11:24:16.234-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer\imq\bin].|#]
[#|2005-10-13T11:24:16.234-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-10-13T11:24:16.750-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-10-13T11:24:17.203-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-10-13T11:24:17.609-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2005-10-13T11:24:17.625-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2005-10-13T11:24:18.296-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2005-10-13T11:24:18.312-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2005-10-13T11:24:18.312-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2005-10-13T11:24:18.984-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2005-10-13T11:24:21.562-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2005-10-13T11:24:22.703-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 74004224866254848|#]
[#|2005-10-13T11:24:22.843-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-10-13T11:24:22.984-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 74004225324023808|#]
[#|2005-10-13T11:24:23.500-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-10-13T11:24:23.500-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2005-10-13T11:24:23.515-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2005-10-13T11:24:23.578-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2005-10-13T11:24:23.640-0500|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-10-13T11:24:23.703-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2005-10-13T11:24:23.718-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2005-10-13T11:24:23.718-0500|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-10-13T11:24:23.718-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2005-10-13T11:24:23.812-0500|INFO|sun-appserver-pe8.1_02|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2005-10-13T11:24:24.671-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-10-13T11:24:24.687-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2005-10-13T11:24:24.734-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-10-13T11:24:24.750-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2005-10-13T11:24:24.796-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2005-10-13T11:24:24.796-0500|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]

Problem in starting Admin server in Obiee 11.1.1.5

Hi,
I'm facing a problem in starting the admin server in obiee 11.1.1.5. Since after the fresh installtion i'm facing difficulty in starting the admin server. so i request someone to give solution for the same.
the admin-server error log as follows:
###<Sep 27, 2011 11:50:45 AM IST> <Critical> <WebLogicServer> <mildh1712> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1317104445891> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
thanks in advance
Praveen

Hi,
I have resolved that issue by commenting that line. Since I'm not using servlets, I hope that wouldn't create any problems !
Sajan

HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

hi all, i am trying to start a managed server using nodeManager, but i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try to start
the managed server via adminserver console, i got the exception mentioned in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards marco

Marco.
Sorry, this is not a solution to your problem but i am trying to solve the same
problem for a week now.
I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
same error. I know that the default certificate installed provides a hostname
verification of weblogic.com. I turned the hostname verification off, i put in
the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
error when starting the managed server. I went ahead and created my own certificate
for machine called mallik, created my own passphrase, created a new keystore,
made the admin server view the keystore, used the same certificate for both the
admin server and the node manager. It still fails with the same error. I went
ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
totally confused now what needs to be done.
My nodeManger.hosts looks like this:
mallik 10.100.10.130
managedServer1 10.100.10.130
managedServer2 10.100.10.13
Below is the startNodeManager.cmd.
@echo off
@rem *************************************************************************
@rem This script can be used to start the WebLogic NodeManager
@rem
@rem This script sets the following variables before starting the NodeManager:
@rem
@rem WL_HOME - The root directory of your WebLogic installation.
@rem NODEMGR_HOME - The home directory for this NodeManager instance.
@rem JAVA_HOME - Location of the version of Java used to start WebLogic
@rem Server. This variable must point to the root directory of
@rem a JDK installation and will be set for you by the
@rem installer. See the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
list of
@rem supported JVMs on Windows NT.
@rem PATH - Adds the JDK and WebLogic directories to the system path.
@rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
@rem JAVA_OPTIONS - Java command-line options for running the server. (These
@rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
@rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
@rem -client, etc.)
@rem MEM_ARGS - The variable to override the standard memory arguments
@rem passed to java
@rem
@rem *************************************************************************
SETLOCAL
set WL_HOME=C:\bea7.0\weblogic700
set NODEMGR_HOME=%WL_HOME%\common\nodemanager
set JAVA_HOME=C:\bea7.0\jdk131_06
Call %WL_HOME%\common\bin\commEnv.cmd
@rem If NODEMGR_HOME does not exist, create it
:checkNodeManagerHome
if exist %NODEMGR_HOME% goto checkJava
echo.
echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
mkdir %NODEMGR_HOME%
@rem Check that java is where we expect it to be
:checkJava
if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
echo The JDK wasn't found in directory %JAVA_HOME%.
echo Please edit this script so that the JAVA_HOME
echo variable points to the location of your JDK.
goto finish
:runNodeManager
if not "%JAVA_VM%" == "" goto noResetJavaVM
rem set JAVA_VM=-hotspot
set JAVA_VM=%COMM_VM%
:noResetJavaVM
if not "%MEM_ARGS%" == "" goto noResetMemArgs
set MEM_ARGS=-Xms32m -Xmx200m
:noResetMemArgs
@echo on
set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
cd %NODEMGR_HOME%
#"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
"-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
"-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
"-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
"-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
goto finish
:finish
ENDLOCAL
I would appreciate if anybody can help me.
Mallik.
"Marco" <[email protected]> wrote:
>
hi all, i am trying to start a managed server using nodeManager, but
i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost
and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try
to start
the managed server via adminserver console, i got the exception mentioned
in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards marco

Problem while starting SAP servers

Hi,
We had a SAP Nw2004 SPS9 installation on a AIX box.
WE ahd downlaoded the SPS20 to upgarde the server.
During the upgrade process the m/c got hang.
As a result i retsrated the m/c.
Now while starting the sap server using "startsap all"
It is waiting at the followign stage
Checking ADA db Database
I coudl see the following lines in the startsap_SCS01.log file
:$
(290996) Starting: local ms.sapCTS_SCS01 pf=/usr/sap/CTS/SYS/profile/CTS_SCS01_ctsaix05
(327904) Starting: local en.sapCTS_SCS01 pf=/usr/sap/CTS/SYS/profile/CTS_SCS01_ctsaix05
(184394) Waiting for Child Processes to terminate.
Instance on host ctsaix05 started
Starting SAP-Collector Daemon
saposcol already running
Running /usr/sap/CTS/SYS/exe/run/startdb
/usr/sap/CTS/SYS/exe/run/startdb completed successfully
Checking ADA db Database
~
It just hangs there
Best Regards
Manoj

Hi Manoj,
Seems like the DB is not running... check the status of the database and try it again when the DB is online...
Also, check dev_w0 for errors...
Regards
Juan
Please reward with points if helpful

Problem getting started weblogic server (for BI Publisher)

Hello,
I am trying to run services BI publisher
But I can't because I have the following error:
SVR_GRP =
JAVA Memory arguments: -Xms256m -Xmx1024m
WLS Start Mode=Production
CLASSPATH=C:\BI11\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\BI11\Oracle_BI1\bifoundation\jdbc\jdk16\bijdbc.jar;;C:\BI11\patch_wls1035\profiles\defaul
t\sys_manifest_classpath\weblogic_patch.jar;C:\BI11\JROCKI~1.2-4\lib\tools.jar;C:\BI11\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\BI11\WLSERV~1.3\server\lib\weblo
gic.jar;C:\BI11\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\BI11\WLSERV~1.3\server\lib\webservices.jar;C:\BI11\modules\ORGAPA~1.1/lib/ant-all.jar;C
:\BI11\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\BI11\wlserver_10.3\server\lib\weblogic.jar;C:\BI11\oracle_common\modules\oracle.dms_11.1.1\dms.jar;C:\BI11\or
acle_common\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\BI11\oracle_common\modules\oracle.jmx_11.1.1\jmxspi.jar;C:\BI11\oracle_common\modules\oracle.odl_11.1.
1\ojdl.jar;C:\BI11\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\BI11\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\BI11\ORACLE~1\modules\orac
le.jrf_11.1.1\jrf.jar;C:\BI11\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\BI11\WLSERV~1.3\server\lib\xqrl.jar
PATH=C:\BI11\patch_wls1035\profiles\default\native;C:\BI11\WLSERV~1.3\server\native\win\32;C:\BI11\WLSERV~1.3\server\bin;C:\BI11\modules\ORGAPA~1.1\bin;C:\BI11\
JROCKI~1.2-4\jre\bin;C:\BI11\JROCKI~1.2-4\bin;C:\oracle11g\dbhome\bin;C:\;C:;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\VAIO;C:\Program Files\Ja
va\jre6\bin;;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\E900\system\bin32;C:\E900\DEMO\bin32;C:\BI11\Oracle_BI1\products\Essbase\EssbaseServer\bin;
C:\BI11\Oracle_BI1\bin;C:\BI11\Oracle_BI1\opmn\bin;C:\BI11\Oracle_BI1\opmn\lib;C:\BI11\Oracle_BI1\perl\bin;C:\BI11\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32,
compiled mode)
Starting WLS with line:
C:\BI11\JROCKI~1.2-4\bin\java -jrockit -Xms256m -Xmx1024m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\BI11\WLSERV~1.3\server\lib\weblogic.policy -D
weblogic.ProductionModeEnabled=true -Doracle.home=C:\BI11\Oracle_BI1 -da -Dplatform.home=C:\BI11\WLSERV~1.3 -Dwls.home=C:\BI11\WLSERV~1.3\server -Dweblogic.hom
e=C:\BI11\WLSERV~1.3\server -Dcommon.components.home=C:\BI11\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk
14Logger -Ddomain.home=C:\BI11\USER_P~1\domains\BIFOUN~1 -Djrockit.optfile=C:\BI11\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config
.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\servers\AdminServer -Doracle.domain.config.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1 -Digf.a
risidbeans.carmlloc=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\arisidprov
ider -Doracle.security.jps.config=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\
servers\AdminServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\BI11\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\BI11\ORACLE~1
\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dbi.oracle.home=C:\BI11\Oracle_BI1
-DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -Dweblogic.MaxMessageSize=50000000 -DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -DHYPERION_HOME=C:\BI11\Oracle_BI1 -DEPM_ORACLE_IN
STANCE=novalue -Dhyperion.home=C:\BI11\Oracle_BI1 -DEPM_REG_PROPERTIES_PATH=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig -Depm.useApplicationContextId=fal
se -Doracle.biee.search.bisearchproperties=C:\BI11\Oracle_BI1\bifoundation\jee\BISearchConfig.properties -Dweblogic.management.clearTextCredentialAccessEnabled=
true -Doracle.notification.filewatching.interval=2000 -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.SSL.enableJSSE=true -Dfile.enc
oding=utf-8 -Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.search.services.BIS
earchServiceConfiguration -Dxdo.server.config.dir=C:\BI11\user_projects\domains\bifoundation_domain\config\bipublisher -DXDO_FONT_DIR=C:\BI11\Oracle_BI1\common\
fonts -Dem.oracle.home=C:\BI11\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dw
lw.logErrorsToConsole=false -Dweblogic.ext.dirs=C:\BI11\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable thi
s check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disabl
e this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true><Apr 10, 2012 3:07:12 PM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting We
bLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32 from Oracle Corporation>
<Apr 10, 2012 3:07:12 PM CEST> <Info> <Management> <BEA-141107> <Version: Weblogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Apr 10, 2012 3:07:14 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Apr 10, 2012 3:07:14 PM CEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Apr 10, 2012 3:07:15 PM CEST> <Notice> <Log Management> <BEA-170019> <The server log file C:\BI11\user_projects\domains\bifoundation_domain\servers\AdminServer
\logs\AdminServer.log is opened. All server side log events will be written to this file.>
Apr 10, 2012 3:07:23 PM oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider pushLdapNamesTolibOvd
SEVERE: JPS-02592
<Apr 10, 2012 3:07:23 PM CEST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception sta
ck trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Er
ror message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseExcep
tion: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.>
<Apr 10, 2012 3:07:23 PM CEST> <Critical> <WebLogicServer> <BEA-000386> <Serversubsystem failed. Reason: weblogic.security.SecurityInitializationException: The
loading of OPSS java security policy provider failed due to exception, see theexception stack trace or the server log file for root cause. If still see no obv
ious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd f
or service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.
SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message:JPS-02592: Failed to push ldap config data to libOvd for service instance "idsto
re.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "def
ault", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
Truncated. see log file for complete stacktraceCaused By: oracle.security.jps.JpsException: JPS-02592: Failed to push ldap conf
ig data to libOvd for service instance "idstore.ldap" in JPS context "default",cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Erro
r) Start of root element expected.
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2855)
at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3099)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:164)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap"
in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column1>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:341)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.igf.IGFException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context
"default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd(OvdIGFServiceProvider.java:321)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd(OvdIGFServiceProvider.java:370)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:339)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
Truncated. see log file for complete stacktrace
Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
at oracle.ods.virtualization.engine.config.parsers.ConfigErrorHandler.fatalError(ConfigErrorHandler.java:101)
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:432)
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:356)
Truncated. see log file for complete stacktrace
Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
Truncated. see log file for complete stacktrace
>
<Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Apr 10, 2012 3:07:23 PM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
help me please
Thanks.
Edited by: 842284 on 10 avr. 2012 07:41

Hi,
Please navigate to the fmwconfig folder and check the adapters.os_xml file.
$DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
There are chances the adapters.os_xml file could be corrupted due to which the Weblogic server fails to start.
Please verify if the adapters.os_xml file is valid.
In case the file is corrupted, please perform the following steps :
1) Take a backup of $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
2) Delete $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
3) copy adapters.os_xml from $MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/templates/ to $DOMAIN_HOME/config/fmwconfig/ovd/default/
4) Restart the server.
Regards,
Kal

Problem in starting managed server

hi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
and

hi all,
i have configure a admin server and 3 managed server. after i startup the
admin server and node manager , i start managed server in admin console, but
got a list of errors as follows:
####<May 3, 2003 4:04:49 PM HKT> <Info> <J2EE> <eg103> <myserver3> <main>
<kernel identity> <> <160037> <J2EE service initializing>
####<May 3, 2003 4:04:49 PM HKT> <Emergency> <WebLogicServer> <eg103>
<myserver3> <main> <kernel identity> <> <000342> <Unable to initialize the
server: Fatal initialization exception
Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
Cannot intialize Resource Manager Connection Factory resources because could
not get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
intialize Resource Manager Connection Factory resources because could not
get JNDI context: javax.naming.ConfigurationException [Root exception is
java.net.MalformedURLException: no protocol: localhost:1099] ]
at
weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
at
weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
i have checked that rmiregistry is up and 1099 port is listening. Does
anyone know why ?
thank you very much
regrds
and

Problem in starting SAP server.

Similar Messages

Maybe you are looking for