07-09-2015 03:04 AM
Hi All,
We are facing issue with the enterprise vault search.
Kindly find the attached screenshot of the same.
We are getting this issue frequently after 2-3 days, can anyone suggest the solution for the same.
Regards,
Vipul
07-09-2015 03:25 AM
HI Vipul,
If you verify the Enterprise Vault server, in the eventlog for EV, do you see errors/warnings?
I had this too (not as frequent), and decided to restart the indexing service only on the EV server daily at 06:00. that has stopped this from occurring.
07-09-2015 05:42 AM
Hi Gertjan,
Thanks for your comment.
When we reset the indexing engine, it starts working and then again after 2-3 days facing same issue.
Event id 7182, 41315 and 41329 in the eventlog.
Regards,
Vipul
07-09-2015 06:44 AM
Hello Vipul,
Could you please give the description of Event ID 41315, 7182 and 41329 as same event id has different descriptions.
Is there any anitvirus sofware on EV server? if so, please share the details.
Thanks.
07-09-2015 07:15 AM
Hi Manideep,
Thanks for your comment.
Yes, Symantec Antivirus is installed on the EV server.
Kindly find the details of the Event ID.
Event id - 41315 - Index query server
A search failed with error "Search engine fault: Unrecognised".
Archive: Priyadarshan
Archive ID: 12C8C4DE8BC0620449C25DC14649BA0781110000EVSERVER
Index volume ID: 290
User: ----\----
Maximum results: 100
Timeout (seconds): 600
Sort order: -date
For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3474&error=V-437-41315
Event id 7182 - Web application
Index Search failed: Index Search failed: Index: Internal reference: (0xc0041c0e)
Index: 1FB6C5744B4519F44A13701DEF89FAA561110000EVSERVER/VolumeSet:615
Internal reference: SRCI
For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3474&error=V-437-7182
Event id 41329 - Index Volume processor
Index volume is marked as failed.
Archive Name: Payel
Index Volume ID: 1C150EE4F3BA6A9498129FB6F24355A971110000EVSERVER_626
Reason: IndexingEngineError
Error Type: CriticalError
Description: Indexing engine exception
For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3474&error=V-437-41329
07-09-2015 07:16 AM
Hi Manideep,
Thanks for your comment.
Yes, Symantec Antivirus is installed on the EV server.
Kindly find the details of the Event ID.
Event id - 41315 - Index query server
A search failed with error "Search engine fault: Unrecognised".
Archive: Priyadarshan
Archive ID: 12C8C4DE8BC0620449C25DC14649BA0781110000EVSERVER
Index volume ID: 290
User: ----\----
Maximum results: 100
Timeout (seconds): 600
Sort order: -date
For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3474&error=V-437-41315
Event id 7182 - Web application
Index Search failed: Index Search failed: Index: Internal reference: (0xc0041c0e)
Index: 1FB6C5744B4519F44A13701DEF89FAA561110000EVSERVER/VolumeSet:615
Internal reference: SRCI
For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3474&error=V-437-7182
Event id 41329 - Index Volume processor
Index volume is marked as failed.
Archive Name: Payel
Index Volume ID: 1C150EE4F3BA6A9498129FB6F24355A971110000EVSERVER_626
Reason: IndexingEngineError
Error Type: CriticalError
Description: Indexing engine exception
For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3474&error=V-437-41329
08-26-2015 12:10 PM
you can dtrace the w3wp service and it should log the process. Also the index is marked as failed so will want to fix that first.
Then make sure you apply Recommended list of antivirus exclusions for Symantec Enterprise Vault:
https://support.symantec.com/en_US/article.TECH48856.html
09-21-2015 02:12 AM
Hi we are having the same issue and have to restart the EV Indexing service every morning. I have a call logged with Symantec for this but wondered if you have a found a solution yet?
09-21-2015 04:57 AM
09-21-2015 08:53 AM
are there any plans to get Vivisimo to not create its files in C:\Windows\Temp as excluding the C:\Windows\Temp is so so so bad, even goes against Symantec's best practices
09-21-2015 10:32 PM
I would love to say yes but to be honest it is down to the developers of Vivisimo and not us unfortunately so our hands are kind of tied at the same time.