Cumulative Indexing hotfix for Symantec Enterprise Vault 10.0.0

Article:TECH172165  |  Created: 2011-10-19  |  Updated: 2014-06-24  |  Article URL http://www.symantec.com/docs/TECH172165
Article Type
Technical Solution


Issue



To which version of Symantec Enterprise Vault (tm) can this cumulative hotfix be applied?

Enterprise Vault 10.0.0  


Error



Etrack 2412185: Processes belonging to the 64bit indexing engine could potentially become blocked from communicating with one another. If this issue occurred, whilst the indexing service remained running, no indexes on the server would be contactable for search, ingest or update operations. The w3wp process hosting the 64bit indexing engine would begin to consume increasing amounts of memory, at the same time the indexing related errors would be noticed in the Enterprise Vault event log.

Etrack 2428331: Collection-service.exe processes belonging to the 64bit indexing engine could potentially become orphaned from the parent process (collection-broker.exe). If this occured whilst data was being actively ingested into the index volume, it could lead to items failing to be indexed.

Etrack 2478351: Processes belonging to the 64bit indexing engine could potentially become blocked from communicating with one another. If this issue occurred, whilst the indexing service remained running, no indexes on the server would be contactable for search, ingest or update operations. The w3wp process hosting the 64bit indexing engine would begin to consume increasing amounts of memory, at the same time the indexing related errors would be noticed in the Enterprise Vault event log.

Etrack 2376615: If ingestion was taking place whilst backup mode was being set on an index server, there was a small window of opportunity (< 1 second) where items could be added to an index after being placed into backup mode.

Etrack 2070960: Recycling the Indexing Engine Application Pool during indexing operations resulted in the Application Pool being terminated due to errors.


Solution



The 64bit indexing engine has had a number of changes added to it that addresses all of the above issues.

 

Files updated
=============
 
The following files will be updated to version 7.5.1010.2024.

Default location C:\Program Files (x86)\Enterprise Vault\EVIndexing\bin

admin.dll
axl-service.exe
axl.dll
collection-broker.exe
collection-service-dispatch.exe
collection-service.exe
converter.dll
crawler-service.exe
crawler.dll
curl.exe
datrie.dll
dispatch.exe
execute-worker.exe
gsf-1.dll
iconv.dll
indexer-service.exe
libeay32.dll
libexpat.dll
libexslt.dll
libgio-2.0-0-vs8.dll
libglib-2.0-0-vs8.dll
libgmodule-2.0-0-vs8.dll
libgobject-2.0-0-vs8.dll
libgthread-2.0-0-vs8.dll
libxml2.dll
libxslt.dll
misc.dll
query-service.exe
search-engine.dll
ssleay32.dll
thai.dll
v-cmd.exe
velocity-config.exe
velocity-shutdown.exe
velocity-startup.exe
vivisimo++.dll
vivisimo-version.dll
vivisimo-versions.exe
vivisimo.dll
zlib1.dll

Default Location C:\Program Files (x86)\Enterprise Vault\EVIndexing\www\asp\bin

admin.dll
axl.dll
charset.dll
converter.dll
crawler.dll
datrie.dll
gsf-1.dll
iconv.dll
libeay32.dll
libexpat.dll
libexslt.dll
libgio-2.0-0-vs8.dll
libglib-2.0-0-vs8.dll
libgmodule-2.0-0-vs8.dll
libgobject-2.0-0-vs8.dll
libgthread-2.0-0-vs8.dll
libxml2.dll
libxslt.dll
misc.dll
search-engine.dll
ssleay32.dll
thai.dll
Velocity.dll
vivisimo.dll
vivisimo++.dll
vivisimojava.dll
VivisimoNET.dll
vivisimo-version.dll
zlib1.dll


Installation instructions
=========================
1. Stop the Enterprise Vault Indexing services.
2. Stop the World Wide Web Publishing Service.
3. Using IIS Manager on your EV server go to the Application Pools and stop the EVIndexingPool
4. Run the "Symantec Enterprise Vault Indexing Redistributable.msi" installer packaged from the "\Files" folder in this hotfix. (Please note that "Symantec Enterprise Vault Indexing Redistributable.msi" installer will finish automatically without prompting the user that installation has finished.)
5. Start the Enterprise Vault Indexing service (this will also restart the EVIndexingPool and the World Wide Web Publishing Service).


Uninstallation instructions
===========================
This requires the new version to be uninstalled and the original version to be reinstalled:-
1. Stop the Enterprise Vault Indexing services.
2. Stop the World Wide Web Publishing Service.
3. Using IIS Manager on your EV server go to the Application Pools and stop the EVIndexingPool
4. Once all services are stopped, run the "Symantec Enterprise Vault Indexing Redistributable.msi" from the "\Files" folder in this hotfix using the uninstall option.
4. Once the uninstall has completed run the "Symantec Enterprise Vault Indexing Redistributable.msi" installer package provided in the “\Files\Original” folder in this Hotfix. (Please note that "Symantec Enterprise Vault Indexing Redistributable.msi" installer will finish automatically without prompting the user that installation has finished. All the files in the files updated list will revert to version 7.5.1010.6.)
5. Start the Enterprise Vault Indexing service (this will also restart the EVIndexingPool and the World Wide Web Publishing Service).

NOTE: It may be necessary for the Indexing service to synchronize the index volume metadata with the index repository and the directory database, this is dependent upon how much has changed between the install and uninstall.(For more information on index volume metadata and the index repository please see the following tech note http://www.symantec.com/business/support/index?page=content&id=HOWTO56259)


Supplemental Materials

SourceETrack
Value2412185
Description

Indexing engine hang


SourceETrack
Value2428331
Description

Collection processes are being orphaned


SourceETrack
Value2478351
Description

New instance Collection Broker/API Lockup


SourceETrack
Value2376615
Description

Indexes are written to after backup mode has been set


SourceETrack
Value2070960
Description

A process serving application pool 'EVIndexingPool' terminated unexpectedly warnings




Article URL http://www.symantec.com/docs/TECH172165


Terms of use for this information are found in Legal Notices