Failed, UPDATE_VER_IS_EMPTY

Discussion in 'Other ESET Home Products' started by SmackyTheFrog, Jan 8, 2009.

Thread Status:
Not open for further replies.
  1. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    This morning I saw that a few of my remote users that pull updates directly from Eset had a newer signature than the server, so I tried to fire off an event to update the RAS only to be greeted with the message "Failed, UPDATE_VER_IS_EMPTY". Clearing the update cache didn't change this behavior. Does anyone know what is going on there?

    RAS 3.0.39
     
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    A little more info since I looked through the event log and starting around 6am this morning it began loggging the error

    Error: "Update failed, code: 4, aditional code 0x2201, aditional description UPDATE_VER_IS_EMPTY"

    every hour when it tries to update.
     
  3. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    Well it looks like the mirror servers are overloaded and failing again since I can mash the update now button and after the 13th mirror it tried it actually started pulling in the new .nup files. Fantastic.
     
  4. Nevell

    Nevell Registered Member

    Joined:
    Nov 25, 2008
    Posts:
    1
    I have the same problem in Office 2, in Office 1 update on RAS work fine! This tip don't help me :( How to fix this bug?
     
  5. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    This problem seems to crop up on days when a larger module update gets released and the update servers get hit hard. Just keep hitting update until you get a server that has capacity. Alternatively, since you have two RACs you could set up a VPN tunnel between the sites (or just the two machines) and point one to pull updates off the other in the event that you are experiencing this issue.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    This problem shouldn't occur if ERAS downloads V3 updates only.
     
  7. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    I only mirror v3 updates and have seen this behavior on August 10th, August 14th, August 15th 2008 as well as on January 8th starting at 6am EST until 12pm EST and most recently on January 28th from 6am to 7am EST.
     
  8. Geosoft

    Geosoft Registered Member

    Joined:
    Jan 7, 2009
    Posts:
    270
    Location:
    Toronto, Ontario, Canada
    I can backup SmackyTheFrog for the 28th EST:

    Code:
    [2009-01-28 06:08:08.388] V1 [4971e84b0000] [0004029c] <UPDATER_ERROR> Update failed, code: 4, aditional code 0x2201, aditional description UPDATE_VER_IS_EMPTY
    
    [2009-01-28 06:23:08.701] V1 [4971e84b0000] [0004029c] <UPDATER_ERROR> Update failed, code: 4, aditional code 0x2201, aditional description UPDATE_VER_IS_EMPTY
    
    [2009-01-28 06:53:37.919] V1 [4971e84b0000] [0004029c] <UPDATER_ERROR> Update failed, code: 4, aditional code 0x2201, aditional description UPDATE_VER_IS_EMPTY
    
    [2009-01-28 07:08:38.763] V1 [4971e84b0000] [0004029c] <UPDATER_ERROR> Update failed, code: 4, aditional code 0x2201, aditional description UPDATE_VER_IS_EMPTY
    
     
Thread Status:
Not open for further replies.