Hi Michael,
We got the same issue. Did you find any solution for this?
Kind Regards
Search found 4 matches
- 31 Dec 2024, 08:47
- Forum: Installation & Configuration
- Topic: Heapsize leads to abort of the OpenWebstart installation
- Replies: 2
- Views: 39587
- 30 Dec 2024, 10:47
- Forum: Installation & Configuration
- Topic: The JVM could not be started. The maximum heap size (-Xmx) might be too large
- Replies: 6
- Views: 25336
Re: The JVM could not be started. The maximum heap size (-Xmx) might be too large
Hi Janak,
I finally succeeded to collect a new log file on a device. I cannot find more info in the i4j_nlog_1.log file. This is the only logfile created.
The only error message is "ERROR: could not initialize JVM" and "ERROR: Could not start JVM". After that the rollback is initiated.
I added the ...
I finally succeeded to collect a new log file on a device. I cannot find more info in the i4j_nlog_1.log file. This is the only logfile created.
The only error message is "ERROR: could not initialize JVM" and "ERROR: Could not start JVM". After that the rollback is initiated.
I added the ...
- 16 Dec 2024, 15:05
- Forum: Installation & Configuration
- Topic: The JVM could not be started. The maximum heap size (-Xmx) might be too large
- Replies: 6
- Views: 25336
Re: The JVM could not be started. The maximum heap size (-Xmx) might be too large
Hi Janak,
Thanks for your reply.
The problem is while installing OWS using SCCM, not while running OWS to run a Jnlp file i.e. while executing the javaws command, right?
Indeed, the problem exists only when running an automated installation during the task sequence using SCCM. There is no issue ...
Thanks for your reply.
The problem is while installing OWS using SCCM, not while running OWS to run a Jnlp file i.e. while executing the javaws command, right?
Indeed, the problem exists only when running an automated installation during the task sequence using SCCM. There is no issue ...
- 13 Dec 2024, 15:41
- Forum: Installation & Configuration
- Topic: The JVM could not be started. The maximum heap size (-Xmx) might be too large
- Replies: 6
- Views: 25336
The JVM could not be started. The maximum heap size (-Xmx) might be too large
Hi All,
We got the following issue when installing OpenWebStart via an SCCM task sequence. An SCCM application for OpenWebStart version 1.11.0 has been made and installs without any problems via Software Center. When installing the same application via a task sequence step, the application fails on ...
We got the following issue when installing OpenWebStart via an SCCM task sequence. An SCCM application for OpenWebStart version 1.11.0 has been made and installs without any problems via Software Center. When installing the same application via a task sequence step, the application fails on ...