Can't open big file about excellibrary HOT 19 OPEN

I have the same problem, I am unable to open large files. (although in my case 
"large" is actually around 10mb). The spreadsheets I am working with are quite 
complex though.

Here's a stacktrace when opening a large file (around 17mb)

The sectorID value was -3..

"Specified argument was out of the range of valid values.\r\nParameter name: 
sectorID"}  System.Exception {System.ArgumentOutOfRangeException}

>   
ExcelLibrary.dll!ExcelLibrary.CompoundDocumentFormat.SectorAllocation.GetNextSec
torID
(int sectorID = -3) Line 45 C#

ExcelLibrary.dll!ExcelLibrary.CompoundDocumentFormat.SectorAllocation.GetSIDChai
n(int 
StartSID = 37508) Line 59 + 0xe bytes   C#

ExcelLibrary.dll!ExcelLibrary.CompoundDocumentFormat.CompoundDocument.GetStreamD
ataAs
Bytes(int StartSID = 37508) Line 153 + 0x25 bytes   C#

ExcelLibrary.dll!ExcelLibrary.CompoundDocumentFormat.CompoundDocument.ReadDirect
oryEn
tries() Line 82 + 0x29 bytes    C#

ExcelLibrary.dll!ExcelLibrary.CompoundDocumentFormat.CompoundDocument.Open(Syste
m.IO.
Stream stream = {System.IO.FileStream}) Line 81 + 0x12 bytes    C#

ExcelLibrary.dll!ExcelLibrary.CompoundDocumentFormat.CompoundDocument.Open(strin
g 
file = "C:\\Users\\Public\\Documents\\PublicContactsTotal\\PublicContactsTotal 
- 
Copy.xls") Line 61 + 0xa bytes  C#

ExcelLibrary.WinForm.exe!ExcelLibrary.WinForm.Form1.openOToolStripMenuItem_Click
(obje
ct sender = {Open(&O)}, System.EventArgs e = {System.EventArgs}) Line 61 + 0x11 
bytes   
C#

Yes, SectorID is -3 because it has type "int", but it should be uint or long.

Did you make this change in your local version? on which places. Can you send a 
patch?

No yet. I have plan to do it if authors can't do it but some time later.

It seems the authors are not responding. You're mentioning that we should use 
uint or 
long instead of int.. Changing the type of the parameter results in many other 
int-
>uint/long changes. Is that the way to go? Just change all the parameters that 
are 
depended into uint or long.. And should we choose uint or long?

Any news on this issue?

From what I can tell, more than 109 SecIDs triggers problems when reading the 
MSAT 
in large files (> 7MB?).  Negative SecIDs have special meaning.

The following patch fixes my issues.

After applying the patch from comment 8 by vromero i still get the negative 
sectorid 
when loading large files (>12mb)

For future reference anyone reading this:

I had the same issue using the compiled DLL writing to a file with approx 
290000 rows by 43 columns. I changed all the int's to int32's and rebuilt the 
project, this appeared to fix the problem. However now I just need to get 
around the OutOfMemory exceptions thrown after it hits 1.3GB on my 2gb machine. 
I'm guessing the code needs to save to disc once the buffer hits a certain 
size, although I've not looked into it.

Hi !
"Jay.Ze..." : can you send me your source code ? I would like to test it for my 
software XL2Csv. This would be a good idea to Upload your fix into the main 
project for ExcelLibrary : there is no new download since 2009 !
Thanks, Patrice.
[email protected]

Hello, it is a very nice software I have been around looking for some 
alternative to read Excel file without Interop nor OleDB and I could not find 
it.

It is a shame that it does not work very good with large files.

Jay.Ze, I tried to do what you said but I am not able to get the complete 
program working, Can you please tell me more details of how you solved the 
problem?

It would be also nice to have the project as Patrice said.

Thanks,

Hello.
Did anybody solved this problem?
I neew excellib for fast reading of big xls file only. Can anybody send me old 
version with his own fixes of this problem?

Hello , did anyone solved this problem ? ,pls help me solve this problem !

System.ArgumentOutOfRangeException was unhandled
  Message=Specified argument was out of the range of valid values.
Parameter name: sectorID
  Source=ExcelLibrary
  ParamName=sectorID
  StackTrace:
       at ExcelLibrary.CompoundDocumentFormat.SectorAllocation.GetNextSectorID(Int32 sectorID)
       at ExcelLibrary.CompoundDocumentFormat.SectorAllocation.GetSIDChain(Int32 StartSID)
       at ExcelLibrary.CompoundDocumentFormat.CompoundDocument.GetStreamDataAsBytes(Int32 StartSID)
       at ExcelLibrary.CompoundDocumentFormat.CompoundDocument.ReadDirectoryEntries()
       at ExcelLibrary.CompoundDocumentFormat.CompoundDocument.Open(Stream stream)
       at ExcelLibrary.CompoundDocumentFormat.CompoundDocument.Load(Stream stream)
       at ExcelLibrary.SpreadSheet.Workbook.Load(Stream stream)
       at ExcelLibrary.SpreadSheet.Workbook.Load(String file)

to [email protected]
yes , i had the same problem , did u solved ? 

Hi
I had this issue with an Excel 2003 file over 16mb.
In the code there is a bug which, after wading through the MS Compound Binary 
File documention,  I found and fixed below. 
Its in the Read of the DIFAT sectors (which the authors of this refer to as the
MasterSectorAllocTable); the read only comes into play with files over 6.8 MB)
Basically they load a bogus FAT idx into the list of FAT (SATs)Indexes.
(Its actually a link to the next DIFAT sector rather than a FAT sector)
My inelegant code which adjusts the SelectSIDs method is below
*****
        private void InitializeMasterSectorAllocationTable()
        {
            this.MasterSectorAllocationTable = new List<int>(NumberOfSecIDs);
            SelectSIDs(Document.Header.MasterSectorAllocationTable,0);
            int msid = Document.Header.FirstSectorIDofMasterSectorAllocationTable;
            while (msid != SID.EOC) 
            {
                CurrentMSATSector = msid;
                int[] SIDs = Document.ReadSectorDataAsIntegers(msid);
                SelectSIDs(SIDs,1);
                msid = SIDs[SIDs.Length - 1];
            }
        }

        private void SelectSIDs(int[] SIDs,int reduce_)
        {
            for (int i = 0; i < (SIDs.Length - reduce_); i++)
            {
                int sid = SIDs[i];
                if (MasterSectorAllocationTable.Count < NumberOfSecIDs)
                {
                    MasterSectorAllocationTable.Add(sid);
                }
                else
                {
                    break;
                }
            }
        }
Hope it works for folks - no guarantee its the same Sector issue as those above.

Thanks for the tip [email protected]

It works fine :)

For those who don't have the means for re-building the dll themselves, I've 
created a new one using [email protected]'s code. It seems to work just 
fine!