Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[NSM] Cannot launch client; error message 'Could not create the Java virtual machine'



Article ID: KB21657 KB Last Updated: 11 Oct 2016Version: 2.0

NSM client will not launch. Error message displays:

Could not create the Java virtual machine

This article describes the Java memory allocation issue causing it and suggests a workaround.


After installing the NSM client on a Windows PC, the following error message is displayed:

Could not create the Java virtual machine

This message is displayed when the NSM client is installed on a PC without enough contiguous memory to load the Java Virtual Machine needed for NSM to start. This is a Java memory allocation limitation.


Several options are possible:


Try to reboot your PC immediately attempt to open NSM before running any other programs.  NSM is a 32 bit application, and may require contiguous memory allocation within the first 3GB of memory. Opening and closing other applications has most likely fragmented the available memory, and there is not a contiguous segment of the required size available. Applications that start at boot, may fragment memory. 

Adjust memory allocation

If the issue still persists, adjust the maximum amount of memory allocated to the NSM client at startup.

  1. Navigate to the NSM installation directory, commonly: C:\Program Files\Network and Security Manager\NSM.lax file.   

    Note: Reducing the amount of memory allocated to NSM on your PC will reduce NSM performance.  Use the largest heap value that NSM will successfully start with.
  2. Open the NSM.lax file and change the heap size value from 1280 to 768. For example:  
    # -------------------------------------
    # Maximum Heap Size
  3. Attempt to open NSM. If you see the same error, adjust memory value down and try again.  Under 768m, the NSM client may fail some operations.

    Note: Some versions of NSM 2012.1 and earlier (possibly early versions of 2012.2) may automatically adjust max heap back to 1280 for schema generation purposes. A message confirming that this has happened should appear.  To work around this behavior, manual schema transfer or NSM upgrade will be needed.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search