Console fails on solaris 8

Hello,
I installed DS50 on a solaris 8 machine. When I start the console I get the following messages:
Font specified in font.properties not found [-b&h-lucida sans-medium-r-normal-sans-*-%d-*-*-p-*-iso8859-1]
Font specified in font.properties not found [-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific]
Font specified in font.properties not found [-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific]
Exception in thread "main" java.lang.NullPointerException: NullPointerException
     at sun.awt.motif.MFramePeer.pSetIconImage(Native Method)
     at sun.awt.motif.MFramePeer.setIconImage(MFramePeer.java:217)
     at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:175)
     at sun.awt.motif.MToolkit.createFrame(MToolkit.java:144)
     at java.awt.Frame.addNotify(Frame.java:274)
     at java.awt.Window.pack(Window.java:259)
     at com.netscape.management.client.console.SplashScreen.<init>(Unknown Source)
     at com.netscape.management.client.console.Console.<init>(Compiled Code)
     at com.netscape.management.client.console.Console.main(Compiled Code)
I removed these font-entries from the font.properties file to no avail, I still get the NullPointerException
Any ideas what's going on?
thanks
Bob

You are probably missing patches. Please run bin/slapd/server/idsktune to see which patches you are missing.
Bob Lannoy wrote:
Hello,
I installed DS50 on a solaris 8 machine. When I start the console I get the following messages:
Font specified in font.properties not found [-b&h-lucida sans-medium-r-normal-sans-*-%d-*-*-p-*-iso8859-1]
Font specified in font.properties not found [-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific]
Font specified in font.properties not found [-urw-itc zapfdingbats-medium-r-normal--*-%d-*-*-p-*-sun-fontspecific]
Exception in thread "main" java.lang.NullPointerException: NullPointerException
at sun.awt.motif.MFramePeer.pSetIconImage(Native Method)
at sun.awt.motif.MFramePeer.setIconImage(MFramePeer.java:217)
at sun.awt.motif.MFramePeer.<init>(MFramePeer.java:175)
at sun.awt.motif.MToolkit.createFrame(MToolkit.java:144)
at java.awt.Frame.addNotify(Frame.java:274)
at java.awt.Window.pack(Window.java:259)
at com.netscape.management.client.console.SplashScreen.<init>(Unknown Source)
at com.netscape.management.client.console.Console.<init>(Compiled Code)
at com.netscape.management.client.console.Console.main(Compiled Code)
I removed these font-entries from the font.properties file to no avail, I still get the NullPointerException
Any ideas what's going on?
thanks
Bob

Similar Messages

Font command fails on solaris

I have a program which runs fine under Windows but fails in Solaris when it gets to the line
font=new Font(null,FONT.plain,current_font_size);
(I have tried SansSerif and Lucida in place of null.
It is being run from a shell script as a batch process on the server. I have to access fonts to work out size of text objects - I presume my problem is to do with X11 - any advice.

Hi,
Can you provide the error you get?
I guess you do need an X Window System ( http://www.xfree86.org ).
If you already have one, try setting the environment variable DISPLAY as follows:
- log on as root
- for sh ksh:
set DISPLAY=localhost:1.0
export DISPLAY
- or for csh:
setenv DISPLAY=localhost:1.0
If this doesn't work, try replacing 1.0 with 0.0
Regards,
Kurt.

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.

Ddi_regs_map_setup fails in solaris 11

Hi
I have a driver (parent=isa) in x86 that ioremaps (ddi_regs_map_setup) a physical address range between 0xE0000 and 0xF0000.
This is a device memory mapped region.
The ddi_regs_map_setup was successful in solaris 10 (32 bit and 64 bit) but fails in solaris 11.
The warning message
WARNING: isa_apply_range: Out of range base <base> size <size>
The ddi_regs_map_setup goes through for the same region if driver made as parent=pci instead of parent=isa.
Would be helpful if someone could point out why this happens in solaris 11?
cheers

each of the registers covers an area of pci bus address space supplied by the card
why don't you print out the return value from ddi_dev_regsize() as that will tell you
how much space the card is exporting for each of the registers .
tim

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/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)
#

Exchange 2010 SP1 management console fail

Exchange 2010 SP1 management console fail on local exchange servers.
The following error occurred while attempting to connect to the specified Exchange server CAS123.domain.co.za
The attempt to connect to
http://cas123.domain.co.za/PowerShell using “kerberos” authentication failed: Connecting to remote server failed with following error message: The WS-Management service cannot process the request because IP address cas123.domain.co.za is invalid. For more
information, see the about_Remote_Troubleshooting Help topic.
However do note that the Exchange Management Shell also fails with the exact same error on both my CAS and Mailbox servers.
Though I am still able to open both tools via my backup server.
All ells works fine.
nslookup resolves the exchange servers as they should be. Frankly I am stumped as to the invalid IP address.
My exchange environment have been running problem free for years and this problem only occurred last week Thursday after some .NET updates.

Hi,
As per the information and details provided by you, the only thing that I can figure out is that: -
You receive an error: Exchange 2010 SP1 management console fail.
There are two methods to resolve this problem: -
Method 1: -
Close all MMC/EMC instances before proceeding.
Open the Registry editor (regedit) as the user you run the EMC under.
Go to
HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14\AdminTools
Look for value, Node structure setting.
If it is there, back it up and then remove it.
Method 2: -
Close all MMC/EMC instance before proceeding.
Open powershell or powershell IDE as the user you run the EMC under and execute the following command:
Remove-Item Property- Path
HKCU:\Software\Microsoft\ExchangeServer\v14\AdminTools\ -Name NodeStructureSettings
Close Powershell
I hope this information will be helpful for you. Correct me if the information that I am having is wrong.
Thanks and regards
Ashish@V

Appserver admin console fails

OK, if this is not the right place to post this just point me in the right direction. I'm trying here because this fails on Solaris 10 b69 using the embedded SJSAS, but works fine on a SJSAS PE8 install everywhere else.
Scenario:
- Created a new application server domain using the asadmin command...used defaults for all but listen port and admin passwd
- Started the new domain
- Deployments into the domain from the command line work fine, as do deployements into the ./autodeploy directory
When I try to access the web admin app, the login works fine but the main page fails with the following exception:
java.lang.RuntimeException: java.lang.IllegalArgumentException: http://margam:9999/asadmin%2Fcom_sun_web_ui/dtd/pagetitle.dtd
I've been all over this thing, removed and recreated domains, but I still get the error. I assume it has something to do with the fact that there is a URL-encoded '%2F' in the URL. I don't know where this is coming from. I've tested with both IE and Firefox.
Any help is appreciated.
-chris

Here is how I solved the problem:
1.
# cd /usr/appserver/lib/install/applications/admingui/adminGUI_war/com_sun_web_ui
2.
# cp -r /usr/share/webconsole/com_sun_web_ui/dtd .
3.
Restart the appserver
There seems to be a problem with the com_sun_web_ui directory, which I think comes from the shared webconsole directory. Either the dtd files were not copied to the right place, or the adminGUI web application resolved the pagetitle.dtd to the wrong place http://host:4848/amadmin/com_sun_web_ui/dtd/pagetitle.dtd. I think it should probably be http://host:4848/com_sun_web_ui/dtd/pagetitle.dtd.
I tried to use symlinks, unfortunately, no luck there.
You can also copy other directories to make the admin gui look better.
Cheers,
Xuekun

Oracle AS - DB Console fails to start after AS install

Hi,
I got an error message at the time of Oracle AS Infra install that setup failed to start the DB Console during DB Configuration assistant run. Also, Oracle AS - DB Console fails to start after the AS install? Any suggestion / remedies would be of help.

hi,
follow this metalink note you will find out the answer
Troubleshooting Database Control Startup Issues
Doc ID: Note:549079.1
Thanks,

IDM Demo always reports connection failed for Solaris target

I'm setting up the IDM Demo, using the Setup Wizard, using a Solaris 10 container as
the target system. For this demo, I'm using telnet directly as root, which seems to be
the only method available. This succeeds when I run telnet by hand from the IDM host
to the target host. When I test the connection from the wizard, after a long delay, it
always reports that the test connection failed. However, the console log on the target
system shows a successful login. The Details button says that it was looking for `_.)#+(:',
regardless of what I specify as the `Login Prompt'. (I assume this really means the shell
prompt.) I've tried changing the shell prompt by setting PS1 in /.profile and tried suppressing
the banner by creating a /.hushlogin file. Still, the test button always reports that the
connection failed. What's wrong here?

ah, familiar territory :)
the string _.)#+(: is something that the adapter uses as a suffix to check whether the previous command executed has changed state or not. The assumption being that _.)#+(: will not be encountered as output of any command on Solaris.
1. Try connecting as root
2. Whats your IDM version?
3. Try this: login as root over putty, and paste whatever strings you get into the adapter configuration page on IM (for say, prompt, etc.)
4. Tracing the following variables can give you better details regarding where its getting stuck:
com.waveset.adapter.SolarisResourceAdapter
com.waveset.adapter.SVIDResourceAdapter
com.waveset.adapter.ScriptedConnection
Hope this helps!
Ankush

Ypinit fails in Solaris 10

I am trying to set up a NIS client Solaris 10 for the first time. Ypinit fails with the errors:
svcadm: Pattern 'network/nis/server:default' doesn't match any instances
svcadm: Pattern 'network/nis/xfr:default' doesn't match any instances
svcadm: Pattern 'network/nis/passwd:default' doesn't match any instances
svcadm: Pattern 'network/nis/update:default' doesn't match any instances
svcs -a doesn;t list any of those services. How do I create them? I have the SUNWnisr and SUNnisu packes on the host.

Turns out the NIS server packages are required for the client to work. Installing SUNypu and SUNWypr tool care of the svcadm errors.
Then, the network/nis.client service got disabled every time I ran ypinit -c.
Turns out the user had a "securenets" file on the master that was not allowing access. After fiddling with svcadm for a while, everything seems to be working.

Installation fails on Solaris 10

After downloading and executing the SGD shell script results in a failure.
Same script
worked fine on Solaris 9. Solaris 10 system details:
root[csh]@broncos15[32]# cat /etc/release
Solaris 10 3/05 s10_74L2a SPARC
Assembled 22 January 2005
root[csh]@broncos15[26]#sh ttaspso.shx
Tarantella Secure Global Desktop Enterprise Edition
Setup is verifying the shx file...
Setup is checking for disk space requirements...
Secure Global Desktop for SPARC Solaris 2.8+
Preparing for installation...
/tmp/install6aaaHh/checkinstall8aaaHh: /tmp/ttainst_1/tta.log: cannot
create
Error during installation. Setup will now exit.
Please correct any errors described in /tmp/tta_inst.log, and then try
again.
root[csh]@broncos15[27]#
root[csh]@broncos15[29]# cat tta_inst.log
===========================================================================
Starting Setup
===========================================================================
11+0 records in
11+0 records out
===========================================================================
Installing package <tta>
===========================================================================
3+0 records in
3+0 records out
Pre-request detail for package <tta>
---> tta.prerequest
24997+0 records in
24997+0 records out
Extraction detail for package <tta>
Transferring <tta> package instance
Install detail for package <tta>
Processing package instance <tta> from </tmp/ttainst_1/ttapkg.3491/pkg>
Tarantella Secure Global Desktop Enterprise Edition for SPARC Solaris
2.8+(SPARC) 4.00.903
Tarantella, Inc.
pkgadd: ERROR: request script did not complete successfully
Installation of <tta> failed.
No changes were made to the system.
Script detail for package <tta>
root[csh]@broncos15[30]#

Have a look at
http://www.tarantella.com/documentation/sgd/ee/4.0/install.html - search
for "Solaris 10" on that page, and try the workaround described there.
Regards,
Bill Weir, Tarantella Engineer.
Ranjit Reddy wrote on 02/06/2005 00:41:
After downloading and executing the SGD shell script results in a failure.
Same script
worked fine on Solaris 9. Solaris 10 system details:
root[csh]@broncos15[32]# cat /etc/release
Solaris 10 3/05 s10_74L2a SPARC
Assembled 22 January 2005
root[csh]@broncos15[26]#sh ttaspso.shx
Tarantella Secure Global Desktop Enterprise Edition
Setup is verifying the shx file...
Setup is checking for disk space requirements...
Secure Global Desktop for SPARC Solaris 2.8+
Preparing for installation...
/tmp/install6aaaHh/checkinstall8aaaHh: /tmp/ttainst_1/tta.log: cannot
create
Error during installation. Setup will now exit.

Adding Company Knowledge with OpsMgr 2012 Console - "Failed to launch Microsoft Word"

Hi everyone!
I'm trying to add company knowledge using the OpsMgr 2012 console (32-bit) on Windows 7 Ultimate (32-bit) using the guidelines provided at the following link...
http://technet.microsoft.com/en-us/library/hh212900.aspx
I'm using Office 2010 Pro Plus SP1 (32-bit) with the .NET Programmability feature and the Microsoft Visual Studio 2005 Tools for Office Second Edition Runtime installed, but I get the dreaded "failed to launch Microsoft Word" error...
...any help or guidance would be greatly apprecaited!
Regards,
JJ

Thanks Andres!
I have confirmed that the following instructions does allow you to use Word 2010 32-bit running on Windows 7 64-bit or Windows Server 2008 R2 to edit company
knowledge...
1. Go to the directory where the OpsMgr console is installed (example: C:\Program Files\System Center\Operations Manager 2012\Console )
2. Make a copy of Microsoft.EnterpriseManagement.Monitoring.Console.exe.config
3. Edit Microsoft.EnterpriseManagement.Monitoring.Console.exe.config using Administrator rights
4. Search for “</dependentAssembly>” and remove the “<publisherPolicy apply="no" />” line immediately following the “</dependentAssembly>” line
Hope this helps!
Regards,
JJ
Well, firstly I have to agree with other people's comments along the lines of "It shouldn't be this hard!", but I can happily say that the solution above (by IM5FOOTNOTHIN)
worked for me...once I noticed this crucial footnote: "Do this for
ALL instances of the
<publisherPolicy apply="no" /> line that immediately follow the </dependentAssembly> line"

9.2.0.3 patch set installation fails on Solaris 8

i've installed Oracle9iR2 (64-bit) client on a Solaris 8 system and i'm now having problems installing the 9.2.0.3 patch set. during the installation process i get the following error message from OUI:
Error in invoking target install of makefile
$ORACLE_HOME/network/lib/ins_net_client.mk
i checked the installation log and then $ORACLE_HOME/install/make.log. make.log reports that the failing command is:
/usr/ccs/bin/make -f ins_net_client.mk install ORACLE_HOME=/opt/oracle9i/u01/app/oracle/product/9.2.0
this command fails when trying to link trcroute. the link command seems to have incorrect paths as it seems to expect to find crt?.o files from $ORACLE_HOME/lib/WS6U1 while they are located in $ORACLE_HOME/lib/WS6U2/lib/v9. i modified $ORACLE_HOME/network/lib/env_network.mk (CCVER, COMPOBJ) so that crt?.o can be found.
after this change the same link command fails with this message:
ld: fatal: file $ORACLE_HOME/network/lib/s0nur.o:
wrong ELF class: ELFCLASS32
ld: fatal: File processing errors. No output written to trcroute
*** Error code 1
make: Fatal error: Command failed for target `trcroute'
i checked the object files in network/lib and they all seem to be ELF 32-bit.
does someone know what's causing these problems with the installation and how to fix it?
best regards,
aspa

that's what i started to suspect as well. it's quite likely that the patch is for 32-bit installations. i'll try it with the 64-bit patch. thanks.

SSL/TLS clients binds fail to Solaris 10 06/06 DS5.2p4 Server

hello all,
this is a bizarre issue that i think is related to the solaris version that is running on the directory server, at least this appears to the the issue. i have 2 SunDS servers running solaris 10 06/06 and the other solaris 10 01/06 with DS5.2p4. both have SSL enabled, the certs i signed with my own CA which i maintain with tinyca2. the directory starts fine and is listening on both 389(ldap) and 636(ldaps). i am able to successfully bind to both servers on the non-secure ports fine, commands like getent, finger, id are pulling the people from the directory. when i enable the clients to use ssl/tls those same commands fail against the solaris 10 06/06 machine but NOT the solaris 10 01/06 server. on the linux machines i'm getting "nscd: pam_ldap: could not search LDAP server" errors and on the solaris machines "Mesg: openConnection: failed to initialize TLS security" and "libsldap: Status: 7 Mesg: Session error no available conn."
using "ldapsearch -x -ZZ" from the clients is successful to both systems, and i can use "openssl s_client" to view the certs fine. another bizzare occurance is when i do "getent passwd" i see the local and ldap users but "getent passwd ldap_user" will return nothing. again this are against the solaris 10 06/06 machine.
has anyone see this before? i'm going to open a service request for sun on this but i wanted to see if anyone else has run into this.

there was a problem with the certificate db which was causing this.

Console fails on solaris 8

Similar Messages

Maybe you are looking for