HistoryRead fails with "Could not encode outgoing message" when returning large number of DataValues (e.g. 100k)

[sudhakar269]

Type of issue

• Bug
• Enhancement
• Compliance
• Question
• Help wanted

Current Behavior

When using Quickstarts.HistoricalAccessServer, and performing a HistoryReadRawModified call that returns ~100,000 DataValue entries, the client fails with the following error:
Opc.Ua.ServiceResultException: Could not encode outgoing message.
at Opc.Ua.ClientBase.ValidateResponse(ResponseHeader header)
at Opc.Ua.SessionClient.HistoryRead(RequestHeader requestHeader, ExtensionObject historyReadDetails, TimestampsToReturn timestampsToReturn, Boolean releaseContinuationPoints, HistoryReadValueIdCollection nodesToRead, HistoryReadResultCollection& results, DiagnosticInfoCollection& diagnosticInfos)
at Opc.Ua.SessionClientBatched.HistoryRead(RequestHeader requestHeader, ExtensionObject historyReadDetails, TimestampsToReturn timestampsToReturn, Boolean releaseContinuationPoints, HistoryReadValueIdCollection nodesToRead, HistoryReadResultCollection& results, DiagnosticInfoCollection& diagnosticInfos)

The server-side RawRead handler successfully returns the data, but the OPC UA core library fails during response encoding.

Is this expected? or any way we can get data reducing load

Observed Behavior:

Server executes successfully and returns data.

OPC UA stack fails to encode the outgoing message due to message size or buffer limits.

Expected Behavior

No response

Steps To Reproduce

https://github.com/OPCFoundation/UA-.NETStandard-Samples/tree/master/Workshop/HistoricalAccess/Server

Here in this repo code change was done to return bulk data when HistoryReadRawModified method invoked, looping the same data multiple times and returning

Environment

- OS:Windows
- Environment:Visualstudio
- Runtime:
- Nuget Version:latest
- Component:
- Server:
- Client:

Anything else?

No response

[romanett]

@sudhakar269 I would suggest to increase the limits or decrease the ammount of data read at once. Or do you see a bug here that needs to be fixed?

[sudhakar269]

Thank you for the info,
Are there any recommended ways to limit the number of records returned in a single read operation from the HDA server to avoid overloading the client?

Is it possible for a sample HDA (Historical Data Access) server to return large historical datasets in chunks — for example, if there are 1 lakh (100,000) historical records, can the server provide the data in batches of 20,000 records per read, and respond with a status code like GoodMoreData to indicate that more data is available?

If so, does the sample HDA server support this kind of iteration mechanism, where I can continue reading using some continuation point or timestamp range until all data is retrieved?