12-22-2010 05:30 PM - edited 12-22-2010 05:36 PM
Ok, beating a dead horse... I think we are definitely getting to the end of our NI lifespan 😞
Background
System installed with Lookout 6.1 in 2008, ran well for about 1.5 years. Random crashes, database corruption, etc. Initially believed to have been the machine (Software RAID 5 sucks). New machine built in Oct. 2010; no RAID, Intel Core2 machine, XP SP3. Upgraded to Lookout 6.2. Could not import the 6.1 database, performance slowed to a crawl, believed to be from a corrupt database. Created a new database.
Today
Machine is experiencing system failures on Citadel and Lookout. We have nothing but AlarmDialer 4 (custom notification software), RealVNC Enterprise, Lookout 6.2, HP Printer and standard system related tools (TrueImage, AVG, Adobe Reader (Latest version, for manuals)) installed on this machine. All updates installed.
Latest Windows Mini-dumps: http://support.forshock.com/files/MRCWD/Minidump.zip
Latest (related) error messages:
Event Type: Error
02-03-2011 12:14 PM
Just the answer I was looking for!
Mike
02-23-2011 10:30 AM
Mike,
You are not alone. We've run Lookout for close to a decade and have had various problems with it over time. We frequently have Citadel database crashes which take quite a bit of time to recover from. We are on 6.1 currently, but have had the issue now for a few years. I have not been able to identify any one thing that is causing the problem. we have a second instance of Lookout at a separate plant that runs without incident, so to be honest, I'm at a bit of a loss as to what is causing the problem. The only thing I can possibly point to in our situation is that the database(s) on the system that crashes are extremely large (up to 20GB) and have been upgrade from 4.x versions of Lookout over time.
02-23-2011 11:25 AM
Thanks for responding.
We have decided to stop actively developing in Lookout. We are currently transitioning to another SCADA/HMI package, developed by a company not too far from NI headquarters...
We have this happening in different impacts on multiple systems. We have one system logging about 25 traces, very small process. It exhibits the same problems.
Have a good day,
Mike
02-27-2012 11:11 AM - edited 02-27-2012 11:15 AM
Year later. We have a system with approximately 8.05GB in citadel. System shutdown, restart. Database is now taking over 1 hour to "rebuild" and is not complete. Secondary has 7.99GB, same issue.
Processes will not function, system is sluggish, basically useless.
Long live Citadel...
02-27-2012 11:14 AM
Forgot to add: In this time, the processes will not function!