Skip to main content
Question

IFS Cloud - DBINSTALLER - Could not create the Java Virtual Machine.


paguin
Sidekick (Partner)
Forum|alt.badge.img+11
  • Sidekick (Partner)
  • 140 replies

Hello,

I am getting following error while deloying a delivery. 

INFO: Running database installer, logs location: C:\ifsuat\ifsroot\logs\ifscloudinstaller
[Wed Nov 0 UTC 2023] - SEVERE: Could not create the Java Virtual Machine.
[Wed Nov 0 UTC 2023] - SEVERE: A fatal exception has occurred. Program will exit.
[Wed Nov 0 UTC 2023] - INFO: Running data import, logs location: C:\ifsuat\ifsroot\logs\ifscloudinstaller
[Wed Nov 0 UTC 2023] - SEVERE: Could not create the Java Virtual Machine.
[Wed Nov 0 UTC 2023] - SEVERE: A fatal exception has occurred. Program will exit.

Server has sufficent memory. Can any one suggest please

Regards

Pankaj

7 replies

Forum|alt.badge.img+10
  • Hero (Employee)
  • 172 replies
  • November 9, 2023

Hi,

Are you using the java in the C:\ifsuat\ifsroot\bin\jdk\bin ?
check the path from where you start the installer

you can add more detailed logging (will perhaps not show more on this issue though), by adding --set logLevel=FINEST on the command line when starting installer.

There might be a crash dump from java in the ifsinstaller folder or ifsinstaller/installers or in the C:\ifsuat\ifsroot\bin\jdk\bin

or search for hs_err_pid*.log files in the entire C:\ifsuat\ifsroot structure


paguin
Sidekick (Partner)
Forum|alt.badge.img+11
  • Author
  • Sidekick (Partner)
  • 140 replies
  • November 10, 2023

@hhanse ,

Thanks for your reply. I could not find any hs_err_pid*.log file

Java Path is correct and there are not log files. i had checked this before

echo %JAVA_HOME%
C:\ifsuat\ifsroot\bin\jdk

Can you please suggest more

Regards

Pankaj


Forum|alt.badge.img+10
  • Hero (Employee)
  • 172 replies
  • November 10, 2023

Hi,

to be precise - it's the path to java that need to be correct not the JAVA_HOME.
"cmd> where java"
I guess it’s ok as well...

Try running the db-deploy.cmd in the ifsinstaller/installers folder.
Is the file (cmd or jar) "blocked"    


If that work, then a java process (installer) don't have permission to start another java application (db-deploy.cmd)
This might be some sort of windows privilegie or file permissions?

Have you tried to run as Administartor? Test to set (properties) the java.exe as “start as Administrator”


paguin
Sidekick (Partner)
Forum|alt.badge.img+11
  • Author
  • Sidekick (Partner)
  • 140 replies
  • November 15, 2023

@hhanse ,

I am doing it via PS - Administrative mode.  cmd and jar are not blocked.

JAVA home is also correctly mapped.

an other sugestions..

Regards

Pankaj


Forum|alt.badge.img+10
  • Hero (Employee)
  • 172 replies
  • November 15, 2023

Have you tried from a CMD - where there are no configurable privilege's that can be affecting. 
I personally never use PS… unless a ps1 script requires it.

Just because main.ps1 need to run in a PS doesn’t mean the installer.cmd need to. 


paguin
Sidekick (Partner)
Forum|alt.badge.img+11
  • Author
  • Sidekick (Partner)
  • 140 replies
  • November 19, 2023

Hello @hhanse ,

Used CMD ths time and identified issue was Java Path only. thanks for sharing. seems it was picking wrong Java Version.

Appriciate your help

Regards

Pankaj


Forum|alt.badge.img+2
  • Do Gooder (Employee)
  • 1 reply
  • March 21, 2025

Hi,
I've encountered the same error, which was caused by multiple Java paths. The delivery process was not picking the correct JDK bin path located inside the ifsroot directory. Below is how I fixed the issue:

  1. Open the command prompt and type:
    where java
  2. If multiple locations appear, remove the incorrect ones and keep only the following in the environment variables:
    C:\ifsroot\bin\jdk\bin

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings