03-30-2012 04:16 AM
03-30-2012 05:23 AM
Huh??
So you are getting an error trying to search? Is this a new install? Could you reboot the server and check the EV Event Log for any errors on startup?
03-30-2012 06:14 AM
whats the actual error when you try and search from http://yourEVServer/EnterpriseVault/Search.asp?
Do not use the evindexing virtual directory as that is for EV Communicatin and searching *only*
04-03-2012 09:37 PM
yes sir this is new install and lots of data has been archived with shortcut creation but getting exect error is (Failed to perform the search request)..
04-03-2012 09:42 PM
actual error is (Failed to perform the search request).indexing service is not runing ,in IIS manager 7 EVindexing site in also not runing as i mention above .
04-03-2012 11:37 PM
So if you check, is the Enterprise Vault Indexing service running ?
Have you configured a different location for the Index Meta Data location ?
04-04-2012 06:40 AM
This being a new install is that 10.0.1 or 10 Base.
When you say Indexing is not running in IIS does that mean you see an error with the Virtual Directory or do you see the App Pool being disabled?
If you see the app pool being disabled can you check which 'Identity' it is running under (NetworkService / ApplicationPoolIdentity?) As a test perhaps switch it around to the other and see what transpires
As previous is the Indexing Service actually starting up as it should fail as well if there are problems checking the functionality of the website on startup, it will normall fail within 2s if there is a problem. Are you seeing any other errors in the EV / System / Security logs when trying to start the Indexing Service if this is failing that is.
Might be worthwhile attaching a dtrace of the EVIndexAdminService process at startup if indexing is failing to start.
04-09-2012 03:09 PM
I would check your IIS settings to see if you can access the EVIndexing site. The Install path in the Registry should also be checked. I had a similar issue with 10.0.1, the EVIndexing folder in the Enterprise Vault directory wasn't even present. I ran the Indexing Redistributable MSI in the EVtmp folder on the Server installation ISO and that fixed the issue.
04-12-2012 06:58 AM
Check for the following registry setting
HKLM\SYSTEM\CurrentControlSet\Control\Lsa
Dword value: DisableLoopbackCheck
Value data (Decimal): 00000001
Why? An issue has been found on Enterprise Vault servers that have been configured with Aliases. When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or IIS 6, you may receive an error message that resembles the following: HTTP 401.1 - Unauthorized: Logon Failed. This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address. Windows Servers include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name. By disabling the loopback check, you avoid "Access Denied" errors in the VAC and Event ID 40974 in the Event Logs.
6. Disable Strict Name Checking
HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Dword value: DisableStrictNameChecking
Value data (Decimal): 00000001
Why? Enterprise Vault utilizes DNS Aliases for optimized design and scalability. When a client computer connects to a Windows server by using an alias name, the client may receive an error message. This problem tends to occur when trying to connect to the server by using a CNAME alias that is created in the DNS zone. The server is not "listening" on the alias, and therefore is not accepting connections to that name. By requesting to disable strict name checking, this issue is resolved
http://www.symantec.com/business/support/index?page=content&id=TECH71173
this might cause the above issue .