After the BI executables were added to Sophos exclusion list, I eventually was able to successfully install 5.2.2.2 and connect the admin console to the BI service. On the surface things appears to be working. However, the Application Event log wrapped a few times and it is now filled with these entries;
G.
I since reverted back to an earlier non 5.2.x version of BI. 5.2.2.2 Update - Console could not connect to service process
Re: 5.2.2.2 Update - Console could not connect to service process
- Attachments
-
- BI_Application_Errors_Event_Log.png (117.82 KiB) Viewed 4735 times
Re: 5.2.2.2 Update - Console could not connect to service process
So I need to clarify: my fix is NOT thru the Sophos web dashboard. It is on your local workstation/server. Double-clicking the `S` in your Notification or System Tray. That opens a dialogue. Follow the directions here:
https://support.home.sophos.com/hc/en-u ... ons-to-run
Option 1 is what worked for me without issue. Again, LOCAL EXCLUSION. I tried thru the dashboard and was unsuccessful. Using these directions it was an immediate fix. It has survived countless reboots, as well.
https://support.home.sophos.com/hc/en-u ... ons-to-run
Option 1 is what worked for me without issue. Again, LOCAL EXCLUSION. I tried thru the dashboard and was unsuccessful. Using these directions it was an immediate fix. It has survived countless reboots, as well.
Re: 5.2.2.2 Update - Console could not connect to service process
Thanks gwp1 for the instructions. Local Exclusions works ... Exclusions from the Sophos Dashboard does not work.
After I upgraded once more (at 5.2.2.3 now) and watched the Event Log for suspicious events, I am convinced that the the Sophos local exclusions did the trick. As soon as I removed the local exclusions to see if 5.5.2.3 fixed the console connection issue, two things happened; The BI admin console could not connect to the service anymore and the Event Log started to create many new error reporting events per minute. So 5.2.2.3 does not fix the problem with Sophos.
After I upgraded once more (at 5.2.2.3 now) and watched the Event Log for suspicious events, I am convinced that the the Sophos local exclusions did the trick. As soon as I removed the local exclusions to see if 5.5.2.3 fixed the console connection issue, two things happened; The BI admin console could not connect to the service anymore and the Event Log started to create many new error reporting events per minute. So 5.2.2.3 does not fix the problem with Sophos.