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.
The below list illustrates the most common solutions pertaining to Event 41293 / V-437-41293.
|Error with the Enterprise Vault Services after an uninstall of the Enterprise Vault Client from the server||000015723|
|Event 41293, 40966 - Indexing service start up error: Missing metadata file||000084008|
|Events 41293 and 41315 - Indexing service is failing to start after the Enterprise Vault (EV) server has been configured for anonymous connections with owauser.wsf||000081279|
|Event 41293, 41301 Indexing Service start up error: (503) Server Unavailable||000085174|
|Event 41293 Indexing Service start up error HRESULT 0x80004015||000085560|
|Event 41293 Index Service fails to start: Compilation Error||000016691|
|Event 41293 Indexing Service start up error: 403 Forbidden||000017054|
|Event 41293 Indexing Service start up error: Cannot read configuration file||000087390|
|Event 41293 Indexing service fails to start: Malformed or corrupt repository.xml||000088150|
|After cluster failover, Index Admin Service triggers Event 41293 start up error||000017982|
|Event 41293 Indexing Service fails to start: No Enterprise Vault License||000019305|
|Event 41293, 40966, 41312 Indexing Service start up error: Child process timeout||000019559|
|Event 41293 Indexing Service fails to start: Configuration Error Corrupt or malformed ASP.net cache on EV Server||000017915|
|Index Service fails to start with Event ID 41293 'An unexpected error has occurred'||000020219|
|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"||000088295|
Index Service fails to start with Event ID 41293 error: 8000401a
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):