topic Re: Error 2208 on Executable in LabVIEW

Error 2208 on Executable

peabody_bass — Fri, 08 Nov 2013 13:19:00 GMT

I have an application that is operational as source code and executable on Windows 7. I tried to run the executable on Windows XP and received (paraphrased):

Error 2208. The full development enviornment is needed to fix this issue.

I tried a mass compile, adjusting exclusion parameters, disabling ActiveX server, enabling Labview 8.x file layout, and disabling SSE2 optimatizion, to no avail.

I only saw a few forum posts and KB articles on error 2208, with no clear solution provided.

Any ideas? Thanks.

Re: Error 2208 on Executable

crossrulz — Fri, 08 Nov 2013 14:31:05 GMT

Do you not have the right drivers installed? What is your application supposed to be doing? What equipment are you using?

Since you are obviously changing computers, I'm guessing it is a driver issue.

Re: Error 2208 on Executable

peabody_bass — Fri, 08 Nov 2013 14:43:23 GMT

It's not directly accessing any hardware. It's mainly just a host program, and communicates via network streams to a RealTime controller.

I installed the same packages that allow the program to run on (multiple) Windows 7. And I tried a second XP machine (which still didn't work), so it's probably not isolated to the hardware configuration.

Are there any other drivers that would need to be installed?

Re: Error 2208 on Executable

CAN_man — Tue, 04 Feb 2014 17:52:53 GMT

I have the exact same issue (works on Windows 7 but not XP). Did you ever find a solution?

Re: Error 2208 on Executable

peabody_bass — Tue, 04 Feb 2014 18:06:54 GMT

It's funny, because I just ran into this again yesterday. This time it was trying to run a executable in Windows 8 (that was compiled in Windows 7). I fixed it by making sure all the Windows Updates were installed, and that .NET 3.5 was installed (sorry, I'm not sure which if they were both needed, I only checked after I did both).

Re: Error 2208 on Executable

Cavarval — Wed, 05 Feb 2014 17:59:02 GMT

In most cases this error occures due to communication problems with dlls, ActiveX or dotnet elements which are corrupt or missing.

If your dotnet version on your computer is up-to-date, try making a debugable executable and try to figure which part of the application is giving the error.

If that dowsn't help, you can download this:

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

It can help you find the error source by showing missing dlls or incorrect communication to elements, if it is caused by a dll or ActiveX/dotnet call.

Let me know how it goes.

Re: Error 2208 on Executable

prvtmg — Thu, 24 Jul 2014 03:35:10 GMT

Hi,

I get similar errors while executing the file. "Error of type 2208.Full development version of labVIEW isrequired to fix the errors". How can i solve this ?

Regds,

Re: Error 2208 on Executable

Dennis_Knutson — Thu, 24 Jul 2014 04:59:14 GMT

Have you looked at the previous responses? You have not provided any information at all on your application so it is impossible to say what is missing on the deployment pc.

Re: Error 2208 on Executable

prvtmg — Thu, 24 Jul 2014 05:31:28 GMT

Yes I did. This is a Hostprogram that communicates mainly through GPIB interface. This code was developed in another system.I am currently using Windows XP and labVIEW version is 8.6

Re: Error 2208 on Executable

Dennis_Knutson — Thu, 24 Jul 2014 05:36:38 GMT

And what hardware drivers did you include in the installer that you created? Are you using IVI drivers? Any .NET?

What happened when you created a debuggable executable?

Re: Error 2208 on Executable

Sam_Sharp — Tue, 30 Sep 2014 12:27:33 GMT

I also just ran into this issue on Windows Server 2012. My application has calls to .NET and WS2012 only installs .NET 4.5 by default and doesn't include .NET 3.5 (which includes 3.0 and 2.0). I hadn't realised that .NET 4.5 doesn't include .NET <= 3.5. Installing .NET 3.5 solved the issue for me.

Re: Error 2208 on Executable

Yamaeda — Tue, 30 Sep 2014 12:50:15 GMT

Yes, LV up to 2012 (i believe) uses .NET2.0 as standard, so it makes sense.

Re: Error 2208 on Executable

KevSalmon — Thu, 22 Jan 2015 17:19:14 GMT

Just had this error (2208) when trying to run an exectuable on WinXP that was compiled with LabVIEW 2012 (32-bit) on a Win7 (64-bit) PC (executable runs fine on build PC)

I'm presently installing .NET 4.0 - as is requred by the NI Update 14.0 software (or so NI Update installer told me...)

update

-> Upgrading to .NET 4.0 and NI Update 14.0 hasn't fixed the 'broken run arrow/error 2208' issue

-> So now busy installing NI-488.2 14.0

--> also got a few Windows updates to install for .NET 4.0

Kev

Re: Error 2208 on Executable (.NET framework missing?)

KevSalmon — Fri, 23 Jan 2015 10:06:28 GMT

Hi,

In the end the answer was simple (?), the 'Microsoft .NET Framework 3.5' was missing, once installed the 'error 2208' message stopped appearing and the executable ran

Kev

Re: Error 2208 on Executable

MichaelAivaliotis — Fri, 12 Feb 2016 10:50:39 GMT

For those stumbling onto this thread like I did. One thing to try which has worked for me is to clear the object cache.

Go to: Tools>Advanced>Clear Compiled Object Cache

Reload the LabVIEW project and do a new build.

Re: Error 2208 on Executable

peper2001 — Thu, 03 Mar 2016 12:53:58 GMT

Hi,

I just ran into error 2208 and error 102208 in executable (Labview 2013). I managed to get rid of those - very vague - error codes by doing the following:

- Keeping the name of libraries, classes and methods as short as possible (seems to solve error 102208)

- Checking if there are any VI incorreclty claimed by a library (right click on project). Once the VI are identified, I remove the Vi from the library and then put it back in.

- Clear the object cache as Michael suggested.

- Recompile all the VIs (CTRL+SHIFT while clicking on the run arrow).

It's not clear what action solved the 2208 error code, though.

Just thought I would share that with the forum.

Regards,

peper

Re: Error 2208 on Executable

KenErik — Thu, 22 Sep 2016 11:27:27 GMT

Hi!

Have a similar problem as described here. Have tried to follow the suggestions given, but can't get it to work anyway.

Have wrote a program using Window Framework to use dialog boxes and GUI's presented to the user. It is working fine in the LabView development environment but can't build a working exe file. Getting the error message 423A8 and 2208, anyone who has any idea the reason and any suggestion how to solve it? Using Labview 2013

Re: Error 2208 on Executable

peper2001 — Thu, 22 Sep 2016 11:37:23 GMT

Hi,

I did not mention in my previous post that I also converted a few libraries to packed libraries to get rid of error 2208. It makes working on the code a bit harder though.

Keeping the names of VI, classes, librairies,... as small as possible seems to help too.

Eventually, I've just ditched Labview 2013 and upgraded to Labview 2015. The executable building process seems way smoother with the latter.

Good luck

peper