When Starting Prizm Service, Service starts but is not listening on expected port


10/02/2017

When starting the Prizm service, the service enters a running state, however, you are unable to get a server status when running http://localhost:18681/admin.

The root cause of this issue may be  due to McAfee security blocking the execution of WMIC.EXE on the server.

To fix the issue, disable  the rule blocking WMIC.exe from being executed on the server running Prizm services.

NOTE: The Prizm Application Service may also error when attempting to start if installed on the same server.