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

Forum Announcement

The Login VSI forum has been disabled and now only serves as an archive. If you would like to submit a new support ticket, please send an email to support@loginvsi.com.

Error using Management Console on Windows 2012

  • ReneB
  • ReneB's Avatar Topic Author
08 Jan 2013 13:14 #673

VSI Version:3.7
Test system: Microsoft RDS
Operating system version target: Server2008R2 x64
Operating system version launcher(s):Server2003R2 x86
Office version target: Office 2010
Host (Management Console) and DC:Windows 2012

When starting a test from the Management console an unhandled exception appears (see screenshot and error below).

Workaround: run Management Console as administrator (using contextmenu on shortcut). The logged in user is domain admin which is member of administrators group, so in my opinnion this should not be necessarily.

Kind regards,
René
======================




Error:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception: Access is denied
at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.Process.get_MainModule()
at LogIn.Libraries.Management.VSIManagementLibrary.LocalAgentRunning()
at VSI_Admin_Console.frmMain.btnStart_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.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.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.6400 (Win8RTMGDR.050727-6400)
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.6387 (Win8RTM.050727-6300)
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.6400 (Win8RTMGDR.050727-6400)
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.6387 (Win8RTM.050727-6300)
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.6387 (Win8RTM.050727-6300)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.6387 built by: Win8RTM
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.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.

Attachments:

Please Log in to join the conversation.

More
08 Jan 2013 16:57 #681

Hi René,

I cannot reproduce this, I have exactly the same setup, logged in as 'domain administrator' and UAC enabled, W2012 DC/AD/DNS/DHCP and the VSI MMC and Launcher Agent in place.
(not facing the unhandled exception when starting a test from the VSI MMC)

Is the following option checked in the MMC; Auto start launcher?

Regards,

Omar

Please Log in to join the conversation.

  • ReneB
  • ReneB's Avatar Topic Author
08 Jan 2013 18:42 #682

Hello Omar,

Thanks for fast response.
The Auto Start Launcher option is not enabled and only the MMC is installed
Just to be sure, the name of the logged in user is ´adminrb (so it´s not a named administrator). I know starting from Windows 7 that makes a difference.

Kind regards,
René

Please Log in to join the conversation.

More
08 Jan 2013 19:31 #683

René,

Is there a process named agent running, other than the VSI launcher agent?

Please Log in to join the conversation.

  • ReneB
  • ReneB's Avatar Topic Author
09 Jan 2013 08:29 #684

Hello Dennis,

Yes, the RES Automation Manager Agent process is called agent.exe. That process is running under the system account.

Kind regards,
René

Please Log in to join the conversation.

More
10 Jan 2013 16:45 #688

René,

I have confirmed this to be a bug. The VSI management console does not expect to encounter a process that does not allow querying of the executable path. I have added this issue to the list of known issues in VSI 3.7. We will work on fixing this issue in a minor update, VSI 3.7.1

You can find the list of known issues here .

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