Use the search and browse 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.

Search Solutions Results By: View All Solutions

Kepware Knowledge Base: Solution


Examples of MS SQL Table/Database Full Errors


Last Update: 11/7/2018

When the server gets one of the following errors from MS SQL, the DataLogger _Error Tag will be set to 1 to indicate that the log group is in an error state.

  • SQL Server 2000: "DataLogger Runtime Unable to query recordset on Log Group 'SQLServerLogGroup' (Reason: 'Could not allocate space for object 'TableName' in database 'SQLdatabase' because the 'PRIMARY' filegroup is full.')."
  • SQL Server 2005:
    • "DataLogger Runtime Unable to query recordset on Log Group 'MSSQLogGroup' (Reason: 'Could not allocate space for object 'dbo.stresswide216'.'PK__stresswide216__7C8480AE' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.')."
    • "DataLogger Runtime Failed to create the data table for log group 'MSSQLogGroup' (Reason 'Could not allocate space for object 'sys.syscolpars'.'clst' in database 'TestNew' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.')"
    • "DataLogger Runtime Unable to query recordset on Log Group 'MSSQL' (Reason: 'Could not allocate a new page for database 'TestingNew' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.')."
Related Products
DataLogger, KEPServerEX