Domain1 Admin Server Won't Start

I'm using Sun ONE Application Server 7.0.0_03 on a Win 2000 server.
The app server was running just perfectly until today, when I added the 2000 server to our windows 2003 domain.
I did the following:
Changed the windows name of the server.
Added the server to our windows 2003 domain.
When I attempted to restart the app server after rebooting the machine, the administrative server on domain 1 failed to start, but my two server instances in domain1 (server1, and server2) start right up.
The error message I receive on the console when trying to start is:
"Could not start the instance: domain1:admin-server
server failed to start: abnormal subprocess termination
Instance domain1:server1 started
Could not start one or more instances in the domain : domain1
Instance domain2:admin-server already started
Instance domain2:Server2 started
Domain domain2 Started.
Could not start one or more domains
Press any key to continue . . ."
When I try and start the service through the windows service console I get:
"Could not start the Sun App Server 7 Admin Server (domain1:admin-server) service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. I f the problem persists, contact your system administrator."
The windows application log reports:
"CORE0103: Error starting: Initialization Failed."
Any ideas as to what the problem might be would be greatly appreciated.
Please let me know if you need any additional information.
Regards,
Josh

Hi,
try by setting the classpath or first uninstall and install freshly.ok.this may solves your pblm I think so .try out.
regards,
Satya

Similar Messages

Wrong JRE Runtime Lib Path on Win2K--Admin Server Won't Start

Running Sun One Web Server 6.0 SP6 on a Windows 2000 server, I inadvertently entered a typo in the iPlanet Administration Server's Global Settings, "Configure JRE/JDK Paths" link.
In the "JRE Runtime Lib Path" field I typed "jjk1.3.1_03" instead of "jdk1.3.1_03". Now the Sun One web server won't start, so I can't go into the Administrative Server to fix the Jre Runtime Lib Path. I havent' been able to find any file where I can change that erroneous setting either. Is it a Registry entry?
I also tried adding the correct JRE Runtime Lib Path at the end of the Windows PATH environment variable on the server, but that didn't help.

Yes we checked the Registry settings and fixed the typo in the path associated with the key NSES_JRE_RUNTIME_LIBPATH. That should have fixed the problem, but the Sun One web server still wouldn't start.
Moved to plan B and removed then reinstalled the Sun One web server. Now it starts and all is well.
Thanks for helping everyone. This also raised the issue for us of whether or not we are entitled to individual support from Sun since we paid for the Sun One web server. According to the web site, the answer is NO - unless we pay $3,000 for a support contract. Other vendors who recommended using Sun One with their products say YES. We're still tracking that down.

Coldfusion 9, Admin server won't start anymore...

We have installed yesterday updates for Windows 2008 R2, but know Adobe Admin server doesn’t start anymore.
The Macromedia JRun CFusion Server service could not be started. Check the server "cfusion" log files for more information.
What to do know?
We running Coldfusion 9.
In the logs I see the following:
Starting Macromedia JRun 4.0 (Build 108795), admin server
11/02 01:44:51 info JRun Naming Service listening on *:2910
11/02 01:44:53 info No JDBC data sources have been configured for this server (see jrun-resources.xml)
11/02 01:44:53 info JRun Web Server listening on *:8000
11/02 01:44:53 info Deploying enterprise application "JRun Management Console" from: file:/C:/JRun4/servers/admin/jmc-app.ear
11/02 01:44:53 info Deploying web application "JRun Management Console" from: file:/C:/JRun4/servers/admin/jmc-app.ear
11/02 01:44:54 user JSPServlet: init
11/02 01:44:55 info Deploying enterprise application "JRun 4.0 Internal J2EE Components" from: file:/C:/JRun4/lib/jrun-comp.ear
11/02 01:44:55 info Deploying EJB "JRunSQLInvoker" from: file:/C:/JRun4/lib/jrun-comp.ear
Server admin ready (startup time: 8 seconds)
Error: Exception thrown by the agent : java.rmi.server.ExportException: Listen failed on port: 8701; nested exception is:
                java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
Error: Exception thrown by the agent : java.rmi.server.ExportException: Listen failed on port: 8701; nested exception is:
                java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
Error: Exception thrown by the agent : java.rmi.server.ExportException: Listen failed on port: 8701; nested exception is:
                java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
Error: Exception thrown by the agent : java.rmi.server.ExportException: Listen failed on port: 8701; nested exception is:
                java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
Error: Exception thrown by the agent : java.rmi.server.ExportException: Listen failed on port: 8701; nested exception is:
                java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
Error: Exception thrown by the agent : java.rmi.server.ExportException: Listen failed on port: 8701; nested exception is:
                java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind

It looks like there was a problem during initial deployment, in the log you posted it indicates a resource failed to get created by the XACML authorization provider, it would seem you are out disk space:
ou=Policies,ou=XACMLAuthorization,ou=myrealm,dc=prismaDomain' MODIFY to Transaction Log: No space left on device>
####<Jan 9, 2008 11:10:44 AM WIT> <Error> <Security> <arspapp2> <prismaAdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1199851844413> <BEA-090064> <The DeployableAuthorizer "myrealm_weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl" returned an error: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource.>
Jeff

WebLogic Admin server fails to start after reboot

Hi Gurus,
Weblogic Admin server won't start up after a server reboot. Note that weblogic was gracefully shutdown before the restart.
Also note that the following files were accidentally deleted after the reboot (but I don't think that should cause an issue..):
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
Looking at the AdminServer.log:
*####<Oct 11, 2012 11:27:53 AM EDT> <Critical> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969273846> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException:*
java.lang.AssertionError: weblogic.management.provider.EditFailedException:
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:79)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: weblogic.management.provider.EditFailedException:
     at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
     at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: org.xml.sax.SAXParseException: Premature end of file.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
     at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
     at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
     at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
     at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
     at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
     at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
     at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
     at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
     at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
     at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
     at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:81)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274051> <BEA-000365> <Server state changed to FAILED>
####<Oct 11, 2012 11:27:54 AM EDT> <Error> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274053> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274069> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274140> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274141> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274146> <BEA-220028> <Web Service reliable agents are suspended.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274153> <BEA-220029> <Web Service reliable agents are shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <MessagingBridge> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274318> <BEA-200001> <The messaging bridge service has successfully shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274426> <BEA-040308> <JMS service is suspending.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274506> <BEA-040107> <Undeployed 8 default connection factories.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274510> <BEA-040015> <JMS shutdown is complete.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274530> <BEA-001144> <Force Suspending the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274536> <BEA-001146> <Force suspend of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274538> <BEA-001147> <Shutting down the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274552> <BEA-001149> <Shutdown of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274694> <BEA-000236> <Stopping execute threads.>
Kindly guide me with this. Thanks!
Edited by: Kent Pawar. on Oct 11, 2012 8:51 AM

Issue is :
Caused By: weblogic.management.provider.EditFailedException:
One probable reason can be some change made to the config.xml file . If you have previous backup for the config.xml file then try to replace the config.xml file and restart the server .
Another reason for this exception may be that there were some changes made to configuration through the Admin Console which were not activated completely and Admin Server was restarted . under this scenario weblogic will create a /pendig dir and have a config.xml file created there with the un-activated changes .
some workaround you can try to restore the Admin Server :
Under domain dir ,
\pending directory -- take backup and delete the dir .
Under Admin Server Dir :
data\store --- take backup and delete the dir .
thanks,
Sandeep

After Setting Up SSO Managed Server Won't Start

I am using the Oracle supplied white paper to set up SSO using Active Directory. Following those instructions everything was working and testing correctly until I added the NegotiateIdentityAsserter provider to the list of WLS providers. Now the managed server won't start. The admin server starts without any errors and goes to the RUNNING state. But the Start BI Services command window gets to the wls.alive: prompt and hangs. And hangs. Eventually the window goes away and it may throw an error but I've never seen it. You can login to the WLS console and EM without a problem. Remove the new provider and everything comes up normally. I have looked at the krb5.ini and krb5login.conf files and even rewritten them from scratch without any change in behavior.
While looking for answers I ran into the SPNEGOCheck webapp that Oracle makes available to diagnose problems. It says everything is OK until it parses the krb5login.conf and then complains that the Username associated with SPN in AD is blank and so doesn't match the SPN specified in the krblogin config. But I can't see anything wrong in the files themselves.
from the log:
In section 'libdefaults'
LSA: Found Ticket
LSA: Made NewWeakGlobalRef
LSA: Found PrincipalName
LSA: Made NewWeakGlobalRef
LSA: Found DerValue
LSA: Made NewWeakGlobalRef
LSA: Found EncryptionKey
LSA: Made NewWeakGlobalRef
LSA: Found TicketFlags
LSA: Made NewWeakGlobalRef
LSA: Found KerberosTime
LSA: Made NewWeakGlobalRef
LSA: Found String
LSA: Made NewWeakGlobalRef
LSA: Found DerValue constructor
LSA: Found Ticket constructor
LSA: Found PrincipalName constructor
LSA: Found EncryptionKey constructor
LSA: Found TicketFlags constructor
LSA: Found KerberosTime constructor
LSA: Finished OnLoad processing
Config name: C:\Windows\krb5.ini
KdcAccessibility: reset
KdcAccessibility: reset
Reachable? true
Connection seems to have succeeded.
Parsing section contents 'com.sun.security.jgss.krb5.accept { com.sun.security.auth.module.Krb5LoginModule required principal="[email protected]" keyTab=biwhse1a.keytab useKeyTab=true storeKey=true debug=true;};'
Section name: 'com.sun.security.jgss.krb5.accept'
Getting next NV pair beginning at 'principal="[email protected]" keyTab=biwhse1a.keytab useKeyTab=true storeKey=true debug=true'
NVPair name: 'principal' value: '[email protected]'
NVPair name: 'keyTab' value: 'biwhse1a.keytab'
NVPair name: 'useKeyTab' value: 'true'
NVPair name: 'storeKey' value: 'true'
Got back 4 name/value pairs.
section com.sun.security.jgss.krb5.accept should probably contain a setting for debug=true
Section com.sun.security.jgss.krb5.accept seems OK
The krb5.ini file:
[libdefaults]
default_realm = SRS1.COM
default_tkt_enctypes = des-cbc-crc
default_tgs_enctypes = des-cbc-crc
ticket_lifetime = 600
[realms]
SRS1.COM = {
kdc = 129.58.120.200
admin_server = adc01.srs1.com
default_domain = SRS1.COM
[domain_realm]
.srs1.com = SRS1.COM
[appdefaults]
autologin = true
forward = true
forwardable = true
encrypt = true
The krb5login.conf file:
com.sun.security.jgss.krb5.accept {
com.sun.security.auth.module.Krb5LoginModule required
principal="[email protected]"
keyTab=biwhse1a.keytab
useKeyTab=true
storeKey=true
debug=true;
[D:\] setspn -L bi_kerb_prin
Registered ServicePrincipalNames for CN=bi_kerb_prin,OU=Non-Person Users,OU=WRC Users,DC=srs1,DC=com:
HTTP/biwhse1a.srs1.com
HTTP/biwhse1a
[D:\]
OBIEE 11.1.1.6.2 BP2
Windows Server 2008 SP1

Did you try -Djava.security.krb5.conf=<path>/krb5.conf before the %EXTRA_JAVA_PROPERTIES%. in your C:\OBI\user_projects\domains\bifoundation_domain\bin\setDomainEnv.cmd .?
Also change your JAAS config file and try with
com.sun.security.jgss.krb5.initiate {
com.sun.security.auth.module.Krb5LoginModule required
principal="HTTP/[email protected]"
keyTab=biwhse1a.keytab
useKeyTab=true
storeKey=true
debug=true;
com.sun.security.jgss.krb5.accept {
com.sun.security.auth.module.Krb5LoginModule required
principal="HTTP/[email protected]"
keyTab=biwhse1a.keytab
useKeyTab=true
storeKey=true
debug=true;
Now restart and see.
Hope this helps. Pls mark if it does.
Thanks,
SVS
Edited by: SSVS on Mar 17, 2013 11:47 PM

Report Application Server won't start. CCM always says Starting....

I am complete newbie to doing admin for Crystal Servers, forgive the question:
(Win Server 2003 r 2 / CR XI)
Report Application Server won't start which is preventing other servers from starting in CCM.
Reboot machine several times and still having the issue.
Get an error msg in Windows before login window appears stating that the crystalras.exe application requested a runtime to terminiate in an unusual way (.Net error).
I get the following error msg in my event viewer.
From Event Viewer:
Event Type: Error
Event Source: BusinessObjects_crystalras
Event Category: Startup
Event ID: 33000
Date: 7/27/2010
Time: 4:24:34 PM
User: N/A
Computer: CRYSTAL
Description:
Failed to start the Report Application Server.
From Logging:
Timestamp ProcessID ThreadID Message
Tue Jul 27 20:24:34 2010 2496 3176 assert failure: (.\sso_wrapper.cpp:94). (SFileSys::exists(ssPath) && SFileSys::isDir(ssPath) : Platform binaries directory not valid.).
We installed some Windows Server Updates about 3 months ago (at the time, over 70 Windows updates were installed) but, this problem hasn't shown up until 2 or 3 weeks ago. I think a .Net Service Pack might have been part of the updates at that time. When we did the updates, Windows was shutdown and updates installed per the preferred option of Windows. But now when rebooting since that time, the server continually reccomends the install updates and shutdown option. Do we need to rollback the server to date prior those updates if possible?
I have also uninstalled .Net Framework back to 2.0. Is 1.0 or 1.1 the max that will work with XI?
Should I also try to uninstall all other Windows updates?
Thanks in advance for any help, Ed

Post this query to the [Business Objects Enterprise Administration|BI Platform; forum.

Messaging Server won't start up, or acts strangely

One of the config files has disappeared, or the Messaging Server
is acting "strangely".
<P>
Because of bugs in the Berkeley DB code, it is possible for a configuration
file to become corrupted. The Messaging Server will remove a severly
corrupted config file, but there is a threshold of corruption that may
impact server operation and may not cause files to be deleted.
<P>
If you notice that one of the config files is gone (your server won't start),
or that your server is acting strangely, DO NOT REPLACE IT WITH A BACKUP COPY.
This will most likely re-introduce the corruption. Instead, make note of
all the configuration changes you've made with the Messaging Server admin gui.
The easiest way to do this is to print out each page. Then replace the
config file with a clean one from the install directory or from the media.
<P>
Before re-starting the server, check each admin gui page to make sure it
matches your printout, and make any necessary changes. Then start the server.
<P>
The installed configuration files are located in the message spool area,
by default: /var/spool/postoffice/config and they are:<BR>
<P>
Account-Handler<BR>
Account-Manager<BR>
AutoReply-Handler<BR>
Configuration-Manager<BR>
Dispatch<BR>
Error-Handler<BR>
Finger-Server<BR>
IMAP4-Server<BR>
MTA-Accounts<BR>
Mailbox-Deliver<BR>
POP3-Server<BR>
Program-Deliver<BR>
SMTP-Accept<BR>
SMTP-Deliver<BR>
SMTP-Router<BR>
UNIX-Deliver<BR>
<P>
Un-configured copies of all these files may be found under the directory
you installed the server at:
<P>
/install/server/data<BR>
<P>
The fresh files will all have a .install appended to them.

Shut the computer dow, remove the power cord and all peripherals, wait for 30 seconds, replace the power cod and press the start button at the same time.
If you do not have the iSight, try the steps in [this|http://docs.info.apple.com/article.html?artnum=300908] Apple article.

I am upgrading to Calendar Server 4.0 on NT with more than 9 nodes (or I already have) and my server won't start

I am upgrading to Calendar Server 4.0 on NT with more than 9 nodes
(or I already have) and my server won't start.
<P>
The steps are the same whether you have already upgraded or are about to.
<P>
Calendar Server 4.0 on the Windows NT platform can only support up to nine
nodes on one server, while 3.51 supported up to 14. If you have a Calendar
Server 3.51 with more than 9 nodes that you want to upgrade to Calendar Server
4.0, Netscape recommends that you migrate the extra nodes to another Calendar
Server 3.51 on another Windows NT system. To accomplish this:
<OL>
<LI>Install Calendar Server on another Windows NT machine and configure it to
use the same directory server as your current Calendar Server.
<LI>Stop and backup your current Calendar Server.
<LI>Individually zip up the node directories you want to move to the new
server. (drive:\unsers\unison\db\Nx
where "x" is the number of the node you want to use.)
<LI>Stop the new Calendar Server.
<LI>Unzip the files into the new Calendar Server in the same place as they
were on the old server.
<LI>Edit the unison.ini
file on the new server to add the nodes you have just migrated.
<LI>Edit the unison.ini
file on the old server to remove the nodes you have moved to the new server.
<LI>Edit the nodes.ini
file on the old server to remove the nodes you just moved and then add them
with the new hostname. Keep in mind that you will only be able to modify the
node network from the old host.
<LI>Run unidbfix -export
on both servers for all nodes.
<LI>Edit the remotenodes.ini
file on both servers to reflect your node topology.
<LI>Run unidbfix -import
to import the changes into the node databases.
<LI>Run unidbfix -c,
then -f,
then -c
again on both servers for all the nodes.
<LI>If you don't get any errors, run uninode -test all
to test if your nodes connections are set properly. If they are not, <B>do not</B>
start either of the servers; instead, fix the errors and try again.
<LI>Start both servers.
<LI>Log in and check to see if you can see people on remote nodes.
<LI>Notify the users on the moved nodes of their new calendar host.
<LI>If you did this in preparation of an upgrade, you can now run the upgrade to
4.0 since both servers contain fewer than 9 nodes.
</OL>

Use Disk Utility whihc is in the Utilities Folder.
Select your Boot Disk on the left.
Select Verify Permissions
If any errors the do Reapir permissions.
You might have to repeat the process.
see this:
Steve

X server won't start after recent catalyst-test and kernel upgrade

Hi,
after recent upgrade of catalyst-test (13.2) and kernel (3.7.5), my x server won't start with this log (WW) and (EE) only:
[ 114.989] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 116.077] (WW) Falling back to old probe method for fglrx
[ 116.093] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[ 116.101] (EE) fglrx(0): DAL initialization failed!
[ 116.101] (EE) fglrx(0): Display Infrastructure Failed
[ 116.101] (EE) fglrx(0): PreInit failed
[ 116.212] (EE) Screen(s) found, but none have a usable configuration.
[ 116.212]
Fatal server error:
[ 116.212] no screens found
[ 116.212] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 116.212] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 116.212] (EE)
[ 116.515] Server terminated with error (1). Closing log file.
My card is mobility radeon hd 5700, I'm running on x86_64 system. I'm using aticonfig generated xorg.conf. I will provide any other information if needed.
I've tried:
- to downgrade to catalyst 12.8 and xorg 1.12 (screen just freezes after trying to get to X, only poweroff button works (system catches the signal and shuts down softly - no errors in Xorg.0.log))
- to use catalyst-total 13.1 / catalyst-generator 13.1 (Xorg.0.log says something about *not* compatible module - i can try it again and give you the whole log, it is probably another problem)
- to use open-source drivers (poor performance, overheating)
- to check nomodeset option (present at all kernel images in generated grub.cfg)
Unfortunately, I could not find any similar issue solved in past few days...

Downgrading kernel to 3.7.4 actually worked for catalyst 13.1. Anyone knows what could be wrong for linux 3.7.5?
Edit: catalyst-test 13.2 beta works with linux 3.7.4.
Last edited by sirkubador (2013-02-05 14:24:44)

Server won't start/Bad JVM?

Running CFMX7.02. After noticing that the Java version was
1.4 something (the version originally supplied with the product in
2006), and that I couldn't do things like use the "browse server"
controls in CFAdministrator without getting Java errors, I
repointed the CF engine to use the version supplied by Java on
their website today. Now the server won't start.
From the CF error log:
Error: no `server' JVM at `C:\Program
Files\Java\jre1.6.0_03\bin\server\jvm.dll'.
Windows event log is no help, reporting that is has received
"server-specific error code 2". Based on the advice of some earlier
topic, I tried to restart the service with "interact with the
Desktop" checked, but no DOS window there.
Any ideas? I'd be happy to point CF back to its own version
of Java, if I could do so without interacting with the
Administrator (which requires starting the server).

quote:
Originally posted by:
JR "Bob" Dobbs
1. CF 7 does not support JVMs higher than 1.4.x
Ah. That explains
that.
quote:
2. You should install the full JDK so you'll get the server
version of the JVM
3. You change change the JVM version by editing the
jvm.config file.
Got it--and thanks for the extremely quick reply.
However, what can I do to fix the Java errors that keep me
from using the GUI file-browsing components in the CFAdministrator,
since I can't upgrade the main Java engine?

EPMA Dimension server won't start using SSL enabled Database

Has anyone had any luck configuring EPMA 11.1.2.2 or 11.1.2.1 EPMA Dimension server with a JDBC SSL connection? I am using the following url to configure my SSL-enabled database:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=slc00qox)(PORT=1529))(CONNECT_DATA=(SERVICE_NAME=slc00qox.us.oracle.com)))
and the Dimension server won't start. Other Foundation, Essbase and Reporting repository connections work with same URL. Getting an error in Event Log:
Service cannot be started. Hyperion.DimensionServer.Interface.Exceptions.EPMAServiceException: Cannot initialize the Session Manager. ---> Hyperion.CommonServices.Exceptions.SessionManagerException: Session Manager could not start because database connectivity could not be established. ---> Oracle.DataAccess.Client.OracleException ORA-12537: TNS:connection closed at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
at Hyperion.DimensionServer.SessionManager.SessionManager.Initialize(String configFileName, Boolean restorePastInstanceSessions, Boolean enableCaching)
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.Service.Main.InitializeSessionManager()
at Hyperion.DimensionServer.Service.Main.Start()
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
AND
[EPMA Server Startup] ERROR SVR_ERR_PROCESSMGR_CANT_INIT_SESSIONMGR:Cannot initialize the Session Manager.Hyperion.DimensionServer.Interface.Exceptions.EPMAServiceException: Cannot initialize the Session Manager. ---> Hyperion.CommonServices.Exceptions.SessionManagerException: Session Manager could not start because database connectivity could not be established. ---> Oracle.DataAccess.Client.OracleException ORA-12537: TNS:connection closed at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.SessionManager.SessionManager.InitializeSqlConnectionString()
at Hyperion.DimensionServer.SessionManager.SessionManager.Initialize(String configFileName, Boolean restorePastInstanceSessions, Boolean enableCaching)
--- End of inner exception stack trace ---
at Hyperion.DimensionServer.Service.Main.InitializeSessionManager()
at Hyperion.DimensionServer.Service.Main.Start()

As you have backup you can try this:
Restore your master database backup to another instance of SQL Server and in the "To
database:" section of the Restore Database dialog box, use an alternate database name such as "recover_master" to avoid conflict with the master database on this instance of SQL Server. This will cause the mdf/ldf to be named "recover_master.mdf"
and "recover_master_1.ldf". Then detach the
recover_master database, go into the file system, copy the recover_master.mdf and recover_master_1.ldf to the instance of SQL Server with the corrupt master database. Delete the corrupt master.mdf and mastlog.ldf files, rename recover_master.mdf to master.mdf,
and rename recover_master_1.ldf to mastlog.ldf. Now you're ready to try starting the SQL Server service again!
http://blogs.technet.com/b/fort_sql/archive/2011/02/01/the-easiest-way-to-rebuild-the-sql-server-master-database.aspx
Once master is online you can restore other database.

Logitech Media Server won't start

Hi,
Logitech Media Server won’t start after I clean installed 10.10.1 and migrated my user data from time machine. I tried tuned of firewall and clean install LMS many times and tried different version of LMS from 7.7.4 to 7.9 but none of them worked.
I builded a new user account for testing, LMS works well in this new user account.
Is there anything I can do to fix my old user account?
Thank you.

Thank you very much! I did not know about the nightly builds. LMS has pretty much worked throughout the years; it may have needed an update now and then but I never had to go looking for beta versions.
I held off upgrading my Mac Pro -- which acts as a server for iTunes and other things around the house -- to Yosemite until today. All was well except for getting LMS to start. I was pretty bummed at the prospect of not having my tunes on my Squeezebox radio. In any case, I'm glad I found my answer in 5 seconds here at the Apple forums. Rock on.

J2EE Application Server Won't Start :-(

Hi, I'm new to J2EE and I'm trying to set up the application server so I can develop an application. I've successfully installed the J2EE SDK and application server however, when I select 'Start Default Server' from the menu I get a command window with the following message:
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Timeout waiting for domain domain1 to go to starting state.
CLI156 Could not start the domain domain1.
Press any key to continue . . .'
I found the following text in the log file.
[#|2005-10-06T02:42:02.015+0100|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Sun/AppServer/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Sun/AppServer/jdk/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Sun\AppServer\jdk\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Sun\AppServer\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Sun/AppServer/jdk/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\j2ee-svc.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\jax-qname.jar;C:/Sun/AppServer/lib\jaxr-api.jar;C:/Sun/AppServer/lib\jaxr-impl.jar;C:/Sun/AppServer/lib\jaxrpc-api.jar;C:/Sun/AppServer/lib\jaxrpc-impl.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\mail.jar;C:/Sun/AppServer/lib\relaxngDatatype.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\saaj-api.jar;C:/Sun/AppServer/lib\saaj-impl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\xsdlib.jar;C:/Sun/AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
*** EXITING ERROR:
Can't create Java VM
Can anyone advise as to what I should do to solve this problem? The path contains an entry that points to Sun/AppServer/jdk/bin so I don't understand why it can't create a JVM.
I'm sorry to repeat a problem that many people have posted about in the past but I've went through all occurences for this problem but none of the solutions solve the problem.
Many thanks in advance.
Ian

Some more information on this problem.
I initially had Java installed in C:\Program Files\Java but one of the errors I initially got after I had installed the server was that my path had spaces in it so to solve this problem I removed Java completely from my system and then simply installed the J2EE bundle that contained the J2SE SDK, I'm assuming that by installing this alone a JVM will be installed with everything else won't it?
My path at the moment contains the following:
C:\Sun\AppServer\jdk\jre\bin;C:\Sun\AppServer\jdk\bin;C:\Sun\AppServer\bin;
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;
Any help at all would be gratefully received as I have spent a long time trying to sort this problem and have got nowhere.
Many thanks in advance

Directory Admin server fail to start

Hello,
When trying to start the directory admin server I get this error:
SunONE-WebServer-Enterprise/6.0SP3 B05/14/2003 17:58
failure: server initialization failed (Interrupted system call)The admin error logs this:
[08/Aug/2005:13:55:42] info (28523): successful server startup
[08/Aug/2005:13:55:42] info (28523): SunONE-WebServer-Enterprise/6.0SP3 B05/14/2003 17:58
[08/Aug/2005:13:55:45] info (28523): Access Host filter is: *.something.com.au
[08/Aug/2005:13:55:45] info (28523): Access Address filter is: *
[08/Aug/2005:13:55:46] failure (28550): Invalid configuration: Could not determine base pathname of the fileI searched google and this forum but came up nothing. Any ideas?

Check file/dir permissions.
or
Uninstall and re-install DS5.2.
Gary

RADIUS Server Won't Start

After running Software Update and installing the Security Update 2008-005 and iTunes 7.7.1 on the server, I noticed none of my wireless clients would authenticate. I checked Server admin and the Radius server was not running. Upon trying to start the RADIUS service in Server Admin the Radius server wouldn't start. Could this software update be to blame? Any Ideas?

+The Logs keep repeating the following sequence:+
Sat Aug 2 10:51:33 2008 : Info: Using deprecated naslist file. Support for this will go away soon.
Sat Aug 2 10:51:33 2008 : Info: rlm_exec: Wait=yes but no output defined. Did you mean output=none?
Sat Aug 2 10:51:33 2008 : Info: rlmeaptls: Loading the certificate file as a chain
Sat Aug 2 10:51:33 2008 : Error: rlm_eap: SSL error error:0906A068:PEM routines:PEMdoheader:bad password read
Sat Aug 2 10:51:33 2008 : Error: rlmeaptls: Error reading private key file
Sat Aug 2 10:51:33 2008 : Error: rlm_eap: Failed to initialize type tls
Sat Aug 2 10:51:33 2008 : Error: radiusd.conf[10]: eap: Module instantiation failed.
Sat Aug 2 10:51:33 2008 : Error: radiusd.conf[1954] Unknown module "eap".
Sat Aug 2 10:51:33 2008 : Error: radiusd.conf[1897] Failed to parse authenticate section.

Domain1 Admin Server Won't Start

Similar Messages

Maybe you are looking for