An invalid argument was encountered

Discussion in 'ESET Smart Security' started by nickster_uk, May 9, 2013.

Thread Status:
Not open for further replies.
  1. nickster_uk
    Offline

    nickster_uk Registered Member

    Hi..

    Since upgrading to v6.0.316.0 I have been seeing the following error message regularly when dealing with firewall prompts:
    Code:
    an invalid argument was encountered
    It's a little annoying as it resets the prompt window position so would appreciate a workaround or fix if possible please.

    Windows 7 Ultimate x64 SP1.

    Thanks.
  2. agoretsky
    Offline

    agoretsky Eset Staff Account

    Hello,

    Which version of ESET Smart Security did you upgrade from?

    Regards,

    Aryeh Goretsky
  3. nickster_uk
    Offline

    nickster_uk Registered Member

    Thanks for the reply Aryeh.

    The previous version installed was 6.0.308.0 but I uninstalled that version before installing the latest version.

    The problem is fairly regular and I often have to reset the window layout settings for the main gui and the firewall prompts for my user profile as well as limited users on the computer. It's extremely inconvenient.

    Thanks.
  4. agoretsky
    Offline

    agoretsky Eset Staff Account

    Hello,

    My initial guess is that the firewall's ruleset may be corrupt. Were those imported from a previously-saved configuration, or did you just start creating a new set after installing the new version of ESET Smart Security?

    Regards,

    Aryeh Goretsky
  5. nickster_uk
    Offline

    nickster_uk Registered Member

    Thanks for the reply Aryeh.

    I usually import the rules after installing the latest version.

    Looking through the rules in xml file, nothing stands out as being the problem. All the paths to files are correct, they're listed in the correct hexadecimal order.

    Is there anything in the rules in particular that may be corrupt and causing the problems please?
  6. agoretsky
    Offline

    agoretsky Eset Staff Account

    Hello,

    I would suggest opening a ticket with your local ESET office and explaining that you're having an issue with migrating the configuration. We will need to have some take a look at the rules in detail to determine why this is happening.

    Regards,

    Aryeh Goretsky
Thread Status:
Not open for further replies.