• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 10 replies
  • Subscribers 15 subscribers
  • Views 1522 views
  • Users 0 members are here
Options
Related

Unexpected catastrophic failure with "INSQL" OLE-DB provider

Xianghui Luo

Hi experts,

 

In our Historian server (Aveva Historian 2023 R2), we have encountered an issue where the "INSQL" OLE-DB provider fails after server restarts.

When querying in SSMS, we received the following errors, which are also documented in Log Viewer

Despite this, the Historian status appears to be normal.

What could be the possible reasons for this issue and is there any solutions?

Best regards,

Xianghui

Parents
  • 0

    Hi,

    We have also seen this issue in a customer project, Version 2023 (no upgrade).

    In our case this happens after a while and we can resolve it by rebooting the server or restarting the Microsoft SQL Server Service.

    We do not have a ticket open for the issue yet and it is very interesting to see how/if you manage to get around it.

    You say that it happens after reboot, are you able to perform any actions to get it working again?

Reply
  • 0

    Hi,

    We have also seen this issue in a customer project, Version 2023 (no upgrade).

    In our case this happens after a while and we can resolve it by rebooting the server or restarting the Microsoft SQL Server Service.

    We do not have a ticket open for the issue yet and it is very interesting to see how/if you manage to get around it.

    You say that it happens after reboot, are you able to perform any actions to get it working again?

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.