Phishing Shield

Discussion in 'Prevx Releases' started by puff-m-d, Nov 10, 2013.

Thread Status:
Not open for further replies.
  1. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    5,703
    Location:
    North Carolina, USA
    Hello,

    I have been seeing the following type of errors in the Log.log in the wrUrl folder:

    11/10 00:45:11:574 4708 Error: Failed to retrieve score; Error 12002 in WinHttpReceiveResponse
    11/10 00:45:11:574 4708 Error: Error processing GetPhreshPhishScore: 11/10/13 00:45:11 HTTP callback returned FALSE.
    11/10 00:45:11:574 4708 Warning: Failed to process on Phishing API (232)

    11/10 01:57:35:577 4708 Error: Failed to retrieve score; Error 12002 in WinHttpReceiveResponse
    11/10 01:57:35:577 4708 Error: Error processing GetPhreshPhishScore: 11/10/13 01:57:35 HTTP callback returned FALSE.
    11/10 01:57:35:577 4708 Warning: Failed to process on Phishing API (232)
    11/10 01:57:35:577 4708 Error: WriteNamedPipe failed Handle=000006F8 (232)
    11/10 01:57:35:577 4708 Error: ReadNamedPipe failed (6)

    Is this anything to worry about? Also, out of curiosity, I see wrPhreshPhish.dll loaded into wrsa.exe. Should it also be loaded in IE (I only ask because of the above erors I am getting in the log)? It may be a dumb question but I am just trying to get a feel for all of the new features in the new Webroot...
     
    Last edited: Nov 10, 2013
  2. PrevxHelp

    PrevxHelp Former Prevx Moderator

    Joined:
    Sep 14, 2008
    Posts:
    8,242
    Location:
    USA/UK
    The dll only needs to be loaded into WRSA, so that shouldn't be a problem. We've been making several improvements to the local and cloud-based components of the antiphishing services which I imagine will resolve this automatically, but it would still be worth us taking a closer look.

    Could you send the full log in to our support team to have them see if there is anything else which could be triggering it?

    The engine referenced in the log is a secondary engine so your actual protection isn't impacted, but it's still worth clearing up.

    Thanks!
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.