Endpoint Protection

 View Only

  • 1.  Scan Failure Unable to Read the Configuration

    Posted Jun 05, 2014 05:40 PM

    After clicking "Active Scan" in SEP 11.0.7 on a Win7 Pro box, a popup appears with title "Symantec Endpoint Protection" that has the message "Scan Failure: Unable to read the configuration."  I searched the KB and forums but came up empty.

    Note that SEP was uninstalled/reinstalled twice where we even resorted to CleanWipe in the end which didn't make a difference.  Anyone come across this issue before?



  • 2.  RE: Scan Failure Unable to Read the Configuration

    Posted Jun 05, 2014 05:57 PM

    Can't say I've seen it. When you re-installed / ran cleanwipe, did you search for any leftover remnants in the registry or file directories because some get left behind.

    What's the exact 11.0.7 version?



  • 3.  RE: Scan Failure Unable to Read the Configuration

    Posted Jun 05, 2014 06:41 PM

    No...didn't search for any leftovers and exact version is 11.0.7400.1398.  CleanWipe is usually my last resort where I believe this is the first time ever that it didn't help.  Any guidance in all of the places to search for SEP remnants which CleanWipe might've missed?



  • 4.  RE: Scan Failure Unable to Read the Configuration

    Posted Jun 05, 2014 06:56 PM

    Usually in Program Files/Common Files

    I usually do a search of the entire reg and delete anything related to symantec



  • 5.  RE: Scan Failure Unable to Read the Configuration

    Posted Jun 09, 2014 01:54 AM

    Can you check the DCOM settings?

    http://www.symantec.com/business/support/index?page=content&id=TECH91648



  • 6.  RE: Scan Failure Unable to Read the Configuration

    Posted Jun 09, 2014 09:14 PM

    Unfortunately I can't check DCOM anymore on the affected PC since we decided to just give up and reimage the box.  However, kind of doubt this was the issue since the SEP client was indeed getting the latest virus defs from our SEPM server with a green dot on its systray icon.  It's just that if you should try kicking off an Active Scan, the described error pops up.