Endpoint Protection

 View Only

  • 1.  Cannot assign a client authentication token. there was a general communication failure

    Posted Jun 02, 2022 05:18 AM
      |   view attached
    Hello all,
    After upgrading clienta sep from 14.2 to 14.3 RU3, there is an error "cannot assign a client authentication token. There was a general communication failure" (see attachment SEP Issue.png). environment: GUP: 14.3.5433.3000 SEPM: 14.3.5413.3000 SEP: 14.3.5433.3000

    Any ideas?
    Thanks,


  • 2.  RE: Cannot assign a client authentication token. there was a general communication failure
    Best Answer

    Posted Jun 03, 2022 02:43 AM
    Hi,

    Do you use EDR?

    https://knowledge.broadcom.com/external/article?articleId=240660
    Original Message


  • 3.  RE: Cannot assign a client authentication token. there was a general communication failure

    Posted Jun 03, 2022 03:48 AM
    Yes, I use. Thanks a lot,

    I will add to WL this URL.
    Original Message


  • 4.  RE: Cannot assign a client authentication token. there was a general communication failure

    Posted Sep 27, 2022 08:16 PM
    Hello.

    This issue is still persistent in RU4 (14.3.7393.4000)!
    Symantec process has high CPU usage all the time from 30 to 60%.
    Application is flooding path C:\ProgramData\Symantec\Symantec Endpoint Protection\14.3.7393.4000.105\Data\CmnClnt\ccSubSDK
    File amount is > 2000 instead of ~100 on healthy installation.

    Fresh windows installation is affected as well as existing machines.

    Is there any additional information?


    Original Message