login vsi company logo login vsi company logo 250x40
header-01.jpg

Unhandled exception when running Management Console

  • aminf13
  • aminf13's Avatar Topic Author
03 Apr 2013 22:07 #874

Hello,

I installed launcher agent and management console on a clean installation of Windows Server 2008 R2, 64-bit. When I start the management console, I receive the following exception. I can choose "Continue" and enter the console, but I'm wondering if something is wrong and how I can resolve this problem.

Thanks,
Amin


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 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
at LogIn.Libraries.Management.VSIManagementLibrary.VSIShareWritable(String VSIShare)
at VSI_Admin_Console.frmMain.frmMain_Shown(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnShown(EventArgs e)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

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.5466 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll


VSI Management Console
Assembly Version: 3.7.3.2
Win32 Version: 3.7.3.2
CodeBase: file:///C:/Program%20Files/Login%20Consultants/VSI/Launcher/Console/VSI%20Management%20Console.exe
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
VSIDataTypes
Assembly Version: 3.7.3.1
Win32 Version: 3.7.3.1
CodeBase: file:///C:/Program%20Files/Login%20Consultants/VSI/Launcher/Console/VSIDataTypes.DLL
LoginCustomControls
Assembly Version: 3.7.3.1
Win32 Version: 3.7.3.1
CodeBase: file:///C:/Program%20Files/Login%20Consultants/VSI/Launcher/Console/LoginCustomControls.DLL
VSILicenseHandler
Assembly Version: 3.7.2.1
Win32 Version: 3.7.2.1
CodeBase: file:///C:/Program%20Files/Login%20Consultants/VSI/Launcher/Console/VSILicenseHandler.DLL
VSIManagementLibrary
Assembly Version: 3.7.3.1
Win32 Version: 3.7.3.1
CodeBase: file:///C:/Program%20Files/Login%20Consultants/VSI/Launcher/Console/VSIManagementLibrary.DLL
VSIIniReader
Assembly Version: 3.7.3.1
Win32 Version: 3.7.3.1
CodeBase: file:///C:/Program%20Files/Login%20Consultants/VSI/Launcher/Console/VSIIniReader.DLL
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.

Please Log in to join the conversation.

  • aminf13
  • aminf13's Avatar Topic Author
03 Apr 2013 22:17 #875

Sorry for the false alarm, I had to go and enable .Net Framework 3.5.1 in Windows Features. That solved the problem.

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200