Event 41293 Indexing Service fails to start: Configuration Error Corrupt or malformed ASP.net cache on EV Server
Problem
Enterprise Vault (EV) Indexing Service fails to start. Event ID: 41293 logged stating Configuration Error. Browsing Velocity.aspx in Internet Explorer shows Exception from HRESULT: 0x80070057.
Error Message
Event : 41293
Source : Enterprise Vault
Category : Index Admin Service
Description: Configuration Error
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 process EVIndexAdminService 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:
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>Configuration Error</title>|
The remote server returned an error: (500) Internal Server Error.| at System.Net.HttpWebRequest.GetResponse()| at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
IIS log on EV Server shows:2013-05-09 09:43:11 ::1 POST /evindexing/velocity.aspx v.app=api-soap& 80 DOMAIN\evsa ::1 - 500 0 0 0
Browsing the velocity.aspx page in Internet Browser: http://localhost/evindexing/velocity.aspxParser Error Message: Could not load file or assembly 'VivisimoNET' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
Source Error:
Line 34: <add assembly="System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL" />
Line 35: <add assembly="System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
Line 36: <add assembly="VivisimoNET" />
Line 37: <add assembly="Velocity" />
Line 38: </assemblies>Source File: C:\Program Files (x86)\Enterprise Vault\EVIndexing\www\asp\web.config Line: 36
Assembly Load Trace: The following information can be helpful to determine why the assembly 'VivisimoNET' could not be loaded.
Pre-bind state information:
LOG: User = IIS APPPOOL\EVIndexingPool
LOG: DisplayName = VivisimoNET (Partial)
LOG: Appbase = file:///C:/Program<file:///C:\Program> Files (x86)/Enterprise Vault/EVIndexing/www/asp/
LOG: Initial PrivatePath = C:\Program Files (x86)\Enterprise Vault\EVIndexing\www\asp\bin
Calling assembly : (Unknown).
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files (x86)\Enterprise Vault\EVIndexing\www\asp\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind)
LOG: The same bind was seen before, and was failed with hr = 0x80070057
Cause
Corrupt or malformed ASP.net cache on EV Server.
Solution
The error Exception from HRESULT: 0x80070057 (E_INVALIDARG) generally points to a corrupt temporary ASP.net cache. This issue can be resolved by clearing the cache or renaming the cached folder location.
1. Login to affected EV server using Vault Service Account (VSA) credentials.
2. From command prompt, run iisreset /stop
3. Rename the folder under ASP.net cache such as C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\evindexing to .old
(It is in Framework64 sub-folder)
3. From command prompt, run iisreset /start
4. Start EV Indexing Service.
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.