LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Vitrek PA900 labview third party drivers installation error

Dear community,

 

When installing the thrid party Vitrek PA900 labview drivers:

 

TTMSService_0-1670253813437.png

The Library name or path was redirected to C:\Users\Steve\Documents folder

 

 

TTMSService_1-1670253813445.png

 

Even when changed to the correct path the virtual instruments are still not working:

 

TTMSService_2-1670253813450.png

 

TTMSService_3-1670253813455.png

 

TTMSService_4-1670253813460.png

 

Does anyone has more experience or encountered the same ?

What was the solution?

 

Secondly the program Vitrek PA900 Screen Editor also crashes. It that related to previous error do you think?

 

 

TTMSService_5-1670254037511.png

 

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.IO.FileNotFoundException: Could not load file or assembly 'NationalInstruments.NI4882, Version=8.9.35.104, Culture=neutral, PublicKeyToken=18cbae0f9955702a' or one of its dependencies. The system cannot find the file specified.

File name: 'NationalInstruments.NI4882, Version=8.9.35.104, Culture=neutral, PublicKeyToken=18cbae0f9955702a'

   at XT2640_Custom_Screens.PA900_Communications.disconnect()

   at XT2640_Custom_Screens.PA900_Communications.GPIBAddrBox_ValueChanged(Object sender, EventArgs e)

   at System.Windows.Forms.NumericUpDown.OnValueChanged(EventArgs e)

   at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)

   at System.Windows.Forms.NumericUpDown.set_Minimum(Decimal value)

   at XT2640_Custom_Screens.PA900_Communications.InitializeComponent()

   at XT2640_Custom_Screens.PA900_Communications..ctor()

   at XT2640_Custom_Screens.Form1.Button1_Click(Object sender, EventArgs e)

   at System.Windows.Forms.Control.OnClick(EventArgs e)

   at System.Windows.Forms.Button.OnClick(EventArgs e)

   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ButtonBase.WndProc(Message& m)

   at System.Windows.Forms.Button.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.9164 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

PA900 Screen Editor

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Workspaces/LabVIEWprojects/Vitrek_PA900/PA900_Screen_Editor/PA900%20Screen%20Editor.exe

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 8.0.0.0

    Win32 Version: 8.0.50727.9157 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

----------------------------------------

System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System.Runtime.Remoting

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

----------------------------------------

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.9157 (WinRelRS6.050727-9100)

    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

 

Thanks for any help or advice!

 

Kind regards,

Robert Kousbroek

 

0 Kudos
Message 1 of 1
(955 Views)