Endpoint Protection

 View Only

  • 1.  PTS has generated an error: code 11: description: Whitelist Failure

    Posted Oct 18, 2007 04:47 AM
    I have a client running WinXP Pro SP2 and they are the only one amongst 30 workstations who is receiving the following error:
     
    PTS has generated an error: code 11: description: Whitelist Failure
     
    Proactive Threat shows as "Off" and "Waiting for Update"
     
    Other SEP components seem fine.
     
    Firewall is off.
     
    Any help would be appreciated.
     
    Thanks,
    Tony


  • 2.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Oct 19, 2007 06:47 PM
    I am having exactly the same problem, but with 3 workstations. I have tried and tried re-deploy.
    I am hopping Symantec get us the proper attention on this matter.
     
     


  • 3.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Oct 19, 2007 08:23 PM
    We initially install the client without white list information. After a couple updates with an up-to-date management server, I am hoping (not too much certainty) that the white listing errors go away. Are these managed clients reporting this information? If yes, have you ensured that the management server is up to date? You can run LiveUpdate on the management server in the Admin -> Servers area. It is called something like "Download updates" or "run LiveUpdate" or "Run downloads" or something. I can boot up my server VM if you need a specific console UI path.


  • 4.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Oct 19, 2007 08:47 PM
    Thanks for the input. I would however like to point out that, as originally stated, this only appears to be occurring on one workstation out of 30 SEPS was deployed to. This would seem to go against the theory that it was either a server or centralized issue.
     
    Add to that the facts that the other workstations were fine immediately, but this one had issues even 24 hours later. I even reinstalled and it was still having the same problem 48 hours after that.
     
    Any additional thoughts would be appreciated.


  • 5.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Oct 20, 2007 01:49 PM
    Exact same problem here. Deployed SEPS to 11 workstations, 10 of them went off without a hitch and updated themselves properly. On the 11th workstation, it failed to update itself at all. I could manually update the virus definitions, but the Proactive Threat Protection is turned off and "Waiting for Updates."

    I looked in the system log and got the same error as the OP. I've tried uninstalling the client, rebooting, and reinstalling multiple times, to no avail.

    "PTS has generated an error: code 11: description: Whitelist Failure"

    Even the Symantec Tech I spent 2 hours on the phone with was confused about the problem and told me he'd get back to me with a higher level technician.

    If anyone has any information I'd be in your debt, the job is done except for the one picky client :)


  • 6.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Oct 20, 2007 02:30 PM
    Please update this post if Symantec gets back to you.:smileyhappy:


  • 7.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Oct 20, 2007 03:03 PM
    I've never had any luck with Symantec techs in the past, and since we have a basic support agreement, we get 0 weekend technical support so the earliest I'll find out anything is Monday.

    Cheers.


  • 8.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Nov 20, 2007 12:45 PM
    I had this error.  What solved it was that i had to enable Anonymous access on the Default Web Site in IIS.  It is in the Directory Security for the web site.

    Hope this helps.


  • 9.  RE: PTS has generated an error: code 11: description: Whitelist Failure

    Posted Nov 29, 2007 10:03 AM
    I have the exact same symptoms, other clients working fine, some are getting the whitelist error.
     
    Anyone else solve this?  I attempted to change IIS to Anonymous access but it is already set that way and still exhibits the same behavior.