Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Access Denied

My LookOut application (that has been running for a year) has recently encountered a problem logging all data to the Citadel database.  The alarms basically says "access denied".  I checked the database path and made sure that the database folder is set to "full control permissions" and have tried several reboots but to no avail.  I have combed thru the website, hard drive memory is ok, the database folder size is 1.99 GB which makes me a little suspicious.  Do you have any ideas?  I will also post this on the forum.  Thanks for any help. 

0 Kudos
Message 1 of 11
(7,015 Views)

Maybe the folder size is limited to 2G by OS or something.

What's your OS?

 

To get a workaround of this issue, you can create a new database and log to the new one. If you use lookout 6.x, open Measurement & Automation Explorer(MAX), select Historical Data, right click on My Computer and create a new database in different folder. In Lookout, set the database in Option->System.

When you need old data, you can archive the data from 1.9GB database to the new one in MAX.

Ryan Shi
National Instruments
0 Kudos
Message 2 of 11
(7,004 Views)

Thanks for your reply, Here are the workstation specs:

 

TopSeller ThinkCentre M58e Tower Pent Dual Core

E5400 2.7GHz / 2MBL2 / 2GB / 250GB / SuperMulti / GNIC

/ W7P / XPP

Lenovo Commercial Systems

 

If I create a new database, I will likely run into the same problem in the future won't I? 

0 Kudos
Message 3 of 11
(6,999 Views)

If the OS or file system has the limitation, you will get the same problem in the future.

 

But I would like you to try the new database, and see if it works.

 

It looks like a new computer, which should not have this limitation. What's your lookout version?

The database itself doesn't have the size limit.

 

 

Ryan Shi
National Instruments
0 Kudos
Message 4 of 11
(6,996 Views)

LookOut Version 6.5

0 Kudos
Message 5 of 11
(6,994 Views)

I created a new database and it solved the problem...for now.  I have a feeling that this problem will re-appear when the database size hits 2 GByte in the future.

0 Kudos
Message 6 of 11
(6,981 Views)

Lookout just writes to files in the database folder. Lookout doesn't check the database folder size. 

The mssql file has the size limit, but it doesn't stop the logging.

 

If the size limit is from system, you need to check if the folder size is configured by the OS.

Ryan Shi
National Instruments
0 Kudos
Message 7 of 11
(6,974 Views)

If I understand you correctly, Citadel uses the free version of MSSQL (MSSQL Express) for its database and that database is limited to 2GB by the MSSQL software. If this is the case then it seems logical that MSSQL prevents any database client from increasing the database file size when it hits 2GB.

0 Kudos
Message 8 of 11
(6,968 Views)

In the Citadel database folder, you see the .cdpg file which is for the data. The mssql.mdf is for the alarm/event.

The SQL Server Express has the 2G size limit. So, the mssql.mdf file has the 2G limit.

But it's not for the whole database folder.

 

When the mssql.mdf hits 2G, the alarm/event will be saved in Citadel instead of SQL Server. So, it may affect the performance, but not functionality. It doesn't stop the logging.

 

And your case seems to be the folder size. It's a different issue.

Ryan Shi
National Instruments
0 Kudos
Message 9 of 11
(6,958 Views)

OK, thanks for clearing that up.  I may conduct an experiment whereby I move the 2 GB of files from my old database folder into the active database folder and find out if LookOut encounters the same problem again.  If so, a quick fix may be periodically move data to a backup folder before the folder size reaches 2 GB.

0 Kudos
Message 10 of 11
(6,952 Views)