 Lj010203
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases v2019.6.0.6 of SP7
		
			Lj010203
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases v2019.6.0.6 of SP7	
				 JensG69
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases updates for XLR8 and SP7
		
			JensG69
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases updates for XLR8 and SP7	
				 heel
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases git4G - a toolkit to integrate Git into the development environment of LabVIEW
		
			heel
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases git4G - a toolkit to integrate Git into the development environment of LabVIEW	
				 Hans-Joachim
		
		
		
		
		
		
		
		
	
			
		
					on:
					Support for Logo!8  ??
		
			Hans-Joachim
		
		
		
		
		
		
		
		
	
			
		
					on:
					Support for Logo!8  ??	
				 SvPHR
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases XLR8 V2.1
		
			SvPHR
		
		
		
		
		
		
		
		
	
			
		
					on:
					DATA AHEAD releases XLR8 V2.1	
				 daniel_rudaz
		
		
		
		
		
		
		
		
	
			
		
					on:
					XLR8 LabVIEW Tools Network DAQ Product of the Year 2014
		
			daniel_rudaz
		
		
		
		
		
		
		
		
	
			
		
					on:
					XLR8 LabVIEW Tools Network DAQ Product of the Year 2014	
				 christopherdoug
		
			christopherdougThe title of this entry should explain it well enough:
There exists a very very annoying bug in LabVIEW 2017 64-bit: You cannot activate a third-party toolkit in this particular LabVIEW version. This has come up several times now with our customers and I'm getting tired of always answering the same. So I'm writing this article and in the future, I just can send a link.
So again:
You will not be able to activate a third-party toolkit like XLR8, SP7 or git4G in LabVIEW 2017 64-bit.
What is the solution?
Do not use this LabVIEW version. Either stick to the 32-bit version of LabVIEW 2017 or since February 2018 if you need the 64-bit version stick to LabVIEW 2017 SP1 64-bit.
If you still experience problems with LabVIEW 2017 SP1 64-bit (I once has those during tests in a virtual machine), it seems that the additional installation of LabVIEW 2016 64-bit can resolve the activation problems.
For further general hints read this article from NI's support forum.
Data Ahead
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.