EMON Attempt to read configuration failed

Discussion in 'NOD32 version 2 Forum' started by sagittarius, Jan 29, 2008.

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

    sagittarius Registered Member

    Joined:
    Apr 19, 2003
    Posts:
    136
    Location:
    Queensland, Australia
    Can anybody tell me why Nod32 is repeatedly (over the course of a week or more) giving this error on somebody's computer & what can be done to stop it:

    1/30/2008 6:27:55 AM - During execution of EMON - Microsoft Outlook email monitor on the computer USERNAME, the following warning occured: Attempt to read configuration (1) failed.
     
  2. Bubba

    Bubba Updates Team

    Joined:
    Apr 15, 2002
    Posts:
    11,271
    That is sometimes caused by improper permissions for the HKLM\SOFTWARE\Eset registry key\subkeys, in particular the EMON key. Assure that the currently logged on user has read permission and local system account full access granted.
     
  3. sagittarius

    sagittarius Registered Member

    Joined:
    Apr 19, 2003
    Posts:
    136
    Location:
    Queensland, Australia
    Can you explain why would this suddenly change? It's been running fine for a couple of years and then for no explicable reason the permissions are changed.
    Does anybody know what causes things like that to happen?
     
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.