LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Error compiling resources - trying to build inherited CVI6 IVI driver in CVI8

I have inherited a LabWindows/CVI 6.0 project (instrument driver, IVI) from an outside contractor and I have been trying to build it for weeks.  I've worked through some problems, and upgraded from 7.0 to 8.01trying to get rid of what is probably the "last" one.  I can't shake it and the error message isn't useful:
 
"Error compiling resources.  Make sure your tmp directory is writable and not full."
 
I've recreated the project, moved the project, removed anything resembling a space from project file names.    I followed the procedure here http://digital.ni.com/public.nsf/allkb/753FCBD48E366B7C862570A00048AFFF as well as the regular "File >> New" method of creating new projects.  I checked my XP tmp and temp directories for writability and emptyness.  They were C:\Documents and Settings\<user>\..., and valid, but I thought from some of the many posts I've read that the spaces might be causing an issue.  I created a brand new directory, C:\TMP, reset my environment variables to point to this, fixed the permissions, restarted LabWIndows/CVI, same problem. 
 
I have the IVI Compliance Package 2.5 installed.  I see it is relatively new, if there is another version you'd like me to try, I can.  I can't find any more breadcrumbs to chase, totally out of ideas. 
 
Thanks in advance,
 
Julie
Certified LabVIEW Developer
NI-VLM Administrator
0 Kudos
Message 1 of 8
(4,311 Views)
Hi Julie,

The following KB refers to building executables (not IVI drivers) but the information may still be useful. Do any of your files have spaces in the name you could try removing?

http://digital.ni.com/public.nsf/websearch/59D645F043CD434D86256516005ABC56?OpenDocument

You mentioned that you had upgraded in an attempt to get these drivers to work. Does that mean you were never able to get it working in CVI 6.0?

Let me know Julie, thanks!
Dan Weiland
0 Kudos
Message 2 of 8
(4,290 Views)
Dan, yes I did remove all the spaces, moved the project to a directory path with no spaces, changed my temp/tmp to a directory with no spaces in the path.
 
I finished watering it down.  There is barely anything left, except enough to cause the errors.
 
Certified LabVIEW Developer
NI-VLM Administrator
0 Kudos
Message 3 of 8
(4,284 Views)
Hi Julie,

I was able to compile the attached version without problem. I am using CVI 8.0.1 and IVI Compliance Package 2.5 as well.

Another Applications Engineer is continuing work on this issue at this thread:

http://forums.ni.com/ni/board/message?board.id=180&message.id=11761
Dan Weiland
0 Kudos
Message 4 of 8
(4,271 Views)
Thanks all for your efforts, I am trying (again) to create a new project.  I am wondering if it is the ole32.* that came with ...\CVI80\sdk, as this file got corrupted in my registry.  It manifested as OLE errors from within Outlook (Word email editor).  I regsvr32'd it to fix.  I might try a different ole32.lib/oleaut32.lib ...
 
(Only a true geek has this many compilers on one system :-b):
C:\>dir /s ole32.lib
 Volume in drive C is IBM_PRELOAD
 Volume Serial Number is 40F6-E6E4
 Directory of C:\Program Files\Microsoft Visual Studio\VC98\Lib
05/13/1998  12:00 AM            68,152 OLE32.LIB
               1 File(s)         68,152 bytes
 Directory of C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\Lib
08/09/2002  11:10 PM            73,416 Ole32.Lib
               1 File(s)         73,416 bytes
 Directory of C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\PocketPC2003\Lib\armv4
09/23/2005  10:17 AM             9,648 ole32.lib
               1 File(s)          9,648 bytes
 Directory of C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\Smartphone2003\Lib\armv4
09/23/2005  10:17 AM             9,648 ole32.lib
               1 File(s)          9,648 bytes
 Directory of C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\Lib
04/14/2005  06:56 PM            73,704 Ole32.Lib
               1 File(s)         73,704 bytes
 Directory of C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\Lib\AMD64
04/14/2005  06:55 PM            82,926 Ole32.Lib
               1 File(s)         82,926 bytes
 Directory of C:\Program Files\National Instruments\CVI70\sdk\lib
07/29/2003  11:00 AM            71,612 ole32.lib
               1 File(s)         71,612 bytes
 Directory of C:\Program Files\National Instruments\CVI70\sdk\lib\borland
07/29/2003  11:00 AM            35,840 ole32.lib
               1 File(s)         35,840 bytes
 Directory of C:\Program Files\National Instruments\CVI70\sdk\lib\msvc
07/29/2003  11:00 AM            71,612 ole32.lib
               1 File(s)         71,612 bytes
 Directory of C:\Program Files\National Instruments\CVI80\sdk\lib
04/10/2006  10:00 AM            71,612 ole32.lib
               1 File(s)         71,612 bytes
 Directory of C:\Program Files\National Instruments\CVI80\sdk\lib\borland
04/10/2006  10:00 AM            35,840 ole32.lib
               1 File(s)         35,840 bytes
 Directory of C:\Program Files\National Instruments\CVI80\sdk\lib\msvc
04/10/2006  10:00 AM            71,612 ole32.lib
               1 File(s)         71,612 bytes
     Total Files Listed:
              12 File(s)        675,622 bytes
               0 Dir(s)  21,882,195,968 bytes free
 

Message Edited by JulieC on 08-14-2006 02:52 PM

Certified LabVIEW Developer
NI-VLM Administrator
0 Kudos
Message 5 of 8
(4,270 Views)

New project (watered down) with MS .Net 2003 ole32/oleaut32 built.  I replaced these in the original watered down project and got the original errors.  Deleted the cvibuild.KETSP directory, rebuilt, same errors.

I deleted the .cws and .prj files from the original project location, recreated, the darn thing finally built!  I think something is rotten with those OLE files in the CVI80 SDK, but I am past the issue.  Thanks and pass the Excedrin.

 

Certified LabVIEW Developer
NI-VLM Administrator
0 Kudos
Message 6 of 8
(4,265 Views)
 
Certified LabVIEW Developer
NI-VLM Administrator
0 Kudos
Message 7 of 8
(4,263 Views)
FYI ... it definately has something to do with adding type library resource to the dll.
 
Certified LabVIEW Developer
NI-VLM Administrator
0 Kudos
Message 8 of 8
(4,158 Views)