InvalidOperationException: Unexpected end of stream

GroupDocs.Search Product Family
1

Hello,

One of our customers has experienced the following exception once:

System.InvalidOperationException: Unexpected end of stream.
   at .()
   at .(Stream )
   at GroupDocs.Search.Common.ExtractedData.Deserialize(Byte[] array)

We were not able to reproduce it. We don’t do anything special… We serialize the ExtractedData and serialize it in a different process. Usually, it works…

2

@jamsharp
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): SEARCHNET-3519

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

3

@jamsharp

Most likely, corrupted data was passed for deserialization or the position in the stream was not zero. Were you able to record/trace this issue/exception again?

4

We started catching the exception and ignoring it when it happens (it was rare). Therefore, we haven’t seen it since then.

5

Hi @jamsharp!

We will address this issue as well in the upcoming release, together with the rest of the issues related to unexpected document content.
Thank you!

6

Hello, just curious… Was this in the last release? I’m asking because I did not see it in GroupDocs.Search for .NET 26.7 Release Notes

7

Hi @jamsharp!

We are going to implement an improved re-indexing process that will rebuild a new index from the existing one without requiring access to all indexed documents. It means, for example, if you added documents from the stream to the index and then created a new index, the current implementation will not be able to include these documents in the index. Still, an updated/improved version will allow to index these documents as well, even without actual access to these files.

Hope it will help to avoid any issues with the index in the futuree!

8

I’m a bit confused. You comment seems to be related to the index migration issue I opened, not to this one.

9

HI @jamsharp!

Yes I missed the topic to comment.

According to this issue -
we could not reproduce this issue as well so potentially we can close this topic
in case if this will appear again - we can start new thread.
Thank you!