System/webconsole:console failed fatally

Getting a failed service every time I boot that I can't seem to fix. Here is the error message:
Jun 3 12:24:14 rhea svc.startd[7]: system/webconsole:console failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
I've tried looking at a few things, but I'm not sure what to try next. Any advice would be greatly appreciated. Here are the pertinent log files and svcs information:
bash-3.00# svcs -xv
svc:/application/print/server:default (LP print server)
State: disabled since Tue Jun 03 12:23:13 2008
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default
svc:/system/webconsole:console (java web console)
State: maintenance since Tue Jun 03 12:24:14 2008
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 1M smcwebserver
See: /var/svc/log/system-webconsole:console.log
Impact: This service is not running.
bash-3.00# vi /var/svc/log/system-webconsole:console.log
[ May 30 17:01:09 Disabled. ]
[ May 30 17:01:09 Rereading configuration. ]
[ May 30 17:01:56 Enabled. ]
[ May 30 17:03:11 Executing start method ("/lib/svc/method/svc-webconsole start") ]
Starting Sun Java(TM) Web Console Version 3.0.2 ...
The console is running.
[ Jun 3 07:56:57 Executing start method ("/lib/svc/method/svc-webconsole start") ]
Starting Sun Java(TM) Web Console Version 3.0.2 ...
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX
ParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:899)
"system-webconsole:console.log" 260 lines, 24468 characters (56 null)

what about:
mkdir -p /usr/java/bin
cd /usr/java/bin
ln -s `which java`.
.7/M.

Similar Messages

System/webconsole:console fail fatally

Hi everyone,
please could you help me resolve this challenging issue encountered on SunOS Release 5.10 Version Generic_125100-09 64-bi at the client site,
the error is stated below
svc.startd[7]: system/webconsole:console fail
ed fatally: transitioned to maintenance (see 'svcs -xv' for details)

FYI.
# svcs -l svc:/system/webconsole:console
fmri svc:/system/webconsole:console
name java web console
enabled true
state maintenance
next_state none
state_time Thu Jul 24 08:14:17 2008
logfile /var/svc/log/system-webconsole:console.log
restarter svc:/system/svc/restarter:default
contract_id
dependency require_all/none svc:/milestone/multi-user (online)
# tail /var/svc/log/system-webconsole:console.log
Shutting down Sun Java(TM) Web Console Version 3.0.2 ...
[ Jul 24 07:50:21 Enabled. ]
[ Jul 24 08:06:33 Executing start method ("/lib/svc/method/svc-webconsole start") ]
Starting Sun Java(TM) Web Console Version 3.0.3 ...
[ Jul 24 08:11:34 Method or service exit timed out. Killing contract 233 ]
[ Jul 24 08:11:34 Method "start" failed due to signal KILL ]
[ Jul 24 08:11:34 Executing start method ("/lib/svc/method/svc-webconsole start") ]
Starting Sun Java(TM) Web Console Version 3.0.3 ...
The console failed to start.
[ Jul 24 08:14:13 Method "start" exited with status 95 ]
# /usr/sbin/smcwebserver status
Sun Java(TM) Web Console is running
# /usr/sbin/smcwebserver stop
Shutting down Sun Java(TM) Web Console Version 3.0.3 ...
The console is stopped
# ps -efZ | grep java
PUBLIC root 800 26592 1 09:07:19 console 0:00 grep java
PUBLICnoaccess 14403 1737 0 08:36:28 ? 2:02 /usr/java/bin/java -server -Xmx128m -XX:+BackgroundCompilation -XX:PermSize=32m
# kill -15 14403
# ps -efZ | grep java
PUBLIC root 806 26592 1 09:08:17 console 0:00 grep java
# /usr/sbin/smcwebserver status
Sun Java(TM) Web Console is stopped
# /usr/sbin/smcwebserver start
Starting Sun Java(TM) Web Console Version 3.0.3 ...
The console is running
# /usr/sbin/smcwebserver status
Sun Java(TM) Web Console is running
# ps -efZ | grep java
PUBLIC root 1176 26592 1 09:12:22 console 0:00 grep java
PUBLICnoaccess 983 1737 6 09:10:47 ? 1:00 /usr/java/bin/java -server -Xmx128m -XX:+BackgroundCompilation -XX:PermSize=32m
# svcs -l svc:/system/webconsole:console
fmri svc:/system/webconsole:console
name java web console
enabled true
state online
next_state none
state_time Thu Jul 24 09:11:38 2008
logfile /var/svc/log/system-webconsole:console.log
restarter svc:/system/svc/restarter:default
contract_id 242
dependency require_all/none svc:/milestone/multi-user (online)
#

System/webconsole:console failed fatally: transitioned to maintenance

Please suggest how can i enable svc:/system/webconsole:console in
bos56164:/> svcs -xv
svc:/application/print/server:default (LP print server)
State: disabled since Sun Dec 12 23:08:07 2010
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default
svc:/system/webconsole:console (java web console)
State: maintenance since Fri Dec 24 01:39:53 2010
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 1M smcwebserver
See: /var/svc/log/system-webconsole:console.log
Impact: This service is not running.
svc:/application/cde-printinfo:default (CDE Print Viewer)
State: maintenance since Sun Dec 12 23:11:20 2010
Reason: Start method failed repeatedly, last exited with status 1.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/dt/share/man -s 1M dtprintinfo
See: /var/svc/log/application-cde-printinfo:default.log
Impact: This service is not running.
bos56164:/>tail -f /var/svc/log/system-webconsole:console.log
Java command "/usr/java/bin/java" does not exist.
Java command "/usr/java/bin/java" does not exist.
[ Dec 23 21:28:45 Method "start" exited with status 95 ]
[ Dec 23 21:40:22 Rereading configuration. ]
[ Dec 24 01:39:52 Leaving maintenance because clear requested. ]
[ Dec 24 01:39:52 Enabled. ]
[ Dec 24 01:39:52 Executing start method ("/lib/svc/method/svc-webconsole start") ]
Java command "/usr/java/bin/java" does not exist.
Java command "/usr/java/bin/java" does not exist.
[ Dec 24 01:39:53 Method "start" exited with status 95 ]
bos56164:/>ls -ltr /usr/java/bin/java
/usr/java/bin/java: No such file or directory
bos56164:/>java -version
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
bos56164:/>

what about:
mkdir -p /usr/java/bin
cd /usr/java/bin
ln -s `which java`.
.7/M.

Directory server - administration console, system server console fail

The server is solaris 10, with the java 1.4, and the Sun One directory server 5.2 was installed from a compressed file
System Administration Server
System Administration Console
Sun Java(TM) System Server Console
All were installed, but there's no connection to the Administration Console on port 390. Isw there any documentation available that will help to troubleshoot this? Any recommendations as to how to resolve the difficulty?

I usually get to the admin console by running /var/opt/mps/serverroot/startconsole.
Its an X application so you will need to have $DISPLAY set.

Password Check Failed, Fatal Error, System Halted, CNU949701P

Hello!
I have a HP netbook model Mini CQ 10, and I have not switched it on in a while.
I recently went to turn it on to recover some important documents and this error message shows up;
Password check failed
Fatal Error... System Halted
CNU949701P
Canu anyone PLEASE HELP ME! I would be so grateful!
Thank you!
x
This question was solved.
View Solution.

Try >> e9lovox132
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

Password check failed fatal error system halted CNU9384PJY

BOOTING ENTER CURRENT PASSWORD THREE TIMES GOES TO PASSWORD CHECK FAILED FATAL ERROR SYSTEM HALTEDCNU9384PJY AFTER NETBOOK SET UP FOR A WHILE THANKS FOR ANY HELP

Enter: e9lofuv2wi ( 3rd character is a llower case L ) Regards, DP-K

Strange Entries in System and Console Logs

I have some strange entries in my system and console logs. In the system log, I regularly see these entries:
Feb 24 21:07:29 joseph-youngs-computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: owner of process not logged in on console - exiting.
Feb 24 21:20:32 joseph-youngs-computer kernel[0]: (82: coreservicesd)tfp: failed on 0:
In my console log, I regularly find these entries:
2006-02-25 09:23:24 -0600
2006-02-24 21:07:30.530 loginwindow[803] FSResolveAliasWithMountFlags returned err = -43
On occasion, I find something like this in my console log:
Assert failed: /Users/dave/dev/flash/player/FlashPlayer/platform/mac/plugins/../../../core/spl ay.cpp:7105
I admit to being something of a novice with the Mac, so I am not sure what to make of these entries, though I never noticed anything like this on my eMac, or on my prior iMac. Also, on the entry above, there are no users named dave on my Mac.
Has anyone else noticed this, and can anyone shed any light on what these messages mean?

Resolved with a clean install.

System Preferences silently fails on relaunch

hi all..
I just installed a utility on 10.7.5 called Orbicule Witness. It adds a pane to System Preferences. On reboot following install of the utility I tried to access System Preferences and see the following in a Console App window:
13-04-01 12:09:19.602 AM System Preferences: dlopen_preflight failed with dlopen_preflight(/Library/PreferencePanes/Witness.prefPane/Contents/MacOS/Witne ss): no suitable image found. Did find:
/Library/PreferencePanes/Witness.prefPane/Contents/MacOS/Witness: GC capability mismatch for /Library/PreferencePanes/Witness.prefPane
and a dialog appears telling me "To use the Witness preferences pane, System Preferences must quit and reopen.". So i press "OK" and it sends the following message to the console:
13-04-01 12:10:35.219 AM launcher: posix_spawnattr_setbinpref_np failed
This is consistently reproducible. It seems that System Preferences is trying to relaunch in a fashion that is compatible with the Witness pane, but silently fails for some reason (btw "silently fails" is Concentrated Evil).
Is there some way to determine why it is failing and fix the problem?
thanks!

I have uninstalled it and, of course, the System Preferences loads. Did it twice to make sure. You can also take a shortcut to de-register the Witness pane and, again, System Preferences loads.
Also tried setting the System Preferences app to 32-bit using Get Info.. that does not work, but I don't see any visual indication that the System Preferences app is actually running in 32-bit mode. Is there some way of telling? If System Preferences cannot run in 32-bit mode then it's probably an OS issue. If it can, and the Witness pane still is not loading, then it seems likely to be app-specific.

I fail to start the sap server with error:Operating system call recv failed

I fail to start the sap server in SAP R3 Management Console and the message in the syslog was :
R/3 Basis System: Operating system call           recv failed (error no. 10053)
Is there any one could tell me how to resolve the problem or give me some advice?I will appreciate him/her very much.Thank you.

trc file: "dev_disp", trc level: 1, release: "620"
Sun May 07 13:14:30 2000
kernel runs with dp version 3(ext=1) (@(#) DPLIB-INT-VERSION-3)
length of sys_adm_ext is 304 bytes
systemid   560 (PC with Windows NT)
relno      6200
patchlevel 0
patchno    674
intno      20020600
pid        3628
***LOG Q00=> DpSapEnvInit, DPStart (00 3628) [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
Sun May 07 13:14:32 2000
WARNING => DpNetCheck: NiAddrToHostCanon() took 2 seconds
Sun May 07 13:14:37 2000
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3212]
MtxInit: -2 0 0
DpShMCreate: sizeof(wp_adm)          12784     (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: 001E0040, size: 1977824)
DpShMCreate: allocated sys_adm at 001E0040
DpShMCreate: allocated wp_adm at 001E0560
DpShMCreate: allocated tm_adm_list at 001E3750
DpShMCreate: allocated tm_adm at 001E3778
DpShMCreate: allocated wp_ca_adm at 00380438
DpShMCreate: allocated appc_ca_adm at 00384A88
DpShMCreate: allocated comm_adm_list at 003861F8
DpShMCreate: allocated comm_adm at 00386210
DpShMCreate: allocated ca_info at 003B5010
DpShMCreate: allocated wall_adm at 003B5018
MBUF state OFF
Sun May 07 13:14:38 2000
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 2458 MB
<ES> 2457 blocks reserved for free list.
ES initialized.
***LOG Q0K=> DpMsAttach, mscon ( db01) [dpxxdisp.c   9115]
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.
Sun May 07 13:15:18 2000
ERROR => W2 (pid 4776) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W2
Sun May 07 13:15:38 2000
ERROR => W5 (pid 4548) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W5
ERROR => W8 (pid 4592) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W8
ERROR => W9 (pid 4584) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W9
ERROR => W12 (pid 4676) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W12
ERROR => W13 (pid 4272) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W13
my types changed after wp death/restart 0xbf --> 0xb7
Sun May 07 13:15:58 2000
ERROR => W4 (pid 4888) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W4
ERROR => W6 (pid 4788) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W6
ERROR => W15 (pid 4596) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W15
Sun May 07 13:16:18 2000
ERROR => W1 (pid 4892) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W1
ERROR => W3 (pid 4904) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W3
ERROR => W7 (pid 4000) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W7
ERROR => W10 (pid 4864) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W10
my types changed after wp death/restart 0xb7 --> 0xb5
Sun May 07 13:16:38 2000
ERROR => W0 (pid 4900) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W0
ERROR => W11 (pid 4500) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W11
ERROR => W14 (pid 4636) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W14
ERROR => W16 (pid 3532) died [dpxxdisp.c   11523]
force unlock of wp_adm mutex W16
my types changed after wp death/restart 0xb5 --> 0x80
DP_FATAL_ERROR => DpEnvCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
DpModState: change server state from STARTING to SHUTDOWN
Sun May 07 13:16:42 2000
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   9341]
MBUF state OFF
MBUF component DOWN
***LOG Q05=> DpHalt, DPStop ( 3628) [dpxxdisp.c   7883]

Weblogic admin console fails to start when commons logging is used.

I have an application that requires commons logging.
I followed the instructions as per the documentation and other forum entries such as How to use log4j into weblogic 10.3 to add the commons logging jar from apache and the weblogic jar specified. Plus I set the system property for the LogFactory.
When I start up the application server I see messages as expected from my application. But when I start up the weblogic Admin console I get and exception and the console fails to start. I even tried to put the jars in my applicaiton instead of the domain/lib directory to try to iscolate the issue but still got issues with starting the Console.
Any ideas on why this is occuring?
See the error below:
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <----------------------------------------Retention Init()---------------------------------------->
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <Thu May 20 05:00:00 EDT 2010>
####<May 19, 2010 4:16:06 PM EDT> <Info> <Health> <TE001XU-CATOR1> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1274300166060> <BEA-310002> <81% of the total memory in the server is free>
####<May 19, 2010 4:35:03 PM EDT> <Info> <WorkManager> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301303146> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<May 19, 2010 4:35:17 PM EDT> <Error> <HTTP> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301317582> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: org.apache.commons.logging.LogConfigurationException: The chosen LogFactory implementation does not extend LogFactory. Please check your configuration. (Caused by java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl cannot be cast to org.apache.commons.logging.LogFactory)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:574)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:254)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.<clinit>(MBeanUtilsInitSingleFileServlet.java:23)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Thank you for replying. Yes that is the first place we looked and tried. Actually to be more specific we followed the instrcutions under: "How to Use the Commons API with WebLogic Logging Services" of the same link.
Are you thinking that maybe we are we missing a step somewhere else within the site?
Not sure if I was clear before but we are using Weblogic 10.3 and also tried up to version 10.3.3. And we get the same results.
We prefer to use the method with commons logging for our application.
One more specific here what we did on our last attempt.
1. added this to the startWeblogic script JAVAOPTIONS -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl
2. we put the WebLogic-specific Commons classes, $BEA_HOME/modules/com.bea.core.weblogic.commons.logging_1.3.0.0.jar, together with the commons-logging.jar file in one of the following locations: APP-INF/LIB or WEB-INF/LIB directory or DOMAIN_NAME/LIB directory server CLASSPATH
We are still not able to get the Weblogic admin console to start
Any other ideas?
Edited by: user13094648 on May 21, 2010 10:29 AM
Edited by: user13094648 on May 21, 2010 10:37 AM

System init function failed, Uunixerr = : msgget: No such file or directory

windows Server 2008 Enterprise
tuxedo11GR1PS1
when I run command "tmboot -y", I got the following error info at ULOG file:
105806.RNO05045.us.oracle.com!BBL.3536.5040.0: LIBTUX_CAT:681: ERROR: Failure to create message queue
105806.RNO05045.us.oracle.com!BBL.3536.5040.0: LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr = : msgget: No such file or directory
What's the problem? Anyone help!!!

I have similar error on Enterprise Linux 64 Bit.
Tuxedo Version 10.3.0.0, 64-bit
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: LIBTUX_CAT:681: ERROR: Failure to create message queue
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr = : msgget: No such file or directory
075418.localhost.localdomain!tmboot.4023.3569636960.-2: CMDTUX_CAT:825: ERROR: Process PSRENSRV at localhost.localdomain failed with /T tperrno (TPEOS - operating system error)
075418.localhost.localdomain!tmboot.4023.3569636960.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
075422.localhost.localdomain!BBL.4020.2558671968.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
075425.localhost.localdomain!PSADMIN.4014: End boot attempt on domain fdmo91
Can someone help me please?
Edited by: user6844468 on Nov 19, 2010 8:58 AM

"Program terminated in remote system NONE: Logon failed" when adding a new table

Hello,
I set up a replication flow from a SAP ERP 6.0 EHP7 with SAP ASE 16.0 source to SAP HANA 1.0 rev 82 target
I am using a standalone SLT system NetWeaver 7.0 with DMIS 2011_1_731 (with SP 1 to 7).
I have 100 tables to replicate.
I succeeded to set up replication for 57 tables. These tables are replicating properly.
Whenever I try to add a new one (with LTRC transaction, Data Provisioning -> Start Replication), the new table is marked as 'Failed' after a little while.
When I press 'Show Error Log' button I got an obscure error message:
"Program terminated in remote system NONE: Logon failed "
I do not understand this message. I checked both on SAP ASE source and SAP HANA target. I am still able to connect against both source and target.
Can you please tell how to troubleshoot this error.
Thanks in advance,
Christian

First thank you for answering my questions. I really appreciate your answers.
I rechecked the documentation.
"Application Operations Guide SAP Landscape Transformation Replication Server Document Version: 2.3 – 2014-07-08"
Page 29 - 30
3.5.2.2 Data Transfer Jobs
This section explains the relationship between the number of data transfer jobs and the number of available background work process.
Data transfer and data transformation processing on SLT server system is accomplished by the background work processes of the underlying SAP NetWeaver ABAP application server. Each job occupies 1 background work process in the SAP LT Replication Server system. For each configuration, the parameter Data Transfer Jobs restricts the maximum number of data load job for each mass transfer ID (MT_ID). In total, a mass transfer ID (MT_ID) requires at least 4 background jobs to be available:
 One monitoring job (master job)
 One master controller job
 At least one data load job
 One additional job either for the migration objects definition, access plan calculation or to change configuration settings in the Configuration & Monitoring Dashboard
Example
If you set the parameter Data Transfer Jobs to 04 in a configuration “SCHEMA1”, a mass transfer ID 001 is assigned. As a result, the following jobs should be in the system:
1 Master controller job: /1LT/IUC_REP_CNTR_001
 At most 4 parallel jobs for MT_ID 001: /1LT/IUC_LOAD_MT_001_001/~002/~003/~004
When configuring your data load or replication scenario, consider the following:
 Do not define more data transfer jobs than the number of available application server background work processes. If all available background work processes are already occupied by jobs, any other job will have to wait until a free work process becomes available. This can lead to long wait times until a new activity (for example creating triggers) can start, and can also result in significantly increased latency times for data replication.
 The number of dialog work processes in the source system corresponds 1:1 with the number of data transfer jobs in the SAP LT Replication Server system.
 Besides the work processes allocated by the data transfer jobs you need to provide additional available work processes for controller and monitoring jobs, the migration objects definition, access plan calculation or to perform configuration changes, and so on.
Sizing for SAP LT Replication Server involves determining how many work processes are required to perform the initial load of data into the target system within an acceptable timeframe, and accomplish the change capturing and the transfer of data changes to the target system within expected latency times.
Ensure that you add enough additional work processes to allow other required SAP LT Replication Server jobs to run.
Finally, you map the number of required application server work processes to their system resource consumption (CPU, memory, disc space) using the formulas provided by the SLT Sizing Guide.
With the simple formula below, you can calculate the number of required application server work processes (WPs) on the SLT Server for each active SLT configuration.
The number of required work processes can be determined by adding
 The Number of required data transfer jobs ,
 plus one background work process for Central Master (Monitoring) Job (only one per system!),
 plus one background work process for Master Controller Job,
 plus 3-5 additional empty background work processes (recommended per configuration),
 plus approx. 3 dialog work processes (recommended for each configuration).
Note: A lack of available free application server work processes can negatively affect the data load or data replication processes.
To summarize everything, the number of 'Data Transfer Jobs' must be set depending of the number of source tables, it is not the actual number of tables.
Assume that for my 100 tables I use 10 'Data Transfer Jobs' :
- The number of work processes on the SLT server would be 20. I took the simple formula of the documentation:
10 data transfer jobs ,
+ 1 background work process for Central Master (Monitoring) Job (only one per system!),
+ 1 background work process for Master Controller Job,
+ 5 additional empty background work processes (recommended per configuration),
+ 3 dialog work processes (recommended for each configuration).
- The number of dialog processes on the source server would be 10 ( equal to the number of 'Data Transfer Jobs')
Am I correct ?
Regards,
Christian

System Image Restore Fails "No disk that can be used for recovering the system disk can be found"

Greetings
                                    - Our critical server image backup Fails on one
server -
Two 2008 R2 servers. Both do a nightly "Windows Server Backup" of Bare Metal Recovery, System State, C:, System Reserved partition, to another storage hard drive on the same machine as the source. Active Directory is on the C: The much larger D: data
partition on each source hard drive is not included.
Test recovery by disconnecting 500G System drive, booting from 2008R2 Install DVD, recovering to a new 500G SATA hard drive.
Server A good.
Server B fails. It finds the backed-up image, & then we can select the date we want. As soon as the image restore is beginning and the timeline appears, it bombs with "The system image restore failed. No disk that can be used for recovering the system
disk can be found." There is a wordy Details message but none of it seems relevant (we are not using USB etc).
At some point after this, in one (or two?) of the scenarios below, (I forget exactly where) we also got :
"The system image restore failed. (0x80042403)"
The destination drive is Not "Excluded".
Used   diskpart clean   to remove volumes from destination drive. Recovery still errored.
Tried a second restore-to drive, same make/model Seagate ST3500418AS, fails.
Tried the earliest dated B image rather than the most recent, fail.
The Server B backups show as "Success" each night.
Copied image from B to the same storage drive on A where the A backup image is kept, and used the A hardware to attempt restore. Now only the latest backup date is available (as would occur normally if we had originally saved the backup to a network location).
Restore still fails.         It looks like its to do with the image rather than with the hardware.
Tried unticking "automatically check and update disk error info", still fail.
Server A SRP 100MB C: 50.6GB on Seagate ST3500418AS 465.76GB Microsoft driver 6.1.7600.16385   write cache off
Server B SRP 100MB C: 102GB on Seagate ST3500418AS 465.76GB Microsoft driver 6.1.7600.16385   write cache off
Restore-to hard drive is also Seagate ST3500418AS.
http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/e855ee43-186d-4200-a032-23d214d3d524      Some people report success after diskpart clean, but not us.
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/31595afd-396f-4084-b5fc-f80b6f40dbeb
"If your destination disk has a lower capacity than the source disk, you need to go into the disk manager and shrink each partition on the source disk before restoring." Doesnt apply here.
http://benchmarkreviews.com/index.php?option=com_content&task=view&id=439&Itemid=38&limit=1&limitstart=4
for 0x80042403 says "The solution is really quite simple: the destination drive is of a lower capacity than the image's source drive." I cant see that here.
Thank you so much.

Hello,
1. While recovering the OS to the new Hard disk, please don't keep the original boot disk attached to the System. There is a Disk signature for each hard disk. The signature will collide if the original boot disk signature is assigned to the new disk.
You may attach the older disk after recovering the OS. If you want to recover data to the older disk then they should be attached as they were during backup.
2. Make sure that the new boot disk is attached as the First Boot disk in hardware (IDE/SATA port 0/master) and is the first disk in boot order priority.
3. In Windows Recovery Env (WinRE) check the Boot disk using: Cmd prompt -> Diskpart.exe -> Select Disk = System. This will show the disk where OS restore will be attempted. If the disk is different than the intended 2 TB disk then swap the disks in
correct order in the hardware.
4. Please make sure that the OS is always recovered to the System disk. (Due to an issue: BMR might recover the OS to some other disk if System disk is small in size. Here the OS won't boot. If you belive this is the case, then you should attach the
bigger sized disk as System disk and/or exclude other disks from recovery). Disk exclusion is provided in System Image Restore/Complete PC Restore UI/cmdline.
5. Make sure that Number and Size of disks during restore match the backup config. Apart from boot volumes, some other volumes are also considered critical if there are services/roles installed on them. These disks will be marked critical for recovery and
should be present with minimum size requirement.
6. Some other requirements are discussed in following newsgroup threads:
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/871a0216-fbaf-4a0c-83aa-1e02ae90dbe4
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/9a082b90-bd7c-46f8-9eb3-9581f9d5efdd
http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/11d8c552-a841-49ac-ab2e-445e6f95e704
Regards,
Vikas Ranjan [MSFT]
------- This information is provided as-is without any warranties, implicit or explicit.-------

HP Photosmart C7280 All-in-one problem printing. Ink System Failure has failed unable to copy--

I'm having a problem printing on my HP Photosmart C7280 All-In-One. The following message is what came up on the printer screen: Ink System Failure has failed unable to copy, receive faxes or print. Refer to printer documentation Error O.cl9a0007.
Does anyone have any suggestions?
This question was solved.
View Solution.

Hey Spider! First off welcome to the forum.
I would recommend removing all the ink cartridges, unplugging the USB cable from the computer that connects to the printer, and then shutting the printer off completely by removing the power cord. Then restart your computer. Turn the printer back on but leave it disconnected from the computer. After it has finished its power on cycle go ahead and insert the ink cartridges back into the printer and be sure to seat them properly.
After you have all the cartridges back in the printer properly then connect it to the computer. See if this resolves the issue. If not post back with any findings.
Thanks,
SeanS
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

SSRS report throwing error :- system.web.aspnethostingpermission failed

Hi,
I am facing an issue with SSRS report after implementing HTTPHandler in its web.config file of Report manager.
My reports were working fine. I deployed a dll in report manager BIN folder and added below tag in the web.config
<add verb="*" path="*.aspx" type="ISHandler.SyncHandler, ISHandler" />
ISHandler is the assembly/namespace and SyncHandler is the class name.
I am getting error when I try to access the report
error :- system.web.aspnethostingpermission failed.
Currently web.config contains below settings.
<securityPolicy>
<trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config" />
</securityPolicy>
<trust level="RosettaMgr" originUrl="" />
Can you please help where the security permission is missing ?
sanmay

I am unable to see that. Please check.
sanmay

System/webconsole:console failed fatally

Similar Messages

Maybe you are looking for