on 09-04-2006 6:24 AM
Hi,
Our team had the following issue with the Netweaver Rapid installer 2004s.
The installer runs fine until the following error pops up during Step 39 of 51 (Preprare to install minimal configuration) under STEP 4 (Execute service) of the rapid installer.
ERROR 2006-09-01 20:01:39
CJS-30150 Java processes of instance KL1/JC01 [Java: UNKNOWN] did not reach state PARTRUNNING after 20:30 minutes. Giving up.
ERROR 2006-09-01 20:01:39
FCO-00011 The step startJava with step key |rapidinstaller|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|7|0|NW_Call_Offline_CTC|ind|ind|ind|ind|7|0|startJava was executed with status ERROR .
We are unable to proceed with the installation. The Retry option also fails. The error comes up after about 30 minutes. The status bar displays the following.
"Starting KL1/JC01 [Java:UNKNOWN] Elapsed Time XX:XX minutes"
The PC configuration has only 2GB of RAM . It does not have the recommended 3GB of RAM. Could this be the issue or is it some other reason?
Any advice is greatly appreciated.
Pradeep.
Chief Solutions Architect.
SGIT, Sri Lanka.
Please note that ram you have specified here is not sufficient. At lease there should be 3GB of RAM.
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi pradeep,
I am currently installing SAP Netweaver on a 32-bit machine, with 3GB of RAM (and PAE enabled) and Windows Server 2003. I have the same problem, at the 23rd step of 47 the installer stops and gives me that error.
Can you please tell how did you manage this error ?
The rest of the system's configuration is SAP Netweaver 2004s SR1, ABAP + JAVA, MSSQL, java j2sdk1.4.2_09 installed.
Message was edited by:
Alexandru Rasuceanu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
We are also facing the same error during the installation of netweaver 2004s in Suse Linux 64 bit system.
<i>CJS-30150 Java processes of instance FC2/JC00 [Java: UNKNOWN] did not reach state PARTRUNNING after 20:30 minutes. Giving up.
ERROR 2007-03-21 23:49:41
FCO-00011 The step startJava with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_StartJava|ind|ind|ind|ind|5|0|startJava was executed with status ERROR .</i>
Whether changing the heap size will solve this problem as discussed in this forum?
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=157690&tstart=0">Thread ID = 157690</a>
Thanks in advance...
This thread is a bit old, but it seems there's still no right answer.
Obviously the problem is the ram. I've faced this problem in a testing system with just 1.5gb of ram, and the solution (as some people said) was just increase the swap size to a minimum 2,5-3gb. If you look at /your server/your instance/work/std_server0.out (we're installing, there's almost nothing @ /usr) you'll see an out of memory error.
By the way, on 32-bit systems I think there's no 1,5gb limitation. The address space just let us to use 2^32 = 4gb; depending on the OS (how they manage the kernel memory/apps memory) we can use more or less memory. MS Windows just leaves 2gb for apps usage, but there are more bussiness-ready OS
You can check this link for more info: http://www.eng.cam.ac.uk/help/tpl/languages/bigprocesses.html.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you need to add /PAE to your boot file so that windows can use the extra memory http://support.microsoft.com/kb/283037/
so that a process can get more physical memory
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Siva,
thanks for your response. I read the kb artical, but it talks about enabling /PAE if we need to use more than 4GB of memory. PAE reminded me of EMM386 (extended memory manager) which came with MS DOS.. i used to tweak the parameters to get my 386DX machine to run faster
The rise of 64-bit Windows server computing :
http://www.markwilson.co.uk/blog/2006/04/rise-of-64-bit-windows-server.htm
cheers,
Harsha.
if u are using a 32bit os then with one server process 2gb is fine for a trainig system because a process in a 32bit os can only use a maximun of 1.5gb , make sure your virtual/paging is 3 time your memory , restart your java engine manully from SAP MMC and the restart the installtion , also please post the log dev_dispatcher and dev_server. i have seen WAS Java systems running on 2gb systems where JVM Heap is 512/1024
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Huseyin,
Is this an SAP limitation? coz from what i learnt during my school computer science class, a 32-bit OS can address up to 4GB of RAM http://en.wikipedia.org/wiki/IA-32.
We actually thought of upgrading memory to 4GB and giving it a try but if SAP cannot use more that 1.5GB.. i dont think that's going to work either.
regards,
Harsha.
Hi Harsha,
Please read note "Note 110172 - Windows: Transactions with large storage requirements" which says what i told you. Here is the part of this note.
Note mentions that there is a solution for windows servers to enable 3 GB per process.
-
Memory problems with background programs, Memory Management under Windows, 32-bit Windows
Reason and Prerequisites
A maximum of 1.2 - 1.5 GB was previously available for a program in the 2 GB address space under 32-bit Windows. The rest of the address space is either used by Shared Memory buffers, program data and loaded DLLs or is too heavily fragmented.
Solution
To enhance or optimally utilize your address space, the following steps are necessary:
1. Install your Windows operating system again or set it up again.
The Windows Server operating system family provides a 3 GB address space for each process with a specific boot option. Programs which are to use this 3 GB address space, must be prepared by a flag in program header. To do this, Windows must be installed again, or an already existing Windows version must be set up according to the Microsoft guidelines.
2. Activate the 3 GB boot option according to Microsoft KB article 283037.
3. Import the current kernel patch for your SAP system, and note the following details for your SAP system:
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.