NOTICEPOTENTIAL 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, please contact Product Support Services prior to attempting the procedure below.
NOTICECOMPLEX PROCEDURE REQUIRED.
The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance.
Unable to enable or disable Enhanced Alarm Logging or Enhanced Alarm Delivery flags in Database Initialization. The Enhanced Alarm Logging flag goes back to what it was set to before making the change and the Enhanced Alarm Delivery flag is greyed out and uneditable.
Continuum Database Initialization
The owner of the ContinuumDB is set to something other than the default andover97.
In this specific case it was set to SA. The SA user was unable to write these changes to the database hence why the settings kept reverting back. To compound the issue it was found that an andover97 user had been created under the Security folder in the ContinuumDB, this then blocked attempts to change the owner to the correct andover97 user.
- Backup the ContinuumDB before making any changes. See Lessons Learned Article #4625.
Attempt to change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query.
- If this produces an error "The proposed new database owner is already a user or aliased in the database" then see Lessons Learned Article #5705 for instructions on how to drop the incorrect user so we can use the correct one.
- After successfully dropping the user from the ContinuumDB, re-run the query in step 2 above to change the database owner to andover97.
- After successfully setting andover97 to the database owner you should now be able to toggle the Enhanced Alarm Logging and Enhanced Alarm Delivery options in Database Initialization. If you want these enabled; toggle them both off, update the database, toggle them both on, update the database again. This will ensure they have been enabled properly.
Note: The definative check to see if the Encanced Alarm logging and Enhanced alarm delivery are both enabled is by checking the dbo.ACCDBVersion table in the SQL database using SQL Server Management Studio (or Express).
New Alarm Logging and New Alarm Delivery should both be set to 1.