LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

LWTCPJSOCKWNDYCLASS 0xc0000005 error

When I install a new program on to a computer I get an LWTCPJSOCKWNDYCLASS (0xc0000005) error.

 

I have looked at all the drivers required by the new program and MAX shows that they exist on the computer at the correct revision.

We have uninstalled and re-installed the program but get the same error.

 

Installing the program on other computers work without any error.

 

What should be our next step?

0 Kudos
Message 1 of 4
(3,805 Views)

What operating system are you using?

What software are you installing?

Take a look at following links it might be becuase of anti virus you might have on your computer.

 

http://forums.ni.com/t5/LabVIEW/LV2009SP1-32-exe-failed-to-initialize-properly-0xc0000005/td-p/11362...

 

http://digital.ni.com/public.nsf/allkb/9FBC76558CBA93588625774D00483881

National Instruments
Applications Engineer
0 Kudos
Message 2 of 4
(3,785 Views)

We are installing on a WIN 7 computer.  The software was written in LabWindows CVI 2010.  The LabWindows CVI created the installer.

0 Kudos
Message 3 of 4
(3,782 Views)

I've had that error before.  It happens when you have a newer version of the CVI Runtime engine installed in the Windows System32 directory, and your application was built with an older version of CVI that includes the CVI Runtime engine in the application directory.  To fix it, you can generally either:

  • Manually delete the copy of the runtime engine in the application directory so that it uses the copy in the System32 directory.  If you don't have the ability to rebuild the application this may be your only option.
  • Deselect the option to install the CVI Runtime in the application directory and rebuild the installer.
  • If only selected some of the components of the CVI Runtime engine in the installation package, select all the components of the CVI Runtime engine to be installed in the application directory and rebuild.  This will work in some cases.
  • Rebuild your application in a newer version of CVI so that the version of the CVI Runtime the application uses is greater than or equal to the version in the System32 directory.
  • Rollback the version in the System32 directory to the same version as your application uses.  This could potentially break other software that depends on that newer version of the CVI Runtime so I wouldn't do this unless you're absolutely sure nothing else requires that version of the CVI Runtime engine.

Hope this helps.

0 Kudos
Message 4 of 4
(3,778 Views)