Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

EV 10.0.1 indexing - 6882 error when attempting to index very large files

Created: 03 Oct 2012 | 14 comments

We are facing issues with EV 10.0.1 indexing - 6882 error when attempting to index very large files

By following the technote below, we don't see any DVSCC file in there, only DVS, DVFCC and DVFSP is present there. How can we resolve this issue where not DVSCC file present there? The technote only states about modifying DVSCC file name.

http://www.symantec.com/business/support/index?page=content&id=TECH191942

Many Thanks

Comments 14 CommentsJump to latest comment

LCT's picture

How large is large? is FSA file or exchange attachments?

LCT's picture

wow...that is large...if I remember correctly there is a limit to the file size, if files larger than this configured limit will still be archived, but only the file name and the metadata will be indexed. I believe the limit is 50MB but you can change this to max of 2GB I think.

http://www.symantec.com/business/support/index?page=content&id=TECH48803

http://www.symantec.com/business/support/index?page=content&id=TECH48611

Check the two links above for archiving size limits.

Hope that helps.

ia01's picture

Hmmmm how can I set indexing to ignore those large files and not to try to index and consume resources and time and through up that error?

Jeff Shotton's picture

Hmm you shouldn't be having the content of those large files indexed. There is a limit to the size of a file that can be indexed, and if memory serves that is around 100MB with EV10. Should you even be trying to index this file type? You can of course exclude certain types from conversion:

http://www.symantec.com/docs/HOWTO37400

Incidentally you are seeing DVFCC/DVFSP because the file has breached the limit where EV will compress it into a saveset file. So the DVFSP is just the original file renamed.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

LCT's picture

I don't believe you can tweak the kind of things you are asking...as the technote you previously posted...Symantec acknowledged that this is a know issue and they are working on it for EV10.

There are a few reg keys that you can go through which may help but I doubt it.

http://www.qassociates.co.uk/downloads/symantec-enterprise-vault-whitepaper.pdf

You should report your issue to them and push them to work faster to fix it ;-)

ia01's picture

Not sure which file type that DVS... corresponds to, is there any way to find which file type is archived in that DVS... file? If yes then we can exclude that file type for conversion.

Jeff Shotton's picture

The transaction ID should be part of the DVFSP file name. If you can query the vault store database and find the transaction ID, then you can use that savesetidentity value to query the savesetproperty table which will contain the filename.

You would need to follow something like this in reverse: http://www.symantec.com/docs/TECH48552

The transaction ID in the saveset is not formatted in the same way as in the database, where there are - characters separating the characters out. This is in the pattern 8-4-4-4-12

Give me the name of the file and I'll try and create the query for you.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

ia01's picture

915D541A2E0D0DF32DD64136672752C1~53~1E8E9C78~00~1.DVFCC

915D541A2E0D0DF32DD64136672752C1~53~1E8E9C78~00~1.DVFSP

Many Thanks

ia01's picture

I have set BypassConversions = 1 reg key, but still getting those errors in event log. We don't need html preview of any file for now, so why indexing is trying to convert although BypassConversions is set to 1? Restarted indexing service, any other service needs restart?

Jeff Shotton's picture

I believe BypassConversions is going to change the data stored in the converted content going forwards, but in your case the converted content already appears to exist - it is now being added to the index. Im not sure this is the answer here...I'd switch that back if i were you.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

Jeff Shotton's picture

select SP.Properties from Saveset SS
inner join savesetproperty SP on SS.Savesetidentity = SP.SavesetIdentity
where SS.IdTransaction = '915D541A-2E0D-0DF3-2DD6-4136672752C1'
 

should give you the xml stored when the file was archived. If you cant see what you need in this, post the XML as well...

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

ia01's picture

BTW, that was a large .LOG file and by default .LOG files are not exlcuded