Problem running LabVIEW code (.exe) using Runtime engine

[Bill in Phoenix]

Ladies and Gentlemen,

Thank you for your help !!!

My version is the USA version running on Windows XP. My office computer is connected to our company network and as such has restrictions placed on it. I am running LabVIEW 8.2 Base version on this system to do development. The executable I created fails on this system. Our lab computers are not connected to the company network. As such, we have an account with administrator privileges. Executing from that account, I still get the errors. On one system I am using LabVIEW 8.2 professional version and on another I am using the LabVIEW 8.2 runtime engine only. I would tend to believe that with LabVIEW 8.2 Base and Professional versions, that everything is installed which is need by LabVIEW. I might mention that my VI executes fine using LabVIEW, of course it does not do anything. I do not know if perhaps the LabVIEW project does not include everything LabVIEW needs when it builds the executable or not. I just installed LabVIEW 8.2 a couple of weeks ago before I started

I am hoping the engineers at NI, perhaps that is one or both of you, would take the lead and research NI's code to attempt to help their "main source of income" out (the users of their product). I would be more than willing to have NI out to our location, Fort Worth, to look at our setup to try and determine if something is not configured correctly on our computers. However, since other users have had this issue, I would tend to think that the problem is not with our specific configuration (maybe the way Windows does a normal XP install causes the problem) or if it is, then NI should correct their installation procedure or code to work around the issue or have specific instructions on how to configure our systems so that this does not occur. The bottom line is that we need to determine why this is happening. I do not have source code for LabVIEW so that I can run NI's code, in whatever language it was written in, and set break points to determine under what conditions the failure generates the error message. I guess my first step might be to search the code to determine how many modules actually generate the error message. If it is only a few, then perhaps I could determine the cause without debugging the code. Then I would admit there is a problem, which would be corrected in a future release, and list the conditions that it occurs under. If a work around is available, I would note that.

I will be on vacation the next 2 weeks so I will not be able to test any possible solution NI or another user comes up with. But please keep looking into the issue if you would. We have an immediate need to resolve this issue.

Again, thank you for all of your assistance on this issue.

[Bill in Phoenix]

Ladies and Gentlemen,

Thank you for your help !!!

My version is the USA version running on Windows XP. My office computer is connected to our company network and as such has restrictions placed on it. I am running LabVIEW 8.2 Base version on this system to do development. The executable I created fails on this system. Our lab computers are not connected to the company network. As such, we have an account with administrator privileges. Executing from that account, I still get the errors. On one system I am using LabVIEW 8.2 professional version and on another I am using the LabVIEW 8.2 runtime engine only. I would tend to believe that with LabVIEW 8.2 Base and Professional versions, that everything is installed which is need by LabVIEW. I might mention that my VI executes fine using LabVIEW, of course it does not do anything. I do not know if perhaps the LabVIEW project does not include everything LabVIEW needs when it builds the executable or not. I just installed LabVIEW 8.2 a couple of weeks ago before I started this

I am hoping the engineers at NI, perhaps that is one or both of you, would take the lead and research NI's code to attempt to help their "main source of income" out (the users of their product). I would be more than willing to have NI out to our location, Fort Worth, to look at our setup to try and determine if something is not configured correctly on our computers. However, since other users have had this issue, I would tend to think that the problem is not with our specific configuration (maybe the way Windows does a normal XP install causes the problem) or if it is, then NI should correct their installation procedure or code to work around the issue or have specific instructions on how to configure our systems so that this does not occur. The bottom line is that we need to determine why this is happening. I do not have source code for LabVIEW so that I can run NI's code, in whatever language it was written in, and set break points to determine under what conditions the failure generates the error message. I guess my first step might be to search the code to determine how many modules actually generate the error message. If it is only a few, then perhaps I could determine the cause without debugging the code. Then I would admit there is a problem, which would be corrected in a future release, and list the conditions that it occurs under. If a work around is available, I would note that.

I will be on vacation the next 2 weeks so I will not be able to test any possible solution NI or another user comes up with. But please keep looking into the issue if you would. We have an immediate need to resolve this issue.

Again, thank you for all of your assistance on this issue.

[Tom Y]

I get the same errors

1. No Supported languages installed!

2. Unable to open resource files.

when trying to run a built app under Linux.  Labview 8.2 under Ubuntu 6.10 Desktop.

Which resource files do I need, where should I put them and what permissions should I give them?

Is there a document somewhere that says how to deploy apps under Linux?  So far I know that I have to install the RTE rpm (and replace the libGL.so.1 file because the one on my system is a NVidia-hacked one).  There are a load of files in <labview>/AppLibs - do I have to put them somewhere on the target platform? Do I need other resource files?

I've tried playing with the permissions on ~/Labview Data as suggested earlier in this thread, but it didn't fix the problem (surely the target PC might not even have this directory?)

BTW, did anyone ever solve how to solve the libGL.so.1 thing without replacing the file in /usr/lib (and hence potentially breaking other apps)?

Thanks very much,

Tom Y.

[Bill in Phoenix]

FYI

I never received a response that helped correct this issue. I finally gave up and decided to write a TCP interface and have the users send messages to my program and I would TCP the data back to them.

I would be interested in a solution to this issue if someone has one.

Thanks.

Bill

[vox]

Today I had the same problem in a software almost 4 years old. The following messages appeared after an OS and application re-installation:1. No Supported languages installed!2. Unable to open resource files.After finding out that the OS was changed from EN to Portuguese I’ve compiled the exe again with “Support for all languages” active. You can find this option in the “Run-Time Languages” category when configuring an exe build. The problem is now solved.Maybe, almost 3 years after you post, this could help someone who has the same problem.