failed to collect frames

Question

continuous sql error logs in secondary read replica always on node, failed to collect frames

Answer 1

Hi Bhavana Yadav,

Thank you for your detailed explanation. It looks like you've already followed the recommended steps, but the issue persists.

To help resolve this further, I recommend raising a support ticket so our support team can assist you directly. Please refer to the following link for instructions on how to create a support ticket:

https://support.serviceshub.microsoft.com/supportforbusiness/create

We appreciate your engagement and thank you for being an active part of the community.

Thanks,

Lakshmi.

Answer 2

I got update from an internal contact. It is a known issue that will be fixed in a future CU. While annoying, the message is harmless. If you don't want to wait for the CU, I can only recommend you to open a support case.

(I posted another tip from my contact earlier, but it turns out that tip is not relevant, so I deleted that post.)

Answer 3

I see that you are running SQL 2025. Query Store on readable secondaries was introduced in SQL 2022, but only as a preview feature. With SQL 2025, it is no longer preview, so noise like that should not occur.

I would suggest that you open a support case, so that Microsoft can investigate. Most likely they will need call stacks and other diagnostics, which they will ask you to collect.

Answer 4

The error "failed to collect frames" in SQL Server's secondary read replica can be indicative of performance issues or connection problems between the primary and secondary replicas. This can lead to intermittent connection time-outs, which may affect the ability of the secondary replica to process incoming log records effectively.

To troubleshoot this issue, you can:

1. Check the SQL Server error logs on both the primary and secondary replicas for any related messages that could provide more context on the failure.
2. Review the performance metrics on the secondary replica to identify any resource contention or high workloads that may be affecting its ability to collect frames.
3. Ensure that the network connection between the primary and secondary replicas is stable and not experiencing intermittent issues.
4. Use the sys.dm_hadr_database_replica_states dynamic management view to check the health and status of the replicas.

If the problem persists, consider investigating the workload on the secondary replica and optimizing it to ensure it can handle the incoming log records without delays.