on 07-04-2012 1:20 PM
Hello everybody,
I have already opened an OSS message but so far the support could not help.
System environment: AS Java running on iSeries V6R1, PC workstation running on Windows XP
On the "old" release (Netweaver 7.0/7.01) I could call the configtool by mapping a network drive (\\<iSeries-hostname>\rootbin)
and double-clicking the configtool.bat in the directory V:\usr\sap\BW1\DVEBMGS03\j2ee\configtool
On the "new" release (Netweaver 7.3) the call itself does still work BUT when I try to change a parameter the following happens:
Purpose: Increase the value for "MaxHeapSize" with the Configtool.
Steps to Reproduce:
the configtool is called on a Windows XP PC (via a NFS mount on Windows Explorer).
Go to V:\usr\sap\BW1\DVEBMGS03\j2ee\configtool
Double-click on "configtool.bat".
Do you want to use the default DB settings: YES
Under "cluster-data", expand "template - Usage_Type-All_in-One".
Click on "instance - ID383857 (ap400c)".
Go to tab "VM Parameters".
Select parameter "maxHeapSize".
In field "Custom Value" enter a different value than the inherited value.
Click button "Set".
-> small error window appears "Config Tool - Error: Java cannot be started"
Result: the new value cannot be saved and is gone when I call the
Configtool a second time (or restart the AS Java).
configtool.0.log:
Jul 4, 2012 12:26:16 PM Error: com.sap.ASJ.cft.000065 JVM validation fails.
Error details: Java cannot be started
configtool.0.trc:
#2.0 #2012 07 04 12:26:16:559#+0200#Error#configtool#
com.sap.ASJ.cft.000065#BC-JAS-ADM-ADM-CFT#sap.com~tc~je~configtool#C0000A3B026F0000000000014D6D50A6###configtool########Thread[AWT-EventQueue-0,6,main]#Plain##
JVM validation fails.
com.sap.engine.lib.config.api.exceptions.ClusterConfigurationException: Java cannot be started
at com.sap.engine.lib.config.impl.jvm.JVMParametersHandlerImpl.validateVMStart(JVMParametersHandlerImpl.java:344)
at com.sap.engine.configtool.scanner.Scanner.checkVMStart(Scanner.java:930)
at com.sap.engine.configtool.visual.panels.VMSettingsPanel.validateVMStart(VMSettingsPanel.java:688)
at com.sap.engine.configtool.visual.panels.VMSettingsPanel.validateVMParams(VMSettingsPanel.java:589)
at com.sap.engine.configtool.visual.panels.VMSettingsPanel.checkTable(VMSettingsPanel.java:866)
at com.sap.engine.configtool.visual.panels.VMSettingsPanel.selectOS(VMSettingsPanel.java:753)
at com.sap.engine.configtool.visual.panels.VMSettingsPanel.actionPerformed(VMSettingsPanel.java:186)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6290)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6055)
at java.awt.Container.processEvent(Container.java:2039)
at java.awt.Component.dispatchEventImpl(Component.java:4653)
at java.awt.Container.dispatchEventImpl(Container.java:2097)
at java.awt.Component.dispatchEvent(Component.java:4481)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4575)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4236)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4166)
at java.awt.Container.dispatchEventImpl(Container.java:2083)
at java.awt.Window.dispatchEventImpl(Window.java:2482)
at java.awt.Component.dispatchEvent(Component.java:4481)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:648)
at java.awt.EventQueue.access$000(EventQueue.java:84)
at java.awt.EventQueue$1.run(EventQueue.java:607)
at java.awt.EventQueue$1.run(EventQueue.java:605)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
at java.awt.EventQueue$2.run(EventQueue.java:621)
at java.awt.EventQueue$2.run(EventQueue.java:619)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:618)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.io.IOException: CreateProcess error=193, %1 is not a valid Win32 application
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:85)
at java.lang.ProcessImpl.start(ProcessImpl.java:30)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:456)
at com.sap.engine.lib.config.impl.jvm.JVMParametersHandlerImpl.validateVMStart(JVMParametersHandlerImpl.java:322)
... 42 more
The next idea was to change the calling workstation and use a Windows Server 2008 (64bit).
On this server I installed the SAPJVM 6.1 so that the entry in configtool.bat points to this Java VM:
set JAVA_CMD="D:\java\sapjvm_6\bin\java.exe"
Still no success...
One last idea:
Maybe I have to change the "Rdbms driverLocation: /usr/sap/BW1/SYS/jdbc/tbx/jt400.jar" in the "Connect - Via Secure Store" properties of the configtool?
Kind regards
Rüdiger Höckel
Hi Rüdiger
We are also facing the same error. Were you able to resolve the problem?
regards
AKD
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
yes, thanks to SAP support the problem was solved:
"I believe I have found the note that describes your issue, but it
has only been released internally:
#1672739-Error message "Java cannot be started" in Config Tool
Symptom
If you work in ConfigTool and set a custom value for a VM Parameter for
instances not running on the host from which ConfigTool is started,
error message "Java cannot be started" is displayed. This behavior
appears on both a template and an instance level.
Other terms
ConfigTool, VM parameters, AS Java
Reason and Prerequisites
A coding issue caused the undesired behavior. When validation of a VM
parameter needs to be done, a Java process is started on the current
machine and the VM parameter is validated against it. However, the path
to the JDK was taken incorrectly from the profile of the remote instanceinstead of the local one and this path is not valid on the local
instance. This was the reason for the malfunction.
Solution
Update your AS Java to an SP or release where the issue is fixed. See
the SP Patch Level section for details and available patches.
________________________________________________________________________
Valid releases
Software Component Release
from to
CORE-TOOLS
CORE TOOLS J2EE ENGINE
7.31 - 7.31
7.30 - 7.30
Please download this SCA from the SMP (for 7.31 SPS04, because 7.30 S
P08 is not available yet):
CORETOOLS04_0-20007067.SCA
Then extract the configtool and let me know if that resolves the issue
for you."
Here is what I did:
I have downloaded CORETOOLS 7.31 patch 4 as you suggested.
I exchanged the COMPLETE "configtool" directory.
I had to use my "old" config.properties file because some parameters
(secstorefs.keyfile) were not properly set.
Afterwards I could set a new value in the configtool.
Hope this helps,
Rüdiger
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.