Pinting to file Events & Alarms with Lookout

[23r23]

I have a weird problem.

In one of the computers, running the same application, with identical lookout.ini file, and same alarm settings, the events can not be printed to file C:\data\events.csv. There is a message coming up saying that the file can not be created. I created the C:\data folder manually, then the computer prints the events.csv file, but it is empty. There is a Spreadsheet object saving in C:\data\'Machine'\'Year'\'Month'\'Day'\Data.csv with a sampling rate of 1 per minute. This database works well for both computers. The empty event.csv file of the second computer when is going to be open with notepad or excel, there is a message saying that another user/program is using this file, it is only allow to have a read only copy. The first computer works just fine.

The windows User Account has full admin rights. I have check everywhere, every single detail, but I can not have the second computer to print the events to a file properly.

Attached there is a very simple application for testing. This application does not work in the second PC.

The Lookout version is 6.0.2.

What I did miss?

[23r23]

Sorry, I forgot to tell about the alarm settings:

Filter options: Alarms & Events.

No filter criteria.

Under Print Options:

Print Range: Today

Under Printouts: Journal

Under Columns: Object, User, Description, Ack User, and Comment

Print to CSV file is checked

In the journal Field: C:\Data\Events.csv

Time format: mm/dd/yy hh:mm

I made sure that the proper process is selected.

Under Options\System\Citadel Database defauult computer has the name of the computer and default name and default path are pointing to the database folde in C:\Program Files\National Instruments\Lookout 6.0\Database.

[23r23]

I just found the mistake, because it was happening due a mistaken typing.

In edit mode, under File\Modify Process\Citadel Database\Computer Name there was a single digit number repeated by mistake. The default database was all wrong because the computer name didn't match. A new database was created.

Now this second computer works fine

Thanks in advance to those who were trying to find an answer.

[Khalid]

Thank you for the update -- this one had me stumped!

-Khalid