ENS Web Control is not responding message on Status windows

[kylekat]

For the last 48hs, I cant seem to get Web Control service to come online. The Systray icon for mcafee has an exclamation mark, the status shows that its not responding and the ENS console shows Web Control as "Not Started".

I have seen this in the past but usually a restart of the systam takes care of it. This time, even after multiple restarts, the module will not go into its normal state.

I'm running ENS 10.6

EndpointSecurityPlatform_Errors.log shows:

09/18/2018 05:28:13.534 AM McChHost(11268.11976) <> WebControl.McBrwCtl.Error (SALog.cpp:173): pSACore->SetOption() failed; recreating pSACore. DB = SAEPolicy.dat, Option = browsertype
09/18/2018 05:28:13.539 AM McChHost(11268.11976) <> WebControl.McBrwCtl.Error (SALog.cpp:173): pSACore->SetOption() failed. DB = SAEPolicy.dat, Option = browsertype
09/18/2018 05:28:13.542 AM McChHost(11268.11976) <> WebControl.McBrwCtl.Error (SALog.cpp:173): pSACore->SetOption() failed; recreating pSACore. DB = SAEPolicy.dat, Option = useragent
09/18/2018 05:28:13.545 AM McChHost(11268.11976) <> WebControl.McBrwCtl.Error (SALog.cpp:173): pSACore->SetOption() failed. DB = SAEPolicy.dat, Option = useragent
09/18/2018 05:28:14.003 AM McChHost(11268.11976) <> WebControl.McBrwCtl.Error (SALog.cpp:173): Unable to read proxy settings from BO.
09/18/2018 05:28:14.131 AM    mfewc(7300.12996) <SYSTEM> WebControl.SaSSHMod.Error (SALog.cpp:173): Failed to configure proxy for Proxy type:1
09/18/2018 05:28:16.683 AM McChHost(11268.11976) <> WebControl.McBrwCtl.Error (SALog.cpp:173): pSACore->SetOption() failed; recreating pSACore. DB = SAEPolicy.dat, Option = viewport
09/18/2018 05:28:16.686 AM McChHost(11268.11976) <> WebControl.McBrwCtl.Error (SALog.cpp:173): pSACore->SetOption() failed. DB = SAEPolicy.dat, Option = viewport
09/18/2018 05:28:47.982 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:150): CheckTechnologyState failed to get technology status from BO: WPFunctionalStateBO, error: 80000100L
09/18/2018 05:28:47.984 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:213): Web Control is not responding.
09/18/2018 05:29:48.137 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:150): CheckTechnologyState failed to get technology status from BO: WPFunctionalStateBO, error: 80000100L
09/18/2018 05:29:48.139 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:213): Web Control is not responding.
09/18/2018 05:30:42.342 AM    mfewc(7300.12996) <SYSTEM> WebControl.SaSSHMod.Error (SALog.cpp:173): Failed to configure proxy for Proxy type:1
09/18/2018 05:30:48.152 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:150): CheckTechnologyState failed to get technology status from BO: WPFunctionalStateBO, error: 80000100L
09/18/2018 05:30:48.153 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:213): Web Control is not responding.
09/18/2018 05:31:48.165 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:150): CheckTechnologyState failed to get technology status from BO: WPFunctionalStateBO, error: 80000100L
09/18/2018 05:31:48.167 AM   McTray(6060.10640) <> McTray.McTrayUPC.Error (TechnologyTopicHandler.cpp:213): Web Control is not responding.
09/18/2018 05:31:54.768 AM MFEConsole(16024.13756) <> MFEConsole.MFEConsole.Error (mfeux_extension.cpp:2104):  WPFunctionalStateBO - getPropertiesEx ( [69118088,"businessObject/EP_TOPIC_NAME_TECHNOLOGY"]) : operation returned non-success: BL_ERROR_FAILED_CONNECTION
09/18/2018 05:31:55.079 AM MFEConsole(16024.13756) <> MFEConsole.MFEConsole.Error (mfeux_extension.cpp:2104):  WPFunctionalStateBO - getPropertiesEx ( [69143560,"businessObject"]) : operation returned non-success: BL_ERROR_FAILED_CONNECTION
09/18/2018 05:32:17.209 AM   mfeesp(7076.14284) <SYSTEM> LPC.CommonLPC.Error (common_prop_collection.cpp:373): RegQueryValueEx for bGlobExclConfigured failed with error: 2

[Former Member]

We started having the same problem with all the computers on our network (all Windows 10) after 12/7/18.

[Former Member]

If you aren't yet using ENS 10.5.5 / 10.6.1 + (at least) November Update, please upgrade to this version as there have been changes to the way ENS integrates with MA. This was the cause of most such issues.

If the issue is still present, then you may want to check if the component in the error is actually not working or if it is "just" cosmetic. Sometimes these errors occurr when a system has a dll which is injecting however this behaviour was mostley addressed back in ENS 10.5.4.

If the issue still occurrs with the mentioned version, please gather the following data and open an SR with Support as this type of issue needs to be properly investigating. Support will need:

* ENS debug logs

* AMTRACE and PROCMON whilst issue occurrs (see https://kc.mcafee.com/agent/index?page=content&id=KB86691 for more info on these traces)