Enterprise Vault (EV) Indexing Service fails to start due to a class not being registered.

book

Article ID: 100029013

calendar_today

Updated On:

Description

Error Message

Indexing service failed. Reason: Class not registered.

Indexing engine exception.

The Index Volume Processor could not complete all the required startup routines: System.ServiceModel.AddressAlreadyInUseException: Cannot listen on pipe name 'net.pipe://localhost/TaskProcessor/' because another pipe endpoint is already listening on that name. ---> System.IO.PipeException: Cannot listen on pipe name 'net.pipe://localhost/TaskProcessor/' because another pipe endpoint is already listening on that name.

Cause

This issue can be caused if Microsoft .NET Framework 4.0 is installed on the EV server. Currently, this version of Microsoft .NET Framework is not supported for EV. See the compatibility charts for current support details. The link to the charts is provided in the Related Articles section of this article.

Resolution

Determine what versions of .NET framework are installed on the EV servers.

To do this check the following registry key which will list all versions installed:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP

Alternatively open up a command prompt and type the following command to determine the .NET versions:

dir %WINDIR%\Microsoft.NET\Framework\*.* /ad

If .NET 4.0 is installed, it needs to be uninstalled.

Finally confirm that .NET 3.5 SP1 is installed.

Note:- Microsoft may need to be engaged to determine if uninstalling .NET 4.0 would affect other components on the Windows servers (such as clustering).

 

 

Issue/Introduction

The EV Indexing Service in versions 10.x.x fails to start with the errors below generated in the EV Event Log.