01-23-2013 02:55 PM
Hello All,
I was wondering if you could share how to address the following problem:
Index Volume for recently (12 days ago) created 10.0.2 Journaling Vault Store started failing today. So far it failed 3 times.
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 1/23/2013 4:18:32 PM
Event ID: 41329
Task Category: Index Volumes Processor
Level: Error
Keywords: Classic
User: N/A
Computer: MyEVServer.MyDomain.com
Description:
Index volume is marked as failed.
Archive Name: MYEVJOURNAL
Index Volume ID: 1126AEF7E8493C346B70D777F8A052E091110000XXX.MyDomain.com_1534
Reason: IndexingEngineError
Error Type: CriticalError
Description: Indexing engine exception
------------------------------------------------------------------------
2 times I was able to 'Synchronize' that index.
3rd time the 'synchronization' task is just there with status 'inactive' (why 'inactive'?), but index is down.
Currently index has 1382806 Indexed Items.
Any ideas how to proceed in my situation will be greatly appreciated.
Thank you!
01-23-2013 03:31 PM
Hey Victor,
you can use this to find why that volume is failing:
Article:TECH168134 | | | Created: 2011-08-26 | | | Updated: 2012-07-28 | | | Article URL http://www.symantec.com/docs/TECH168134 |
To find index volumes that have failed, use the query:
use EnterpriseVaultDirectory
Select *
from IndexVolumeView
where Failed = 1
01-24-2013 07:21 AM
Hi Tony,
Thank you so much for the respond.
Indexing works strange (to me) in the EV 10.0.2.
It has been failing through the night: the error I mentioned above was recorded in the event log: @23:25; 01:06; 02:05; 3:05 – though nobody “synchronized” indexes between failures, so I would expect failed index to stay failed. And yet – this is not the case.
In the morning index appeared to be healthy and SQL query returned no failed indexes.
Could you shed some light on the logic of EV behavior, if possible, please?
Thank you in advance!
01-24-2013 08:06 AM
Hi Tony,
So it failed again.
The FailedVolumeReason column has 13, which is "Indexing Engine Error".
What would you suggest as the next step?
Thank you!
01-24-2013 08:16 AM
that error code would imply the Indexing is overloaded. Are you currenlty updating your 32 bit indexes? Is your Index location still local to the EV Server?
Any other events around those in the app log?
01-24-2013 08:34 AM
Thank you, Tony!
This is the brand new cluster: there were no 32bit indexes; I would assume it should not have any “updating” running. Nothing interesting in the event logs before the index fails.
01-24-2013 09:24 AM
01-24-2013 09:27 AM
01-24-2013 10:37 AM
Thank you for the reply.
Not noticing any interesting messages in the system log.
4 min. before the index reported as failed last time it reported following informational message:
"Log Name: System
Source: Service Control Manager
Date: 1/24/2013 1:08:53 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: MyServer.MyDomain.com
Description:
The Application Experience service entered the stopped state."
1 min before that I am noticing:
"Log Name: System
Source: Service Control Manager
Date: 1/24/2013 1:11:03 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: MyServer.MyDomain.com
Description:
The WMI Performance Adapter service entered the running state."
And
"Log Name: System
Source: Service Control Manager
Date: 1/24/2013 1:11:03 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: MyServer.MyDomain.com
Description:
The WMI Performance Adapter service entered the stopped state."
None of these looks very "interesting" to me.
01-25-2013 11:53 AM
01-25-2013 12:41 PM
Have you talked to Symantec Support about this issue?
01-28-2013 09:52 AM