NAV 2003 and Windows XP slow startup

[Rugz]

Since Jan 7, 2004 my machine's performance during startup
has degraded significantly.

System 2.4GHz, 512MB RAM, OS: Windows XP Home Edition.

At startup, my desktop appears and my icons appear but I
cannot launch anything for aprox. 2-3 minutes afterwhich
the intro music comes on and all of the systems finally
boot and appear in the systems tray.

Uninstalling Symantec NAV 2003 solves the slow starup
problem. Reinstalling NAV 2003 (without updates, ie.
straight out the box) reintroduces the slow startup
problem. The latest "fixes" posted from Symantec
regarding CCEVTMGR.ext files and VeriSign Root
Certificates do not solve the problem either. I guess
we'll have to wait for a better solution.

Rugz.

[Tom Pepper Willett]

http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/2004010810205113

Tom
"Rugz" > wrote in message
...
| Since Jan 7, 2004 my machine's performance during startup
| has degraded significantly.
|
| System 2.4GHz, 512MB RAM, OS: Windows XP Home Edition.
|
| At startup, my desktop appears and my icons appear but I
| cannot launch anything for aprox. 2-3 minutes afterwhich
| the intro music comes on and all of the systems finally
| boot and appear in the systems tray.
|
| Uninstalling Symantec NAV 2003 solves the slow starup
| problem. Reinstalling NAV 2003 (without updates, ie.
| straight out the box) reintroduces the slow startup
| problem. The latest "fixes" posted from Symantec
| regarding CCEVTMGR.ext files and VeriSign Root
| Certificates do not solve the problem either. I guess
| we'll have to wait for a better solution.
|
| Rugz.

[Bill L.]

I have the same problem as reported here:

http://groups.google.com/groups?q=ccevtmgr&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=e47bd336.0401091259.1c8b083d%40posting.google .com&rnum=2

Once ccevtmgr.exe service start after a 2min delay, all the other
services start in XP Pro and everything is fine thereafter. I've
tried the symantec fix for the Verisign certificates but it doesn't
make any difference.

I have found one Toshiba XP Pro laptop that does not exhibit the
problem. I don't dare run LiveUpdate on it in case it breaks that
machine too.


bill

[Bill L.]

From my own tests, it is Not the Norton Live-updates which is causing
this slow boot problem. I had a PC which I had not run LiveUpdate
since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
Also, I tried de-installing and reinstalling AV2003 and still
encountered the same symtoms.

All I do know, is if I wind the date back on the PCs to before 7th
Jan, everything boots up fine.

So although Symantec's fix for the Verisign certificates may resolve
the main problem experienced by a lot of Symantec users who had
expired certificates, it does NOT resolve the problem of slow
ccevtmgr.exe startup on 'some' PCs.

I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
continues to boot up okay with no delay.

Try changing the startup mode for the Symantec Event Manager service
to 'Manual'. The service is still started, but on one of my XP PCs
running just AV2003 and no other Symantec products, it resolved the
slow ccevtmgr.exe start problem.

[Rich s]

(Bill L.) wrote in message >...
> From my own tests, it is Not the Norton Live-updates which is causing
> this slow boot problem. I had a PC which I had not run LiveUpdate
> since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> Also, I tried de-installing and reinstalling AV2003 and still
> encountered the same symtoms.
>
> All I do know, is if I wind the date back on the PCs to before 7th
> Jan, everything boots up fine.
>
> So although Symantec's fix for the Verisign certificates may resolve
> the main problem experienced by a lot of Symantec users who had
> expired certificates, it does NOT resolve the problem of slow
> ccevtmgr.exe startup on 'some' PCs.
>
> I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> continues to boot up okay with no delay.
>
> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.


Hate to say me too but me too.
I have exactly the same problem as Bill L which the work-around of
changing the event
manager service from automatic to manual seems to fix. BTW I completly
re-installed my version NAV 2003 just in case but no difference.
For what it's worth my wife has XP pro with NAV 2003 fully updated and
her machine does not exhibit the same problem as mine which has XP
Home Edition.
The problem started to occur around the same time as the versign issue
but my symptoms were different and for what it's worth I've updated
the certs and the
problem is exactly the same. Also I have trawled through every
potential solution on symantec but to no avail. For the time being I'm
content the switch of service startup from auto to manual fixes the
painfully slow boot (an extra 90 seconds so the app event log tells
me). The 90 seconds feels more like 5 minutes ;-).
What concerns me is the radomness of the problem which makes me think
I could have a currently unknown virus or some adware problem.
I love to hear from anyone who has truly nailed this problem.

[PCEngWork]

This problem of a slow boot can be the result of Norton services
not starting in the correct mode.

For Norton Internet Security 2004, You are going to have the following
start at boot, in "Automatic" mode. (MMC View)

Symantec Core LC
Symantec Event Manager
Symantec Network Drivers Service
Symantec Network Proxy
Symantec Password Validation
Symantec Settings Manager
Norton AntiVirus Auto Protect Service

However, From the Registry's CurrentControlSet you have the following
Symantec services that start as well.
ccEvtMgr
ccProxy
ccPwdSvc
ccSetMgr
These services can have one of the following Start Modes defined, If they
are changed from default values - Norton can take an excessive amount
of time to boot, as timeouts will occur.
0 Boot (Drivers Only)
1 System (Drivers Only)
2 Automatic
3 Manual
4 Disabled

This is why some machines with Nav/Nis boot fairly quickly & others with
the same installs boot poorly.

"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Bill L.]

Pleased to learn that the 'fix' appears to work for your NAV2003
installation too.

The 'fix' sadly does not work on my other desktop PC which runs
Nav2003 and Norton Firewall 2003 (separate products, not NIS2003).
I'm sure if I removed Firewall 2003 and changed the Symantec Event
Manager to start in 'Manual' mode, that would resolve the slow startup
issue on that computer too.

fwiw, both my desktops and my laptop run XP Pro, so I personally don't
think the issue has anything to do with whether one has the Home or
Professional edition.

Clearly since the 7th Jan, the ccevtmgr.exe has become more
temperamental on startup on certain PC builds. Winding the clock back
on our affected PCs to any date before the 7th Jan definitely cures
the startup problem, but we certainly should Not have to do this.

All we can do is hope Symantec take notice and issue an updated
version of ccevtmgr.exe.

[capt]

Symantec has posted a fix for this (?) problem. It worked for me. Click here
http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
or search their site for document ID 2003100708212113. Good luck...


"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Adam]

(Bill L.) wrote in message >...

> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.

This worked for me. No more delay at startup.

[Bill L.]

Yes, I am aware of this knowledgebase article that referred to a
similar problem which afflicted ccevtmgr.exe version 1.09. But
myself and other Symantec users have the current version 1.0.3.4 and
at present, there is no newer version since the 7th Jan 2004.

[Bill L.]

hi

if you already have v1.0.3.4, this is the most current version.

[Rich s]

(Bill L.) wrote in message >...
> From my own tests, it is Not the Norton Live-updates which is causing
> this slow boot problem. I had a PC which I had not run LiveUpdate
> since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> Also, I tried de-installing and reinstalling AV2003 and still
> encountered the same symtoms.
>
> All I do know, is if I wind the date back on the PCs to before 7th
> Jan, everything boots up fine.
>
> So although Symantec's fix for the Verisign certificates may resolve
> the main problem experienced by a lot of Symantec users who had
> expired certificates, it does NOT resolve the problem of slow
> ccevtmgr.exe startup on 'some' PCs.
>
> I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> continues to boot up okay with no delay.
>
> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.


Hate to say me too but me too.
I have exactly the same problem as Bill L which the work-around of
changing the event
manager service from automatic to manual seems to fix. BTW I completly
re-installed my version NAV 2003 just in case but no difference.
For what it's worth my wife has XP pro with NAV 2003 fully updated and
her machine does not exhibit the same problem as mine which has XP
Home Edition.
The problem started to occur around the same time as the versign issue
but my symptoms were different and for what it's worth I've updated
the certs and the
problem is exactly the same. Also I have trawled through every
potential solution on symantec but to no avail. For the time being I'm
content the switch of service startup from auto to manual fixes the
painfully slow boot (an extra 90 seconds so the app event log tells
me). The 90 seconds feels more like 5 minutes ;-).
What concerns me is the radomness of the problem which makes me think
I could have a currently unknown virus or some adware problem.
I love to hear from anyone who has truly nailed this problem.

[PCEngWork]

This problem of a slow boot can be the result of Norton services
not starting in the correct mode.

For Norton Internet Security 2004, You are going to have the following
start at boot, in "Automatic" mode. (MMC View)

Symantec Core LC
Symantec Event Manager
Symantec Network Drivers Service
Symantec Network Proxy
Symantec Password Validation
Symantec Settings Manager
Norton AntiVirus Auto Protect Service

However, From the Registry's CurrentControlSet you have the following
Symantec services that start as well.
ccEvtMgr
ccProxy
ccPwdSvc
ccSetMgr
These services can have one of the following Start Modes defined, If they
are changed from default values - Norton can take an excessive amount
of time to boot, as timeouts will occur.
0 Boot (Drivers Only)
1 System (Drivers Only)
2 Automatic
3 Manual
4 Disabled

This is why some machines with Nav/Nis boot fairly quickly & others with
the same installs boot poorly.

"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Bill L.]

Pleased to learn that the 'fix' appears to work for your NAV2003
installation too.

The 'fix' sadly does not work on my other desktop PC which runs
Nav2003 and Norton Firewall 2003 (separate products, not NIS2003).
I'm sure if I removed Firewall 2003 and changed the Symantec Event
Manager to start in 'Manual' mode, that would resolve the slow startup
issue on that computer too.

fwiw, both my desktops and my laptop run XP Pro, so I personally don't
think the issue has anything to do with whether one has the Home or
Professional edition.

Clearly since the 7th Jan, the ccevtmgr.exe has become more
temperamental on startup on certain PC builds. Winding the clock back
on our affected PCs to any date before the 7th Jan definitely cures
the startup problem, but we certainly should Not have to do this.

All we can do is hope Symantec take notice and issue an updated
version of ccevtmgr.exe.

[capt]

Symantec has posted a fix for this (?) problem. It worked for me. Click here
http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
or search their site for document ID 2003100708212113. Good luck...


"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Adam]

(Bill L.) wrote in message >...

> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.

This worked for me. No more delay at startup.

[Rich s]

(Bill L.) wrote in message >...
> From my own tests, it is Not the Norton Live-updates which is causing
> this slow boot problem. I had a PC which I had not run LiveUpdate
> since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> Also, I tried de-installing and reinstalling AV2003 and still
> encountered the same symtoms.
>
> All I do know, is if I wind the date back on the PCs to before 7th
> Jan, everything boots up fine.
>
> So although Symantec's fix for the Verisign certificates may resolve
> the main problem experienced by a lot of Symantec users who had
> expired certificates, it does NOT resolve the problem of slow
> ccevtmgr.exe startup on 'some' PCs.
>
> I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> continues to boot up okay with no delay.
>
> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.


Hate to say me too but me too.
I have exactly the same problem as Bill L which the work-around of
changing the event
manager service from automatic to manual seems to fix. BTW I completly
re-installed my version NAV 2003 just in case but no difference.
For what it's worth my wife has XP pro with NAV 2003 fully updated and
her machine does not exhibit the same problem as mine which has XP
Home Edition.
The problem started to occur around the same time as the versign issue
but my symptoms were different and for what it's worth I've updated
the certs and the
problem is exactly the same. Also I have trawled through every
potential solution on symantec but to no avail. For the time being I'm
content the switch of service startup from auto to manual fixes the
painfully slow boot (an extra 90 seconds so the app event log tells
me). The 90 seconds feels more like 5 minutes ;-).
What concerns me is the radomness of the problem which makes me think
I could have a currently unknown virus or some adware problem.
I love to hear from anyone who has truly nailed this problem.

[PCEngWork]

This problem of a slow boot can be the result of Norton services
not starting in the correct mode.

For Norton Internet Security 2004, You are going to have the following
start at boot, in "Automatic" mode. (MMC View)

Symantec Core LC
Symantec Event Manager
Symantec Network Drivers Service
Symantec Network Proxy
Symantec Password Validation
Symantec Settings Manager
Norton AntiVirus Auto Protect Service

However, From the Registry's CurrentControlSet you have the following
Symantec services that start as well.
ccEvtMgr
ccProxy
ccPwdSvc
ccSetMgr
These services can have one of the following Start Modes defined, If they
are changed from default values - Norton can take an excessive amount
of time to boot, as timeouts will occur.
0 Boot (Drivers Only)
1 System (Drivers Only)
2 Automatic
3 Manual
4 Disabled

This is why some machines with Nav/Nis boot fairly quickly & others with
the same installs boot poorly.

"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Bill L.]

Pleased to learn that the 'fix' appears to work for your NAV2003
installation too.

The 'fix' sadly does not work on my other desktop PC which runs
Nav2003 and Norton Firewall 2003 (separate products, not NIS2003).
I'm sure if I removed Firewall 2003 and changed the Symantec Event
Manager to start in 'Manual' mode, that would resolve the slow startup
issue on that computer too.

fwiw, both my desktops and my laptop run XP Pro, so I personally don't
think the issue has anything to do with whether one has the Home or
Professional edition.

Clearly since the 7th Jan, the ccevtmgr.exe has become more
temperamental on startup on certain PC builds. Winding the clock back
on our affected PCs to any date before the 7th Jan definitely cures
the startup problem, but we certainly should Not have to do this.

All we can do is hope Symantec take notice and issue an updated
version of ccevtmgr.exe.

[capt]

Symantec has posted a fix for this (?) problem. It worked for me. Click here
http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
or search their site for document ID 2003100708212113. Good luck...


"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Bill L.]

Yes, I am aware of this knowledgebase article that referred to a
similar problem which afflicted ccevtmgr.exe version 1.09. But
myself and other Symantec users have the current version 1.0.3.4 and
at present, there is no newer version since the 7th Jan 2004.

[Bill L.]

hi

if you already have v1.0.3.4, this is the most current version.

[Rich s]

Thanks. I read about this problem but I already have the latest
version which off the top of my head is 1.0.3.4.

"capt" > wrote in message >...
> Symantec has posted a fix for this (?) problem. It worked for me. Click here
> http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
> or search their site for document ID 2003100708212113. Good luck...
>
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Rich s]

Thanks for the explanation which I agree could cause the difference in
boot speed but it's not the problem on my machine. NAV has been
running OK for months. I have not modified it at all, virus updates
are configured to auto install and that's about it. One day the booted
fine and next day it didn't. I don't think I even used the machine
during that period. I'm one of those people that needs to know "why".
As soon as I switch ccevtmgr back to auto the delay returns whereas my
wifes machine with the same NAV config works fine with ccevtmgr set to
auto. Bill's solution works for me although it doesn't explain the
mystery of where the problem came from in the first place. It almost
seems like a residual effect of the verisign problem but my certs are
all ok.


"PCEngWork" > wrote in message et>...
> This problem of a slow boot can be the result of Norton services
> not starting in the correct mode.
>
> For Norton Internet Security 2004, You are going to have the following
> start at boot, in "Automatic" mode. (MMC View)
>
> Symantec Core LC
> Symantec Event Manager
> Symantec Network Drivers Service
> Symantec Network Proxy
> Symantec Password Validation
> Symantec Settings Manager
> Norton AntiVirus Auto Protect Service
>
> However, From the Registry's CurrentControlSet you have the following
> Symantec services that start as well.
> ccEvtMgr
> ccProxy
> ccPwdSvc
> ccSetMgr
> These services can have one of the following Start Modes defined, If they
> are changed from default values - Norton can take an excessive amount
> of time to boot, as timeouts will occur.
> 0 Boot (Drivers Only)
> 1 System (Drivers Only)
> 2 Automatic
> 3 Manual
> 4 Disabled
>
> This is why some machines with Nav/Nis boot fairly quickly & others with
> the same installs boot poorly.
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Rich s]

(Bill L.) wrote in message >...
> From my own tests, it is Not the Norton Live-updates which is causing
> this slow boot problem. I had a PC which I had not run LiveUpdate
> since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> Also, I tried de-installing and reinstalling AV2003 and still
> encountered the same symtoms.
>
> All I do know, is if I wind the date back on the PCs to before 7th
> Jan, everything boots up fine.
>
> So although Symantec's fix for the Verisign certificates may resolve
> the main problem experienced by a lot of Symantec users who had
> expired certificates, it does NOT resolve the problem of slow
> ccevtmgr.exe startup on 'some' PCs.
>
> I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> continues to boot up okay with no delay.
>
> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.


Hate to say me too but me too.
I have exactly the same problem as Bill L which the work-around of
changing the event
manager service from automatic to manual seems to fix. BTW I completly
re-installed my version NAV 2003 just in case but no difference.
For what it's worth my wife has XP pro with NAV 2003 fully updated and
her machine does not exhibit the same problem as mine which has XP
Home Edition.
The problem started to occur around the same time as the versign issue
but my symptoms were different and for what it's worth I've updated
the certs and the
problem is exactly the same. Also I have trawled through every
potential solution on symantec but to no avail. For the time being I'm
content the switch of service startup from auto to manual fixes the
painfully slow boot (an extra 90 seconds so the app event log tells
me). The 90 seconds feels more like 5 minutes ;-).
What concerns me is the radomness of the problem which makes me think
I could have a currently unknown virus or some adware problem.
I love to hear from anyone who has truly nailed this problem.

[PCEngWork]

This problem of a slow boot can be the result of Norton services
not starting in the correct mode.

For Norton Internet Security 2004, You are going to have the following
start at boot, in "Automatic" mode. (MMC View)

Symantec Core LC
Symantec Event Manager
Symantec Network Drivers Service
Symantec Network Proxy
Symantec Password Validation
Symantec Settings Manager
Norton AntiVirus Auto Protect Service

However, From the Registry's CurrentControlSet you have the following
Symantec services that start as well.
ccEvtMgr
ccProxy
ccPwdSvc
ccSetMgr
These services can have one of the following Start Modes defined, If they
are changed from default values - Norton can take an excessive amount
of time to boot, as timeouts will occur.
0 Boot (Drivers Only)
1 System (Drivers Only)
2 Automatic
3 Manual
4 Disabled

This is why some machines with Nav/Nis boot fairly quickly & others with
the same installs boot poorly.

"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Adam]

(Bill L.) wrote in message >...

> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.

This worked for me. No more delay at startup.

[Bill L.]

Pleased to learn that the 'fix' appears to work for your NAV2003
installation too.

The 'fix' sadly does not work on my other desktop PC which runs
Nav2003 and Norton Firewall 2003 (separate products, not NIS2003).
I'm sure if I removed Firewall 2003 and changed the Symantec Event
Manager to start in 'Manual' mode, that would resolve the slow startup
issue on that computer too.

fwiw, both my desktops and my laptop run XP Pro, so I personally don't
think the issue has anything to do with whether one has the Home or
Professional edition.

Clearly since the 7th Jan, the ccevtmgr.exe has become more
temperamental on startup on certain PC builds. Winding the clock back
on our affected PCs to any date before the 7th Jan definitely cures
the startup problem, but we certainly should Not have to do this.

All we can do is hope Symantec take notice and issue an updated
version of ccevtmgr.exe.

[capt]

Symantec has posted a fix for this (?) problem. It worked for me. Click here
http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
or search their site for document ID 2003100708212113. Good luck...


"Rich s" > wrote in message
om...
> (Bill L.) wrote in message
>...
> > From my own tests, it is Not the Norton Live-updates which is causing
> > this slow boot problem. I had a PC which I had not run LiveUpdate
> > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > Also, I tried de-installing and reinstalling AV2003 and still
> > encountered the same symtoms.
> >
> > All I do know, is if I wind the date back on the PCs to before 7th
> > Jan, everything boots up fine.
> >
> > So although Symantec's fix for the Verisign certificates may resolve
> > the main problem experienced by a lot of Symantec users who had
> > expired certificates, it does NOT resolve the problem of slow
> > ccevtmgr.exe startup on 'some' PCs.
> >
> > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > continues to boot up okay with no delay.
> >
> > Try changing the startup mode for the Symantec Event Manager service
> > to 'Manual'. The service is still started, but on one of my XP PCs
> > running just AV2003 and no other Symantec products, it resolved the
> > slow ccevtmgr.exe start problem.
>
>
> Hate to say me too but me too.
> I have exactly the same problem as Bill L which the work-around of
> changing the event
> manager service from automatic to manual seems to fix. BTW I completly
> re-installed my version NAV 2003 just in case but no difference.
> For what it's worth my wife has XP pro with NAV 2003 fully updated and
> her machine does not exhibit the same problem as mine which has XP
> Home Edition.
> The problem started to occur around the same time as the versign issue
> but my symptoms were different and for what it's worth I've updated
> the certs and the
> problem is exactly the same. Also I have trawled through every
> potential solution on symantec but to no avail. For the time being I'm
> content the switch of service startup from auto to manual fixes the
> painfully slow boot (an extra 90 seconds so the app event log tells
> me). The 90 seconds feels more like 5 minutes ;-).
> What concerns me is the radomness of the problem which makes me think
> I could have a currently unknown virus or some adware problem.
> I love to hear from anyone who has truly nailed this problem.

[Bill L.]

Yes, I am aware of this knowledgebase article that referred to a
similar problem which afflicted ccevtmgr.exe version 1.09. But
myself and other Symantec users have the current version 1.0.3.4 and
at present, there is no newer version since the 7th Jan 2004.

[Bill L.]

hi

if you already have v1.0.3.4, this is the most current version.

[Adam]

(Bill L.) wrote in message >...

> Try changing the startup mode for the Symantec Event Manager service
> to 'Manual'. The service is still started, but on one of my XP PCs
> running just AV2003 and no other Symantec products, it resolved the
> slow ccevtmgr.exe start problem.

This worked for me. No more delay at startup.

[Bill L.]

Yes, I am aware of this knowledgebase article that referred to a
similar problem which afflicted ccevtmgr.exe version 1.09. But
myself and other Symantec users have the current version 1.0.3.4 and
at present, there is no newer version since the 7th Jan 2004.

[Bill L.]

hi

if you already have v1.0.3.4, this is the most current version.

[Rich s]

Thanks. I read about this problem but I already have the latest
version which off the top of my head is 1.0.3.4.

"capt" > wrote in message >...
> Symantec has posted a fix for this (?) problem. It worked for me. Click here
> http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
> or search their site for document ID 2003100708212113. Good luck...
>
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Rich s]

Thanks for the explanation which I agree could cause the difference in
boot speed but it's not the problem on my machine. NAV has been
running OK for months. I have not modified it at all, virus updates
are configured to auto install and that's about it. One day the booted
fine and next day it didn't. I don't think I even used the machine
during that period. I'm one of those people that needs to know "why".
As soon as I switch ccevtmgr back to auto the delay returns whereas my
wifes machine with the same NAV config works fine with ccevtmgr set to
auto. Bill's solution works for me although it doesn't explain the
mystery of where the problem came from in the first place. It almost
seems like a residual effect of the verisign problem but my certs are
all ok.


"PCEngWork" > wrote in message et>...
> This problem of a slow boot can be the result of Norton services
> not starting in the correct mode.
>
> For Norton Internet Security 2004, You are going to have the following
> start at boot, in "Automatic" mode. (MMC View)
>
> Symantec Core LC
> Symantec Event Manager
> Symantec Network Drivers Service
> Symantec Network Proxy
> Symantec Password Validation
> Symantec Settings Manager
> Norton AntiVirus Auto Protect Service
>
> However, From the Registry's CurrentControlSet you have the following
> Symantec services that start as well.
> ccEvtMgr
> ccProxy
> ccPwdSvc
> ccSetMgr
> These services can have one of the following Start Modes defined, If they
> are changed from default values - Norton can take an excessive amount
> of time to boot, as timeouts will occur.
> 0 Boot (Drivers Only)
> 1 System (Drivers Only)
> 2 Automatic
> 3 Manual
> 4 Disabled
>
> This is why some machines with Nav/Nis boot fairly quickly & others with
> the same installs boot poorly.
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Rich s]

Thanks. I read about this problem but I already have the latest
version which off the top of my head is 1.0.3.4.

"capt" > wrote in message >...
> Symantec has posted a fix for this (?) problem. It worked for me. Click here
> http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
> or search their site for document ID 2003100708212113. Good luck...
>
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Rich s]

Thanks for the explanation which I agree could cause the difference in
boot speed but it's not the problem on my machine. NAV has been
running OK for months. I have not modified it at all, virus updates
are configured to auto install and that's about it. One day the booted
fine and next day it didn't. I don't think I even used the machine
during that period. I'm one of those people that needs to know "why".
As soon as I switch ccevtmgr back to auto the delay returns whereas my
wifes machine with the same NAV config works fine with ccevtmgr set to
auto. Bill's solution works for me although it doesn't explain the
mystery of where the problem came from in the first place. It almost
seems like a residual effect of the verisign problem but my certs are
all ok.


"PCEngWork" > wrote in message et>...
> This problem of a slow boot can be the result of Norton services
> not starting in the correct mode.
>
> For Norton Internet Security 2004, You are going to have the following
> start at boot, in "Automatic" mode. (MMC View)
>
> Symantec Core LC
> Symantec Event Manager
> Symantec Network Drivers Service
> Symantec Network Proxy
> Symantec Password Validation
> Symantec Settings Manager
> Norton AntiVirus Auto Protect Service
>
> However, From the Registry's CurrentControlSet you have the following
> Symantec services that start as well.
> ccEvtMgr
> ccProxy
> ccPwdSvc
> ccSetMgr
> These services can have one of the following Start Modes defined, If they
> are changed from default values - Norton can take an excessive amount
> of time to boot, as timeouts will occur.
> 0 Boot (Drivers Only)
> 1 System (Drivers Only)
> 2 Automatic
> 3 Manual
> 4 Disabled
>
> This is why some machines with Nav/Nis boot fairly quickly & others with
> the same installs boot poorly.
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Rich s]

Thanks. I read about this problem but I already have the latest
version which off the top of my head is 1.0.3.4.

"capt" > wrote in message >...
> Symantec has posted a fix for this (?) problem. It worked for me. Click here
> http://service1.symantec.com/SUPPORT/sharedtech.nsf/d3c44a1678bd8f45852566aa005902cb/89410544230ada0888256db800538813?OpenDocument&prod=Norton%20Utilities&ver=for%20Norton%20SystemWorks%202003&src=sg&pcode=nu&svy=&csm=no
> or search their site for document ID 2003100708212113. Good luck...
>
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Rich s]

Thanks for the explanation which I agree could cause the difference in
boot speed but it's not the problem on my machine. NAV has been
running OK for months. I have not modified it at all, virus updates
are configured to auto install and that's about it. One day the booted
fine and next day it didn't. I don't think I even used the machine
during that period. I'm one of those people that needs to know "why".
As soon as I switch ccevtmgr back to auto the delay returns whereas my
wifes machine with the same NAV config works fine with ccevtmgr set to
auto. Bill's solution works for me although it doesn't explain the
mystery of where the problem came from in the first place. It almost
seems like a residual effect of the verisign problem but my certs are
all ok.


"PCEngWork" > wrote in message et>...
> This problem of a slow boot can be the result of Norton services
> not starting in the correct mode.
>
> For Norton Internet Security 2004, You are going to have the following
> start at boot, in "Automatic" mode. (MMC View)
>
> Symantec Core LC
> Symantec Event Manager
> Symantec Network Drivers Service
> Symantec Network Proxy
> Symantec Password Validation
> Symantec Settings Manager
> Norton AntiVirus Auto Protect Service
>
> However, From the Registry's CurrentControlSet you have the following
> Symantec services that start as well.
> ccEvtMgr
> ccProxy
> ccPwdSvc
> ccSetMgr
> These services can have one of the following Start Modes defined, If they
> are changed from default values - Norton can take an excessive amount
> of time to boot, as timeouts will occur.
> 0 Boot (Drivers Only)
> 1 System (Drivers Only)
> 2 Automatic
> 3 Manual
> 4 Disabled
>
> This is why some machines with Nav/Nis boot fairly quickly & others with
> the same installs boot poorly.
>
> "Rich s" > wrote in message
> om...
> > (Bill L.) wrote in message
> >...
> > > From my own tests, it is Not the Norton Live-updates which is causing
> > > this slow boot problem. I had a PC which I had not run LiveUpdate
> > > since Xmas, and that exhibits the same 2min delay start of ccevtmgr.
> > > Also, I tried de-installing and reinstalling AV2003 and still
> > > encountered the same symtoms.
> > >
> > > All I do know, is if I wind the date back on the PCs to before 7th
> > > Jan, everything boots up fine.
> > >
> > > So although Symantec's fix for the Verisign certificates may resolve
> > > the main problem experienced by a lot of Symantec users who had
> > > expired certificates, it does NOT resolve the problem of slow
> > > ccevtmgr.exe startup on 'some' PCs.
> > >
> > > I have since run LiveUpdate on the XP Pro laptop, and fortunately, it
> > > continues to boot up okay with no delay.
> > >
> > > Try changing the startup mode for the Symantec Event Manager service
> > > to 'Manual'. The service is still started, but on one of my XP PCs
> > > running just AV2003 and no other Symantec products, it resolved the
> > > slow ccevtmgr.exe start problem.
> >
> >
> > Hate to say me too but me too.
> > I have exactly the same problem as Bill L which the work-around of
> > changing the event
> > manager service from automatic to manual seems to fix. BTW I completly
> > re-installed my version NAV 2003 just in case but no difference.
> > For what it's worth my wife has XP pro with NAV 2003 fully updated and
> > her machine does not exhibit the same problem as mine which has XP
> > Home Edition.
> > The problem started to occur around the same time as the versign issue
> > but my symptoms were different and for what it's worth I've updated
> > the certs and the
> > problem is exactly the same. Also I have trawled through every
> > potential solution on symantec but to no avail. For the time being I'm
> > content the switch of service startup from auto to manual fixes the
> > painfully slow boot (an extra 90 seconds so the app event log tells
> > me). The 90 seconds feels more like 5 minutes ;-).
> > What concerns me is the radomness of the problem which makes me think
> > I could have a currently unknown virus or some adware problem.
> > I love to hear from anyone who has truly nailed this problem.

[Bill L.]

I have the same configuration as you, NAV2003 and NPF2003. I still
have not been able to resolve the slow start up problem too.

Removing NPF2003 and changing the ccevtmgr service to start in manual
mode appears to be the only workaround for NAV2003 left on the
machine.

[Bill L.]

I've sent an email to symantec and referred this thread to them.

If I hear anything positive, I'll post here.

bill

[spark]

Have the exact same problem which occurred on or about 1/7/2004. Hopefully someone brighter than I is able to figure this one out

[Gandalf]

I have NAV2003 and NPF2003, tried all the workarounds (service set to manual, update ccevtmgr etc.) but nothing is helping.
Any news about this problem?

[Bill L.]

I got an email from Symantec four days ago. Unfortunately, their
suggestion of booting up with various services disabled using MSCONFIG
utility, then running Live Update did not resolve the problem.

I'm awaiting for another response from them but I don't hold much
hope.

In the mean time, I've removed NPF2003 and installed the free version
of Zone Alarm. I have left NAV2003 installed and changed the Symantec
Event Manager service to start in 'Manual', to resolve the startup
delay issue on my PCs.

In fact, since replacing NPF2003 with ZA, I've noticed my webpage
browsing appears to be faster on my 600k broadband internet access.


b

[johnc]

I had the same problem and am awaiting a reply from Symantec but I tried the suggestions of altering Symantec Event Manager(in services) from Auto to Manual and also Symantec Password Validation Service from Manual to Auto.After a reboot - Hey Presto every
thing back to normal.

[Trevor Pinnington]

Hi Bill,

After weeks of tearing my hair out over this problem, I believe I may
have found a solution.

Downloading and installing all the certificates from the following
location has resolved the 90sec boot pause on one of my customer's
computers:

https://www.verisign.com/support/roots.zip

I hope this solves the problem for you too!

Regards,

Trevor Pinnington.

---

(Bill L.) wrote in message >...
> I got an email from Symantec four days ago. Unfortunately, their
> suggestion of booting up with various services disabled using MSCONFIG
> utility, then running Live Update did not resolve the problem.
>
> I'm awaiting for another response from them but I don't hold much
> hope.
>
> In the mean time, I've removed NPF2003 and installed the free version
> of Zone Alarm. I have left NAV2003 installed and changed the Symantec
> Event Manager service to start in 'Manual', to resolve the startup
> delay issue on my PCs.
>
> In fact, since replacing NPF2003 with ZA, I've noticed my webpage
> browsing appears to be faster on my 600k broadband internet access.
>
>
> b

[Bill L.]

Thanks Trevor for the tip, I will try this next time I need to rebuild
my XPpro PC and reinstall NAV2003 and/or NPF2003.

Following your posting, I checked my PC which only now runs NAV2003 (I
did have NPF2003 installed too) and have observed when I have the
Symantec Event Manager set to 'automatic', I do NOT see the 90sec
startup delay which was a problem previously. I can only speculate
that perhaps Symantec may have addressed the problem through a recent
LiveUpdate.


bill