Jump to content

Norm@Home

Members
  • Posts

    55
  • Joined

  • Last visited

Posts posted by Norm@Home

  1. On 2/11/2019 at 9:40 AM, Marcos said:

    Please carry on as follow:
    - Under Help and support -> Details for customer care, enable advanced logging
    - Reboot the machine (via "shutdown -r -t 0", just in case)
    - Run manual update
    - Stop logging after approximately 10 seconds of no update activity
    - Gather logs with ESET Log Collector and provide me with the generated zip file.

    Fast startup is disabled so no need to do "shutdown -r -t 0"; in regards to "Stop logging after approximately 10 seconds of no update activity" how am I supposed to do that when the problem is that "Updating product" never completes so there is no instance when there is no update activity? I'll let it run with advanced logging enabled for a couple hours and then gather the logs and post them here so you can look at it.

  2. As TomFace suggested, I uninstalled but using the normal "Programs and features" control panel app ended with an error something like "you may not have permissions" or some such error so I had to download the Eset Uninstaller and reboot into safe mode in order to remove the original installation. After reinstalling activation did take an unusually long time, almost an hour but it did activate. I haven't rebooted yet as the program is doing it's initial scan but also update its again "Updating product" and has been for more than an hour; this is the same problem that it had originally and this update never seems to finish. Previously no matter how many reboots the "Updating product" never finished and I have no reason to expect that this time it's going to be any different.

    Once the initial scan finishes I'll try and reboot with "shutdown -r -t 0" since Fast Startup is enabled on this notebook computer.

  3. I attempted to upgrade a computer with ESet Endpoint Security 6.x to 7.x; the 6.x version was uninstalled by the installer but the 7.0.2091.0 version failed with a message "Service ESET Service (ekrn) could not be installed. Verify that you have sufficient privileges to install system services" with Retry or Cancel options.

    I googled and did turn up this page https://support.eset.com/kb3544/?locale=en_US&viewlocale=en_US and I ran it with the suggested parameters and there was no error or other messages but trying again to install produced the same error message.

    The user I'm installing under is the sole user of this computer and they are an Administrator; the computer is running Windows 7 x64 Home.

    Any idea's on how to fix this?

  4. 4 hours ago, Marcos said:

    Did you also contact Customer care? This forum is not meant to be a substitute for customer care and does not allow tracking of issues. It's rather just an additional channel where you can discuss issues, provide feedback, etc. with other users and moderators.

    Please collect install logs as per the instructions at https://support.eset.com/kb406/ and provide them to customer care. You can post them here as well so that we can check if there's something obvious which is causing installation to fail.

     

    As I posted, the log collector failed with an error as I mentioned above. If I can't get the logs what then?

  5. 8 hours ago, Marcos said:

    Please provide ELC logs to start off.

    I followed the instructions and tried using the Default collection profile and it ended with an error "An error occured during collection of files. See the log for more info." where would this log file be that it makes reference to? I don't see any error messages in the system application log. I searched the entire C: drive for any log file and ordered them by date / time and I don't see any log within the timeframe of running the Log Collector.

  6. I'm trying to install the latest NOD32 with the live installer and it's failing with this error MSI.1406. How do I fix this error and get the product installed?

    BTW Since the installer says "This may be the result of malware activity" I scanned the computer with the online Eset scanner and Malwarebytes and neither found anything?

  7. Just recently my Eset Smart Security informed me that a new version upgrade to 11.0.159.0 was available; I've tried upgrading multiple times; rebooting etc and each time the upgrade ends with a "File corrupted" message. I've gone to the page that "Troubleshoot update issue" sends me to but my internet connection is good and it working find. Any idea's how to fix this? Is there an offline installer I can download?

  8. On 11/25/2017 at 1:16 AM, bbahes said:

    No, they are not interested in v5. It is considered old and will reach End of Life on Dec 2020. It now has Limited Support  and will later have only Basic Support.

    Have you tried accessing from localhost?

    I tried telneting to 127.0.0.1:2221 but still got "Could not open connection to host"

    I tried netstat -an again and the only two entries for port 2221 now are:

      TCP    0.0.0.0:2221           0.0.0.0:0              LISTENING

      TCP    [::]:2221              [::]:0                 LISTENING

    It's listening but not on either 127.0.0.1 or the actual server address 192.168.1.10; I believe that this is what the problem is that for some reason the server is listening but on on any actual IP address but on no address which is why the clients can't connect. If it worked up to Server 2012 why would it not work on Server 2016 (not R2)? This has got to be some kind of configuration problem either with the  ERA server or the servers TCP configuration. I'm gone over both and I don't see anything obvious. There has got to be an answer as to why this isn't working.

  9. On 11/20/2017 at 2:12 PM, foneil said:

    j-gray is right that our Knowledgebase and Download page only list support up to 2012 R2 for ERA 5.x, so we don't officially support Server 2016 with ERA v5. 

    So what? That means no one is even going to make an attempt to try and help me figure out why this doesn't seem to be working?

    I uninstalled and reinstalled, also I believe that I found at least part of the problem which was a different program which I uninstalled. Netstat -an now shows that port 2221 is listening but not on the IPV4 address of the server; what it shows is  "TCP    [::]:2221              [::]:0                 LISTENING", anyone have an idea why 2221 doesn't seem to be associated with the IP address of the server?

  10. On 11/16/2017 at 11:40 AM, bbahes said:

    Have you tried this article: https://support.eset.com/kb3504/?locale=en_US and sub article https://support.eset.com/kb3281/ ?

     

    I have now, but still not working; I have a feeling the problems on the server. Doing some research I found that running "Netstat -an" will give a list of ports that are listening and 2221 is not on the list so for some reason the administrative server isn't listening on that port. Also I tried telnet to the server from one of the clients "telnet 192.168.1.11:2221" and I get "Connecting To 192.168.1.10:2221...Could not open connection to the host, on port 23: Connect failed".

    I've checked the server again and the management console and as usual the Updates tab says "Provide update files via internal HTTP server" which is checked and the HTTP server port is 2221 and authentication is none.

    So if the ERA server is not working properly on Window Server 2016 Standard for some reason how do I trouble shoot it and find out why the internal HTTP server is not working?

    Netstat.txt

  11. I installed a new server to replace our old Server 2003, the new server is running server 2016. The problem I'm having is that I have everything installed and configured; the server has downloaded all the latest updates and I've turned the Windows Firewall off but not of the clients can connect and download updates from the server.

    Looking at the even log on the server I see errors happening usually either "Download Interrupted" or "Could not connect to server"; the clients are basically showing the same errors.

    I've gone through all the server and security options multiple times "Enabled unauthenticated access for Clients" is checked; the HTTP server port is set to the default of 2221 and I just can't figure out why clients can't seem to connect. Does anyone have an idea?

  12. The suggestion to delete / rename the PendingFileRenameOperations value described in hxxp://support.eset.com/kb3361/ is also suggested in knowledgebase articles of other software vendors. Weird that it didn't work for you.

    I really don't know, as I said I've checked those keys or values and they simply don't exist on this computer even though I've rebooted multiple times and rechecked them multiple times; I've been a little busy on other projects but I have to try RvW's suggestion of using the Eset Uninstaller. I'll try that tomorrow and get back to you.

  13. I had tried to update a system with Eset Endpoint Anti-virus 5 (on a Windows 8.1 machine) to the latest available version of 5 and at the end of the install (after it had uninstalled the old version) I get this message: "A system restart from a previous installation or update is pending, and that setup cannot continue" I found the support article about this problem hxxp://support.eset.com/kb3361/?viewlocale=en_USbut the thing is that none of the registry keys that it mentions HKLM\Software\Microsoft\Updates\UpdateExeVolatime or HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations or HKLMSoftware\Microsoft\Windows\CurrentVersion\Installer\InProgress seem to exist and no matter how many reboots I've done I keep getting this message. I've also tried searching the registry for these keys and they just don't exist.

     

    Does anyone have an idea how to fix this problem?

×
×
  • Create New...