Loading...

Knowledge Center


Failed to ImpersonateLoggedOnUser. Error code 718
Technical Articles ID:   KB50297
Last Modified:  12/30/2016
Rated:


Environment

McAfee Agent (MA) 5.x, 4.x
McAfee VirusScan Enterprise (VSE) 

Problem

You see the following error in the Agent_<computername>.log when you try to start UpdaterUI:
 
20060504062906  e  #xxxx  UsrSpCt  Failed to ImpersonateLoggedOnUser. Error code 718
 
NOTE: The default location for Agent_<computername>.log is C:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework\Db.

Problem

You see the following error in the UpdaterUI_<computername>.log when trying to start UpdaterUI:
 
20060525164120  I  #xxxx  AgtMon  CUpdateUIModule -- Failed to create interfaces hr=0xffffffdf

NOTE: The default location for UpdaterUI_<computername>.log is C:\Documents and Settings\<logged on account>\Local Settings\Temp\NAILogs.

System Change

Default DCOM permissions have been modified.

Solution

Reset the DCOM permissions to default settings so the McAfee services can start successfully:
  1. Click Start, Run, type gpedit.msc, and press ENTER. This launches the Group Policy Object Editor.
  2. Expand Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options.
  3. Under Security Options, double-click DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax.
  4. Click Edit Security.
  5. Select ANONYMOUS LOGON and click Allow for Local Access.
  6. Select Everyone and select Allow for Local Access and Remote Access.
  7. Click OK, and then OK again to save your changes. 
  8. Under Security Options, double-click DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax.
  9. Click Edit Security.
  10. Select Administrators and select Allow for Local Launch, Remote Launch, Local Activation and Remote Activation.
  11. Select Everyone and select Allow for Local Launch and Local Activation.
  12. Click OK, and then OK again to save your changes.
  13. Close the Group Policy Object Editor.
 

Rate this document

Did this article resolve your issue?

Please provide any comments below

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.