LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

TELOG_LogVal.vi; Error Code: -1967390704 (0x8ABC0010)

I am using Labview DSC 6.1, logos 4.5 on Windows 2000 professional
 
 
I am getting following error in syslog.
ERROR  11/27/2005 07:43:13 PM Error accessing historical database! Error Code: -1967390704 (0x8ABC0010)
ERROR  11/27/2005 07:43:13 PM Error Accessing Historical Database! Error Code: -1967390704 (0x8ABC0010)
EVENT 11/27/2005 07:43:13 PM Historical database error. Message: TELOG_LogVal.vi; Error Code: -1967390704 (0x8ABC0010)
EVENT 11/27/2005 07:43:13 PM Historical database error. Message: TELOG_LogVal.vi; Error Code: -1967390704 (0x8ABC0010)
EVENT 11/27/2005 07:43:13 PM Historical database error. Message: TELOG_LogVal.vi; Error Code: -1967390704 (0x8ABC0010)
EVENT 11/27/2005 07:43:13 PM Historical database error. Message: TELOG_LogVal.vi; Error Code: -1967390704 (0x8ABC0010)
EVENT 11/27/2005 07:43:13 PM Historical data logging turned off.
 
When this happend before this I also get following error in my event log
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date:  11/27/2005
Time:  5:01:51 PM
User:  N/A
Computer: HZL
Description:
The Lookout Citadel Server service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 0 milliseconds: No action.
 
Also when I do ODBC query from ciatal database I get following error
 General SQL error.Unable to connect to data source: Data path="C:\Program Files\National Instruments\LVDSC Run-Time System\DATA"[Microsoft][ODBC Driver Manager] The driver returned invalid (or failed to return) SQL_DRIVER_ODBC_VER: %s
Alias: EMSCitadel
 
 
What is the possible cause  and solution of  this problem any help will be useful
 
Regards
Uttam
0 Kudos
Message 1 of 4
(3,923 Views)

Uttam,

If you haven't already, please apply the LabVIEW DSC 6.1 patch, carefully following the installation instructions in the readme.  Also, please see the following threads:

http://forums.ni.com/ni/board/message?board.id=170&message.id=45622&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=48075&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=51999&requireLogin=False


 
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me 🙂
0 Kudos
Message 2 of 4
(3,904 Views)

Yes I had already applied the patches.

I am facing this problem more frequently on the machines where I upgrade from Logos 4.4 to logos 4.5. Do you have any clue about this or known problem of logos 4.5.

Regards

Uttam

0 Kudos
Message 3 of 4
(3,894 Views)
Uttam,
I am not aware of any problems using Logos 4.5 over 4.4 -- 4.5 should be more stable.  Are you still having issues with this? Have you tried creating an entirely new database since upgrading to Logos 4.5 to see whether you are still having this issue?
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me 🙂
0 Kudos
Message 4 of 4
(3,859 Views)