Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

JVM Error when running ConfigurationManager

Avatar

Avatar
Level 3
_James_J_Gallag
Level 3

Likes

0 likes

Total Posts

54 posts

Correct Reply

0 solutions
View profile

Avatar
Level 3
_James_J_Gallag
Level 3

Likes

0 likes

Total Posts

54 posts

Correct Reply

0 solutions
View profile
_James_J_Gallag
Level 3

19-08-2008

When I attempt to run ConfigurationManager.bat I'm getting the following error:



Java Virtual Machine Launcher - Could not find the main class. Program will exit.



The command that the batch file is running is:



...>"javaw" -Xms128m -Xmx512m com.adobe.livecycle.lcm.gui.LCMGUI



I followed the steps in "Configuring the JVM arguments and properties" in the "Installing and Deploying LiveCycle ES for WebSphere" document but am still getting this error.



Any ideas what could be wrong ?

Replies

Avatar

Avatar
Boost 5
Level 3
JohnFait
Level 3

Likes

6 likes

Total Posts

67 posts

Correct Reply

12 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Level 3
JohnFait
Level 3

Likes

6 likes

Total Posts

67 posts

Correct Reply

12 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
JohnFait
Level 3

19-08-2008

What JDK vendor and version are you using?



Rather then double clicking the bat file can you try running it from a dos prompt to get some addition output about the issue.

Avatar

Avatar
Level 4
Jayan_Kandathil
Level 4

Likes

0 likes

Total Posts

140 posts

Correct Reply

0 solutions
View profile

Avatar
Level 4
Jayan_Kandathil
Level 4

Likes

0 likes

Total Posts

140 posts

Correct Reply

0 solutions
View profile
Jayan_Kandathil
Level 4

19-08-2008

Make sure that your environment variables JAVA_HOME and PATH point to the right JDK and its /bin folder respectively.

Avatar

Avatar
Level 3
_James_J_Gallag
Level 3

Likes

0 likes

Total Posts

54 posts

Correct Reply

0 solutions
View profile

Avatar
Level 3
_James_J_Gallag
Level 3

Likes

0 likes

Total Posts

54 posts

Correct Reply

0 solutions
View profile
_James_J_Gallag
Level 3

19-08-2008

Ok I have it now.



What I was doing wrong was tring to run ConfigurationManager.bat from a Mapped network drive.



I went onto the server itself that its installed on and ran the same bat file and it worked.



Thanks for your help.



James

Avatar

Avatar
Give Back
Level 1
robkoch
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Give Back
View profile

Avatar
Give Back
Level 1
robkoch
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Give Back
View profile
robkoch
Level 1

10-11-2020

Noticed the AEM installer for Windows puts in JAVA_HOME_32 variable. Had to change it to JAVA_HOME then it worked.

Avatar

Avatar
Establish
Employee
Kosta_Prokopiu1
Employee

Likes

133 likes

Total Posts

317 posts

Correct Reply

88 solutions
Top badges earned
Establish
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Establish
Employee
Kosta_Prokopiu1
Employee

Likes

133 likes

Total Posts

317 posts

Correct Reply

88 solutions
Top badges earned
Establish
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Kosta_Prokopiu1
Employee

10-11-2020

These days (contrary to 2008) we usually run 64-bit JREs and JDKs and JAVA_HOME usually points to those vs JAVA_HOME_32 that would point to a possibly non-existent 32-bit Java.