Enterprise Vault Event 2258 Errors - Troubleshooting Digest
Article ID: 100038538
Updated On:
Description
Description
Information on resolving the most common problems related to Enterprise Vault (EV) Event ID 2258 / V-437-2258. Event 2258 can occur in EV for numerous reasons with many accompanying event IDs. Event 2258 is generated when the EV Journal Task fails to start.
The table below illustrates more information about the error. Pay close attention to the event category, exception and description within the Event ID. These identifiers help determine the cause of the error and point to the resolution.
| Sample Event | Example | Description |
| Event ID | 2258 | Relates to the Veritas Enterprise Vault Error message number |
| Event or Task Category | Journal Task | Identifies the Enterprise Vault process that generated the error |
| Description | The Journal Task 'XXXX' could not be started due to startup errors. | Illustrates that a program fault occurred at the time of execution |
Solutions for Event 2258 have been separated into two distinct tables:
- Table 1: Provides technical solutions that contain Event 2258 without Event 3305
- Table 2: Provides technical solutions that contain Event 2258 in conjunction with Event 3305
| Table 1: Description of Issue | Article # |
| Event 2256, 2258 or 2949: Archiving task fails due to global catalogue connectivity issues | 100021695 |
| Event 3220 and 2256, 2258 or 2949: Archiving tasks fail during startup referring to MSMQ | 100006362 |
| Event 2256, 2258 or 2949: Archiving task fails due to incorrect SQL database configuration | 100013480 |
In addition, the below solutions referenced contain both Event 2258 along with Event 3305
| Table 2: Description of Issue | Article # |
| Event 3305 and 2256, 2258 or 2949: Archiving task fails to start due to incorrect stored credentials | 100004832 |
| Event 3305 and 2256, 2258 or 2949: Archiving task fails to connect when using a Network Load Balancer (NLB) | 100004192 |
| Event 3305 and 2256, 2258 or 2949: Varonis Auditing Software monitoring Exchange 2010 CAS Servers causing Archiving tasks to fail. | 100008499 |
| Event 3305 and 2256, 2258 or 2949: Archiving tasks fail due to corrupt or excessive number of Outlook mail profiles | 100008333 |
| Event 3305 and 2258: The Journal Archiving task and the JournalMailboxManager process get into an Exclusive Lock problem race condition | 100012379 |
IMPORTANT: Do not edit this content in Information Manager
Internal Notes
IMPORTANT: Do not edit this content in Information Manager
The content of this document is referenced in Veritas Quick Assist. Do not make changes to this article. If you would like changes to be made to this content, use the Information Manager feedback feature. Alternatively, you can send an e-mail to the owner or the Enterprise Vault Knowledge Management team DL-CS-KM
Issue/Introduction
