Jump to content

Recommended Posts

Posted

Hello, I am getting the above topic error every time I try to update my anti-virus.

 

License ID: 33B-53E-DNP
Computer name: WALLE
Seat name: walle-1
Product name: ESET Internet Security
Product version: 12.2.23.0
Operating system: Windows 10 Home Single Language(64-bit)
Machine: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 8104 MB RAM

eis_logs.zip

  • Administrators
Posted

It looks like the communication is manipulated by your ISP. It's redirected to http://flex.vodacom.co.za/err/?err=404

The problem is the updater receives 302 Temporary redirect from your ISP instead of the standard 404 response.

Posted

Use the following settings ( received from ESET support earlier today ). Vodacom has a global problem with this.

 

1. Open ESET

2. Press F5 to open advanced setup

3. Navigate and Select Tools > Proxy Server

4. Enable Use proxy server and enter the details below

 

Proxy Server: esetsa.dedicated.co.za

Port: 5057

 

 

 

Posted (edited)
4 hours ago, JFB said:

4. Enable Use proxy server and enter the details below

Proxy Server: esetsa.dedicated.co.za

Port: 5057

Believe this will only work for South Africa. For Eset Vodacom users in other countries, it would be best to contact your local Eset customer support for the appropriate server name/port.

Edited by itman
  • Administrators
Posted

We don't have this issue reported from other countries and all 3 users who have posted in this topic are from South Africa.

Posted

I am also a vodacom client. Will try proxy server.

Posted

I followed JFB's advice - it worked! Thanks a lot. It seems a Vodacom RSA problem.

  • 2 weeks later...
Posted

WE KEEP ON GETTING THE SAME FAULT: BAD LINK TO UPDATE SERVER

 

License ID: 3AB-35C-57X
Username: EAV-0197546714
Computer name: USER-PC
Seat name: USER-PC
Product name: ESET NOD32 Antivirus
Product version: 12.0.31.0
Operating system: Windows 7 Home Premium(64-bit)
Machine: Pentium(R) Dual-Core  CPU      E5400  @ 2.70GHz

 

AFTER "ENABLED ADVANCED LOGGING" WE RECEIVED THESE FILE LOGS AND WE STILL CANNOT FIX THE PROBLEM:
 

updater_20190911_125622.etl

  • Administrators
Posted
1 hour ago, liana said:

WE KEEP ON GETTING THE SAME FAULT: BAD LINK TO UPDATE SERVER

It appears that you too use Vodacom ISP which returns 302 Moved temporarily and redirects to flex.vodacom.co.za/err/?err=404 via a relative link.

We'll make a change in updater to accommodate to this behavior, however, if they finally return 200 OK and send a custom html, update will still fail with "Update information is not consistent" error.

The ISP should correctly send 401 if a file is not found.

Posted

We can only use Vodacom 

In my help & support is no "details for customer care" 

I only see "details for technical support" and we tried that and waited 4hours. Only sent results we got.

  • Administrators
Posted

You can find it here, however, further logs are not needed since we have already narrowed it down:

image.png

Posted

IT IS THE SAME THAT I SUPPLIED IN MY FIRST REQUEST:

License ID: 3AB-35C-57X
Username: EAV-0197546714
Computer name: USER-PC
Seat name: USER-PC
Product name: ESET NOD32 Antivirus
Product version: 12.0.31.0
Operating system: Windows 7 Home Premium(64-bit)
Machine: Pentium(R) Dual-Core  CPU      E5400  @ 2.70GHz
 

  • Administrators
Posted

I merely wanted to show where advanced logging can be enabled, however, this is not needed any more since the issue has been pinpointed. The problem is with Vodafone. We'll make a little change in the updater, however, whether update will work with Vodafone then will depend on whether they'll respond correctly with 401 after redirection instead of 200 while providing a custom html notification to the updater.

Theoretically we could make a special updater.dll for your that would work with Vodafone and that you'd need to install (copy) manually in safe mode.

Posted

Thank you. How will I know if the change has been made?

I really appreciate your support!!

  • Administrators
Posted

We've made the change. Not sure if there will be another v12 build before v13 is released. V13 should have the change included. However, as I mentioned it will not help if the ISP doesn't return 401 but 200 and serves a custom html page if a url is not found.

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...