ODBC database processor does not react correctly to SQL Server restart
Summary
Whenever an operation fails (like due to the error shown in the description), the cached objects are cleared. This forces a recreation of the prepared statement after statement execution fails and connectivity comes back online.
Description
Whenever an operation fails (like due to the error shown in the description), the cached objects are cleared. This forces a recreation of the prepared statement after statement execution fails and connectivity comes back online.
Information
Restart Service Engine
Issue Number: 250818
Fixed on Date: 12.4.2022
Versions: 10 0 BUILD 98635
Related Articles
FAQ: What SQL server interfaces are offered by zenon?
The most common ones are: The zenon Historian The Extended Trend The zenon Report Generator The zenon Report Engine The zenon SQL export functions The zenon SQL Driver and The zenon Process Gateway SQL module All these modules depend on an ODBC / ...
FAQ: SQL Server 2019 End of Life and Product Update Recommendations
This article contains link to external information not maintained by Ing. Punzenberger COPA-DATA Gmbh. Which SQL Server version is included in your installation? In the zenon versions 12, 11, and 10, the installation package included Microsoft SQL ...
Database cannot be opened! (SQL Authentication Error)
When opening zenon, one may encounter the following message in the output window: Taking a glimpse at the logs reveals that there are authentication errors regarding zenon's default database user "zenOnSrv". Therefore, no projects can be opened. ...
Checklist: OPCDA Server
Time estimate: 20 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Do NOT use DCOM in combination ...
Database error 0x80040154: Class not registered.
Issue: Archive can not be evacuated Log shows error: Database error 0x80040154: Class not registered. Problem: Engineering Studio configured a SQL provider to be used, which does not exist on the Service Engine PC. Solution: Install the configured ...