Lookout Exe high memory usage

[Ryan.S]

Do you set Lookout application to start up automatically as service? If not, the only thing related to database is the Citadel service. A simple test can be done is not to set lookout as service and also set Citadel service as "manual". You can find it in Control Panel->Administrative Tools->Services->National INstruments Citadel. Set it to "Manual" from properties. In this way, this service won't start up automatically with windows. Without Citadel service running and lookout running, the database will not be loaded when windows starts. And then try to restart computer and see if it is still very slow. Remember to set it back to "Automatic".

Actually you can backup the database. In MAX, Historical Data->Citadel 5 Universe, right click on My Computer and create a new database for backup. Right click on current database, and select Archive. Archive the old data to another database so that the current database will have a small size.

The communication between Server database and client is handled by NI Logos. First please make sure the client time is synchronized with server. Maybe the database is replicated from server to client, but the current time on client is incorrect. Also check if there are any firewalls on either computer.

Any alarm message in Lookout client? Do all traces stop updating on client?

I'm sorry for late response on last question. I don't have further progress since I cannot reproduce the high memory usage by your process. Do the several Report objects in your process work correctly?

You can submit the request via email from www.ni.com/ask. Or give me your email address and let's contact you.

Message Edited by Ryan.S on 04-13-2010 04:36 AM

[iwanhoo]

My e-mail is krantic@ulpr.com, and my skype contact is iwanhoo92.

Do you have any idea how I can automaticaly minimize or maximize lookout?

Ivan Krantic

UNO-LUX Processing

[iwanhoo]

I uploaded the dump file to your ftp as you said to me. We had another Lookout crush yesterday. Can you tell us something more according to dump file I uploaded. It's name is dump.zip.

Ivan Krantic

UNO-LUX Processing

Message Edited by iwanhoo on 04-27-2010 07:32 AM

[Ryan.S]

The crash happened in Citadel. When it tried to write alarm/event to the SQL Server database, it crashed. The problem is related to the database.

What's the size of the database?  If it's huge, I suggest you to archive old data and alarms to a backup database.

[iwanhoo]

We thought so. Yes, the base is huge, larger than 8GB. We already told to the people there to archive the base. We hope that it will solve the problem.

Thanks a lot.

Ivan Krantic

UNO-LUX Processing

[iwanhoo]

Yesterday we have tried to archive the database manualy. We archived database without deleting data. But when we tried to archive the database with deleting the data older then certain period of time, lookout crushed again. Coleague will probably send me dump file again, and if so I will upload it to ftp again.

During the deleting the client PC was powered on. And it's connected to the same database. Can that cause crush of the lookout? Do we have to turn off the client SCADA when performing the deleting of the database?

Ivan Krantic

UNO-LUX Processing

[iwanhoo]

I just uploaded new dump file. dump_20100430.ZIP

Ivan Krantic

UNO-LUX Processing

[Ryan.S]

I don't think the running lookout process could cause the crash during archiving. Could you try to archive that period again? If it crashes again, that period of data may be corrupted.

One workaround now is to use a new database. Create a new database in different folder by MAX. And then configure the Lookout to use the new database. This can by done by File->Modify process or Option->System. By default, the process uses the system default database. You just need to configure this on lookout server computer, unless you use the ODBC on lookout client to connect the database directly.

The new database is empty. You can archive a certain period of recent data from old database to the new database for historical data viewing in lookout process. If the crash is because of the corrupted data in old database, the new database should solve the problem.

You can detach the old database by MAX. Right click on it in MAX and select Detach. Don't delete it. All the database files won't be deleted. If you need them in the future, you can attach it back for data viewing.

Because your database is huge, I guess you cannot upload it to ftp for me to debug it. So I suggest to use a new one and see if it still has the problem.

[iwanhoo]

We will try to create new database and see if it will solve the problem.

Thanks again

Ivan Krantic

UNO-LUX Processing

[iwanhoo]

We had another crush during creating report on PC with a server application. The problem is that they doesn't use that PC only as a SCADA PC, but like a regular office PC with minimized SCADA application, that they maximize only somethimes if needed to see some information. Creating report process is connected to some operation in the factory and in the moment of creating report on the client machine SCADA must be maximized, othervise the hypertrend will be empty (report is actualy printscreened hypertrend, and if SCADA is minimized the hypertrend has no data). Now we maximize the SCADA with a trigger batch file (process set some bit and that bit run the batch file that starts lookout.exe again). That's maybe not a best solution, can that cause some problems? And is there any other way to maximize SCADA if needed?

Ivan Krantic

UNO-LUX Processing