Enterprise Vault Event 41293 Errors - Troubleshooting Digest
Article ID: 100010866
Updated On:
Description
Error Message
The below list illustrates the most common solutions pertaining to Event 41293 / V-437-41293.
IMPORTANT: Do not edit this content in Information Manager
Internal Notes
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 e-mail to the owner or the Enterprise Vault Knowledge Management team.
Resolution
| Error Description | Article |
| Event 41293, 40966 - Indexing service start up error: Missing metadata file | 100025882 |
| Event 41293 Indexing Service start up error HRESULT 0x80004015 | 100027036 |
| Event 41293 Index Service fails to start: Compilation Error | 100008474 |
| Event 41293 Indexing Service start up error: 403 Forbidden | 100008770 |
| Event 41293 Indexing Service start up error: Cannot read configuration file | 100028401 |
| Event 41293 Indexing service fails to start: Malformed or corrupt repository.xml | 100029025 |
| Event 41293 Indexing Service fails to start: No Enterprise Vault License | 100010533 |
| Event 41293, 40966, 41312 Indexing Service start up error: Child process timeout | 100010750 |
| Event 41293 Indexing Service fails to start: Configuration Error Corrupt or malformed ASP.net cache on EV Server | 100009465 |
| Event 41293 Indexing Service fails to start: Configuration Error "The content type text/html; charset=utf-8 of the response message does not match the content type of the binding" | 100029155 |
|
Index Service fails to start with Event ID 41293 error: 8000401a |
100011350 |
Issue/Introduction
These events commonly occur when the Enterprise Vault Indexing Admin Service is unable to start or initialize properly. It can occur for numerous reasons with many accompanying event ID's.
Was this article helpful?
Yes
No
Powered by
