Lookout 5.0 Logos faulting everytime I boot?

[RobMiller2002]

Hi

For the last 3 weeks I am getting an error from Logos everytime I boot my Windows XP Pro Machine (SP2). It causes the desktop to not appear for about 40 seconds and then I get a Application Fault error from Logos. I am running lookout 5.0 Build 7 and the Logos version is 4.3.0.27. Here is the event log on the error:

Event

Date 10/17/2006         Source: Application Error

Time: 10:05:04 PM     Catagory: (100)

Type: Error                  Event ID: 1000

User: N/A

Computer: NEWCADSTATION

Description:

Faulting application lkcitdl.exe, version 4.4.0.0, faulting module unknown, version 0.0.0.0, fault address 0x0012e7e4.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6c 6b 63   ure  lkc
0018: 69 74 64 6c 2e 65 78 65   itdl.exe
0020: 20 34 2e 34 2e 30 2e 30    4.4.0.0
0028: 20 69 6e 20 75 6e 6b 6e    in unkn
0030: 6f 77 6e 20 30 2e 30 2e   own 0.0.
0038: 30 2e 30 20 61 74 20 6f   0.0 at o
0040: 66 66 73 65 74 20 30 30   ffset 00
0048: 31 32 65 37 65 34         12e7e4 

All of my other software is functioning properly and I have no hardware errors. Please let me know what I should do to resolve this problem.

Thank You

Rob

[Ryan.S]

Try to upgrade the Logos.

Logos 4.5.1 can be downloaded here ftp://ftp.ni.com/support/logos/

[RobMiller2002]

Updating Logos has fixed my problem! Thank you for your help.

Rob

[Edwinred]

Yes,

My Pc also send my fault about the citadel can`t run and must be stoped, I am to install the logos 4.5. msi.

I don`t have access to the hypertrend grafics only I to see the tag values od the temperature, pressure, etc but the database is not running.

I hope to find the answer with your help.

regards.

Edwin

[Ryan.S]

Citadel 4 is not as stable as Citadel 5 is. First suggest is to update the Logos to 4.5.1 for Lookout 5 user, even repair Lookout before update Logos.

Also try to create a new database and use a new lookout process to use that new database. If this works fine, it means your current database has something wrong. You can use the new database and archive the historical data to the new one.

[Edwinred]

Ryan,

This mean that I lost my database, the application is in a cement plant for supervisory of the control process, in those database we have the signals of the temperature, pressure, current and others.

Now you say that I have to create other process file and other database. I have that explain to my boss and doesn`t like very much.

I downloaded the update of logos 4.5.1 from the ftp://ftp.ni.com./

good

see you

[Ryan.S]

I didn't mean you have to create other process and other database. I meant you can do a test in this way. If other process with different database works fine, it means your current database has the problem.  If any process with any database will meet the same problem, it's not a specific database's issue, it's not a specific process issue, it may be the Citadel service's issue.
If it's the Citadel service or Logos's issue, upgrade the Logos, or repair the Lookout may help. But if it's your current database's issue, maybe it's corrupted, upgrade Logos won't help, you have to either fix it or use a new one.
Take a look at this KB. Try to fix it if upgrade Logos doesn't help. Backup the database files before you do it.

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/6fc62f75b74d706d8625694900768f69?O...

Even if you use a new database, the historical data in old one can be archived to the new one. They won't be lost in most cases.