TheSkymanDC

Is there ANY chance the LiveGrid not accessible report in the ERA console is false? On the one computer that I can always remote into and that goes in and out of the LiveGrid problem - all I have to do is open the eset console on the computer - it begins running an update and then the error goes away. Something seems really odd about that.

Here's another from the 7 computers that now say LiveGrid not accessible - seat ID (HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info\WebSeatId) cef62078-2f05-421d-bb8d-d85d820830de - information if a license file is present in the "C:\ProgramData\ESET\ESET Security\License" folder License file is present 4k dated 1/12 - information if the Username and Password values are missing in the key HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Plugins\01000400\Settings Username and password values are present.

OK - one computer just appeared in the LiveGrid not accessible list -

I was more than a little surprised to find NO computers listed as "LiveGrid not accessible" when I arrived this morning. That may change as people arrive and power up their computer. 5 computers were list as Product is not activated - activation task only work on 2 so that leaves 3 still not right. Hopefully there will be more good surprises today.

This is getting crazy. 1 computer that wasn't on the LiveGrid is not accessible list has joined it today. Deactivated in ELA but ERA doesn't show any change yet. 4 computers that were successfully deactivated-activated have now rejoined the LiveGrid is not accessible list. 2 of those computers have now removed themselves from the list. 4 deactivated computers refuse to activate. The task fails. This is like the old game of Whack-A-Mole.

An additional computer showed up in the LiveGrid not accessible list late yesterday and was deactivated so that makes 10 computers. This morning 5 of the computers I deactivated yesterday finally showed as Product is not Activated. Ran activation task on all 5. Task failed on 4 of 5. So we have 4 successful activations from yesterday and 1 from today, 4 failed activations and one remote computer awaiting power-up. And now - one of the successful activations from yesterday has now rejoined the LiveGrid not accessible list. Should I plan for the other "successful" computer to rejoin also? What a mess.

OK - it's been over 1 hour. 1 computer is offline. I computer has shown "Product is not activated" and been successfully activated. The other 7 computers continue to check in but do not show as needing activation. Any ideas?

Right - but when? Do I wait for the computers to show "not activated" in ERA? None of them are currently showing that message.

Marcos - I've just deactivated 9 computers in the ELA portal. When do I activate them in the ERA portal?

Here's today's report. This computer changes from day to day - sometimes hour to hour. It started yesterday reporting no errors. If I do a Software Install task and push 2068 the problem will go away - only to return later. Quite frustrating. updater_20180110_072546.etl

On this system (different from previous) as soon as I turned on diagnostic logging it did an update and the error went away. updater_20180108_134458.etl

Here ya go! updater_20180108_130725.etl

Before reboot this is what I see. After reboot no errors are shown in ESET. But rest assured, the error will return!

So far my favorite is the disappearing/reappearing computers with ESET LiveGrid® is not accessible. Sometimes it shows 11 computers, sometimes it shows 3, sometimes 6. Quite annoying.

OK - What do we need to do?

And now I have a computer that changes its mind. Sometimes it says Not Activated. Sometimes it says Could Not Connect to Server. Sometimes it says LiveGrid is Not Accessible. Sometimes it's fine. Guess it's time for a complete uninstall - re-install. What a pain. Only about 10 more computers to fix. Yipeee!

Marcos - Please describe "fixed automatically". Do we still have to deactivate - reboot - activate?

Does this mean that all that needs to be done is that the new build be installed over the bad build? Please update us ASAP. ESET being closed tomorrow is making us anxious about this problem continuing until next week.

UPDATE - I have had NO success deactivate - activate without a reboot in between.

Marcos - so we're sure - is a reboot needed between deactivation - reactivation?

A couple of reboots and the uninstall was finally successful. Friends don't let friends install 2068.

And anticipating the always good to hear response of "you'll have to uninstall then reinstall" I've been sitting on this screen for the past 15 minutes. * That ended up pretty small - it says "Preparing Uninstallation"

Here are today's surprises

Based on problems we’re seeing I’d wait this update out until they get it fixed

I’m seeing some of the same. This is a mess. Will update things in the morning. Not having support until 9am EST is a pain.