06-11-2013 11:51 PM
Same problem that EV007 had in this thread:
https://www-secure.symantec.com/connect/forums/ev-1001-indexing-6882-error-when-attempting-index-very-large-files
Too bad it is closed, because there is no solution, as far as I understand it.
Same version, EV 10.0.1, indexing error 6882, "The compound file is too large for the current implementation (0x80030111)". No DVSCC, just DVFCC.
Problem file is 708CA20552AB00BA1B1097C812F103C1~5E~ABA2FF78~00~1.DVFCC and the size is 2,65GBs.
I made the query as Jeff Shotton advised in the thread:
select SP.Properties from Saveset SS
inner join savesetproperty SP on SS.Savesetidentity = SP.SavesetIdentity
where SS.IdTransaction = '708CA205-52AB-00BA-1B10-97C812F103C1'
Short version of results:
<originalSize>1416544586</originalSize>
<fileName>model.dmp</fileName>
EV007 found a large log-file that caused the problem. But then what?
07-20-2013 10:07 AM
Did you get chance to look at tech note http://www.symantec.com/docs/TECH191942, it seems to fixed in 10.0 sp2.
07-20-2013 10:10 AM
Forget to mention that EV 10.0 SP4 is release few days back so you can consider to upgrade directly to latest Service Pack.
Regards
EV-Counselor
09-03-2013 11:14 AM
The issue was addressed in 10.0.4 full release or 10.0.2 CHF2 so the best option would be to go to 10.0.4. Issue occurred when trying to convert the large file for HTML view, but this should have not been occurring.
From the 10.0.4 Updates_en.htm file.
Some items or attachments can result in very large files of converted content. The conversion and indexing of these files could affect archiving performance. Files of several gigabytes could cause archiving errors.
This has been fixed. By default, when converted content is larger than 30MB, that converted content is neither indexed nor stored. The original item or attachment is archived as normal.
You can use the MemLimitForTextConversionFallback registry value to control the maximum size of converted content that can be indexed and stored. See the Registry Values manual.