'X' in the scan log

Discussion in 'Prevx Releases' started by jmc777, Sep 4, 2010.

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

    jmc777 Registered Member

    Joined:
    Aug 6, 2004
    Posts:
    244
    What does that mean? Couldn't be verified? I have a metric ton of them in my scan log.
     
  2. Triple Helix

    Triple Helix Webroot Product Advisor

    Joined:
    Nov 20, 2004
    Posts:
    12,014
    Location:
    Ontario, Canada
    Could you post a couple of lines from the log that have the X?

    TIA,

    TH
     
  3. jmc777

    jmc777 Registered Member

    Joined:
    Aug 6, 2004
    Posts:
    244
    Sure. The initial learning scan took 5mins 50secs — which is unusual!


    Edit: Uninstalled/reinstalled and everything's back to normal. Weird.
     
    Last edited: Sep 4, 2010
  4. Triple Helix

    Triple Helix Webroot Product Advisor

    Joined:
    Nov 20, 2004
    Posts:
    12,014
    Location:
    Ontario, Canada
    Interesting we will see what Joe has to say! ;)

    Thanks,

    TH
     
  5. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    Yes - this means that the file couldn't be verified. This would likely be caused from a firewall blocking Prevx. If the reinstall has cleared it up, everything should be working properly now :)
     
  6. Clive T

    Clive T Registered Member

    Joined:
    Dec 24, 2002
    Posts:
    189
    Location:
    Kent, UK
    I don't know if there is a list of these codes anywhere - I can't find one and it would be useful to have a reference to them handy.
     
  7. jmc777

    jmc777 Registered Member

    Joined:
    Aug 6, 2004
    Posts:
    244
    It must have been some kind of network issue, as Windows Firewall wouldn't have blocked anything at my end. Was there any issues at Prevx last night at 23:35? I ask because the log is nothing but X's and U's, which would suggest that some kind of communication took place (but genuinely good Windows files were marked 'U' in the log). I'll attach the entire log: View attachment scan.log

    Edit: Event Viewer suggests that the problem was at my end. There was an entry relating to my network adapter at 23:31:27, which would have happened during the scan.


    This post explains some of them.
     
    Last edited: Sep 5, 2010
  8. Triple Helix

    Triple Helix Webroot Product Advisor

    Joined:
    Nov 20, 2004
    Posts:
    12,014
    Location:
    Ontario, Canada
    The codes are for Prevx internal use to help users if they have problems they don't mean much to the end user. Here is a post with most mentioned: https://www.wilderssecurity.com/showpost.php?p=1510147&postcount=2

    TH

    EDIT: jmc777 beat me to the link! ;)
     
  9. Clive T

    Clive T Registered Member

    Joined:
    Dec 24, 2002
    Posts:
    189
    Location:
    Kent, UK
    Thanks for the link both of you! Thanks for the link both of you! (Stereo response)
     
Thread Status:
Not open for further replies.