Endpoint Protection

 View Only

  • 1.  XP appears event ID 1053 after upgrade from SAV to SEP

    Posted Jul 18, 2011 05:25 AM

    - One Server 2008 (AD/DNS/DHCP Server)
    - Client: Windows XP Pro. SP3
     

    Win XP user will appear event log error ID 1053 after upgrade from SAV TO SEP 11 and then client PC cannot execute the login.bat file which is mapping network drive.  The client PC cannot map the network drive lastly. It happens on first few days when the user turn on the computer firstly on every morning. If cannot see network drive, user will need to restart computer once or twice so that he can run the login.bat.

    Event id 1053 Error
    Windows cannot determine the user or computer name. (The RPC server is unavailable).  Group Policy processing aborted

    I've check the DNS server which is under normal condition and ever re-create the host record for user. But cannot solve this problem.

    Here is my upgrade steps to upgrade to SEP for user.

    1. Upgrade the SAV directly (use remote deploy or run setup directly)

    2. Remove client from SAV console manually after client upgrade to SEP successfully.

    Anything I did wrong? Please kindly advise.



  • 2.  RE: XP appears event ID 1053 after upgrade from SAV to SEP

    Posted Jul 18, 2011 05:56 AM

    Have you installed Network threat protection component too?

    Did you check the SEP client logs and check if thats set to scan anything.



  • 3.  RE: XP appears event ID 1053 after upgrade from SAV to SEP

    Posted Jul 18, 2011 06:17 AM

    Not install Network threat protection component.

    SEP clients log wasn't find any wrong too.

    I've disabled weekly schedul full scan in policy



  • 4.  RE: XP appears event ID 1053 after upgrade from SAV to SEP
    Best Answer

    Trusted Advisor
    Posted Jul 18, 2011 07:26 AM

    Hello,

    There could be many reasons to have Event id 1053

    Please Check the Symantec Article:

    1) Unable to start SEP service , Error 1053: The service did not respond to start or control request in a timely fashion.

    https://www-secure.symantec.com/connect/articles/unable-start-sep-service-error-1053-service-did-not-respond-start-or-control-request-timely

    2) Symantec Settings Manager will not start after an infection and the command prompt will not open

     
     
    Try the steps in the Articles above, hope that might help!!!