Cannot Successfully run Novell Access Manager identity server on Windows 2003 R2 Enterprise Edition French language OS

  • 7008160
  • 18-Mar-2011
  • 07-Jun-2013


Novell Access Manager 3.1.3-247 Windows Novell Identity Server



Install Novell Access Manager Identity Server (IDS) component on Microsoft Windows 2003 R2 Enterprise edition French language localization with 4Gb of RAM or more.


The installation process goes fine without errors and complete successfully, however, the IDS will not be registered in the Admin console and, after the server reboot, both Tomcat and JCC services cannot start.

The "jakarta_service_yyyymmdd.log" reports the following errors:

[2011-01-25 15:07:59] [info] Starting service...
[2011-01-25 15:07:59] [info] Error occurred during initialization of VM
[2011-01-25 15:07:59] [info] Could not reserve enough space for object heap
[2011-01-25 15:07:59] [info]
[2011-01-25 15:07:59] [418  javajni.c] [error] CreateJavaVM Failed
[2011-01-25 15:07:59] [1000 prunsrv.c] [error] Failed initializing java C:\Program Files\Novell\Tomcat\common\lib\tools.jar;C:\ProgramFiles\Novell\Tomcat\bin\bootstrap.jar
[2011-01-25 15:07:59] [1269 prunsrv.c] [error] ServiceStart returned 2
[2011-01-25 15:07:59] [info] Run service finished.


Please note that this issue is specific to French language localization of Windows 2003 R2 Enterprise edition and does not occur installing Novell Access Manager 3.1.3-247 on Windows 2008 R2 Enterprise Edition.

If you are suffering this issue and Windows 2008 is not a viable option, please open a Service Request with Novell Technical Support and refer to this TID.


In order to allow Tomcat to successfully start you can implement the following:

Using regedit go to the following keys:

\HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Fundation\Procrun2.0\Tomcat5\Parameters\Java\JvmMs

\HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Fundation\Procrun2.0\Tomcat5\Parameters\Java\JvmMx

and change their decimal value from 1024 to 512.

In order to allow the JCC service to successfully start, the only viable solution at the moment is to reduce the amount of RAM to be below 4 Gb (tested with 3Gb, 2Gb and 1Gb) and restart the server.