EV indexing will not start after new installation

book

Article ID: 100047096

calendar_today

Updated On:

Description

Error Message

 

IIS 10.0 Detailed Error - 500.19 - Internal Server Error

"The type "System.ServiceModel.Activation.HttpModule" in the assembly "System.ServiceModel, Version = 3.0.0.0, Culture = neutral, PublicKeyToken = b77a5c561934e089" could not be loaded.Description: Unhandled exception when executing the current web request. Check the batch monitor for more information about this error and to determine where the error was caused in the code.Exception details: System.TypeLoadException: The type "System.ServiceModel.Activation.HttpModule" in the assembly "System.ServiceModel, Version = 3.0.0.0, Culture = neutral, PublicKeyToken = b77a5c561934e089" could not be loaded."

 

Cause

 

This can be down to a problem within the ApplicationHost.Config file, for Windows Process Activation, found in the below location on the EV Server:- %windir%\System32\Inetsrv\config and the missing Registry Key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\SkipTempFolderCheck

 

Resolution

 

The issue is resolved with the article 100034309
and by adding the registry key:

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS
Name: SkipTempFolderCheck
Type: DWORD32
Value: 0 (checks enabled), 1 (checks disabled)

The EVAdminService can be started successfully after following the steps from the article and the Registry Key.

 

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Issue/Introduction

Enterprise Vault indexing will not start after new installation