Print Alarms to file

[23r23]

Not too far ago, I had a problem printing alarms and events to a file in C:\Data\ folder. That was with the Development and Run Time Lookout 6.0. In this development computer it works great (after some work around and fixing a mistyping when the database was created). Now, I have also several other computers with Lookout 6.0 Run Time Only Servers. I can't find a way to print the alarms/events to a file for those computers.

Is there any difference, something I should know, when setting up the database of the Run Time Only computers? Are there restrictions accessing the database if the security level is lower than the administrator in Run Time Only? The manual, the web resources, and the help don't have too much written about this issue.

Any other one have had experiences like this before?

Thanks in advance.

[23r23]

One more detail of what is happening with the Lookout 6.0.2 Run Time Only: The file is printed to C:\Data\ but it is empty. When Excel opens it and Lookout is running, there is a message telling: the file is being modified by another user. Open as Read-Only, or choose to notify to be alerted when it is available.

Sounds like Lookout 6.0.2 tries to access all the time, or can not open the folder. When Lookout is closed, Excel opens that empty folder without messages.

The development computer allows Excel to open that file when Lookout is open. No messages, there are events recorded.

I put side by side both computers and checked the settings. All the alarms and event settings are the same.

Honesty, I'm running out of bullets.

[Paul M.]

23r23,

Do you have any underscores ("_") in your process names?  Lookout treats these characters differently and can cause problems like you described.

Let me know,

[23r23]

No, the process name is as simple as 'Motion' for all the computers. Actually it is the same application everywhere. The fact is that I made two more Run Time Only to work with the same application since last post. One is working fine, the other is not. This is driving me crazy.

Lookout Version 6.0.2.

Any other suggestion?

[Paul M.]

This could also be a permissions issue. Are you running Windows XP? Are you logged on the PC as an administrator or a user with adminstrator rights?  Did you install the Run Time engine as an administrator?  Also, are you using the menu option to print alarms or are you using the print alarms object?

[23r23]

Yes to all.

I have been making more Run Time Only Severs with the same application. Recently, I have been opening FIRST an empty application and use it to setup the Alarm Filters and the Print options. Once these are done, the main application can be open and IT WORKS. It looks like to me that we must create the destination folders and make the corresponding alarm setups BEFORE load the application with print to file enabled.

If all these days of work, tries, and experiments are useful for any one else, I'll be glad.

By the way, this could be considered to be fixed for the new revisions of Lookout.

[Paul M.]

23r23,

Thanks for the feedback.  We'll keep it in mind. 

-"By the way, this could be considered to be fixed for the new revisions of Lookout."

Do you mean it does work correctly in 6.0.2 or you want it to be fixed in the next version?

[23r23]

It does work in 6.0.2 Run Time Only IF the developer sets Alarms\ Filter Options and Alarms\ Print BEFORE loading the application that uses the print to file feature. The way I found was to create an empty application, just to setup the alarms. Once Alarm options are properly set, the final application can be loaded.

What DOES NOT work is lo load the final application using the print to file feature, and FROM there  setup the Alarms Filter Options and Print to file.

If the destination file is out of Lookout folder, that folder has to be created with windows before loading the final application that uses print to file feature.

Again, this is for Run Time Only Server 6.0.2. I didn't try with other rev numbers.

[Ryan.S]

The destination folder needs to be created before you click "OK" to print alarms.
But I can't reporduce your problem. I open the process, configure the parameters and then OK. It prints the alarms and events well. My system is Runtime 6.0.2.1.

[23r23]

Same Revision: 6.0.2 build 1

It might be then related with administrator rights in the computer. I asked to our System Department to have full admin rights on those PCs. The reality is that they have more power than me, they can get settings I can not. I'm not quite sure how much admin rights has my account. That could be a reason.

Regards.