You are viewing limited content. For full access, please sign in.

Question

Question

LFFTS: Reached max pages in page system

asked on April 4, 2022

Hello,

Anyone seen this error message in the LFFTS logs:

"Reached max pages in page system. c:\fti index\SEARCH\lfword.idx."

It correlates with the following error:
"Required invalid page 4294967293 in page system."

Customer just started having this issue last Thursday.

Is the number value in the second error message the page count for a document that someone is trying to bring into Laserfiche?

Whatever this is, it is causing the LFFTS service to crash.

Any feedback greatly appreciated.

Jeff Curtis

0 0

Answer

APPROVED ANSWER
replied on April 6, 2022

"Pages" in this context refers to the number of pages in the lfword.idx file that it can support. The default limit is just under 2³² pages. You can increase this limit by doing the following:

  1. Stop the Laserfiche Full Text Indexing and Search service
  2. Go into the registry to HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\LFFTS\Config and set DictionaryFileExpansionOption to some multiplier, i.e. 4. What this means is that lfword.idx can now support 4x the number of pages compared to its default
  3. Start the Laserfiche Full Text Indexing and Search service
1 0

Replies

replied on April 4, 2022 Show version history

... how big is this repository?

Is there any chance there are actually on the order of 4.3 billion pages?

@████████?

Edit: I found a few support cases where this error message was mentioned. It would be best if you open a support case for this one.

0 0
replied on April 5, 2022

Hey Sam,

Thanks for the reply.

I doubt there is that many pages as this customer just setup Laserfiche in December of 2021.

I will get more details from this customer and open a Support Case.

Thanks,
Jeff

0 0
replied on April 5, 2022

Yeah, I realized it's not talking about document pages but (likely) rather memory pages. Either way, please proceed with the support case.

Cheers,
Sam

0 0
replied on April 5, 2022 Show version history

The support case is likely your best bet. 

That said...  It kind of sounds like MSSQL ran out of memory.

If I'm not mistaken, that number is just shy of 4GB (2³² or 4 x 1024³) - might be worth checking what memory you have allocated to MSSQL...

Edit to add - My knowledge might be out of date , but I think Windows also has limitations on the number of files in a folder in NFTS that matches that number and the maximize drive size of 4GB in FAT32 (which I believe is still used for some removable drive media).

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.