Why won't my L4P and LKS files launch on customer's computer?

[JW_Tech]

Events make me almost sure I caused this, but would appreciate help if there's a way to prevent doing this all over again...

Customer had a process file that was running fine, but with an increasing number of staff with access to Lookout he wanted user accounts created and security levels assigned to numerous Lookout objects (accounts and objects were all at default settings). He emailed me the LKS and L4P files, I edited them, and emailed them back. 

The L4P and LKS launch fine on my computer, but won't on the customer's. On the customer's computer, launching the LKS file produces a compile error, but doesn't identify the error. I've also emailed the files to a colleague, who replied he had no problem either. Should mention colleague (like me) is running North American Win XP. 

Files were generated in Ver 6.02(1) on WinXP machines, and bench tested fine on a Ver 6.1 Runtime also under XP.

The customer is located in Poland, has a Ver 6.1 Runtime, and is running it on a Win NT machine. 

So assuming for a moment I caused this anomaly during my editing, why do the files not work at customer's location and why won't the compiler identify what it is?

More to the point, how do I fix this? 

JW_Tech 

[JPhillips]

You may have already checked in this location, but look in the lookout folder on the computer giving you the compile error, and look for the file "cbl.err".

In the past, I have had LKS files produce compile errors with no explanation in the dialogue box, but when I go to the Lookout folder and open the "cbl.err" file, the reason for the compile error was there.

Good Luck!

[Ryan.S]

What if the customer open the 6.1 .l4p file? What's the error message?

If you cannot figure it out or there is no error message, upload the .lks and .l4p files to ftp://ftp.ni.com/incoming. Let me try on my computer.

[JW_Tech]

Yo, JPhillips:

Thanks for the tip. Took a look at the err file (see for yourself)... 

Lookout Process File Compiler Version 6.1 (build 27)

Copyright National Instruments 1992-2007  All rights reserved.

cannot open source file: C:\Program Files\National Instruments\Lookout 6.1\cedrob.lks 

This is the same folder where the unedited files WILL work. 

 Ryan, I've uploaded the cedrob2.zipfile to the ftp site. Would appreciate you having a look at it.

There is certainly a mystery here. If I'm working at a site where the OS is all English, I weigh how much editing I might have to perform and consider moving my Integrator license from my laptop to the customer's computer (to take advantage of the bigger screen, mouse, keyboard and the on-line editing of Lookout) for the duration of the session. In this case, I was at the site (in Poland) in August and since Polish is not my strong suit, I did all my editing on my laptop and transfered the files to customer's computer via memory stick. Everything worked fine during all that, so emailing the files should not be any different, yes? 

[Ryan.S]

I'm able to run your process without any problem.

I look into the lookout source code. The error "cannot open source file" means that the .lks file cannot be opened by Lookout. The error happened at the very beginning when lookout tried to open the file. It looks like a permission issue. It's not something wrong in the codes of lks file, but the user doesn't have enough access right to the file.

For example, if I set all the file permissions for my windows account to "Deny", I will get exactly the same error when I open it by Lookout.

But I'm not sure what happened in your case.