6.7. OPSWAT Central Management failed to start with memcached/mongod shells hanging in the foreground

Term

Detail

Problem

OPSWAT Central Management failed to start with memcached/mongod shells hanging in the foreground

Cause

System variable Path is not set properly to Windows\System32 location.

Troubleshooting

Open OPSWAT Central Management's activity log in C:\ProgramData\OPSWAT\Central\Logs\<date>.txt and check for the error " The term <> is not recognized as the name of a cmdlet, function, script file, or operable program."

Solution

Add %SystemRoot%/system32 to system variable Path.

OPSWAT Central Management requires the use of command-line utilities such as netstat, which is located in the Windows\System32 folder. In order to access these commands, the system variable Path must include this folder.

Without access, the mongod and memcached services that OPSWAT Central Management depends on may hang in the foreground.

images/download/attachments/1967406/image_%283%29.png

Navigating to OPSWAT Central Management's activity log in C:\ProgramData\OPSWAT\Central\Logs\<date>.txt, the exact error is shown.
images/download/attachments/1967406/image2019-8-27_15-20-5.png

To solve this problem, navigate to the Environment Variables window from the Start menu.
images/download/attachments/1967406/image2019-8-27_15-11-31.png images/download/attachments/1967406/image2019-8-27_15-11-48.png images/download/attachments/1967406/image2019-8-27_15-12-14.png

Under Path (as highlighted), add "%SystemRoot%\system32" in a new line.

images/download/attachments/1967406/image2019-8-27_15-16-30.png

Restart the machine to ensure the change is propagated properly.