Server 2019 Indexing incomplete results

%3CLINGO-SUB%20id%3D%22lingo-sub-2465670%22%20slang%3D%22en-US%22%3EServer%202019%20Indexing%20incomplete%20results%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2465670%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20I%20have%20a%202019%20server.%20Wich%20is%20indexing%20my%20network%20drives.%20The%20index%20always%20turns%20up%20incomplete%2C%20meaning%20it's%20missing%20countless%20files.%20Some%20files%20in%20a%20folder%20is%20indexed%20and%20others%20are%20not.%20So%20my%20search%20results%20are%20incomplete.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20rebuilding%20several%20times%2C%20restarted%20the%20server.%20Rebuild%20again.%20The%20search%20results%20are%20the%20same%20every%20time.%20Some%20files%20are%20indexed%2C%20others%20are%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHeres%20an%20example%20on%202%20files%20that%20are%20and%20are%20not%20indexed.%20They%20are%20residing%20in%20the%20same%20folder.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E6063%20-%20P295%20GH%20KEDELPLADE%2090%20-%20charge%20AHF724-02-06%20plade%20623593A%20-%20LM%20507381.pdf%20(is%20indexed%20every%20time)%3C%2FP%3E%3CP%3E6075%20-%20P295%20GH%20KEDELPLADE%2070%20-%20charge%20AHF732-02-01%20plade%20624083A%20-%20LM%20507381.pdf%20(is%20never%20indexed)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBoth%20resides%20in%20the%20same%20folder.%20It%20seems%20like%20it%20stops%20indexing%20when%20it%20reaches%20a%20specific%20size%20or%20similar.%20The%20windows.edb%20file%20is%2010.944.512%20KB%20%26nbsp%3BBut%20I%20can't%20seem%20to%20find%20a%20setting%20that%20should%20prevent%20it%20growing%20bigger.%20It's%20placed%20on%20a%20drive%20that%20has%20199%20Gb%20and%20184%20GB%20free%20data.%20Its%20an%20NTFS%20drive.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETried%20all%20possible%20solutions.%20Theres%20no%20errors%20in%20the%20event%20log%2C%20the%20indexer%20runs%20fine.%20It%20states%20that%20it%20has%20indexed%201.730.583%20Items.%20And%20that%20the%20Indexing%20is%20complete.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20fileserver%2C%20was%20replaced%20recently%20with%20a%20Fresh%202019%20install.%20And%20since%20then%2C%20the%20error%20has%20persisted.%20The%20old%20server.%20A%202012R2%2C%20never%20had%20any%20issues%20regarding%20the%20search%20index.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20good%20suggestions%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2465670%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2465731%22%20slang%3D%22en-US%22%3ERe%3A%20Server%202019%20Indexing%20incomplete%20results%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2465731%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20found%20the%20error%20myself.%20It%20seems%20that%20SYSTEM%20should%20have%20rights%20in%20the%20folders.%20Dooh%20!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1083867%22%20target%3D%22_blank%22%3E%40mb_Prodan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi. I have a 2019 server. Wich is indexing my network drives. The index always turns up incomplete, meaning it's missing countless files. Some files in a folder is indexed and others are not. So my search results are incomplete.

 

I've tried rebuilding several times, restarted the server. Rebuild again. The search results are the same every time. Some files are indexed, others are not.

 

Heres an example on 2 files that are and are not indexed. They are residing in the same folder.

 

6063 - P295 GH KEDELPLADE 90 - charge AHF724-02-06 plade 623593A - LM 507381.pdf (is indexed every time)

6075 - P295 GH KEDELPLADE 70 - charge AHF732-02-01 plade 624083A - LM 507381.pdf (is never indexed)

 

Both resides in the same folder. It seems like it stops indexing when it reaches a specific size or similar. The windows.edb file is 10.944.512 KB  But I can't seem to find a setting that should prevent it growing bigger. It's placed on a drive that has 199 Gb and 184 GB free data. Its an NTFS drive.

 

Tried all possible solutions. Theres no errors in the event log, the indexer runs fine. It states that it has indexed 1.730.583 Items. And that the Indexing is complete.

 

The fileserver, was replaced recently with a Fresh 2019 install. And since then, the error has persisted. The old server. A 2012R2, never had any issues regarding the search index.

 

Any good suggestions

3 Replies

I've found the error myself. It seems that SYSTEM should have rights in the folders. Dooh !

 

@mb_Prodan 

Poor you