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
Similar Messages
-
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,
GiladSpecify 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. -
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
ShamilHi,
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. -
Could not start the Crystal Report Application Server service on local computer
Post Author: [email protected]
CA Forum: Deployment
Hi
I have a following problem.
I have installed Crystal report application server(RAS)(CE embeded 10) on Windows server 2003 enterprise x64 edition.
When i start it, i see an error:
Could not start the Crystal Report Application Server service on local computerError 1067: the process terminated unexpectedly
Sometimes, i can start it but it stops a few minutes later.
I have disabled DEP (data execution prevention).
Log:
Faulting application crystalras.exe, version 10.0.0.533, faulting module unknown, version 0.0.0.0, fault address 0x00000000.
Please help
Thanks for your helpThis error occurs after an initial install, when the Oracle suite is installed logged in as the user(who has admin rights on the machine). If this is the case,
1.Go to Services (Admin Tools > Services)
2.Double click the Oracle services( BI Server or Presentation or TNS Listener).
3.Go to Log On tab
4.If local system account is checked , un-check that option. Check "This Account" option
5.Give the user information for that machine(e.g domain\username)
6.Specify password associated with the user ( the username/pwd that is used to login to the machine)
7.Confirm pwd and click Apply.
8.re-start the service.
This is what i did , and it worked.
good luck and hopefully oracle addresses these issues , they become frustrating to use the product.
Thanks,
Ram -
SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host
HI,
I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
Error: An error occured while starting a cluster instance.
Oct 14, 2008 5:14:41 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
Please check if there is an appropriate running cluster instances
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
I am pasting the full LOG File details:-
Oct 14, 2008 6:32:00 PM Info: Starting cluster instance processes.
Oct 14, 2008 6:32:00 PM Error: An error occured while starting a cluster instance.
Oct 14, 2008 6:32:00 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
Oct 14, 2008 6:32:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 14, 2008 6:32:00 PM Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 14, 2008 6:32:04 PM Info: Starting to save the repository
Oct 14, 2008 6:32:05 PM Info: Finished saving the repository
Oct 14, 2008 6:32:07 PM Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
Oct 14, 2008 6:32:07 PM Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
Failed deployment of SDAs:
development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
Please, look at error logs above for more information!
I have checked the CONFIGTOOl and the properties seem to be OK.
I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
Pls suggest.
Regards,
Abhijeet
IHi George,
Thnx for your reply.
I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
Have checked the Visual admin,it is not in SAFE mode,it working normally.
Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
Kindly suggest what other steps I shud take.
Regards,
Abhijeet -
Today I installed Adobe Director 11.5. I received a couple of errors in the FLEXnet Licensing Service. It looks It could not start. I tried to download the Licence fix what I found on Google but that doesn't work, so I checked the 'Service' at service (windows).
It's status is empty. When I double click on the FLEXnet Licensing Service, clicked on start at the opened window and an error is coming:
Windows could not start the FLEXnet Licensing Service service on Local Computer
Error 1068: The dependency service or group failed to start.
I don't understand what it says with this message, only that it is impossible to start. However, that is not what I am trying of course, I want to start the FLEXnet Licensing Service, service.
Re-installing of the software, doesn't make any change. How can I start it so Director is also working?Hi Don1233,
Please consider seek help at the software vendor side.
For the services didn't start, follow the suggestions posted by Elton in the thread below:
https://social.technet.microsoft.com/Forums/en-US/e35da253-f0df-41d1-8df2-b73fa54742a0/windows-could-not-start-the-flexnet-licensing-service-service-on-local-computer-error-1068-the?forum=w7itproinstall
Best regards
Michael Shao
TechNet Community Support -
Wndows could not start the SQL Server (MSSQLSERVER) service on Local computer
I have 2 instance of SQL Server in same server. A is installed first and B next.
Somehow A cannot start at all when I try to start from Windows Services.
B can be started normally.
A worked normally week ago. There has been only one thing what I may have to server since that.
I have installed MondoDB. Currently MondoDB it is stopped.
windows could not start the SQL Server (MSSQLSERVER) service on Local computer
Error 31: A device attached to the system is not functioning.
Kenny_II don't see anything special in event logs.
Data file of both SQL Server instance are located on same C drive of same server.
Kenny_I
Hello Kenny,
The main issue is not related to SQL server .SQL is at receiving end its hardware or the cables ( not sure which one) are the one causing issue.
I serached
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/111da2ae-0a86-41a5-ba03-7d1c0cc91ea9/windows-error-code-31a-device-attached-to-the-system-is-not-functioning-properly?forum=wdk
http://www.chicagotech.net/netforums/viewtopic.php?f=1&t=6467
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Error in Fiori Launchpad "could not start the app due..."
Hello everyone,
I am having a previously unseen (well, at least for me) error which raises on a click on the tile "Track Purchase Orders" on the SAP Fiori Launchpad:
"Could not start the app due to an internal error" (see the screenshot attached)
I haven't found any help on this error on Google and SAP portals.
The other applications work fine. So did this one before the implementation of SAP_UI 740 SP09 (before that it was SAP_UI 740 SP08). We applied all the notes specified in this post http://scn.sap.com/docs/DOC-56967
Components needed for Track Purchase Orders are patched to their maximum levels (UIX01EAP 100 SP03 and SRA020 600 SP05). OData and UI5 services are activated.
Plus, this error doesn't appear in the Gateway error logs (transaction /iwfnd/error_log) so troubleshooting is difficult.
The issue is systematically reproducible and has been reproduced on several computers.
Thanks a lot if you have any insight about this issue!
Best regards,
GuillaumeThank you for replying.
I have inspected the element and clicked on the tile. The network tab is below:
The status seems OK.
The response for ResolveLink:
{"d":{"results":[{"__metadata":{"id":"http://<server>:<port>/sap/opu/odata/UI2/INTEROP/NavTargets('PurchaseOrder-track~68')","uri":"<server>:<port>/sap/opu/odata/UI2/INTEROP/NavTargets('PurchaseOrder-track~68')","type":"INTEROP.NavTarget"},"id":"PurchaseOrder-track~68","shellType":"FLP","postParameters":"","text":"Track Purchase Order","applicationData":"SAPUI5.Component=ui.s2p.mm.purord.tracking","applicationAlias":"TrackPurchaseOrder","applicationType":"URL","url":"/sap/bc/ui5_ui5/sap/mm_purord_tpo"}]}}
I'm surprised that gbapp_poapproval and sra001 OData services are called here (with an intriguing ";mo")... We have found these errors in our /iwfnd/error_log screen after the SAP_UI 740 SP09 patch. Seeing this, we have installed GBAPP002 600 SP6 and SRA001 600 SP4 and activated the OData services but have not tried to use the corresponding apps (meaning that we have not done any other app implementation tasks because we don't really intend to for the moment).
In case the two problems are related, these are the responses to these requests:
For gbapp_poapproval request
{"error":{"code":"GBAPP_APV_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB173F121613F0E1008000A87C135A","timestamp":"20140814124456.5404250","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"GBAPP_APV_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
For gbapp_prapproval request
{"error":{"code":"GBAPP_APV_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB0B1112160FA0E1008000A87C135A","timestamp":"20140814124456.4449070","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"GBAPP_APV_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
For sra001_pcapproval request
{"error":{"code":"SRA001_CMN_MSG/013","message":{"lang":"en","value":"Workflow Task Type is not passed as filter criteria"},"innererror":{"transactionid":"53EB0E4512161140E1008000A87C135A","timestamp":"20140814124456.3244590","Error_Resolution":{"SAP_Transaction":"Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"SRA001_CMN_MSG/013","message":"Workflow Task Type is not passed as filter criteria","propertyref":"","severity":"error"},{"code":"/IWBEP/CX_MGW_BUSI_EXCEPTION","message":"An exception was raised.","propertyref":"","severity":"error"}]}}}
Regards,
Guillaume -
Could not start the hyperion workspace-web application Error 1067
Hi,
I have installed hyperion from scratch in a distributed environment...everything was working fine.......i.e. shared services, workspace, essbase, sql server, and hfm. I was able to logon and navigate different options in the hyperion products...but essbase stopped working when I re-started all four servers ....?
(1) When I restarted all four servers and stopped and restarted all hyperion services as per giving sequence then everything works fine but essbase EAS console and workspace web console...i was getting error message " could not connect to administration server" whenever i try to connect EAS console to essbase then I went to services there I saw workspace agent and workspace web application service is down.
(2) as soon as I started those both services then my shared services automatically stopped but I was able to logon in Essbase console and workspace console but my shared services are down...
(3) as soon as I start shared service they started but my workspace agent and workspace web application automatically stopped...and when I try to start again workspace web application then I get this error "[ Could not start the hyperion workspace-web application services on local computer. Error 1067: the process terminated unexpectedly]"
I have been searching online and googling but have a hard luck to get some best solution for this...can some one help me or guide me to walk through with this issue...
Thank you very much in advance ...
Regards,
SafiI solved this issue...It was with Hyperion Services those were stop responding some how.....but I stopped each service and restarted then those started working again...
Regards,
Safi -
Using Windows 8.1 Pro on Toshiba Satellite i7 Laptop with 8Gb Ram
After upgrade from Windows 8 Pro to 8.1 Pro, the Offline Files/CSC service refuses to start and gives the error message:
"Windows could not start the offline files service on local computer. Error 3: The system cannot find the path specified"
Before the upgrade, offline files worked fine... how do I re-enable offline files?I had a similar issue - couldn't make any files available offline.
I found that the offline folder service would not start
This was because the CSC permission were totally screwed. I had to take ownership of each folder and file, one by one, then grant everyone full access.
then delete the full contents of the CSC folder
format the CSC database using the registry fix then reboot
in control panel, disable the offline files, reboot, then re-enable. and now its working :)
2hrs to resolve this, with grateful thanks to this thread and some others.
damn windows8 -
When trying to start the camera I get this message..Could not start the camera. Close other applications and try opening the camera again.
I have nothing else running other than the phone itself waiting for a call. I can not find anything on Blackberry support for this issue unless I am missing it.
When I first got the phone a couple of months ago it worked fine and I could send pictures, now it is stuck.
Thanks for any help.
CB
Solved!
Go to Solution.Some say that removing the battery cover and pushing down around the camera lens will solve this problem. Apparently, it's a hardware issue. If it keeps up, you will likely need a replacement device.
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you! -
"could not start the camera. Close other apps and try again"
It shows up saying could not start the camera. Close other apps and try again when i try to open the camera but no other apps are open.
how do i fix this?Hi.....i am new here and is not sure as yet how to start a new thread.
I have a bb curve 8310 and think i may ave caused my camera to stop working via uninstalling it....if that is possible.
wen i click on di camera it opens, makes shutter sound and flashes wen i click di trackball but after that it doesnt show di picture that it supposedlt took.
Before this happened i was foolin around with the hide a folder option in pictures and not sure what i did wrong.......my video is not clear either.....please can you help me .....in addition i do not get any of those messages that i see the other users saying that they got for example could not start camera....i am not getting anything like that. all dat i get is a white screen...... -
Could not start the oracle service on local computer
Could not start the oracle service on local computer, did not return an error blah, blah.
I am running Oracle 9i r2 Windows, and have choosen to start my instances manually. When i start them up I get the above error message. But if I am a little patient the services do start up and all is fine, so far as i can see anyway.
I am curious to know why does this error message arise.
Thanks in anticipation
FergusTo start the database in windows you have to start first the OracleService<SID> service.
These are the steps that you have to do at the command line:
NET START OracleService<SID>
SET ORACLE_SID=<database sid>
sqlplus /nolog
conn sys/password as sysdba
startupJoel Pérez
http://otn.oracle.com/experts -
RWD Server "could not start the autonomyIDOLServer"
Dear All
i have an RWD server. When i try to start services of AutonomyIDOLServer on application server. it gives error
Could not start the AutonomyIDOLServer services on Local Computer.
Error 2: The system cannot find the file specified
Can somebody help me to sort out this issue that what sort of file it is trying to search the services. how can i sort out this issue.
Thanks in advance.
Regards
Ravi Kant Arya
+9540990385Hello Ravi Kant,
The Uperform application contacts a search engine which searches an index to find documents. Rebuilding the index will find all new and existing documents. You can try the following to troubleshoot the search issue: ->
1. Stop AutonomyIDOLServer and AutonomyDISH Services on the SearchServer
2. Stop Vignette Collaboration and VignFileSystemFetch serices on the
Application Server
3. On the application server, open a command prompt.
4. Navigate to <InstallDirectory>\Vignette\Collaboration.
5. Run the command #bin\stoprmid.bat#
6. Restart the AutonomyDISH service (this should start AutonomyIDOLServe
r)
7. Open http://<searchservername>:9000/Action=GetStatus in Internet
Explorer
8. Confirm that the XML page displays (You may need to refresh the page
several times)
9. Restart the Vignette Collaboration service (this should start
VignFileSystemFetch).
10. Login to the uPerform Website using an Admin account.
11. Click Administration->Server Administration.
12. Click Global Settings.
13. Click Administration->Services->Search Services.
14. Click the Recreate Search Database button.
15. You should begin to see results when searching in 5-10 minutes.
Let me know how it goes.
Regards,
Rafa
Maybe you are looking for
-
How do you get your old back ups back
how do you get your old back ups back
-
Interference between mutliple SSLSocket
Hello, I wrote a client and a server applications using SSLSocket and Channels. A single communication from client to server is Ok but if a second connection is made by the same client, there is interference between both connection. The first input c
-
Pls. help, SQL script page problem
Hi, Im using the Hands On Oracle Database 10g Express Edition for Linux. Im in chap06 already p. 218. I just uploaded the SYSMGMT1 script. After that I Clicked the script's icon but I cannot see any SQL DDL commands inside. Nothing happened. It said
-
Object does not existis in applicant number
Hi, While ubdating the infotype 0024 to the applicant. i m getting the error object does not exists in applicant number. Pls let me know how to solve this issue. Thanks and Regards, Revathi.
-
Does the latest version of Numbers have anything like Excel's goal seek?
Does the latest version of Numbers have anything like Excel's goal seek? I frequently use goal seek to solve non-algebraic equasions for an unknown. Thanks.