slarkins
-
Posts
165 -
Joined
-
Last visited
Posts posted by slarkins
-
-
All my problems started with 2254(this is the version i upgraded all my 4.x clients to when i upgraded to 5.x)...it hasnt been resolved in this version....i actually upgraded on of my bad clients to 2260....error tripped after running for 2 days...this is not WIndows update related as this pc has had windows updates turned off since January and started the error in April....the only pc's with 2260 are the ones i upgraded to try to fix the error downloading update....
...i still say something changed in the definition update packaging back in April...my standalone pc had 2254 installed for almost a year...runs 24/7...only reboot is monthly for windows updates...never had an issue....until 3 weeks ago...shut down pc to move it....8 or so days later...i got a warning about av being out of date...to my surprise....same error downloading update ...stuck for 2 days,....reboot to continue downloads...
-
I have the issue in both 5.0.2254(only about 5-6 pc's so far) AND one client i upgraded to 5.0.2260. in order to try to solve the error...after upgrading that one client to 2260(the one that seems to trip the error the most)...2 days later...same error downloading update...
....actually the first pc on my network that got this error a month ago....was a x32 WinXP pc....
I see no pattern to the problem...Win 7 x64, WinXP x32....i have pc's with update errors pointing to 2 different ERA servers...i even have a standalone pc not linked to a ERA server and downloading updates directly from ESET that got the update error once a couple of weeks ago...i upgraded that client to 2260 and havent seen the error since...it used to be pc's that didnt get rebooted for over a week but the client i upgraded to 2260 only went 2 days before it had an issue...2 observations on stuck clients...in ERA...the configuration tab for last configuration download...is hours before...usaully when the last successful signature installed....and also watching the actual update process on the client...it completes the download...then the second page...it gets as far as 1 / 2 then errors out befroe the 2 /2 completes...
-
Any updates ESET?
-
i had a similar issue on 4.5 file server endpoint....policy and end point showing no updates option chosen...but still kept popping up about os being out of date......the way i got it to go away....open windows update...then do a check for updates....thats all i had to do to make it go away....
-
Any updates on a fix? The reboot option didnt work for a couple of pc's that were off for a few days and missed many signature updates.....the only way i got them to update was to switch their update server to my other ERA server ...
-
Hopefully some log file will allow Eset to determine a fix for this....the only common factor i see for pc's on my network that have the same issue......they have gone at least 10 days since a restart...and the only fix for updates to work is to restart the computer....I have a stand alone pc with same problem...not configured with an ERA server and gets its updates directly from ESET..
-
come on eset..you need to fix this....something changed in the last month or so with regards to the update process......
-
I am thinking this is a problem with the client itself...i have a windows 7 pc...a standalone version of 5.x....configured to download directly from eset and has never been configured with any sort of policy....strictly standalone...yesterday, windows popped up a message about signatures being out of date...and it showed signature update failed...couldnt get the update to work until i rebooted....this was an upgrade over 4.x and never had an issue the 6 or so months it has been running on this pc...the only time this pc is rebooted is windows updates...the signature failure happened after 11 days since the last reboot...i am wondering if eset changed something in their definition files....??
-
what is the process to upgrade era from 5.2.x to 5.3.3? just run the install and it will upgrade automatically?
-
mine are all WIndows 7 pc's
-
I have the same probelm...submitted a support request to ESET...their answer was for me to upgrade to 6.x....i just finished upgrading my 4.x to 5.x...so that isnt an option at this time...i di notice the pc's in question are usually ones that the users doesnt restart their pc very often...
-
I manually ran my ERA updater...it now shows downloaded signature 10425 (20140916)...i have one client on a laptop who updates via internet if he cant see ERA server and he is at 10437...all the rest of my endpoints show 10435
-
I manually ran my updater...it now shows downloaded signature 10425 (20140916)...i have one client on a alptop who updates via internet if he cant see ERA server and he is at 10437...all the rest of my endpoints show 10435
-
Just downloaded update on server...then ran manual update on my laptop...i no longer receive the error....i am going to test on a few other pc's....one question....was the def # supposed to remain 8358?
"Error Downloading the Update"
in ESET Endpoint Products
Posted · Edited by slarkins
i received same instructions via support request email...i actually think your steps above were updated and changed to something a little different as i received a followup email from support with different instructions..
-Download the tracelog.exe utility from hxxp://ftp.nod.sk/~petrik/update_issues/tracelog.exe
-Run Process Monitor (Procmon.exe), click on Filter and check “Enable advanced output”
-Run Wireshark, click on Capture > Interfaces, choose the active interface and click “Start“
-Create “C:\log“ folder (it needs to exist before running the tracelog utility)
-Run the command prompt with administrator permissions from the folder where you saved the tracelog.exe utility
-In the command prompt, run this command:
tracelog -start updater -guid #f329ae9a-556d-4934-920f-234e835d9ece -f c:\log\update.etl -append -UsePerfCounter -flag 0xff -level 0xff
-At this stage, all logging has started, now go reproduce the update issue
(run the VSD update and wait till it fails, mark down the exact error and the current time along with your timezone)
....as soon as i get the error again i will do this....
getting to a point where something that should be transparent and work without issue...getting to be an awful lot of work on users ends to get your product working