Index Issues

When you log in to VAC check for the proper index volume Volume:334 , As it might be an issue with only one index volume and the other indexes for the journal archive are in normal state. Run update on the specific volume mentioned in the event .

Hi Rahul,

While updating the index i get the above 3 errors in event.. Any idea why would i get this errors.

EV Will automatically put a failed index on line every 2 hours until such a time as it just can't update it
If its the same index everytime, trying going to the folder where that index is located and look for a file called "avtrace.log" and see if its throwing any errors that coincide with the ev errors, it could be an issue with missing or corrupt files within the index itself

avtrace.log shows me the below results.

Thu May 19 10:53:19.441 2011 (thread:10144) avs_makestable: error: I/O
Thu May 19 10:53:21.144 2011 (thread:10144) avs_makestable: error: I/O
Thu May 19 10:53:22.832 2011 (thread:10144) avs_makestable: error: I/O
Thu May 19 10:53:24.488 2011 (thread:10144) avs_makestable: error: I/O

Not sure what does this mean.

a makestable is when the indexing commits the items it has in memory to disk, I/O could be something such as disk or memory, did this error in the index coincide with anything in the event viewer?

When this logs were writteng in Avtrace at the same time there was event which occured in the Application logs as below.

=================================
Event Type: Error
Event Source: Enterprise Vault
Event Category: Index Server
Event ID: 7292
Date:  5/19/2011
Time:  10:53:22 AM
User:  N/A
Computer: VaultServer
Description:
The index volume has been marked as failed.
Index Volume: 1C8A2E6A8DBEC064D9A1B2F03A7D5286D1110000journaling/Volume:334 (Vault)
Index Volume Path: D:\Index Data\index2\1C8A2E6A8DBEC064D9A1B2F03A7D5286D1110000journaling_81543440
Reference: Makestable
           
 
Due to errors accessing the index volume it has been marked as 'failed' to prevent further errors.  The index volume will remain inaccessible until it has been repaired.

======================

Is this something related i am clueless now i have already started the update and its been quite  a while the index is showing me as 0 in total items and also in failed items not sure if the Index update is actually happening

Ok so some questions
1. What kind of device are the indexes stored on? Local NTFS? SAN? NAS? iSCSI? NetApp etc?
2. Have you disabled opslocks on the EV Server and the Server that controls the device?
3. Is Anti-Virus excluded from attempting to scan the locations?
4. Are there any errors or warnings in the system or application logs relating to the disks or storage?


As lame as it may sound, if those check out, you may just want to try rebooting the machine

Below are the answers.

1. What kind of device are the indexes stored on? Local NTFS? SAN? NAS? iSCSI? NetApp etc?
Local NTFS

2. Have you disabled opslocks on the EV Server and the Server that controls the device?
opslocks ?? i am not sure what is that and how to check that.

3. Is Anti-Virus excluded from attempting to scan the locations?
Yeah Antivirys is already exlucded for this location

4. Are there any errors or warnings in the system or application logs relating to the disks or storage?
I cross verified and didnt see any errors on the server for Disk.

OpsLocks TN from M$

http://support.microsoft.com/kb/296264

OpsLocksdisabled Registry Key is set to 1 on my server is that a correct setting????