topic Re : svd 8.20 error in LabVIEW

svd 8.20 error

Olivier M — Mon, 27 Nov 2006 14:58:16 GMT

Hi,

I get the follwoing error with the SVD decomposition VI :
"[...] exception error while calling a dll [...]
NI_AALBase.lvlib:A x Vector.vi:5"

I have installed LV 8.20 on another PC and it works properly !

PC that works :
windows XP sp 2
dell dimension 8300
Intel P4 2.8GHz and 1Go RAM

PC that doesn't work :
windows XP sp 2
dell Optiplex GX745
Intel core2CPU 6400@ 2.13GHz and 2Go RAM

Does somebody have an idea ?

Sincerly

Olivier

Re : svd 8.20 error

jp_Braud — Wed, 29 Nov 2006 08:36:31 GMT

Hi,

This is a very strange behaviour. Could you please try to copy your math dll from the working computer to the other one? Because honestly, a dll problem is the most logical issue I can see by now.

Regards,

Re : svd 8.20 error

Olivier M — Fri, 01 Dec 2006 08:20:10 GMT

Hi,

I've copied my math dll from the working computer to the other one, and it didn't work.
I've reinstalled Labview 8.2 and I have the same error.

Olivier

Re : svd 8.20 error

jp_Braud — Mon, 04 Dec 2006 17:02:46 GMT

Hi,

... So strange ...

By chance, do you have an error number with this error?

Regards,

Re : svd 8.20 error

Olivier M — Thu, 07 Dec 2006 12:47:08 GMT

Hi,

Unfortunately, I don't have any error number.
You can find a screenshot of the error that occurs when I run the SVD decomposition...

The error number on the picture occurs only when the matrix A isn't set. (In this case, the error doesn't appear)
When I set this matrix to [1,0,0;0,1,0;0,0,1] for eg, the error occurs.

I find a new strange behaviour : << when I run one more time the vi, after changing the error indicator, it works !! >>
Nevertheless, I restart Labview 8.20, run the VI, and the error still occurs...

Sincerly,

Olivier

Re : svd 8.20 error

jp_Braud — Thu, 07 Dec 2006 13:15:12 GMT

Hi Olivier,

I founded that this error occur one time ago to someone! The VI used to work fine until the customer download the latest WindowsXP security update. in this case, he only solution we could give you would be to completely reinstall the NI softwares without forgotting to use a stuff like "MSI Blast" or like.

I'm sincerely sorry, this kind of error occurs when a dll is seen corrupted by a programming environment.

Regards,