Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

Unable to Query Recordset on Log Group '<Group Name>' (Reason: 'Could Not Complete Cursor Operation Because the Table Schema Changed After the Cursor was Declared')

Last Update: 11/7/2018

The following error message is received while logging data to a table in the SQL server with DataLogger: "Unable to query recordset on Log Group '<Group Name>' (Reason: 'Could not complete cursor operation because the table schema changed after the cursor was declared')". DataLogger continues to log data.

Possible Cause:
In most cases, the database or data table is locked by another user or a background maintenance task that cleans and compresses the data table.

Ensure that no tasks are running that will lock the table while data is being logged.

Note: Users that cannot implement the solution should be aware that every time the error message is posted, data will not be logged.

Related Products