cidital dabase alarm not logging

[mwjenn]

One of our HMI suddenly stop trending. the alarm screen shows a cidital database alarm stating that the information has stopped looging.

Nothing has been done to this machine in quite a while so it is not going to be a result of recent activity (programming).  Any one have an idea of what is going on.

Ver 6.0.1 build 1

[Bob_L]

Check the database size. I believe the limit is 2 gb. Search this forum for similar incidents.

Good luck

Bob

[mwjenn]

Database folder is 891 MB

[Ryan.S]

Check the database service. Control Panel->Administrative Tools->Services, find National Instruments Citadel. Restart this service.

Open Measurement Automation Explorer, Historical Data->Citadel 5 Universe, expand My Computer, check if the database is still in the list.

Check the database folder's user permission. Give everyone full control.

[mwjenn]

I stopped and restarted the service.

The database is still in the list

everyone using the computer (only logon / full administrator) has full control

[Krands]

Hello I have the same problem, no events or alarms are stored, I can't see them in MAX - I have tried to restart Citadel service, I have tried to delete some of the data in the database, but nothing helps! Are the alarms and events stored in the Citadel or SQL database? Would it help to reinstall the complete Lookout or only some parts of the program?

Max version 4.0.0.3010

Lookout 6.0.2

Win XP

[Ryan.S]

The alarm and event are logged to SQL Server database. Try to restart the service SQL Server(Citadel).

If it doesn't help, create a new database in different folder by MAX. Configure your lookout process to log to the new database. See if the mssql.xxx files are created in database folder.

[GeorgeStokes]

Hi!

I recently had the same problem as mentioned by TS.

My problem was that I changed the computer name after installing LV with the DSC module. The problem here is MSSQL that binds itself up to a machine name. This name can be seen if you download and install the MS SQL server management studio. 

In order to fix this the easiest solution is to rename your computer back to the original name.

Another solution is to uninstall labview and mssql and all related programs, and reinstall labview

A third solution is to go into computer management (windows; right click on computer and select manage). Go to local users and groups, select groups and change the three parameters containing sql to include the current machine name. Then open the sql server management studio,  and go to security, logins and rename the parameter with sql in it's name to include the current machine name.

I hope this should do the trick.

Best regards

Fredrik