Video Screencast Help

Error 1921 When Upgrading from Client Security 10 to Endpoint 11

Created: 17 Dec 2007 • Updated: 21 May 2010 | 5 comments
jmb's picture

I get this message while trying to perform the upgrade as stated in the subject:
Error 1921. Service Symantec Event Manager (ccEvtMgr) could not be stopped. Verify that you have sufficient privileges to stop system services.

I have no other option but to click Cancel since retry does not work. The rollback the installer performs breaks Client Security Firewall after reboot. So I have to uninstall/reinstall that.

I manually stopped the service before trying the install with the same results.

The computer is a Dell Latitude D620 Laptop. I have not had this problem on a desktop. I've also done the upgrade on a Latitude D610 without any issue.

Comments 5 CommentsJump to latest comment

jmb's picture

More info on this from the event log. 

Event Type:    Error
Event Source:    MsiInstaller
Event Category:    None
Event ID:    11921
Date:        12/18/2007
Time:        8:54:07 AM
User:       *\Administrator
Computer:    *
Product: Symantec Client Security -- Error 1921.Service Symantec Event Manager (ccEvtMgr) could not be stopped.  Verify that you have sufficient privileges to stop system services.

For more information, see Help and Support Center at
0000: 7b 43 32 30 37 32 39 41   {C20729A
0008: 34 2d 43 38 43 32 2d 34   4-C8C2-4
0010: 44 45 33 2d 39 34 42 45   DE3-94BE
0018: 2d 35 45 33 41 32 45 39   -5E3A2E9
0020: 45 46 42 36 33 7d         EFB63}  

jmb's picture

Another update. After re-booting, and trying the install again (with broken client security still in place), the install completes. After another reboot auto protect is automatically disabled.

jmb's picture

Bumping this up. Someone must have a similar problem. Or someone from Symantec must have some type of recommendation to get around this.

I've literally searched the net for hours with no luck finding anything.

jmb's picture

I've sort of found a solution. Installing XP Sp3 release canidate, then trying the upgrade from Symantec Client Security to Endpoint protection seems to have fixed the problem.  But it's not like we are going to roll out Sp3 as soon as the final version comes out.

Anyone at Symantec reading this? Looking into the problem? Anyone at all?

Yort's picture

I too was having this problem, removing Windows Desktop Search (version 3.01), rebooting then installing seems to have done the trick.