Problem
Enterprise Vault (EV) Indexing Service fails to start. Event 41293 logged stating repository.xml file corrupt.
Error Message
Log Name: Application
Source: Enterprise Vault
Event ID: 41293
Task Category: Index Admin Service
Level: Error
Description:
warning (0 ms) - Enterprise Vault_load : XML index [C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata\repository.xml.index] is corrupt. Rebuilding. (ID: XML_INDEX_CORRUPTED)error (0 ms) - Enterprise Vault_load : Malformed XML file [C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata\repository.xml]: [junk after document element at line 1 col 77:lone="yes" ?><vce version="7.x" />+++ERROR+++> ] (ID: XML_FILE_MALFORMED) For more information, see Help and Support Center at _http://entced.symantec.com/entt?product=ev&language=english&version=10.0.2.0&build=10.0.2.1112&error=V-437-41293Event Xml
V-437-41293
Dtrace Information:
To validate if this is the issue a Dtrace is needed, please perform the following steps on the EV server that has generated Event ID 41293 while re-creating the issue.
- For more information about Enterprise Vault’s Dtrace Utility please see 100038975.
- Dtrace the EVIndexAdminService process for no less than 5 minutes while re-creating the issue.
- Open the log file created and search for either of the following the strings:
12:38:18.450 [14864] (EVIndexAdminService) <10596> EV-H {IndexingWCFProxy`1} Exception: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<html>| <head>| <title><br><br>warning (16 ms) - vivisimo_load|: XML index [C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata\repository.xml.index] is corrupt. Rebuilding. (ID: XML_INDEX_CORRUPTED)<br><br>error (16 ms) - vivisimo_load|: Malformed XML file [C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata\repository.xml]
The remote server returned an error: (500) Internal Server Error.
Cause
Corrupt Repository.xml file. To confirm, try opening the xml using internet explorer (IE).
Solution
This issue can be resolved by deleting or moving the corrupt repository.xml file away from Indexmetadata folder. Before deleting the file, save a backup copy of the file outside the Indexmetadata folder.
1. Login to affected Enterprise Vault (EV) server using Vault Service Account (VSA) credentials.
2. Stop the IIS Admin Service and World wide web publishing service OR run iisreset /stop from command prompt.
3. Move corrupt repository.xml file from the Install_Path\Enterprise Vault\EVindexing\data\indexmetadata folder.
4. Start the IIS Admin Service and World wide web publishing service OR run iisreset /start from command prompt.
5. Start the EV Indexing service.
6. Upon starting indexing service, it will recreate the repository.xml file as part of initializing process, if it isn't there. This will delay the indexing start up, which will be notified via event:
Type : Warning
Event : 41395
Source : Enterprise Vault
Category : Index Admin Service
Description: Enterprise Vault will now create the indexing metadata.
The Indexing service will be unavailable until the metadata has been created. The creation will begin immediately and may take some time to complete.
V-437-41395
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.