検索機能を使用して 500 を上回る Kepware の知識ベース記事の中から閲覧します。結果を絞り込むか、クエリーを下部の検索フィールドに入力します。

解決策が見つからなかった場合には、当社の PTC eSupport Portal で追加資料を確認することもできます。eSupport Portal へのログインを要求された場合、My Kepware の認証情報を使用できます。My Kepware アカウントが必要ですか? こちらで作成

各種検索方法:
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: 2018/11/07

Problem:
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.

Solution:
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
DataLogger