Compile Error

[mwjenn]

I have this process running for a while.  The operator mistakenly shut down the process.  When he restarted, lookout stated this was not a process file.

I tried recompiling and with the same result.  I have included the files in hope someone can repair the source file.

I have a lot of work in this one and the copy even my backup has the same result.

Any help would be appreciated.

Michael

[Rkdomer]

Search the lks file for INVALIDSIGNAL, you’ll find it as a parameter of Gauge8.  That’s preventing the source file from compiling.  My guess is after the compile fails it tries to load the original l4p.  If you fix the INVALIDSIGNAL problem it will probably compile.

[mwjenn]

Search the lks file for INVALIDSIGNAL, you’ll find it as a parameter of Gauge8.  That’s preventing the source file from compiling.  My guess is after the compile fails it tries to load the original l4p.  If you fix the INVALIDSIGNAL problem it will probably compile.

I opened the lks file and found the INVALIDSIGNAL as you had stated in Guage8. 

I deleted this from Guage 8 to reflelct the look of Guage 7.  I then saved and ran the file but it still will not compile.

[mwjenn]

I completely deleted Guage 8, then recomplied.  Seems to work at this time.

[Mike@Forshock]

Just to add,

This happened a lot on our 5.1 systems and not so often on our 6.1 systems.  Not sure what the exact cause it but it seems to be when using Symbolic Links and the system runs low on resources it writes INVALIDSIGNAL to the LKS and corrupts the L4P.

Mike

[T@TPCG]

This has happened to me when I copy/paste an object from one panel to another using a keyboard shortcut after toggling between edit and run modes. A <Ctrl>C or <Ctrl>V keyboard shortcut will allow some copy/paste instances that a Pulldown copy/paste will not. The .lkp and .lks are generated at save but the pasted object causes problems when compiling from the .lks. My advice is to used the pulldown Copy/paste and stay away from the keyboard method.