Solaris 10 for x88 install issue: cannot start X11 server

AFter fixing my "can't set locale" problem I am moving onto the "Server for display :0 can't be started" issue.
Checking /etc/dtc/Xerrors yields:
1) error (PID 380) : Server unexpectedly died
2) error (PID 380) : Server for display :0 can't be started
I've tried running kdmconfig and setting XSun not XOrg. I am using a 2 channel KVM with a 3 button mouse (the only PS2 mouse I have lying around...) but it seems to pick it up without any problems. But, editing the config and saving (F4...) doesn't work. The changes don't commit and running kdmconfig again I see the choices have not changed.
Also, I notice this message when I try to boot up:
svccfg (/tmp/kdm_svccfg_cmds, ;ine 1): Pattern 'application/x11/x11-server' doesn't match any instances or services.
Feel free to reply direct to me g.h.lawrence<at>gmail.com if you wish. Thanks in advance for any and all replies.
Greg

Hello Greg,
unfortunately you're posting in the wrong forum.
These forums are for Sun Hardware, you have a configuration problem with a piece of software - the x-server. Please post in one of these forums
Solaris on x86
http://forum.sun.com/jive/forum.jspa?forumID=291
Installation
http://forum.sun.com/jive/forum.jspa?forumID=292
General Solaris 10 Discussion
http://forum.sun.com/jive/forum.jspa?forumID=298
Michael

Similar Messages

A lot of problem for an error: Cannot start Managed Server through NM

Hi, all. Thank for coming here.
My main problem is cannot start Manager server through Node Manager. I've configured with the same way on my friend's network and It's works but It's wrong with mine.
my weblogic domain:
Machine 1: Administration Server + 1 Managed server
Machine 2: 1 Managed server
all of these servers communicate through SSL protocol. When I try to start Managed Server on remote machine:
output from console which was invoked startWebLogic.sh
+<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
+<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
And this is MS01 log:
starting weblogic with Java version:
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
+JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
The application has requested the JVM to exit with an fatal error from JNI. Error message:
JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Starting WLS with line:
+/opt/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=MS01 -Djava.security.policy=/opt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xrs -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/opt/Oracle/Middleware/wlserver_10.3 -Dwls.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.35:7001 -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/opt/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/patch_wlp1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/wlportal_10.3/p13n/lib/system:/opt/Oracle/Middleware/wlportal_10.3/light-portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/lib/system:/opt/Oracle/Middleware/wlportal_10.3/analytics/lib/system:/opt/Oracle/Middleware/wlportal_10.3/apps/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/Oracle/Middleware/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/Oracle/Middleware/wlportal_10.3/portal/lib/security weblogic.Server+
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
+JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
The application has requested the JVM to exit with an fatal error from JNI. Error message:
JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Stopping PointBase server...
PointBase server stopped.
And this is output from console which node manager runs on:
+<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
+<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
I tried to start Managed server some times again, but I face up to strange issue, this is output from console which Admin Server runs on (these exception messages throws continuously):
+<Sep 9, 2010 12:42:53 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "p13nDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceAlwaysXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
I can ensure that all of these connection pool has configured to run on 9093 port already. Then I view the DOMAIN_NAME/pointbase.log, it said:
Unable to start the server. start server error: java.net.BindException: Address already in use
I cannot understand what's run on pointbase address ?
All of these error make me angry, because I've configured with the same way on other system and It's work. I've spent all of week to fix these bug, but I'm having nothing :((
Please help me.

Thank Jay SenSharma.
I've looked for these JAVA_OPTION values you said, but I cant found them. That value is content of JAVA_DEBUG option, not JAVA_OPTION. In my situation, JAVA_DEBUG=" " (it's not set by default).
Please re-view my error log:
Node Manager output:
+<Sep 9, 2010 11:32:44 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 11:32:44 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Managed server MS01's log:
+<Sep 9, 2010 11:45:05 PM> <INFO> <NodeManager> <Server output log file is '/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.out'>+
+<Sep 9, 2010 11:45:07 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>+
+<Sep 9, 2010 11:45:09 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010+
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
+<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://xmlns.oracle.com/weblogic/domain>+
+<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - /opt/Oracle/Middleware/user_projects/domains/devdomain/<unknown>:11:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>+
+<Sep 9, 2010 11:45:14 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320400> <The log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log00002. Log messages will continue to be logged in /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log.>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log is opened. All server side log events will be written to this file.>+
+<Sep 9, 2010 11:45:17 PM EDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details..+
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)+
+     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
+     Truncated. see log file for complete stacktrace+
Caused By: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)+
+     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
+     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
+     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
+     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
+     Truncated. see log file for complete stacktrace+
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)+
+     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
+     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
+     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
+     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
+     Truncated. see log file for complete stacktrace+
Caused By: java.lang.RuntimeException: There were errors initializing your configuration: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal store error> org.apache.openjpa.util.StoreException: com.pointbase.jdbc.jdbcUniversalDriver
+     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:123)+
+     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.createConnectionFactory(JDBCConfigurationImpl.java:776)+
+     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:683)+
+     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
+     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+     at java.lang.reflect.Method.invoke(Method.java:597)+
+     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:288)+
+     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
+     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
+     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
+     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
+     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
+     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+     at java.lang.reflect.Method.invoke(Method.java:597)+
+     at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)+
+     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)+
+     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
+     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
+     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
+     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
+     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)+
+     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
+     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
+     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
+     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
+     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)+
+     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)+
+     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
+     at weblogic.security.SecurityService.start(SecurityService.java:141)+
+     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
+     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
Caused by: java.lang.ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
+     at java.lang.Class.forName0(Native Method)+
+     at java.lang.Class.forName(Class.java:169)+
+     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:85)+
+     ... 38 more+
+     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:302)+
+     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
+     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
+     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
+     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
+     Truncated. see log file for complete stacktrace+
+>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>+
+<Sep 9, 2010 11:45:17 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:+
There are 1 nested errors:
+weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)+
+     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)+
+     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
+     at weblogic.security.SecurityService.start(SecurityService.java:141)+
+     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
+     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
+>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>+
+<Sep 9, 2010 11:45:17 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>+
+<Sep 9, 2010 11:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 16443>+
+<Sep 9, 2010 11:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>+
+<Sep 9, 2010 11:45:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>+
ps:
I've come your weblog and found alot of tips for debugging WebLogic Server exceptions. It's really helpful. Thanks.
Edited by: Doubt_Man on Sep 10, 2010 10:49 AM
Edited by: Doubt_Man on Sep 10, 2010 3:54 PM

Cannot start weblogic server anymore after conf. jena for oracle database

Hi,
My weblogic server 10.3.4.0 installed in oracle developer days in oralce linux guest was able to start before using the oracle user account. Following the seman. tech. dev. guide, I set up jena adapter for oracle in my guest linux system. Since the oracle user doesn't have permission to copy folders into the autodeploy directory in weblogic server, so I login as root to copy the joseki.war folder into the autodeploy directory. However, after that, I am not able to start the weblogic server console anymore using the oracle user account. Any suggestions will be much appreciated. Thanks a lot in advance.
Hong

Pl do not post duplicates - cannot start weblogic server anymore in oracle user after config. in root

Cannot start SQL Server Service (SQLEXPRESS).

Cannot start SQL Server (SQLEXPRESS). When i tried to start the SQL Server Services, the warning: This request failed or the service did not respond in a timely fashion. Consult the event log or other application error logs for details.
I opened the Event Viewer, Error is shown as : An error occurred in the Service Broker / Database Mirroring transport manager. Error: 9694, Stare 27.

Here is the ERRORLOG
2015-03-16 11:20:30.50 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2015-03-16 11:20:30.50 Server (c) Microsoft Corporation.
2015-03-16 11:20:30.50 Server All rights reserved.
2015-03-16 11:20:30.50 Server Server process ID is 6816.
2015-03-16 11:20:30.50 Server System Manufacturer: 'LENOVO', System Model: '20C5A01K00'.
2015-03-16 11:20:30.50 Server Authentication mode is MIXED.
2015-03-16 11:20:30.50 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-03-16 11:20:30.50 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2015-03-16 11:20:30.50 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-03-16 11:20:30.50 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-03-16 11:20:30.64 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-16 11:20:30.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-16 11:20:30.64 Server Detected 7906 MB of RAM. This is an informational message; no user action is required.
2015-03-16 11:20:30.64 Server Using conventional memory in the memory manager.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 27.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server Error: 9643, Severity: 16, State: 1.
2015-03-16 11:20:30.75 Server An error occurred in the Service Broker/Database Mirroring transport manager: Error: 9694, State: 27.
2015-03-16 11:20:30.75 Server Error: 9694, Severity: 16, State: 30.
2015-03-16 11:20:30.75 Server Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
2015-03-16 11:20:30.75 Server SQL Server Audit failed to record the SERVER SHUTDOWN action.

Solaris 10 for X86 Install issue: "Server for display :0 can't be started"

After fixing my "can't set locale" problem I am moving onto the "Server for display :0 can't be started" issue.
Checking /etc/dtc/Xerrors yields:
1) error (PID 380) : Server unexpectedly died
2) error (PID 380) : Server for display :0 can't be started
I\ve tried running kdconfig and setting XSun not XOrg. I am using a 2 channel KVM with a 3 button mouse (the only PS2 mouse I have lying around...) but the config seems to pick it up without any problems.
Feel free to reply direct to me g.h.lawrence<at>gmail.com if you wish. Thanks in advance for any and all replies.
Greg
Message was edited by:
MaristFlanker
Also, I notice this message when I try to boot up:
svccfg (/tmp/kdm_svccfg_cmds, ;ine 1): Pattern 'application/x11/x11-server' doesn't match any instances or services.
Any help/suggestions appreciated and thanks again!

Hello Greg,
unfortunately you're posting in the wrong forum.
These forums are for Sun Hardware, you have a configuration problem with a piece of software - the x-server. Please post in one of these forums
Solaris on x86
http://forum.sun.com/jive/forum.jspa?forumID=291
Installation
http://forum.sun.com/jive/forum.jspa?forumID=292
General Solaris 10 Discussion
http://forum.sun.com/jive/forum.jspa?forumID=298
Michael

Solaris 10 x86 (gold) will not install - Cannot start X-Server

(Originally posted in the wrong forum. Oops)
Okay,. this is really stupid. I don't understand this one at all.
I cannot install Solaris x86 (gold - as in "non-beta") at all. I have tried both the ATI Rage 128 Pro and NVidia GeForce chipsets. Both cards are correctly detected; however, regardless of what selection or driver option I choose, the installation crashes immediately thereafter.
If I let the installation go on its own, it stops completely at the "Detecting additional network parameters" or whatever that particular error message is.
If I manually select the standard (non XF86) drivers of the card, black-on-yellow text complains about how it cannot detect the card (that it correctly identified) and that it cannot start the X server. It then improperly displays the text menu for language selection and stops.
If I manually select the XF86 drivers, it gets all of the way through to where I test the video mode and then just dies. No error message or anything.
{rant mode on}
Jesus, Sun! What the hell is going on? These are two INDUSTRY STANDARD video cards! These aren't some run-of-the-mill, no-name chipsets we're talking about! It's exactly because of idiotic driver issues like this that people laugh when given the choice between Solaris and Linux while looking for Windows alternatives for the desktop!
{rant mode off}
Sorry for the rant, but I've been complaining for years that issues like this are exactly why Windows has been allowed to dominate the desktop. Now here comes Linux which supports just about everything, and Sun still apparently has no clue about supporting desktops. I know , I know-- servers are Sun's strengths, but if Sun is going to try to get JDS onto the desktop, this is not the way to go about it.
Now that I've gotten that off my chest (I really needed that), does anyone know what needs to be done to get this to install properly and of course function properly thereafter without having to jump througha ton of hoops?

That's just what really bothers me about this!
Last week, I installed from the very same CDs onto an old Celeron 633 w/ 128 MB and ATI Rage video chipset just for giggles. Everything went beautifully except for the network. (Once again, Sun shows its pathetic weakness on drivers thus giving Linux a major edge.) The only video error that I got was remedied by switching to the standard driver from the XF86 driver. It ran like a champ afterwards except that it got confused on the network card and therefore prevented network connectivity.
So, this time I tried to install it on a Pentium 4 1.8 GHz w/ 512 MB RAM, and it's puking on me with same video chipset family (ATI Rage) as well as NVidia chipsets! Absolutely ridiculous!

Cannot start managed server domains for SOA Suite 11g with Weblogic

Hi all,
I have installed Oracle 11gR1 (11.1.1.3) SOA Suite with Oracle 11gR1 (10.3.3) Weblogic on Oracle Enterprise Linux 5 (64 bit OS) platform and cannot get the managed server domains to start due to the following
authentication errors.
$ sh startManagedWebLogic.sh soa_server1 http://xxx.xxx.xx.xxx:7001
<Dec 14, 2010 11:12:44 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 14, 2010 11:12:44 AM EST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 14, 2010 11:12:44 AM EST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Dec 14, 2010 11:12:44 AM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log00005. Log messages will continue to be logged in /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log.>
<Dec 14, 2010 11:12:44 AM EST> <Notice> <Log Management> <BEA-170019> <The server log file /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log is opened. All server side log events will be written to this file.>
<Dec 14, 2010 11:12:46 AM EST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjp
<Dec 14, 2010 11:12:46 AM EST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:891341 fatal store error> kodo.jdo.FatalDataStoreException: error result.
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:891341 fatal store error> kodo.jdo.FatalDataStoreException: error result
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:465)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Dec 14, 2010 11:12:46 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 14, 2010 11:12:46 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 14, 2010 11:12:46 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Caused By: netscape.ldap.LDAPException: error result (49)
at weblogic.ldap.EmbeddedLDAPConnection.bind(EmbeddedLDAPConnection.java:639)
at weblogic.ldap.EmbeddedLDAPConnection.determineFailover(EmbeddedLDAPConnection.java:2204)
at weblogic.ldap.EmbeddedLDAPConnection.connect(EmbeddedLDAPConnection.java:366)
at com.bea.common.ldap.LDAPConfiguration.getConnection(LDAPConfiguration.java:78)
at com.bea.common.ldap.LDAPStoreQuery.executeQuery(LDAPStoreQuery.java:199)
Truncated. see log file for complete stacktrace
>
<Dec 14, 2010 11:12:46 AM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 14, 2010 11:12:46 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
When I remove boot.properties file from $MIDDLEWARE_HOME/user_projects/domains/dummy_domain/servers/AdminServer/security
I am able to start AdminServer, however, the ManagedServers do not start. When I try to use boot.properties file for AdminServer it will not start neither will Managed Servers.
If anyone has idea how to resolve the issue, please let me know. I have tried using the following commands to change the passwords for ManagedServers to no success:
cd /weblogic1033/oracle/user_projects/domains/dummy_domain/security
java -cp /weblogic1033/oracle/wlserver_10.3/server/lib/weblogic.jar:$CLASSPATH weblogic.security.utils.AdminAccount newuser newpassword .
It works but fails to change the password. I also tried changing settings for LDAP and security in the admin console to no success in resolving this issue.

Take a backup of ldap folder under servers/managedServerName/data folder and delete those and thn restart managed servers,

Kinect for Windows V2 Device cannot start

I was able to use my Kinect for Windows V2 sensor yesterday with all of the applications in the SDK browser but the next day after restarting my computer I was no longer able to use the device. Looking at the device manager I get this message under the properties
for WDF KinectSensor Interface 0 (the only device listed under Kinect sensor devices):
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I'm plugged into a USB 3.0 input. Any ideas?

I encounter the exact same issue:
WDF KinectSensor Interface 0
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I'm using an Intel 4ghz i7 processor plugged into an ASUS Sabertooth Mk1 Z97 Motherboard. The ASMedia on the board had some issues, so i'm using a USB 3.0 PCI/E card by Manhatten. Diagnostics indicates that everything but depth checks out. Depth fails because
the camera reports all black.
This is particularly frustrating since I built this computer to offer USB 3.0 support specifically so I could do work with Kinect and Unity. This was before I knew the issues Kinect has with ASMedia, so for me this has been a significant investment for a
black screen.
Edit: To clarify, the Kinect is plugged into the PCI/E card (Manhatten 150491) and not into the board or a case slot.
Additonal note: The Kinect does not function properly plugged into my old PC (a USB 2.0 with an i7) or into my Surface Pro (1st gen)
- Matt Eland

Issues with starting weblogic server for my domain

This is part of the adminserver log file:
####<Apr 29, 2009 3:47:18 PM EDT> <Critical> <WebLogicServer> <mycomputername> <AdminServer> <main> <<WLS Kernel>> <> <> <1241034438142> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
     at weblogic.descriptor.internal.AbstractDescriptorBean$SecurityService._invokeServiceMethod(AbstractDescriptorBean.java:1011)
     at weblogic.descriptor.internal.AbstractDescriptorBean$SecurityService.decrypt(AbstractDescriptorBean.java:1039)
     at weblogic.descriptor.internal.AbstractDescriptorBean$SecurityService.access$200(AbstractDescriptorBean.java:963)
     at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:960)
What could the issue be?

I finally got so frustrated that I uninstall and reinstalled it. I did not import any projects at this time, but created a simple, out-of-the-box domain. Then tried to start the server under that domain, and now I get:
Invalid table name "USERS" specified at position
Please find part of log output below (I don't see a place in this forum to attach a file). I've copied the portions out of the log that reference exceptions. I appreciate the help!
ava.sql.SQLException: Invalid table name "USERS" specified at position 23.
     at com.pointbase.net.netJDBCPrimitives.handleResponse(DashoA13*..:335)
     at com.pointbase.net.netJDBCPrimitives.handleJDBCObjectResponse(DashoA13*..:383)
     at com.pointbase.net.netJDBCConnection.prepareStatement(DashoA13*..:545)
     at weblogic.security.providers.authentication.DBMSSQLReadOnlyDatabaseConnectionImpl.getPreparedStatement(DBMSSQLReadOnlyDatabaseConnectionImpl.java:37)
     at weblogic.security.providers.authentication.shared.DBMSSQLRuntimeQueryImpl.passwordStringQuery(DBMSSQLRuntimeQueryImpl.java:78)
     at weblogic.security.providers.authentication.shared.DBMSSQLRuntimeQueryImpl.executeUserPassword(DBMSSQLRuntimeQueryImpl.java:71)
     at weblogic.security.providers.authentication.shared.DBMSAtnLoginModuleImpl.authenticateDBMS(DBMSAtnLoginModuleImpl.java:666)
     at weblogic.security.providers.authentication.shared.DBMSAtnLoginModuleImpl.login(DBMSAtnLoginModuleImpl.java:270)
     at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:91)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
     at $Proxy17.login(Unknown Source)
     at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
     at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:80)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
     at $Proxy19.authenticate(Unknown Source)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:366)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:911)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<May 1, 2009 7:50:55 AM EDT> <Critical> <Security> <lmv25-ite89695> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1241178655172> <BEA-090403> <Authentication for user weblogic denied>
####<May 1, 2009 7:50:55 AM EDT> <Critical> <WebLogicServer> <mycomputername> <AdminServer> <main> <<WLS Kernel>> <> <> <1241178655172> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:947)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Can't Install Leopard "Cannot Start up from this volume"

I have 10.4.10 currently installed on my MacBook (120GB aftermarket HD).
HD works fine and is properly partition/formatted and working just fine in 10.4 (GUID partition, journaled, etc). Ran repair permission/disk to be safe and it checked out ok.
10.5 installer loads up ok but when I get the list of drives to install to my HD has a red exclaimation on it and when I try and select it I get the message "You cannot install Mac OS X on this volume. Mac OS X cannot start up from this volume."
I have no problems running 10.4 on that volume and I don't want to reformat unless I am 100% sure it will fix the problem.

Since nobody replied after 26 views I assumed nobody wanted to help me.
So I ended up reformatting my HD to the same options it currently had and that fixed it. SO I am starting to do the install now.
Thanks to the 26 people who viewed it and didn't offer any help.

Cannot start SQL Server Agent (Version 2014 enterprise core)?

The SQL Server Agent log file has the following information. I already set the firewall for inbound 1433.
2014-11-04 11:59:43 - ? [100] Microsoft SQLServerAgent version 12.0.2000.8 (X64 unicode retail build) : Process ID 6108
2014-11-04 11:59:43 - ? [495] The SQL Server Agent startup service account is ......
2014-11-04 11:59:43 - ! [150] SQL Server does not accept the connection (error: 0). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2014-11-04 11:59:43 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [298] SQLServer Error: 27, Client unable to establish connection [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to
allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2014-11-04 11:59:43 - ! [382] Logon to server '(local)' failed (DisableAgentXPs)
2014-11-04 11:59:43 - ? [098] SQLServerAgent terminated (normally

Is this new SQL Server installation or originally it was working fine ?
Below message makes me think you might as well need to repair your installation
>SQLServer Error: 27, Registry information is corrupt or missing. Make sure the provider is installed and registered correctly. [SQLSTATE 08001]
Please see below link
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d2a97cf4-54b2-40b7-836a-b9f146442855/unable-to-open-sql-server-logs?forum=sqlsetupandupgrade
Without errorlog it would be difficult to say why this happened but as errorlog says it has found registry inconsistent so repairing installation would help
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Cannot start web server on executable

Hi
We have an interesting problem with a webserver - we cannot get it to initialise using property nodes or the ini file on a compiled executable.
As part of our application we start the webserver to publish a status page to be viewed remotely. This works fine when we are running in the development environment and also when we are running an executable on a PC with the development environment installed, however it will not initialise on a PC with just the runtime engine installed.
I've attached a portion of code which functionally does exactly the same as in our main application. I've been using this as my tester code and built it into an exe while trying many different things to fix it.
When executed:
The code will sit in the while loop until I press stop.
Web server: Server Active = FALSE
error out = NO ERROR
In the full application the while loop waits for a couple of seconds before throwing an error if the server has not started. In this example I can leave the loop running for some time without it starting. Normally startup time is <50ms when succesful.
This is the ini file for the executable:
[WebTest]
server.app.propertiesEnabled=True
server.ole.enabled=True
server.tcp.serviceName="My Computer/VI Server"
server.vi.propertiesEnabled=True
WebServer.Enabled=True
WebServer.TcpAccess="+*"
WebServer.ViAccess="+*"
DebugServerEnabled=False
DebugServerWaitOnLaunch=False
And this is the webserver config file:
ErrorLog "$LVSERVER_ROOT/logs/error.log"
LogLevel 3
ServerName default
DocumentRoot "$LVSERVER_ROOT/../../www"
Listen 8000
ThreadLimit 10
TypesConfig "$LVSERVER_ROOT/mime.types"
DirectoryIndex index.html
LoadModulePath "$LVSERVER_ROOT/modules" "$LVSERVER_ROOT/LVModules" "$LVSERVER_ROOT/.."
LoadModule LVAuth lvauthmodule
LoadModule LVSnapshot lvsnapshotmodule
LoadModule LVRFP lvrfpmodule
LoadModule dir libdirModule
LoadModule copy libcopyModule
AddHandler LVAuthHandler
AddHandler LVSnapshotHandler .snap
AddHandler LVRFPHandler
AddHandler dirHandler
AddHandler copyHandler
CustomLog "$LVSERVER_ROOT/logs/access.log" "%h %l %u %t \"%r\" %>s %b"
KeepAlive on
KeepAliveTimeout 60
Timeout 60
As a side note, can anybody tell me where the $LVSERVER_ROOT variable is configured?
Things I have tried:
Copying a new config file from the default location before initialisation
Writing a pre-defined (hard-coded) config file before initialisation
Setting root directory locaitons before initialisation (this one actually throws an error because the server isn't active...)
Setting WebServer.Active = TRUE repeatedly inside the while loop
Enabled/disabled the web server in the ini file
System:
Labview 2010
PC's with running Windows 7
Thanks for any help because this is driving me slowly mad!
Ben
Solved!
Go to Solution.

Hi Marco, thanks for replying.
I had looked at that guide previously and had done everything in it but one small section did give me a hint of something to try and I have solved my problem, so thanks!
Here is the issue if anyone is interested:
The DocumentRoot folder in the config has to exist otherwise the webserver cannot be started. So basically, make sure that the file points to a folder that exists!
This does leave two slight annoying issues though - you can't see if the folder exists (and then create it) before starting the webserver because you can't query the folder path without the webserver running.
AND
You can't really set the config file programatically because the settings from the file are loaded on execution, not on webserver start.
The result of this is that the config file and the document root folder should be created (and matching of course...) when the executable is built / installed on the system. Not a massive headache but it means remembering to put things into the build spec and not rely on the software to do the work on boot

Cannot start Windows Server installation

Hi,
I want to upgrade my Server 2008 R2 to Server 2012 R2. But everytime I start the setup in Windows for an in-place upgrade, an error message pops-up saying "Windows Setup experienced an unexpected error. To install Windows, restart the
installation.", right after the "Setup is starting..." stage.
This doesn't have to do with the media or drive. I tried with a virtual drive, and still the same. It doesn't have to do with the image as well, the same error appears if I try to start a Server 2008 R2 installation or any other Windows installation.
The OS hard disk is a dynamic hard disk.
Here is the log from Setup.act:
2013-12-21 03:24:09, Info                  IBS    InstallWindows:Successfully loaded resource language [en-US]
2013-12-21 03:24:09, Info       [0x0601c1] IBS    InstallWindows:Install Path = C:\$WINDOWS.~BT\Sources
2013-12-21 03:24:09, Info       [0x0601c2] IBS    InstallWindows:Setup Phase = 1
2013-12-21 03:24:09, Info       [0x0606cc] IBS    LogBootDeviceInfo:The firmware boot device ARC path is [multi(0)disk(0)rdisk(0)partition(1)] and NT path is [\Device\Harddisk1\Partition1].
2013-12-21 03:24:09, Info       [0x0606cc] IBS    LogBootDeviceInfo:The system boot device ARC path is [multi(0)disk(0)rdisk(0)partition(2)] and NT path is [\Device\Harddisk1\Partition2].
2013-12-21 03:24:09, Info       [0x0601c3] IBS    InstallWindows:Starting downlevel phase of Setup.
2013-12-21 03:24:09, Info       [0x0601c5] IBS    InstallWindows:Setting Working directory as C:\$WINDOWS.~BT\Sources\Panther
2013-12-21 03:24:09, Info       [0x0601ce] IBS    Setup has started phase 1 at 2013-12-21 03:24:09
2013-12-21 03:24:09, Info       [0x0601cf] IBS    Install source is C:\$WINDOWS.~BT\Sources
2013-12-21 03:24:09, Info       [0x0601d0] IBS    Build version is 6.2.9200.16384 (win8_rtm.120725-1247)
2013-12-21 03:24:09, Info       [0x06403d] IBSLIB CreateSetupBlackboard:Creating a new persistent blackboard. Path is [C:\$WINDOWS.~BT\Sources\Panther\SetupInfo] Setup phase is [1]
2013-12-21 03:24:09, Info       [0x090008] PANTHR CBlackboard::Open: C:\$WINDOWS.~BT\Sources\Panther\SetupInfo succeeded.
2013-12-21 03:24:09, Info       [0x064043] IBSLIB CreateSetupBlackboard:Successfully created/opened Setup black board path is [C:\$WINDOWS.~BT\Sources\Panther\SetupInfo]
2013-12-21 03:24:09, Info                  IBS    InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [en-US].
2013-12-21 03:24:09, Info                  IBS    InstallWindows:Setup architecture is [x64]
2013-12-21 03:24:09, Info                         SetupSetVolume: Marking [C:\] for tracking as [TildeBTVolume]
2013-12-21 03:24:09, Info                  IBSLIB SetBTVolumePaths: BTSources folder path = [C:\$WINDOWS.~BT\Sources]
2013-12-21 03:24:09, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\Harddisk1\Partition1].
2013-12-21 03:24:09, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\Harddisk1\Partition1].
2013-12-21 03:24:09, Info                  IBSLIB SetSystemVolumePath:Could not find DOS path for system partition; looking for NT path...
2013-12-21 03:24:09, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\Harddisk1\Partition1].
2013-12-21 03:24:09, Info                  IBSLIB SetSystemVolumePath:Found NT path for system partition: \Device\Harddisk1\Partition1; assigning temporary drive letter...
2013-12-21 03:24:09, Error      [0x0601d3] IBS
InstallWindows:SetSetupBBProperties failed.[gle=0x00000002]
2013-12-21 03:24:19, Info       [0x090009] PANTHR CBlackboard::Close: c:\$windows.~bt\sources\panther\setupinfo.
Any thoughts about this issue?
Thanks in advance!

2013-12-21 03:24:09, Info                  IBSLIB SetSystemVolumePath:Found NT path for system partition: \Device\Harddisk1\Partition1;
assigning temporary drive letter...
2013-12-21 03:24:09, Error      [0x0601d3] IBS
InstallWindows:SetSetupBBProperties failed.[gle=0x00000002]
assigning temporary drive letter...
I think the HDD has only 1 partition and Windows could not extract into another partition so, it hasn't reach the point where it can roll back

Cannot Start Portal Server.

Hi
I am using EP 7.0. I am not able to start portal server. From the log file I have found out the following details.
<b>Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
     ... 7 more
Caused by: java.lang.ClassNotFoundException: com.sap.portals.jdbc.oracle.OracleDriver</b>
Any Suggestion where is the problem. The portal was working fine before stopping it.
Regards
Debasish

There is no clear documentation available to enable custom security but IBM info center has decent documentation for LDAP based security. I would say follow the steps mentioned for IBM directory and then modify the necessary configuration parameters for OID. This should solve your issues. For better help open a PMR with IBM to get necessary quick help.

Cannot start Managed Server- after creating a new domain

I created a new domain, I could start Admin Server but ,I am unable to start Managed Server.
My DB is up & running
at com.collaxa.cube.engine.CubeEngine.finalizeActivity(CubeEngine.java:2842)
at com.collaxa.cube.engine.CubeEngine.checkBlockConditions(CubeEngine.java:3557)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2490)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1133)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:219)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:327)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4350)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4282)
at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:713)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:545)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:654)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:88)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
at oracle.security.jps.wls.JpsWeblogicEjbInterceptor.runJaasMode(JpsWeblogicEjbInterceptor.java:61)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:106)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:106)
at sun.reflect.GeneratedMethodAccessor840.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy245.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:396)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
at java.lang.Thread.run(Thread.java:619)
Caused By: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ReadInputDataSelect' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
DemoDBAdapter:ReadInputData [ ReadInputData_ptt::ReadInputDataSelect(ReadInputDataSelect_inputParameters,CustomerCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510
JCA Resource Adapter location error.
Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/>
The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/DemoConnection'.
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or
2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DemoConnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR).
Please correct this and then restart the Application Server

Dear Anuj,
I created a connection pool in DB adapter with JNDI name "eis/DB/DemoConnection"? and then updated
BUT WHEN I SEE DB ADAPTER in deployments, the sate is New . It should be ACTIVE . right?
Again when I start Managed Server,although my soa_server is up and running, I get this error
However, I did not create any JMS for this domain.
<Aug 9, 2010 11:21:45 AM CDT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter HelloWorld JMSMessageConsumer_init: Retrying connection; attempt #5>
<Aug 9, 2010 11:21:45 AM CDT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter HelloWorld
BINDING.JCA-12135
ERRJMS_ERR_CR_QUEUE_CONS.
ERRJMS_ERR_CR_QUEUE_CONS.
Unable to create Queue consumer due to JMSException.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:620)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
... 8 more
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:87)
at weblogic.jms.dispatcher.Request.getResult(Request.java:52)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:1124)
at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
... 12 more
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:289)
at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:914)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:864)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:106)
... 2 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.jms'. Resolved 'weblogic.jms.backend'; remaining name 'jms'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at weblogic.jms.frontend.FEManager.destinationCreate(FEManager.java:287)
at weblogic.jms.frontend.FEManager.invoke(FEManager.java:548)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherImpl.syncRequest(DispatcherImpl.java:184)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSyncNoTran(DispatcherImpl.java:287)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
... 2 more
>
<Aug 9, 2010 11:21:46 AM CDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Aug 9, 2010 11:21:46 AM CDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 192.168.128.102:8001 was shutdown.>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:8001 was shutdown.>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[3]" listening on 0:0:0:0:0:0:0:1:8001 was shutdown.>
<Aug 9, 2010 11:21:47 AM CDT> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on fe80:0:0:0:20c:29ff:fe81:998f:8001 was shutdown.>
INFO: JMSAdapter JmsResourceAdapter_endpointDeactivation: Deactivating endpoint Endpoint_1
[TopLink Info]: 2010.08.09 11:21:53.232--ServerSession(382132253)--deferred_session logout successful
[TopLink Info]: 2010.08.09 11:21:53.232--ServerSession(381072707)--tracking_session logout successful
<Aug 9, 2010 11:21:54 AM CDT> <Notice> <LoggingService> <BEA-320400> <The log file /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Aug 9, 2010 11:21:54 AM CDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log00021. Log messages will continue to be logged in /u01/app/oracle/product/Middleware/user_projects/domains/base_domain4/servers/soa_server1/logs/soa_server1.log.>
[oracle@OracleTest1 bin]$

Solaris 10 for x88 install issue: cannot start X11 server

Similar Messages

Maybe you are looking for