Knowledge Base
cancel
Showing results for 
Search instead for 
Did you mean: 

Continuum showing SQL errors. Controllers are online but unable to modify existing objects or create new ones.

Warning

Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance.

Issue

1. Cyberstation PC Windows Application Event Logs showing SQL errors about being unable to allocate space for each of the event tables. Similar to the below errors.

Could not allocate space for object 'dbo.AlarmEvent'.'PK_AlarmEvent' in database 'ContinuumDB' 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.

Could not allocate space for object 'dbo.ExtendedLogReservation'.'IDX_EXTENDEDLOGRESERVATION' in database 'ContinuumDB' 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.

2. Controllers are online but unable to modify existing objects or create new ones. In addition;

  • all events were not being logged to the database. This was seen by reviewing the AlarmEvent, ActivityEvent, AccessEvent, AlarmEvent, and ExtendedLog tables not having any new events being recorded at all.
  • reviewing the distribution properties after performing tasks in Continuum showed no entries at all. Normally, user events initiated from the Workstation are shown in the distribution properties window as they occur.

Environment

Continuum Cyberstation

SQL Server

Cause

1. One of the Database files is set to not grow with Autogrowth set to none. This stops any new data from being able to be entered into the database. One example of this is when the ContinuumDev file was modified by the end-user to inhibit its growth by changing this setting to none.

Check all of the following databases files (both the DEV and LOG file) to ensure that they are all set to either autogrowth or to an adequate restricted value so that they are able to write new entries.

  • ContinuumDB
  • MSDB
  • TempDB

 

2. The disk where the database resides does not have enough available disk space.

Resolution

1. Change this database file growth setting to "by 10MB, unrestricted growth" or to an adequate restricted value.

  • Use SQL Server Management Studio Express, see LL#4635 on where to get this if it is not already installed on your SQL Server. It is highly recommended to backup the ContinuumDB before attempting any changes to the database, steps on how to do this are in the above article.
  • Start up SQL Server Management Studio, or in my example, Management Studio Express.
  • Log in with your SQL SA password or windows administrator.
  • Expand the server tree, expand the Databases tree.
  • Right-click on ContinuumDB and select "Properties" from the menu; this will show the Database Properties window.
  • Select the Files tab on the RH side of this window and you are now where you need to be to check the Autogrowth setting.

 

2. If the problem is due to disk out of space your options are;

a) Make room on the disk,

b) Shrink the ContinuumDB, 

c) Install a larger disk in the machine.

Tags (1)
Labels (1)
Version history
Revision #:
2 of 2
Last update:
2 weeks ago
Updated by:
 
Contributors