| Event Id | 167 |
| Source | NAVMSE |
| Description | the process navesp has terminated unexpectedly |
| Event Information | According to Symantec: Solution: NAVMSE is working as designed. Explanation When a scan engine failure occurs, this generates the first message (event ID 167). Event ID: 89, <the reason for termination> is generated next. The final entry is Event ID: 168 is generated when the scan process restarts. Whenever NAVMSE encounters a scan engine failure, the scan process automatically stops and restarts. The first thing that NAVMSE will scan upon process restart will be the item that initially caused the scan engine failure. NAVMSE 2.1x contains new architecture to restart the scan process that fail automatically. Now if any processes take too long to complete, it dies and NAVMSE will then kill the process and generate a new one. |
| Reference Links | Multiple entries are made in the Windows application event log file after a scan engine failure when Norton AntiVirus for Microsoft Exchange is installed |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.