Unexpected catastrophic failure with "INSQL" OLE-DB provider

Hi, this is definitely that you need to raise a ticket with support, as a first measure ill look into the SQL database and search for Runtime.dbo.History , see if you can open and check for security on it. Can i ask if this was an upgrade project from a really old Historian ? 

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?

Since in our case, have no way of reproducing the issue it would be very interesting to perform the following when the problem is active in your system.

1. First - Test the connection for the linked server.  You can do this using sp_testlinkedserver InSQL or by right clicking on the linked server in Server Object > Linked Servers and choosing Test Connection.  
    or
   
    
2. See if you are able to execute a very simple query and if you get the same error
   

   SELECT TOP 1 * FROM OPENQUERY(INSQL, "SELECT DateTime, [SysTimeHour]
   FROM WideHistory
   WHERE wwRetrievalMode = 'Cyclic'
   AND wwCycleCount = 100
   AND wwQualityRule = 'Extended'
   AND wwVersion = 'Latest'
   AND DateTime >= DateAdd(mi,-5,GetDate())
   AND DateTime <= GetDate()")

Hi experts, thanks for your advice. 

We just raised a support ticket.

Upon conducting our investigation, we discovered than the server restarts after a scheduled windows update.

The installed patch is 

KB5036335 - Description of the security update for SQL Server 2019 CU25: April 9, 2024 - Microsoft Support

This may be the cause of the error, but we are awaiting further analysis from the support.

To your questions: 

 RAINER CARLTON DSOUZA No, it is not upgrade from an old historian.

Richard Köhlerstrand We implemented your suggestion on the server and had following results: 

1. Test Connection: success

2. Test OPENQUERY: failed and it replied the same error message

I did some basic testing with SQL Server 2019 and the CU25 referenced above and didn't see the same problem. That may still be a factor, but not the only one.

We experienced this same issue. Any update to your investigation?

Hi Xianghui Luo 

I have seen a similar issue. One of my colleagues reported this following error when installing System Platform 2023 R2 using the shipped SQL Express 2022 on a Windows Server 2022 machine. He found SP installer tries to install OLE DB Driver (v18.5.0) that caused the following error. He then downloaded the latest OLE DB Driver installer (v19.3.0) from MS website and installed without a problem. 

It is possible that your issue may be caused by the OLE DB driver. What is the driver version being used in your system and what Windows version? Maybe, you should consider upgrading the driver.

Though both errors are related to the OLEDB provider, the one reported by Jacky above is a different error. This appears to happen at installation/upgrade time when there is already an older version of the driver installed. The workaround is to manually install/upgrade the driver, then rerun the System Platform install. You can download the driver from Microsoft, but it is also included on the System Platform under "D:\InstallFiles\Redist\MSOLEDBSQL"

At least in some cases, using the System Platform installer's "Repair" option resolves this (sometimes also requiring a reboot).

Hi all, 

thanks for your engagements to the issue.

After communication with TechSupport, we solved the issue with the following workaround: 

• Run the aahSecurity.exe in Administrator Mode from "C:\Program Files (x86)\Wonderware\Historian\x64"
• Reboot the machine

Then the OLEDB Provider works as usual.