CLI156 Could not start domain domain1 error when J2ee is installed

Whenever I install J2ee 1.4 sdk the first time the application server starts and everything works fine. But when the system is restarted and the server is started again i get the above mentioned error.
Domain domina1 failed to startup. Could not start domain domain1. I have installed and uninstalled the application many times but yet I am experiencing the same error.
Please give me a solution to this error asap.
Thanks,
Poonam

Did you check server log for the exact cause of startup failure? One thing that is possible is that some of the ports associated with server listeners start being used by other processes after system restart (it seems that Windows use ports in 10xx range for remote drive mappings - so that might be one area where you might run into issues). If so, changing server port numbers might help. In any case, check logs for the exact cause of error .

Similar Messages

CLI156 Could not start the domain domain1

I installed successfully the Appserver on desktop, but when I try to start it from laptop, comes the message below. Both are w2k and 512 memory.
Environment:
C:\>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Luis Araujo\Application Data
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=LAQA
ComSpec=C:\WINNT\system32\cmd.exe
HOMEDRIVE=C:
HOMEPATH=\
J2EE_HOME=C:\\Sun\\AppServer
LOGONSERVER=\\LAQA
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Os2LibPath=C:\WINNT\system32\os2\dll;
Path=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\WINNT\system32\nls;C:\WINNT\system32\nls\ENGLISH;C:\Program Files\C
ommon Files\Autodesk Shared\;C:\Sun\AppServer\bin;C:\Sun\AppServer\jdk\bin;C:\Sun\AppServer\lib
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 8 Stepping 10, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=080a
ProgramFiles=C:\Program Files
PROMPT=$P$G
SystemDrive=C:
SystemRoot=C:\WINNT
TEMP=C:\DOCUME~1\LUISAR~1\LOCALS~1\Temp
TMP=C:\DOCUME~1\LUISAR~1\LOCALS~1\Temp
USERDOMAIN=LAQA
USERNAME=db2admin
USERPROFILE=C:\Documents and Settings\Luis Araujo
windir=C:\WINNT
Prompt message:
Domain domain1 failed to startup. Please check the server log for more details.
CLI156 Could not start the domain domain1.
Press any key to continue . . .
Server.log:
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr) ...
[#|2004-01-03T06:36:00.436-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-01-03T06:36:04.612-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-01-03T06:36:05.283-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-01-03T06:36:07.587-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-01-03T06:36:08.037-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-01-03T06:36:08.057-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-01-03T06:36:08.087-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-01-03T06:36:14.306-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-01-03T06:36:30.510-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-01-03T06:36:32.042-0200|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-01-03T06:36:35.046-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-01-03T06:36:39.062-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-01-03T06:36:39.072-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-01-03T06:36:39.903-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-01-03T06:36:40.023-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-01-03T06:36:44.860-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
Remote message: Processing beans ....
[#|2004-01-03T06:36:45.121-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
Remote message: Compiling wrapper code ....
Compilation failed: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.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-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.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\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:361)
     at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:210)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1144)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:326)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:196)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:277)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:163)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:128)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:79)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:216)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:152)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:270)
     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:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:266)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:268)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
     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:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:468)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:364)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:343)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.ejb.codegen.JavaCompilerException: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.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-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.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\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.Compiler.compile(Compiler.java:76)
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:353)
     ... 44 more
Caused by: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.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-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.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\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.ProcessRunner.makeTimeoutException(ProcessExecutor.java:348)
     at com.sun.ejb.codegen.ProcessExecutor.execute(ProcessExecutor.java:140)
     at com.sun.ejb.codegen.Compiler.runProcess(Compiler.java:165)
     at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:128)
     at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:65)
     at com.sun.ejb.codegen.Compiler.compile(Compiler.java:67)
     ... 45 more
[#|2004-01-03T06:37:46.269-0200|WARNING|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.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-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.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\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:361)
     at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:210)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1144)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:326)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:196)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:277)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:163)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:128)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:79)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:216)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:152)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:270)
     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:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:266)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:268)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
     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:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:468)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:364)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:343)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-01-03T06:37:46.269-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 65565 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2004-01-03T06:37:46.309-0200|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|No local string defined|#]
[#|2004-01-03T06:37:46.319-0200|SEVERE|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|No local string defined
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: com.sun.ejb.codegen.ProcessExecutorException: Process timed out.
Timeout was 60,000 msecs
Attempted command: C:\Sun\AppServer\jdk\bin\javac.exe -extdirs C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext -g -d C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp -classpath C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.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-rt.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\commons-logging.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\mail.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar;C:\Sun\AppServer\domains\domain1\lib\classes;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\applications\j2ee-apps\MEjbApp\mejb_jar;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp;C:\Sun\AppServer\domains\domain1\generated\ejb\j2ee-apps\MEjbApp @C:\Documents and Settings\Luis Araujo\Local Settings\Temp\681e45_f9dae089d50000_29515.s1a
Output from command:
     at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:361)
     at com.sun.ejb.codegen.IASEJBC.compileAndRmic(IASEJBC.java:210)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1144)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:326)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:196)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:277)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:163)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:128)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:79)
     at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:216)
     at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:152)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:270)
     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:324)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:266)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:268)
     at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:212)
     at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:218)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:808)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:781)
     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:324)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:468)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:364)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:343)
     at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:164)
     at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:185)
     at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:160)
     at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:82)
     at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     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:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-01-03T06:37:46.329-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-01-03T06:38:03.483-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-01-03T06:38:04.955-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-01-03T06:38:06.988-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-01-03T06:38:07.038-0200|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-01-03T06:38:07.119-0200|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-01-03T06:38:07.119-0200|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-01-03T06:38:07.409-0200|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-01-03T06:38:53.896-0200|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-01-03T06:38:56.249-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-01-03T06:38:56.359-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-01-03T06:38:56.980-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-01-03T06:38:56.990-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-01-03T06:38:57.080-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-01-03T06:38:57.100-0200|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-01-03T06:40:59.587-0200|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 120000 milli

Which J2SE version are you using - is that version corrupted - looks like some of the JAXP classes are not found

CLI156 Could not start the domain domain1. in Application Server 8

Hi everybody!
Sorry to post this message here at Application Server 7. But I'm using the Application Server 8 along with NetBeans 4.1 early access. Suddenly, the application server stop working on my computer and now, every time I try to start the default server, I get this error message:
CLI156 Could not start the domain domain1.
With the following log:
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2004-12-28T22:46:39.359+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2004-12-28T22:46:42.296+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-12-28T22:46:42.625+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-12-28T22:46:46.921+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded).|#]
[#|2004-12-28T22:46:46.921+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|
log4j:WARN Please initialize the log4j system properly.|#]
[#|2004-12-28T22:46:47.687+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-12-28T22:46:47.718+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-12-28T22:46:47.750+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-12-28T22:46:53.718+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-12-28T22:46:56.984+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-12-28T22:46:57.984+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-12-28T22:46:59.328+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-12-28T22:47:00.468+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-12-28T22:47:00.640+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-12-28T22:47:00.640+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-12-28T22:47:02.390+0000|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-12-28T22:47:04.640+0000|ADVERTENCIA|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.err|_ThreadID=10;|
CharScanner; panic: ClassNotFoundException: com.sun.jdo.spi.persistence.support.ejb.ejbqlc.EJBQLLexer$EJBQLToken|#]
I'm running this application server on Windows XP, like I said, I was working with NetBeans and suddenly, the AS stop working.. I did not delete anything, I did not move anything either.
Please, does any of you have any ideas of how can I fix this issue?
Best regards!

You may try this soultion. I fixed this in my Window 2000 machine(Application Server 8) by:
1. Edit domain.xml($DEFAULT_DOAMIN/config)
2. Update the port="4702" for http-listener tag, and change to something else(e.g. 4802).
3. Save it
4. Make sure the Application Server is shut down.
5. Start the Application Server.
Hope it helps!
Ming-wei

CLI156 Could not Start the domain - new session

Hi,
I'm trying to start my doamin but get the following message:
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Could not create temporary files - check C:\DOCUME~1\Γ∞≥π\LOCALS~1\Temp\ to see
if its writeable and not-full
CLI156 Could not start the domain domain1.
I guess the problem is with the library name in hebrew. But I don't know where can I change the path for the temporary files.
Can anyone help?
Thanks,
Gilad

Specify TempDir directive in your server's instance_dir/config/init.conf file.
Syntax is:
TempDir path
Or change environment's TEMP variable. Application server uses this variable for temp files writing by default.

Could not start domain

Dear all,
I'm experiencing a rather strange issue with the "asadmin" utility for Sun ONE Application Server 7 on Solaris 9, where the default domain "domain1" could not be found.
Whenever the command "asadmin start-domain --domain domain1" is issued, the error,
Could not start the domain.
domain1 is not a registered domainWhen I check the Sun ONE Application Server's installation directory, I found two files "domains.lck" and "domains.bin" both with 0 bytes length.
I've checked with another Sun ONE Application Server's installation directory and found that "domains.bin" is not 0 bytes in length.
Any idea on how to resolve this issue?
Thanks in advance.

Found a solution.
After uninstalling the SUN ONE Application Server, some packages must be removed as stipulated in the post with SunOne ID:7887.
The processes must be killed as well.
After that, the /opt/SUNWappserver7 directory was removed as well.
Reinstalling the application server did not cause any problems. Even the domain "domain1" was registered properly as well!
However, when starting the "domain1", the following error was found in the server.log,
[27/Jan/2004:18:25:08] INFO ( 720): CORE1116: Sun ONE Application Server 7.0.0_01
[27/Jan/2004:18:25:08] INFO ( 721): CORE3016: daemon is running as super-user
[27/Jan/2004:18:25:10] INFO ( 721): CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.4.2_02] from [Sun Microsystems Inc.]
[27/Jan/2004:18:25:10] SEVERE ( 721): CORE4007: Internal error: Unexpected Java exception thrown (unknown exception, no description), stack: java.lang.NoClassDefFoundError: com/sun/messaging/jmq/jmsclient/JMSXATopicConnectionFactoryImpl
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminFactoryImpl.getJMSAdmin(JMSAdminFactoryImpl.java:53)
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminFactoryImpl.getJMSAdmin(JMSAdminFactoryImpl.java:39)
     at com.iplanet.ias.jms.IASJmsUtil.getJMSAdminFactory(IASJmsUtil.java:99)
     at com.iplanet.ias.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:157)
     at com.iplanet.ias.server.ApplicationServer.onInitialization(ApplicationServer.java:206)
     at com.iplanet.ias.server.J2EERunner.confPreInit(J2EERunner.java:114)
[27/Jan/2004:18:25:10] SEVERE ( 721): CORE3186: Failed to set configurationAny workarounds would be greatly appreciated... Thanks!!

Win OS could not start becasue of error in the software on Satellite A85-S107?

Windows could not start because of an error in the software. Please report this problem as:
Load needed DLLs for kernel.
Please contact your support person to report this problem."
A blue screen was suddenly pop up when i was surfing a website, the above warning in black and white was showed after i took out the battery and restarted the windows.
I thought it was just a simple step if i took out the recovery disk, but i was wrong.
The recovery procedure was doing fine to 100% finished. But after pressing any key, the above warning kept appear, no matter how many times i had re-installed by recovery disk or (every time reached 100% )or by using full version of window Xp.
Neither it worked by formatting the HD I had connected it with a IDE2USB link to my friend's XP laptop nor changing another HD.
I excluded the HD problem, then i guess it might be the BIOS was being hacked (?) I downloaded the BIOS update to see whether it works or not?
but the result was disappointing. It just stop at the step 4 of the updating procedure, it just freeze at performing flash initiating step.
I want to take out the CMOS battery for few seconds, but i am not that pro and i might cause damage by improper handling.
Could anyone tell me what happen to my computer and how i can show the above problem?

Hello Wai
If your unit make troubles after recovery image installation it is probably hardware related issue. Can you enter BIOS settings as usual? If not I am afraid the BIOS chip is damaged. It happen if BIOS update is interrupted whatever the reason can be.
Removing CMOS battery doesnt work like on desktps. Forget it!

TS4036 could not sign in server error when trying to restore iphone from icloud

I am trying to restore my iPhone from an iCloud backup. I deleted everything on the phone per restore instructions. Connected to wireless on iPhone. Logged on to my iCloud account. Told the iPhone to restore from iCloud backup. I keep getting ""could not sign in" server error OK. I get this messge over and over.

I actually noticed when I had this problem just now that my iPhone 4 wasn't on wif. Only connected to 3G even though I entered my network info and clicked connect. So I backed up a few steps and re selected to connect to wifi and it fixed my issue!

"System Update could not start properly" - New error just started (WinXP SP3)

I can no longer run System Update; it displays the splash screen, then a small window pops up with the above error message. I just ran it last a day or two ago, and it installed a few things; since then I have also run Microsoft Update and it also installed a few things, which I backed out one at a time (except for the malicious software removal updates)--all to no avail. Anyone else seen this, any suggestions?
Thanks,
Jonathan
--T61 (6460-8VU) - WinXP SP3, all the latest patches (except for KB961260, which is still backed out); .NETFramework 3.5 SP1

Hello,
I have reinstalled the system update after I did clean and download the last version from Lenovo website but still have the same pop up message says: Syystem Update could not start properly.
what's wrong??????

Could not access network location %APPDATA%\ when attempting to install update

Received error message "Could not access network location %APPDATA%\ " when attempting to update itunes and safari on my pc running windows 7 premium home addition. Everything had been working fine. Needed to update becuase Itunes no longer recognized itouch.

With that particular variety of 1606 (it's a 1606 error message even though the 1606 error message number isn't returned by the iTunes installer), the following Microsoft document is worth a try:
You receive an "Error 1606" error message when you try to install or remove a Microsoft program

"Could not find a match" error when passing parameter prefixed with "std::"

We're moving from Solaris 8 to Solaris 10, and I'm compiling our C/C++ applications using the Sun Studio 8 C++ compiler to verify that they'll still run correctly under Solaris 10.
All is well except for an error I'm getting on my Solaris 10 system but not on my Solaris 8 system.
Specifically, this line of code compiles correctly on both systems:
    if ( std::find_if(ident.begin(), ident.end(), is_not_alnum) != ident.end() )
        throw invalid_ident(caption, ident, code);but this line produces an error on Solaris 10 (but not on a Solaris 8 server):
    if ( std::find_if(ident.begin(), ident.end(), std::islower) != ident.end() )
        throw invalid_ident(caption, ident, code);The error returned is:
"auth_validate.C", line 140: Error: Could not find a match for std::find_if<std::InputIterator,
std::Predicate>(const char*, const char*, extern "C" int(int)).Clearly the "std::" prefix is involved... but why would this code compile successfully under Solaris 8 but fail under Solaris 10?
I've eliminated the usual suspects: the compiler is the same (including the include files) on both servers; there are no differences in the makefiles; there are no differences in the source code; all the referenced include directories exist on the Solaris 10 server.
At this point I'm stumped. My guess is that there's some environmental variable somewhere in Solaris 10 that is telling the Sun Studio 8 compiler to behave in a particular way (which Solaris 8 isn't telling the compiler), but I can't guess where such a thing might be occurring or what it might look like.
I've tried changing the source code to simply delete the "std::" prefix, and that code then compiles correctly on both my Solaris 8 and Solaris 10 servers. However, I'd very much prefer not to have to change any source code -- if this is an environmental issue with Solaris 10 affecting how the Sun Studio 8 C++ compiler behaves, I'd like to know about that.
If anyone can shed some light on this problem, or even propose additional tests I might try, I'd appreciate it!

clamage45, thanks very much for the response.
I'm looking into putting together a small example app. Meanwhile, I took your suggestion to check the patch levels of the two compiler instances and lo! there is a discrepancy.
The compiler installed on our Solaris 8 server reports itself from a CC -V command as "CC: Sun C++ 5.5 Patch 113817-19 2006/10/13", while the version on the Solaris 10 server reports as "CC: Sun C++ 5.5 2003/03/12". So although my eyeball comparison of the compiler's include files and libraries (including file sizes and timestamps) showed no differences, that was just a spot check; it wasn't the more "official" check that you helpfully suggested.
I've asked our sysadmin to look into this. No guarantees, of course, but I would not be surprised if patching the compiler on our Solaris 10 system resolved the problem. (Assuming we can find a version of the most recent patch for the Sun Studio 8 C++ compiler that's valid for Solaris 10.)
Regarding Sun Studio 8, we're definitely aware that it's reached its expiration date. We already have plans to transition to a more up-to-date version (probably Sun Studio 12) at a later date -- all I'm doing currently is testing to verify that the current application compiles and runs properly on Solaris 10. If possible, I'd like to get that working independently of any potential code changes driven by a significant compiler version upgrade.
Thanks again, and I'll add a new comment with additional information if our patching doesn't help.

When trying to import photos from a memory card I get error "The following files were not imported because they could not be read.". When i first installed Lightroom i was able to import from the very same card because there are photos in my library. I

Someone please help...I am very annoyed with Lightroom as I have been trying to import photos with no success

This message means that you don't have permission to write to the destination folder or disk drive. This is an operating system issue that can be resolved by changing permissions. And you can get plenty of information on how to do that by doing a web search for "change disk permissions".

"Service 'Apple Mobile' (Apple Mobile Device) failed to start. Verify that you have sufficient privilages to start system services" error when trying to install newest Itunes program.

I am trying to install the newest Itunes program and get the following error.
Service 'Apple Mobile Device' (Apple Mobile Device) failed to start. Vertify that you have sufficient privileges to start system services.
I've tried several times including uninstalling itunes and restarting the process.
At one point I got an error 7 and downloaded and ran "dotNetFx40_Full-x86_64
Please help me.
Wendi

See Troubleshooting issues with iTunes for Windows updates.
tt2

Sun J2EE 1.4 Server domain could not start (org/apache/common/launcher/..)

I am having problem with starting Sun J2EE Server 1.4. I had no problem with starting and stopping the server until today. I was not able to figure out what the problem is. I have tried reinstallation but did not work either. I also have reinstalled my J2SDK, but did not fix the problem. I am using J2SDK1.4.2_03 on Windows 2003 Server. Before the problem occured, I was working on a simple JMS applcation and trying to connect to J2EE server from a standalone JMS client at different machine. I am not sure what really caused the problem, but uninstalling it and reinstalling it does not change anything.
Here is my error message when I do start-domain domain1 at asadmin mode:
asadmin> start-domain domain1
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
abnormal subprocess termination: Detailed Message:Error: org/apache/commons/launcher/LaunchFilter
CLI156 Could not start the domain domain1.
I have tried to start it by using startserv.bat at domain1 directory and also the desktop shortcut Start Default Domain. Nothing works. I'do apprecited it if you can share any ideas or suggestions regarding this issue.
Thank you in advance.

I made some changes to my enviroment variables and added jar files to the J2SDK <<J2SDK_HOME>>/jre/lib/ext folder in order to run the standalone JMS client.
Here is my classpath settings:
.;C:\Sun\AppServer\lib\j2ee.jar;
C:\Sun\AppServer\lib\appserv-admin.jar;
C:\Sun\AppServer\lib\appserv-rt.jar;
C:\Sun\AppServer\lib\appserv-rt.jar;
C:\Sun\AppServer\lib\appserv-ext.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imq.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imqadmin.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imqjmsra.jar;
C:\Sun\AppServer\lib\install\applications\jmsra\imqutil.jar;
C:\Sun\AppServer\imq\lib\fscontext.jar;C:\J2EE\tutorial\j2eetutorial14\examples\ejb\simplemessage\SimpleMSGAppClient.jar
I also have added appserv-rt.jar, appserv-rt.jar, appserv-ext.jar, imq.jar, imqadmin.jar, imqjmsra.jar, and imqutil.jar in the <<J2SDK_HOME>>/jre/lib/ext/ folder. I know they were redundant but just wanted to make sure. Can any of these be causing the problem?
Again, thank you and let me know if you need any other info.

ORA-12154 TNS could not resolve service name error

Hi
I'm having trouble connecting to database throug sql*plus.I'm able to connect through TOAD but getting 'ORA-12154 TNS could not resolve service name error' when trying to login through sql*plus using same credentials .
I tried running sqlplus through command prompt,but when i enter the user-name i'm getting ORA-12203:TNS:unable to connect to destination.
Can someone help me with this error.
Thanks.

It would probably give you an idea where to start looking. You need to make sure that you have the correct .ora files needed for establishing connections. I don't know if your service desk just does the installation but no setup or if they also do the setup configuration. You can also try doing the setup on your own to check. You can use net easy config.

Windows could not start the Cluster Service on Local computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.

Dear Technet,
Windows could not start the Cluster Service on Local computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.
My cluster suddenly went disappear. and tried to restart the cluster service. When trying to restart service this above mention error comes up.
even i tried to remove the cluster through power-shell still couldn't happen because of cluster service not running.
Help me please.. thank you.
Regards
Shamil

Hi,
Could you confirm which account when you start the cluster service? The Cluster service is a service that requires a domain user account.
The server cluster Setup program changes the local security policy for this account by granting a set of user rights to the account. Additionally, this account is made a member
of the local Administrators group.
If one or more of these user rights are missing, the Cluster service may stop immediately during startup or later, depending on when the Cluster service requires the particular
user right.
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

CLI156 Could not start domain domain1 error when J2ee is installed

Similar Messages

Maybe you are looking for