Probelm with 2004s Java installation
I´ve downloaded Sneak Preview 2004s Java and when I try to go through the steps in the sapinstGUI, I get following messages in the prerequisites chck:
Operation System Version>Condition not met>Windows XP not supported!!
Only Windows Version 5.2 supported!
How could tjis be?Thats strange because in the sneak preview system requirements, Windows XP Professionall is
mentioned as supported?!
Has anyone any hints!
Hi
Receommended Operating System is: Windows 2000 (Service Pack 3); Windows XP Professional (Service Pack 1) or Windows Server 2003
If you are getting any error in xp sp2 , please ingnore it and continue installing.
It will work
Cheers
Jawahar Govindaraj
PS:Reward pts
Similar Messages
-
GP Tutorials don't work with 2004s Java Trial Version
Hi,
I know that the SAP Composite Application Framework - CAF Tutorial Center [original link is broken] [original link is broken] require the Callable Object types "Content Package" and "Interactive Form" which at least in my installation are not visible.
Is my installation corrupt? Or are the tutorial descriptions incorrect?
Thanks.
DickHi,
The problem was a role problem. Solution is noted in my GP Tutorials don't work with 2004s Java Trial Version
Thanks.
Dick -
Help Needed With A Java Installation
Hello,
I'm beyond being a novice with regards to Java. To be quite honest, I don't have the time right now to learn the language, nor do I have the need for anything other than what I am about to ask. I say this upfront to avoid unfriendly comments from people who may criticize my "laziness", NOT to sound disrespectful to those who post or answer questions in this forum.
With that said, here's my question...
I have a Sun/Cobalt RaQ4i server. I'd like to run a few free license Java games that I found on a website. The problem is, RaQ appliances do not ship with Java installed. I've been looking for some way to get it on my server for a few days now, with little luck. I've searched the Java help forums, the Sun/Cobalt forums and a few other help sites such as www.raqzone.com. (...which is why laziness is in quotes up there.) I did find this page... "http://developer.cobalt.com/java/java.raq.php". I have now installed both, the package and the update, on the server. However, the applet still does not run. I don't need the JSP feature, as my site is done in ASP. I don't know what a servlet is, but thought it might be similar to an applet, and would do the trick. *?* Apparently, I was wrong. Can ANYONE tell me what I need to do to get the desired results when I try to run a Java applet on my Cobalt RaQ?? I'd also be willing to be a fee to have it installed... correctly, of course! :)
Thanks in advance for any directions or guidance,
-Daniel
[email protected]Assuming you're running Solaris, you can download the Java Runtime Environment (JRE) from http://java.sun.com/
One of the provided programs is appletviewer, which you will be able to use to run applets if they are on your local machine. I'm not entirely sure about Solaris, but the JRE may also install the Java Plugin to your browser so you can view applets in the browser.
Apologies if this was already mentioned in the link you provided - registration/login is required, so I didn't read it.
I hope you have more luck with your applets,
-Troy -
SAP NetWeaver 2004s Java Trial Version Installation error
Dear Techies,
I tried to install the trial version (SAP NetWeaver 2004s Java Trial Version
) downloaded from SDN, but I am getting an error immediately after started the installation. The log as given below.
Please suggest me where I can delete this special character mentioned in the log file ? The full log also is given below
INFO 2007-04-13 21:55:17
Execute step collect of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0.
ERROR 2007-04-13 21:55:17 [syxxcpath.cpp:58]
CSyPath::CSyPath("C:\SAP\MS2\SYS\profile\START_JC00_MythiliKannan")
FSL-02107 Path component contains reserved character ('"'): "C:
ERROR 2007-04-13 21:55:17 [syxxcpath.cpp:519]
CSyPath::CSyPath("C:\SAP\MS2\SYS\profile\START_JC00_MythiliKannan")
FSL-02106 Path contains reserved character ('"'): "C:\SAP\MS2\SYS\profile\START_JC00_MythiliKannan"
Thanks and best regards,
Shiju
Full log :
SAPinst is getting started.
Please be patient ...
starting gui server process:
sapinstport: 21200
guiport : 21212
guistart : true
command : "C:\Program Files\Java\j2re1.4.2_09/bin\javaw.exe" -cp "C:/DOCUME1/MYTHIL1/LOCALS1/Temp/sapinst_exe.2644.1176481451\jar\instgui.jar;C:/DOCUME1/MYTHIL1/LOCALS1/Temp/sapinst_exe.2644.1176481451\jar\inqmyxml.jar" -Xmx256M -Dsun.java2d.noddraw=true SDTServer config=jar:sdtserver.xml guiport=21212 sapinsthost=localhost sapinstport=21200 guistart=true
load resource pool C:\Netweaver_FullKit\SAPNW2004sJavaSP9_Trial\SAPNW2004sJavaSP9_Trial\SAP_NetWeaver_2004s_SR_1_Installation_Master_DVD__ID__NW05SR1_IM1\IM_WINDOWS_I386\resourcepool.xml
guiengine: no GUI connected; waiting for a connection on host MythiliKannan, port 21200 to continue with the installation
guiengine: login in process.
IRunModeReceiver CChoiceDialogModifier::continuePreviousRun()
INFO 2007-04-13 21:55:09 [synxcfile.cpp:493]
CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/inifile.2.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
Copied file 'C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/inifile.xml' to 'C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/inifile.2.xml'.
INFO 2007-04-13 21:55:09 [synxcfile.cpp:493]
CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/inifile.3.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
Copied file 'C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/inifile.xml' to 'C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/inifile.3.xml'.
INFO 2007-04-13 21:55:09
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2007-04-13 21:55:16 [synxcfile.cpp:493]
CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/keydb.2.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const
Copied file 'C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/keydb.xml' to 'C:/Program Files/sapinst_instdir/NW04S/SNEAK_PREVIEW/FULL/INSTALL/keydb.2.xml'.
INFO 2007-04-13 21:55:16
Execute step setNWOption of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|0|0.
INFO 2007-04-13 21:55:17
Execute step collect of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0.
ERROR 2007-04-13 21:55:17 [syxxcpath.cpp:58]
CSyPath::CSyPath("C:\SAP\MS2\SYS\profile\START_JC00_MythiliKannan")
FSL-02107 Path component contains reserved character ('"'): "C:
ERROR 2007-04-13 21:55:17 [syxxcpath.cpp:519]
CSyPath::CSyPath("C:\SAP\MS2\SYS\profile\START_JC00_MythiliKannan")
FSL-02106 Path contains reserved character ('"'): "C:\SAP\MS2\SYS\profile\START_JC00_MythiliKannan"
ERROR 2007-04-13 21:55:17
CJSlibModule::writeError_impl()
MUT-03025 Caught ESyException in Modulecall: Bad path component: "C:.
ERROR 2007-04-13 21:55:17
FCO-00011 The step collect with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|collect was executed with status ERROR .
INFO 2007-04-13 22:00:30 [iaxxgenimp.cpp:787]
showDialog()
An error occured and the user decide to stop.\n Current step "|NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|collect".
Exit status of child: 1Hi,
I changed the system name but still I am getting the same error. Previously there was an SAP system was installed in my pc later I uninstalled that, but still there are two SAPsid_00 and SAPsid_01 (where in sid is MS) is running. I think this is the problem. I disabled the services as well but still I am getting the same error during the installation. How to delete the windows services ? and how to do a clean up for registry ?. I feel if I do theses two then I can install.
Thans a lot for your helps and support.
Shiju -
SAP NetWeaver 2004s Java Trial Version installation problem
I am trying to install SAP NetWeaver 2004s Java Trial Version in my windows xp machine.
I have the following error.
Nothing is written in to my E:\usr\sap folder which I have share as saploc and sapmnt.
I read the forum threads on this.
I still do not know how to do this.
Please help
vijay
INFO 2006-12-17 21:23:58
Execute step getSID of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0.
ERROR 2006-12-17 21:24:01
FJS-00003 TypeError: dir_profile has no properties (in script NW_Java_OneHost|ind|ind|ind|ind, line 39640: ???)
ERROR 2006-12-17 21:24:01
MUT-03025 Caught ESAPinstException in Modulecall: executing JS script failed.
ERROR 2006-12-17 21:24:01
FCO-00011 The step getSID with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|getSID was executed with status ERROR .Rajat,
Sorry for the delay. I was on vacation.
Which environment variable are you referring to?
JAVA_HOME is set to C:\j2sdk1.4.2_09.
I am using j2sdk1.4.2_09.
Only port changes I tried was
#sapdp01 3201/tcp.
I tried with and without the # .
Both had the same results.
I have given below the last few statememts from the sapinst log file
Any help to solve my problem will be greatly appreciated.
Thanks.
Vijay
INFO 2007-01-02 16:13:25
Execution of the command "C:\j2sdk1.4.2_09\bin\java.exe -classpath C:/DOCUME1/VIJAYV1/LOCALS1/Temp/sapinst_exe.5432.1167783061/JAR/ins-j2ee.jar com.sap.ins.j2ee.GetSystemProperty" finished with return code 0. Output: ##Tue Jan 02 16:13:25 PST 2007java.runtime.name=Java(TM) 2 Runtime Environment, Standard Editionsun.boot.library.path=C\:
j2sdk1.4.2_09
jre
binjava.vm.version=1.4.2_09-b05java.vm.vendor=Sun Microsystems Inc.java.vendor.url=http\://java.sun.com/path.separator=;java.vm.name=Java HotSpot(TM) Client VMfile.encoding.pkg=sun.iouser.country=USsun.os.patch.level=Service Pack 2java.vm.specification.name=Java Virtual Machine Specificationuser.dir=C\:
Program Files
sapinst_instdir
NW04S
SNEAK_PREVIEW
FULL
INSTALLjava.runtime.version=1.4.2_09-b05java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironmentjava.endorsed.dirs=C\:
j2sdk1.4.2_09
jre
lib
endorsedos.arch=x86java.io.tmpdir=C\:
DOCUME1
VIJAYV1
LOCALS1
Temp
line.separator=\r\njava.vm.specification.vendor=Sun Microsystems Inc.user.variant=os.name=Windows XPsun.java2d.fontpath=java.library.path=C\:
j2sdk1.4.2_09
bin;.;C\:
WINDOWS
system32;C\:
WINDOWS;e\:
sapdb
programs
bin;e\:
sapdb
programs
pgm;C\:
MCC18
mpasm;C\:
MCC18
bin;C\:
MCC18
mpasm;C\:
MCC18
bin;C\:
MCC18
mpasm;C\:
MCC18
bin;f\:
oracle
product
10gDSHome
jdk
jre
bin
classic;f\:
oracle
product
10gDSHome
jdk
jre
bin;f\:
oracle
product
10gDSHome
jdk
jre
bin
client;f\:
oracle
product
10gDSHome
jlib;f\:
oracle
product
10gDSHome
bin;f\:
oracle
product
10gDSHome
jre
1.1.8
bin;f\:
oracle
product
10.1.0
Db_1
bin;f\:
oracle
product
10.1.0
Db_1
jre
1.4.2
bin
client;f\:
oracle
product
10.1.0
Db_1
jre
1.4.2
bin;C\:
WINDOWS
system32;C\:
WINDOWS;C\:
WINDOWS
System32
Wbem;C\:
Program Files
Microsoft SQL Server
80
Tools
BINN;C\:
Program Files
Microsoft SQL Server
80
Tools
Binn
;C\:
WINDOWS
Microsoft.NET
Framework
v1.1.4322;F\:
maven
Maven 1.0
bin;C\:
Program Files
QuickTime
QTSystem
;C\:
MCC18
mpasm;C\:
MCC18
bin;C\:
MCC18
mpasm;C\:
MCC18
bin;C\:
MCC18
mpasm;C\:
MCC18
bin;java.specification.name=Java Platform API Specificationjava.class.version=48.0java.util.prefs.PreferencesFactory=java.util.prefs.WindowsPreferencesFactoryos.version=5.1user.home=C\:
Documents and Settings
vijay vijayakumaruser.timezone=America/Los_Angelesjava.awt.printerjob=sun.awt.windows.WPrinterJobfile.encoding=Cp1252java.specification.version=1.4java.class.path=C\:/DOCUME1/VIJAYV1/LOCALS~1/Temp/sapinst_exe.5432.1167783061/JAR/ins-j2ee.jaruser.name=vijay vijayakumarjava.vm.specification.version=1.0java.home=C\:
j2sdk1.4.2_09
jresun.arch.data.model=32user.language=enjava.specification.vendor=Sun Microsystems Inc.awt.toolkit=sun.awt.windows.WToolkitjava.vm.info=mixed modejava.version=1.4.2_09java.ext.dirs=C\:
j2sdk1.4.2_09
jre
lib
extsun.boot.class.path=C\:
j2sdk1.4.2_09
jre
lib
rt.jar;C\:
j2sdk1.4.2_09
jre
lib
i18n.jar;C\:
j2sdk1.4.2_09
jre
lib
sunrsasign.jar;C\:
j2sdk1.4.2_09
jre
lib
jsse.jar;C\:
j2sdk1.4.2_09
jre
lib
jce.jar;C\:
j2sdk1.4.2_09
jre
lib
charsets.jar;C\:
j2sdk1.4.2_09
jre
classesjava.vendor=Sun Microsystems Inc.file.separator=
java.vendor.url.bug=http\://java.sun.com/cgi-bin/bugreport.cgisun.io.unicode.encoding=UnicodeLittlesun.cpu.endian=littlesun.cpu.isalist=pentium i486 i386
INFO 2007-01-02 16:13:25
Execute step setNWOption of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|0|0.
INFO 2007-01-02 16:13:26
Execute step collect of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0.
ERROR 2007-01-02 16:13:28
FJS-00003 TypeError: this._name has no properties (in script NW_Java_OneHost|ind|ind|ind|ind, line 8987: ???)
ERROR 2007-01-02 16:13:29
FCO-00011 The step collect with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|collect was executed with status ERROR . -
SAP ECC 6.0 EHP4 installation with ABAP+JAVA stack
Hi,
I need to install SAP ECC6.0 EHP4 with ABAP+JAVA stack on windiws server 2008 with oracle.
I have read that for this, we need to install ECC 6.0 EHP4 ready and then upgrade to EHP4 using ehpi installer.
I have found the documents seperately for ABAP and JAVA stack and not for ABAP+JAVA.
I need clarifications on these.
1.Do we need to install ABAP and JAVA instances seperately with EHP4 and then upgrade(In that case I have to install both instances on single host)?
2.Should we give seperate <SID> for both instances and create seperate databases?
3.Hard disk requirement for this set up.(We have 150 GB including C drive)
4.Steps to perform after installing ECC6.0 EHP4 ready
5.Please send me the doc. if anyone has
Anyhelp would be highly appreciated.
Regards,
Surya> 1.In the installation document for EHP4 ready for SAP ERP 6.0 ABAP.It is mentioned that this installation contains only basic EHP4 for ERP 6.0 and we need to install additional EHP4 functionality in the SAP ERP 6.0 -EHP4 ready system.
> It states that atleast Support pacakge stack (SPS) 1 of SHP4 needs to be installed.So If I install this stack using EHPi installer in the post installation activities my SAP ERP 6.0 EHP4 will be in place?Please confirm.
Yes..
>
> 2.Can I install SAP SR3 with dual stack and upgaradte it directly to EHP4 at a time?
Yes you can do it.....as SAP still supports dual stack ERP systems to EHP4
>
> Any solutions or suggestions from others also welcome.
Why do u want a dual stack ECC ystem?? any specific requirement???
Regards,
Nirmal.K
Edited by: nirmal konchada on Feb 2, 2011 12:16 PM -
Installation failed NW2004s with SP9 (Java Trail Version) failed
Hi All,
I am trying to install NW2004s with SP9 (Java Trail Version) , that's failing Phase 14 of 32 in CreateDatabaseInstance failing.
<b>This is the log :
</b>
ERROR 2007-05-19 19:43:40
The dbmcli call for action PARAM_INIT_INST failed. Check the logfile XCMDOUT.LOG.
ERROR 2007-05-19 19:43:53
The dbmcli call for action PARAM_INIT_INST failed. Check the logfile XCMDOUT.LOG.
ERROR 2007-05-19 19:43:53
FCO-00011 The step sdb_init_instance_type with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_init_instance_type was executed with status ERROR .
Please suggest what is going wrong.
Thanks in advance.
AWI got the same error, this is from my XCMDOUT.LOG
> Subprocess starts at 20070528020028
Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n microdot-c01534 -d J2E -u CONTROL,******** db_start
Execute Session Command : exit
> Subprocess stops at 20070528020029
> Subprocess call failed
ERR
-24961,ERR_STATE: cannot determine current db state -
Can't execute web app from NetBeans 3.6 with Sun Java App Server 8
Hi there,
I'm tyring to execute a java web application called myfirstjsp.
In directory ...\myfirstsjp I've got:
- index.jsp
- WEB-INF dir
- META-INF dir.
I can run myfirstjsp from NetBeans if I choose the Netbeans default server, Tomcat 5.0.19 (this web server is configured to port 8084).
However, when I try to execute myfirstjsp from NetBeans with Sun Java System Application Server 8(configured to port 8080), it gives me an annoying message:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I checked port conflicts but none found.
The other two options don't give me a place to start (I don't know what to do with domain.xml)
I'm working with:
- Windows XP Pro
- J2SE 1.4.2_04 (installed in C:\Program Files\j2sdk1.4.2_04)
- Sun Java Application Server 8 (installed in C:\Program Files\Sun\AppServer)
- Netbeans 3.6 + Sun Java System Application Server Plugin (installed in C:\Program Files\NetBeans3.6).
My PC has the following environment variables:
PATH(in user MGoncalv)=C:\Program Files\Sun\AppServer\bin;,?ut
PATH(system variable)=C:\Program Files\j2sdk1.4.2_04\bin;D:\ProgramFiles\OraReportNT\bin;C:\OraHome92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Personal Communications\;C:\Program Files\IBM\Trace Facility\;%SystemRoot%\system32\nls;%SystemRoot%\system32\nls\ENGLISH
CLASSPATH(system variable)=.;C:\OraHome92\jdbc\lib\ojdbc14.jar
By looking at the Sun App Server log file, I discovered that the log outputs of
- Start Default Server (a link in the folder created by the installation of Sun App Server)
- and trying to execute myfirstjsp from NetBeans through Sun App Server
are very similar.
Below is a piece of server.log when I tried to execute myfirstjsp from NetBeans through Sun App Server. Please, pay attention to the EJBC error:
Starting Sun Java System Application Server Platform Edition 8.0 (build b57-fcs) ...
[#|2004-05-19T17:20:05.198+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-05-19T17:20:08.713+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-05-19T17:20:09.384+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-05-19T17:20:14.752+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-05-19T17:20:14.772+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-05-19T17:20:14.792+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-05-19T17:20:20.200+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-05-19T17:20:23.645+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-05-19T17:20:24.336+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-05-19T17:20:26.098+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-05-19T17:20:27.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-05-19T17:20:27.921+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-05-19T17:20:27.931+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-05-19T17:20:30.004+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-05-19T17:20:33.459+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are: |#]
[#|2004-05-19T17:20:33.479+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.stream.err|_ThreadID=10;|Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
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:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.JavaCompiler.javacCompile(JavaCompiler.java:139)
at com.sun.ejb.codegen.JavaCompiler.internal_compile(JavaCompiler.java:60)
at com.sun.ejb.codegen.Compiler.compile(Compiler.java:57)
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:293)
... 45 more
|#]
[#|2004-05-19T17:20:33.739+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Deployment Error
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
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:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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-05-19T17:20:33.739+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5187 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
[#|2004-05-19T17:20:33.759+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.deployment|_ThreadID=10;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
at com.sun.ejb.codegen.IASEJBC.compileClasses(IASEJBC.java:301)
at com.sun.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:230)
at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:617)
at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:565)
at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:360)
at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:208)
at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:292)
at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:173)
at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:105)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:124)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
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:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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-05-19T17:20:33.789+0100|SEVERE|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|Exception while deploying : Fatal Error from EJB Compiler -- Compilation failed: Native compiler returned an error: 2
Error messages are:
.|#]
[#|2004-05-19T17:20:33.799+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Program Files\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-05-19T17:20:33.879+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-05-19T17:20:34.811+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-05-19T17:20:35.111+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-05-19T17:20:35.121+0100|WARNING|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-05-19T17:20:35.161+0100|INFO|sun-appserver-pe8.0|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-05-19T17:20:35.181+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-05-19T17:20:35.201+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-05-19T17:20:35.412+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-05-19T17:20:37.945+0100|INFO|sun-appserver-pe8.0|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-05-19T17:20:38.456+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.556+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-05-19T17:20:38.847+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.887+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-05-19T17:20:38.987+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.007+0100|INFO|sun-appserver-pe8.0|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-05-19T17:20:39.558+0100|INFO|sun-appserver-pe8.0|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\Sun\AppServer\imq\bin].|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1084983639568|#]
[#|2004-05-19T17:20:39.568+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-05-19T17:20:39.588+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-05-19T17:20:44.475+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[com.sun.enterprise.admin.event.ConfigChangeEvent -- server [1 Change(s), Id:1, ts:1084983644465]]|#]
[#|2004-05-19T17:20:44.545+0100|INFO|sun-appserver-pe8.0|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1046:A change notification was not handled sucessfully, the server will need a restart for the change to be effective.|#]
Is this EJB compilation error normal ? if not what does it mean ? Sun Java App Server installation isn't OK ?
I tried to look into the Sun App Server Troubleshooting, searched forums... but couldn't squeeze any valuable info from any of them.
If you have any sugestion regarding this problem, or you know some web site that addresses it please tell me !
Many thanks,
MiguelI seem to have the same problem, I cant run sun application server 8.1. The server is in c:\sun\appserver\, I am using netbeans 4.1. I recieve the same comment above:
The Sun Java System Application Server 8 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
I cant see any port conflict, the server is set to port 4848. I dont know about any configurations.
This is the Exception:
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.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/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:45:43.930+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:45:43.940+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:45:43.940+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:45:43.950+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:45:43.960+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:53.507+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:47:53.517+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.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/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:47:57.533+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:47:57.543+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:47:57.543+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:47:57.563+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:47:58.224+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
[#|2005-11-02T11:49:01.705+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:49:01.715+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/jre/lib/ext;C:/Sun/AppServer/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Sun/AppServer/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Sun/AppServer/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0_04\jre\bin\client;C:\Sun\AppServer\lib;C:\Sun\AppServer\lib;C:\Program Files\Java\jdk1.5.0_04\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\lib;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\Sun\AppServer\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Rational\ClearQuest;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0_04/lib/tools.jar;C:/Sun/AppServer/lib/appserv-rt.jar;C:/Sun/AppServer/lib\admin-cli.jar;C:/Sun/AppServer/lib\appserv-admin.jar;C:/Sun/AppServer/lib\dom.jar;C:/Sun/AppServer/lib\jmxremote.jar;C:/Sun/AppServer/lib\jmxremote_optional.jar;C:/Sun/AppServer/lib\jsf-api.jar;C:/Sun/AppServer/lib\jsf-impl.jar;C:/Sun/AppServer/lib\rmissl.jar;C:/Sun/AppServer/lib\xalan.jar;C:/Sun/AppServer/lib\xercesImpl.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ja.jar;C:/Sun/AppServer/lib\appserv-cmp_ja.jar;C:/Sun/AppServer/lib\appserv-rt_ja.jar;C:/Sun/AppServer/lib\commons-launcher_ja.jar;C:/Sun/AppServer/lib\deployhelp_ja.jar;C:/Sun/AppServer/lib\j2ee_ja.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh.jar;C:/Sun/AppServer/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/AppServer/lib\appserv-cmp_zh.jar;C:/Sun/AppServer/lib\appserv-cmp_zh_CN.jar;C:/Sun/AppServer/lib\appserv-rt_zh.jar;C:/Sun/AppServer/lib\appserv-rt_zh_CN.jar;C:/Sun/AppServer/lib\commons-launcher_zh.jar;C:/Sun/AppServer/lib\commons-launcher_zh_CN.jar;C:/Sun/AppServer/lib\deployhelp_zh.jar;C:/Sun/AppServer/lib\deployhelp_zh_CN.jar;C:/Sun/AppServer/lib\j2ee_zh.jar;C:/Sun/AppServer/lib\j2ee_zh_CN.jar;C:/Sun/AppServer/lib\appserv-assemblytool_ko.jar;C:/Sun/AppServer/lib\appserv-cmp_ko.jar;C:/Sun/AppServer/lib\appserv-rt_ko.jar;C:/Sun/AppServer/lib\commons-launcher_ko.jar;C:/Sun/AppServer/lib\deployhelp_ko.jar;C:/Sun/AppServer/lib\j2ee_ko.jar;C:/Sun/AppServer/lib\appserv-assemblytool_fr.jar;C:/Sun/AppServer/lib\appserv-cmp_fr.jar;C:/Sun/AppServer/lib\appserv-rt_fr.jar;C:/Sun/AppServer/lib\commons-launcher_fr.jar;C:/Sun/AppServer/lib\deployhelp_fr.jar;C:/Sun/AppServer/lib\j2ee_fr.jar;C:/Sun/AppServer/lib\appserv-assemblytool_es.jar;C:/Sun/AppServer/lib\appserv-cmp_es.jar;C:/Sun/AppServer/lib\appserv-rt_es.jar;C:/Sun/AppServer/lib\commons-launcher_es.jar;C:/Sun/AppServer/lib\deployhelp_es.jar;C:/Sun/AppServer/lib\j2ee_es.jar;C:/Sun/AppServer/lib\appserv-upgrade.jar;C:/Sun/AppServer/lib\appserv-ext.jar;C:/Sun/AppServer/lib\j2ee.jar;C:/Sun/AppServer/lib\activation.jar;C:/Sun/AppServer/lib\appserv-cmp.jar;C:/Sun/AppServer/lib\appserv-jstl.jar;C:/Sun/AppServer/lib\commons-launcher.jar;C:/Sun/AppServer/lib\commons-logging.jar;C:/Sun/AppServer/lib\j2ee-svc.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/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer/imq/lib/jaxm-api.jar;C:/Sun/AppServer/imq/lib/fscontext.jar;C:/Sun/AppServer/lib/ant/lib/ant.jar;C:/Sun/AppServer/pointbase/lib/pbclient.jar;C:/Sun/AppServer/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5034: Could not start the JMS service broker process.|#]
[#|2005-11-02T11:49:05.671+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-11-02T11:49:05.681+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.resource.jms|_ThreadID=10;|JMS5024: JMS service startup failed.|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:289)
at com.sun.enterprise.server.ss.ASLazyKernel.startLifecycle(ASLazyKernel.java:188)
at com.sun.enterprise.server.ss.ASLazyKernel.startMQ(ASLazyKernel.java:163)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:52)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.appserv.server.ServerLifecycleException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:276)
... 5 more
Caused by: java.io.IOException: CreateProcess: C:\Sun\AppServer\imq\bin\imqbrokersvc.exe -javahome "C:/Program Files/Java/jdk1.5.0_04" -varhome C:/Sun/AppServer/domains/domain1\imq -name imqbroker -console -port 7676 -bgnd -silent error=3
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:464)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.startProvider(JMSAdminImpl.java:769)
at com.sun.enterprise.jms.JmsProviderLifecycle.onInitialization(JmsProviderLifecycle.java:269)
... 5 more
|#]
[#|2005-11-02T11:49:05.691+0300|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
java.lang.NullPointerException
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:389)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
[#|2005-11-02T11:49:06.432+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
[#|2005-11-02T11:50:38.915+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-11-02T11:50:38.925+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0_04\bin\java
-client
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9009
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer/domains/domain1/logs/server.log
-Dcom.sun.aas.jdwpOptions=transport=dt_socket,server=y,suspend=n,address=9009
-Djava.endorsed.dirs=C:/Sun/AppServer/lib/endorsed
-Djava.security.policy=C:/Sun/AppServer/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Sun/AppServer/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Sun/AppServer/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Sun/AppServer/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_04/ -
SAP NetWeaver 2004s Java Trial Version on Windows Vista
Hello everyone,
I have been trying to install SAP NetWeaver 2004s Java Trial Version for three days now on Windows Vista Ultimate. Since Microsoft has a new security infrastructure implemented in Windows Vista, it is not that easy to install SAP NetWeaver 2004s Java Trial Version. Windows Vista has some sort of User-account security. In summary, in Windows Vista, you are logged in as an administrator, but when it comes to change system files or do registry entries, you or respectivly third party programs (e.g. SAP NetWeaver 2004s Java Trial Version installer) has no rights to do things like registry entries. There is a possibility to rightclick on the setup.bat file and start it in administrative mode, but that doesn't change a thing.
I hope you guys get my problem.
This is the error log:
WARNING 2007-01-28 21:09:35
Error 5 (acces denied
) in execution of a 'RegOpenKeyEx' function, line (69), with parameter (SYSTEM\CurrentControlSet\Services\DPS).
WARNING 2007-01-28 21:09:35
The Subkey 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DPS' does not exist on the 'localhost' host.
ERROR 2007-01-28 21:09:35
MOS-01185 The subkey 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DPS' does not exist on the 'localhost' host.
ERROR 2007-01-28 21:09:35
FCO-00011 The step collect with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|collect was executed with status ERROR .
Please help!
yours
erikWindows Vista isn't on the support matrix of SAP Netweaver 2004s!
you may play arround with regedit and chaning the security settings of SYSTEM\CurrentControlSet\Services\DPS key. SAPinst is doing a KEY_ALL_ACCESS when enumerating the services registry.
Starting with Vista some registry values have special protection which do not allow administrators to open them with KEY_ALL_ACCESS.
peter -
EP6,SP3 WAS640 Java Installation in a distributed environment....
Hi Freinds,
While installing WAS Java 640 instance in a distributed environment (with oracle 9.2 DB instance in separate host & WAS640 on another), the installation setup stops at the last step (i.e. during registration of SDM of SCS/CI installation). Kindly suggest, what cud be the problem?
The details of errors are as mentioned below:
ERROR 2004-10-09 15:04:05
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\WEBAS_640_J2EE_ONLY\DS\CI\callSdmViaSapinst.log.
The details of CallsdmViaSAPinst.log is as follows:
Oct 9, 2004 2:13:26 PM Info:
Oct 9, 2004 2:13:26 PM Info: ============================================
Oct 9, 2004 2:13:26 PM Info: = Starting to execute command 'deploy' =
Oct 9, 2004 2:13:26 PM Info: ============================================
Oct 9, 2004 2:13:26 PM Info: Starting SDM - Software Deployment Manager...
Oct 9, 2004 2:13:32 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3003.00.0000.20031126161800.0000
Oct 9, 2004 2:13:33 PM Info: SDM operation mode successfully set to: Standalone
Oct 9, 2004 2:13:35 PM Info: Initializing Network Manager (50317)
Oct 9, 2004 2:13:35 PM Info: Checking if another SDM is running on port 50318
Oct 9, 2004 2:13:35 PM Info: -
Starting deployment -
Oct 9, 2004 2:13:35 PM Info: Loading selected archives...
Oct 9, 2004 2:13:36 PM Info: Loading archive 'I:\CD\51030277_WAS640SP3_Installation\J2EE1\J2EE-ENG\JDD\SYNCLOG.SDA'
Oct 9, 2004 2:13:36 PM Info: Selected archives successfully loaded.
Oct 9, 2004 2:13:36 PM Info: Error handling strategy: OnErrorStop
Oct 9, 2004 2:13:36 PM Info: Update strategy: UpdateLowerVersions
Oct 9, 2004 2:13:36 PM Info: Starting to execute deployment action (deploy) for "synclog".
Oct 9, 2004 2:13:44 PM Info: Creating connections to database "EPQ".
Oct 9, 2004 2:13:55 PM Info: Creating vendor connection to database.
Oct 9, 2004 2:13:57 PM Error: Creation of vendor connection failed.
Original error message is:
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
Stack trace of original Exception or Error is:
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3695)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:352)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:362)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:536)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:328)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:472)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:253)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)
at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)
at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:58)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:84)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:61)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:78)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:88)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:74)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:121)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:90)
at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:162)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:54)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:52)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Oct 9, 2004 2:13:57 PM Error: Execution of deployment action for "synclog" aborted:
Db connect failed.
Oct 9, 2004 2:13:57 PM Error: Deployment NOT successful for synclog
Oct 9, 2004 2:13:57 PM Error: -
At least one of the Deployments failed -
Oct 9, 2004 2:13:57 PM Info: Summarizing the deployment results:
Oct 9, 2004 2:13:57 PM Error: Aborted: I:\CD\51030277_WAS640SP3_Installation\J2EE1\J2EE-ENG\JDD\SYNCLOG.SDA
Oct 9, 2004 2:13:57 PM Error: Processing error. Return code: 4Hi Rajenda,
I'm really stucked in distributed Java installation.
Can you help me? I'd like to ask you some questions.
My email address is: [email protected]
Regards,
Tibor
ps.: I'm using my friend account in SAP SDN (Nándor) -
Download SAP NetWeaver 2004 Java Trial Version for Windows
Hi there,
I'm currently working on a project where I need to develop with EP 6.0. For testing my development I wanted to download the SAP NetWeaver 2004 Java Trial Version from
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d058ab2c-e206-2a10-47b7-c05df8a3ae76]
But the files doesn't seem to exist on the server anymore. Has anyone an idea where to find these download files?
Thanks,
David.Hi Parsman,
You only need SAPGui to logon to ABAP instance...
If you installed a Java Instance.. you need to logon using your browser... URL is in the manual.
For the J2EE engine page,
http://<hostname_with_fqdn>:500<instance_number>
If there a portal installed,
http://<hostname_with_fqdn>:500<instance_number>/irj/portal
All this info is contained in the installation guide.
Regards
Juan -
Java installer in Windows Vista: error 1721
Hi,
I cant install java SE in Windows Vista. I get always this error:
error 1721. There is a probleme with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor.
Anyone knows how I can solve it? I tryed with other java versions but I get the same error.
Thanks in advance.If all else fails, your Vista could just be screwy.
If you're willing to go that far, and you've exhausted all other options, you could try reformatting and reinstalling Vista. (Or even XP, since it's way more stable. :D)
At any rate, this doesn't seem to be the file's problem, as plenty of people have gotten it working.
Have you installed any ... "distasteful" software on your computer, or tweaked stuff like a hardcore techie? Because it's quite easy to screw with Windows. :) -
BI Java Installation: Clarification Needed!
I'm wondering if someone could help clear this up for me:
We have installed NW2004s SPS08 on Solaris with only the usage type EP (AS Java/EP). Awhile back I was tasked with connecting our BW ABAP system to our Portal ("Integration into the Portal" - transaction SPRO etc).
After starting this task I noticed I was missing things that the instructions were telling me to configure; i.e. Items that were related to BI that weren't in the Portal such as certain roles, the BI Repository Manager etc.
Reading around, it seemed like I need to install the BI usage type.
I have now been tasked with another installation of the Portal (NW2004s SR1 this time), but am trying to head off the problems I'm experiencing trying to connect the Portal to our BW ABAP system. This will be a Java only installation. I've read that BI-Java requires EP and AS Java, and that if I install the BI-Java usage type, EP and AS-Java will be installed automatically.
My question is, if I do the BI-Java installation and it automatically installs EP/AS-Java, will the Portal still act the same way as it does in my EP/AS-Java only installation I already have? We have many plans to use the Portal as an entry point for all of our backend systems, so if the Portal's capabilities are not what we see already (in our first installation of just EP/AS-Java) then we will have problems.
Any clarification is greatly appreciated and I will award points accordingly.
THANKS!
Beau.I think that's what I needed to know.
I was actually wondering about DI as well. Our developers are having problems deploying .EAR files to our original EP-only install. They can deploy .PAR files with no problems, but .EAR files always error out. Maybe having DI will solve this problem as well? I'm a little concerned about the hardware capacity of this box with having BI, EP and DI all installed on it. I had contacted SAP about installing DI a while back and basically they had told me to install it on a seperate server, by itself. We're running a Sun Enterprise 420R, 4G of memory and a 450 mhz processor for this new installation. Do you think this box is capable of handle EP, BI and DI (AS-JAVA)?
Thanks for your help! -
Hi,all:
I did the installation of BI Java Installation yesterday,but it terminated during process"SAP J2EE Engine Online Deployment". It informs "MUT-02041 SDM call of deploySdaList ends with returncode 4". I check the callSdmViaSapinst.log, below is the error information:
05/11/20 22:49:59 - ***********************************************************
05/11/20 22:50:01 - Start updating EAR file...
05/11/20 22:50:01 - start-up mode is lazy
05/11/20 22:50:01 - EAR file updated successfully for 137ms.
05/11/20 22:50:01 - Start deploying ...
05/11/20 22:50:02 - EAR file uploaded to server for 385ms.
05/11/20 22:50:02 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deplo
ying/bi_mmr_bi_4.0.ear.
Reason: None of the available containers recognized the components of application sap.com/
bimmrbi_4.0; it is not possible to make deploy.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.jav
a:480)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServic
eImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.
java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageList
ener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(Unorder
edChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
For detailed information see the log file of the Deploy Service.
05/11/20 22:50:02 - ***********************************************************
Nov 20, 2005 10:50:02... Info: End of log messages of the target system.
Nov 20, 2005 10:50:02... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 20, 2005 10:50:02... Error: Aborted: development component 'bi/mmr/bi_4.0'/'sap.com'/'SAP AG'/'350.6918.000
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/bi_mmr_bi_4.0.ea
r.
Reason: None of the available containers recognized the components of application sap.com/bimmrbi_4.0; it is
not possible to make deploy.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(Deployme
ntActionTypes).REMEXC)
Nov 20, 2005 10:50:02... Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not restore s
tate of J2EE Engine now.
Nov 20, 2005 10:50:02... Info: -
Deployment was successful -
Nov 20, 2005 10:50:03... Info: Summarizing the deployment results:
Nov 20, 2005 10:50:03... Error: Admitted: /Inst_CDs/BW/BW-UDI/ONLINE/BIUDI09_0.sca
Nov 20, 2005 10:50:03... Error: Processing error. Return code: 4
My platform is SUSE Linux Enterprise Server 9. I do the installation on a NetWeaver ABAP+Java 640 system. Also I have installed BI content 3.53.
Please help me.
Thanks,
DanielI am having the same problem.
Can anyone help on this topic please? -
How to cooperate the current mail system with Sun Java Commnication Suite 5
Dear all and Shane,
Excuse me for bothering you again.
Due to time limited, I would like to know how to cooperate the current mail system with Sun Java Commnication Suite 5. I mean I would like to use current mail system (mailscanner + postfix + courier-IMAP + clamav + spamassassin + webmail) and use the outlook connector to connect to Sun Java COMMS 5 to share the calendar, contacts only.
Right now I have done the testing by using outlook, mac mail, thunderbird to share calendar,contacts via Sun Java COMMS 5 in Centos Linux 5.
My plan is as following
1. Sun Java Communication suites 5 server ( I called it comms5 ) will be in DMZ zone and will open the necessary ports in firewall.
2. I will create more than six sub domain name in Sun Delegate server and the necessary accounts within these domain names.
3. All messages will be transmitted via Postfix and clients will retrieve from Courier-IMAP
4. All Clients included other branch offices will use different mail clients to share their calendars, contacts via COMMS5 ( But how will COMMS handle the messages such like invitation ? )
Any suggestions will appreciate.
PS: Is it possible to classify the contacts in outlook address book ?
For example, when user click the receiver, it will show like as following
GLOBAL ADDRESS BOOK
--Director
--and so on
----CN.BRANCH OFFICE
-----------CN01 EMAIL ADDRESS
-----------CN02 EMAIL ADDRESS
-----------CN03 EMAIL ADDRESS
and so on
----JP.BRANCH OFFICE
-----------JP01 EMAIL ADDRESS
-----------JP02 EMAIL ADDRESS
-----------JP03 EMAIL ADDRESS
and so on
----TW.BRANCH OFFICE
and Due to the user account is located in CN.BRANCH OFFICE, it will extend the CN.BRANCH OFFICE contacts level.
Excuse me for bad English, hope you can understand it.
Best Regards,
BruceDogz wrote:
Due to time limited, I would like to know how to cooperate the current mail system with Sun Java Commnication Suite 5.
I mean I would like to use current mail system (mailscanner + postfix + courier-IMAP + clamav + spamassassin + webmail) and use the outlook connector to connect to Sun Java COMMS 5 to share the calendar, contacts only.Getting your current mail system to 'co-operate' in this way will require more time then simply migrating the accounts of users on the current mail system to the comm-suite-5 installation and making use of UWC for Webmail access and ClamAV/SpamAssassin integration within the messaging MTA.
Also the use of Outlook Connector with a non-Sun IMAP backend isn't supported, nor is the use of a non-Sun IMAP backend possible with UWC.
Right now I have done the testing by using outlook, mac mail, thunderbird to share calendar,contacts via Sun Java COMMS 5 in Centos Linux 5. Once again I should remind you that CentOS is not a supported platform for comm-suite-5
Regards,
Shane.
Maybe you are looking for
-
Cannot see any Wireless networks
After installing the latest security update for 10.3.9, I can no longer see any wireless networks. I have tried reseating my airport card along with unpluging the antenna with no luck. I have also repaired permissions and trashed the Network Interfac
-
Script for generating warning message during Shutdown by GPO
Hello, I want to apply GPO in my AD to generate a warning message in the pop-up window just after when user click SHUT-DOWN in their system . But I don't know what are the script for the same in batch file. Any body please suggest me. Thanks
-
Symptom: You might see an error in Software Update Point Status Message when you run software updates synchronization. (Figure 1) WSUS Configuration Manager failed to subscribe to update categories and classifications to WSUS Server "Server Name" Fig
-
Help stop music disappear from ishuffle!
How can I stop the default in iTunes that is set to update iPod automatically. When you connect your iPod to your computer, iTunes opens, then transfers selected songs in your library and playlists to your iPod, and erases songs from iPod that aren't
-
BADI HRBAS00INFTY in transaction PV15
Hello, I am implementing the badi HRBAS00INFTY method BEFORE_UPDATE to control the creation of the relation A032 between person (object p) and qualifiquation (object Q) from transaction PV15. The issue I have is how to change the content of tables pa