Smarts NCM - Windows 2012 Server has Required RAM to Install NCM However the Installer Reports the Following; ERROR: The amount of system memory does not meet the minimum requirement
book
Article ID: 330979
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
During installation of NCM 9.4 on a Windows 2012 Server the following error is reported and installation fails:
Total Physical Memory in Windows= 16 MB MIN_MEMORY Required= 5700 MB
Checking if Total Memory is more than Minimum memory ERROR: The amount of system memory does not meet the minimum requirement. Please review the server requirements in the installation guide.
The Windows Server does in fact have 16GB of memory but it is getting reported as 16MB and thus it is not meeting the required memory to install NCM.
Environment
VMware Smart Assurance - NCM
Cause
The reason for this particular issue is down to the regional settings of the server. NCM uses a prerequisite check script to check for required install conditions. This script uses the systeminfo utility in Windows to gather the amount of memory in the server. In Windows, systeminfo reports all server environment values and variables. It can be run from the command line, c:\systeminfo. The systeminfo utility reports memory in megabytes.
For this issue, the systeminfo utility was reporting the memory as 16.383 MB as follows:
Total Physical Memory: 16.383 MB Available Physical Memory: 15.120 MB Virtual Memory: Max Size: 18.687 MB Virtual Memory: Available: 17.246 MB Virtual Memory: In Use: 1.441 MB
However, the prerequisite check script run by the NCM installer does not recognize the full stop in the memory values. Most systeminfo utilities report memory using a comma like so:
Total Physical Memory: 5,888 MB Available Physical Memory: 4,512 MB Virtual Memory: Max Size: 11,773 MB Virtual Memory: Available: 10,814 MB Virtual Memory: In Use: 959 MB
So in this scenario, the NCM prerequisite check script reads the 16.383 MB as 16MB instead of 16GB.
As there is no full stop, NCM will not parse that symbol and will read it literally as a period.
Resolution
To resolve this issue, change the regional settings of the Server to the standard comma separated value method.
1. Open Control Panel 2. Click on Regional and Language 3. In the Regional and Language window, click Additional settings
4. In the Additional settings window, review the settings and make sure that commas are used and not full stops
Once the settings are set to comma separated, re-run the installation of NCM. It should now read the memory correctly and the installation will proceed.