error 1097 for NI_AALBase.lvlib: Real Dot Product.vi

[RVR]

Hello,

I have recently upgraded to version 8.2 from version 7.1 (which I thought was superb!).

Anyway, when I transferred my code over to 8.2 I got the following error message:

'An exception occurred within the external node called by a Call Library Function Node. This might have corrupted LabVIEWS's memory. Save any work to a new location and restart LabVIEW.

VI "Myprogram.vi" was stopped at a node " " at a call to "NI_AALBase.lvlib:Real Dot Product.vi:7"

Note that I get similar errors for other vi's that use NI_AALBase.lvlib

I follwo instructions to save in other directory and when I rerun the program all is well, until next time i start up LVIEW when it happens again.

Now I thought that this may be a compatability issue between 7.1 and 8.2 as i did not unistall 7.1 from my machine.

So i have now unistalled all NI software following NI instructions (editing regedit, etc) and I have only installed 8.2, but when i run my program, the error is still there.

I looked up error codes in Labview and found that this is error 1097.

I followed similar post on this website but not really got an answer on how to solve this problem.

Can somwone please help?

[Steven_C]

Hi RVR,

I actually have 7.1 and 8.2 on my machine, so this particular combination should not be causing an issue. One thing I would suggest that you do is try repairing the 8.2 installation. This has been the solution to a similar issue involving problems with the NI_AALBase.lvlib. Please let me know if this does not work. Thanks!

Best regards,

Steven

[RVR]

Hi Steven

thanks for the response. I did the repair with no luck.

I also tried uninstalling again and installing using a previous release of 8.2 and no luck either.

I have been triing various things for a few days now with no luck.

Is there anything else that you can suggest?

What other support can NI offer for this problem?

[NIJanell]

Hello RVR,

Any chance that you actually installed LabVIEW 8.2.1?  That could be causing this issue.

Good luck!

Janell R | applications engineer

[RVR]

Hi Janell

not at all. I do not have 8.2.1.

can you suggest what else I can try?

Do any of the NI engineers have any idea of what is causing this problem and how I may solve it?

It is quite incredible that I am th eonly one with this problem and that no one seems to have any clues on how to fix it.

I hav been trying various things for a week and a bit now and have had very little support from NI.

I really do hope that someone can help.

Cheers

[NIJanell]

Hello RVR,

In a previous post, you said "I also tried uninstalling again and installing using a previous release of 8.2 and no luck either."  What do you mean a previous release?  There was only one LabVIEW 8.20 release, which was followed by the 8.2.1 release this month.

Do you still have a fresh copy of the 7.1 VI?  If so, I would try installing 8.2 on another machine and moving the VI over.  I truly think this will show that something happened during your previous installation.  To fix your current computer, we may need to remove all NI software.

Good luck!

Janell R | applications engineer

[RVR]

Hello Janell

thanks for the reply. to answer your questions:

-I installed and uninstalled about 4 times - each time removing all NI components and clearing the registry. Finally checking that all NI components were removed using MSIBLAST.

What i mean by a previous release is that I got sent 2 lots of LVIEW discs for 8.2 - one lot in August and one in November 2006. So what i mean by a previous version I mean the 8.2 discs sent to me in August - same version 8.2 just different discs.

I tried installing on another computer and moving the vi's over - it did not work.

I tried everything! my local NI support engineers did not know where else to go.

Finally yesterday, one of them sent me version 8.2.1 and the problem was solved.

So, it is a bug in the 8.2 version!

Thanks for your help.

[NIJanell]

Hello RVR,

How interesting - I haven't heard of this bug at all and cannot find documentation on it.  However, I am very glad your system is now up and running - good job!

Janell R | applications engineer