application error nicitdl5.exe

[JosephLi]

When I shutdown my windows XP - windows application error message - nicitdl5.exe. Not sure why?
Lookout version 5.1 Build 8

Many Thanks!

[Robert_Jackson]

Joseph,
I have XP and Lookout 5.1 with other current NI software. This is most likely an issue with Citadel 5.0 which is not even used by Lookout 5.1, so my guess is that you have other NI Software installed. If true can you provide those software versions? It might also be useful to call NI support for assistance.
Regards,
Robert Jackson
Application Engineer
National Instruments

[JosephLi]

Robert,

Thanks for the answer. The other NI software are:
LabView Express 7.0
MAX 3.0.2.3005
DIA Academic 8.1.1292 TDM

Thanks!

Joseph

[Robert_Jackson]

Joseph,
Do you have Logos installed? I have Logos 4.3 and this will install some components of Citadel 5.0. In Lookout you could also try to specifically repair the Citadel install portion, and again first check the version of Logos.
Regards,
Robert Jackson
Application Engineer

[JosephLi]

Hi Robert.

The Logos version is 4.5.1.432

Thanks!

Joseph

[Robert_Jackson]

Joseph,
I think the best way for us to work through this issue most efficiently is for you to contact our Applicaton Engineers. I will be glad to upgrde Logos, but I think we still need to discuss what happens when you repair or reinstall software.
http://www.ni.com/support/
Regards,
Robert Jackson
Application Engineer

[dbz]

I have the same issue. Did you find a solution?

[mgcampo]

I'm running Labview 8.6 on Windows-XP and I get...

Runtime Error!
Program C:\Windows\system32\nictdl5.exe
This application has requested the Runtime to terminate it in unusual way.
Please contact the application's support team for more information.

...when I shutdown windows.

I don't know why it happens but I can't prevent it if I manually stop the service 'National Instruments Citadel' before shutting down. This must be done every time you shut down. I don't know any other way to solve this.

[Ryan.S]

It's probably because one database is corrupted.

To locate which database has the problem, you can detach(don't delete) the databases one by one. After you detach each database, try to stop the Citadel service. I guess the problem database is the one you are using.

After you locate a specific database, archive it to a new one and detach it. To archive the database solves most of the corrupted issues.