FIRST Robotics Competition Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem after installing SP1 update

File of NI License Manager has been attached

0 Kudos
Message 11 of 20
(1,613 Views)

I am having the same problem (I applied SP1) with the same error but in NIIMAQDX.DLL. I have fully uninstalled and reinstalled Labview and the FRC patch. I have also tried installing "NI Vision Acquisition Software August 2014 f1" with the reinstall option (suggested on another forum post), but the error still comes up usually at boot time or when running the NI Update Service. Before Labview would not work at all with the code, now it seems to be okay (after removing SP1), but this error keeps coming up. (It may not matter for now because we are not using the vision software at this point, but we may decide to do so in the future so we need to make sure this machine is working correctly.)

Thanks for any help you could provide.

0 Kudos
Message 12 of 20
(1,613 Views)

Im currently having the same issue working with LabVIEW 2012SP1. Was there a final work around for the error Gen_MarkExternalBufferNoThreadeCore in the nivissvc.dll file?

0 Kudos
Message 13 of 20
(1,613 Views)

Sorry. I should have replied as soon as I found a solution. Please do NOT do this unless you are familiar with messing in the System32 folder and with critical system files. You can damage the OS, lose data, and your computer may NOT be able to boot without reinstalling. I will not be held responsible for the following directions. They are for reference only and only to be used by an experienced system admin. This is not for the faint of heart. Backup your stuff first.

The details are a little fuzzy since I last worked on it 4 months ago, but if I remember correctly, I had to uninstall all the NI software, modules, and add ons and reboot. Then I had to go into my Windows\System32 folder and delete any NI support dll files that the uninstall did not properly delete. (You can right click a file, go to properties, and on the Details tab it will say it is copyright National Instuments if it is one of their files.) Most start with NI. I think there were about 5 of them. (I can't find the list right now.) The trick I missed was deleting those same files from the Windows\SysWOW64 folder. I missed SysWOW64 during my first cleanup attempts and so the error remained after reinstalling. Then reinstall all the components and patches without SP1 and the error no longer came up.

To NI: please fix your uninstaller to remove ALL your files. (Or provide a program to clean up after your uninstaller.) Thanks.

0 Kudos
Message 14 of 20
(1,613 Views)

Hi,

I am getting the same problem about "niimaqdx.dll". I have tried to reinstall my windows system and labveiw. But it didn't make any difference. Have you ever dissolved this failure? If yes,could you tell me the disposal method?

Thank.

0 Kudos
Message 15 of 20
(1,613 Views)

You reinstalled Windows entirely and still see this?

What versions of LabVIEW and Vision did you install after the fresh Windows installation?

Message 16 of 20
(1,613 Views)

When you reinstalled labview did you reinstall SP1? SP1 is the issue. If you wipe windows and reinstall labview without SP1 the message should not come up. You should only go up to the f1 update.

Message 17 of 20
(1,613 Views)

I installed labview 2013 and tried both VAS_2014_08 and VAS_2015_08_f1. They all didn't work. But now I install Labview2014 and VAS_2015_08_f1. It works well. Thank you very much.

0 Kudos
Message 18 of 20
(1,613 Views)

Yeah, I think you give me a good idea. Now I upgrade my labview to version 2014. The,message doesn't come up again. Thank you very much.

0 Kudos
Message 19 of 20
(1,613 Views)

A heads up rowan.  These forums are for the FIRST Robotics Competition and are discussing things dealing with their installation.  The answers you were receiving didn't reference which versions of LabVIEW and the such to install (outside of which version of the VAS to not install with LabVIEW 2014) as the FRC teams generally don't see the version of LabVIEW they have installed.  Their LabVIEW is setup in a way that's geared specifically to their competition.

http://forums.ni.com/t5/LabVIEW/bd-p/170  Check out these forums for typical LabVIEW questions.

0 Kudos
Message 20 of 20
(1,613 Views)