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

normal Saving report from analyzer = unhandled exception

  • enichols
  • enichols's Avatar Topic Author
20 Jun 2013 22:00 #1175 by enichols
enichols created the topic: Saving report from analyzer = unhandled exception
How do we fix this?

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

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Login.AutomaticReporting.OverViewReport.GenerateReport(String filename, VSILogEntry log, List`1 Charts, Hashtable Settings)
at VSI_Analyzer.ChartClass.GenerateReportToolStripMenuItem_Click(Object sender, EventArgs e)
at VSI_Analyzer.frmMain.toolStripMenuItem1_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
Login VSI Analyzer
Assembly Version: 4.0.42.1556
Win32 Version: 4.0.42.1556
CodeBase: file:///C:/temp/Analyzer/Login%20VSI%20Analyzer.exe
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
VSIIniReader
Assembly Version: 4.0.40.1329
Win32 Version: 4.0.40.1329
CodeBase: file:///C:/temp/Analyzer/VSIIniReader.DLL
VSILicenseHandler
Assembly Version: 4.0.40.1329
Win32 Version: 4.0.40.1329
CodeBase: file:///C:/temp/Analyzer/VSILicenseHandler.DLL
VSIDataLibrary
Assembly Version: 4.0.41.1555
Win32 Version: 4.0.41.1555
CodeBase: file:///C:/temp/Analyzer/VSIDataLibrary.DLL
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
Interop.ADOX
Assembly Version: 2.8.0.0
Win32 Version: 2.8.0.0
CodeBase: file:///C:/temp/Analyzer/Interop.ADOX.DLL
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
System.Windows.Forms.DataVisualization
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.116
CodeBase: file:///C:/temp/Analyzer/System.Windows.Forms.DataVisualization.DLL
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
System.Data.DataSetExtensions
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Data.DataSetExtensions/3.5.0.0__b77a5c561934e089/System.Data.DataSetExtensions.dll
AutomaticReporting
Assembly Version: 4.0.41.0
Win32 Version: 4.0.41.0
CodeBase: file:///C:/temp/Analyzer/AutomaticReporting.DLL
DocumentFormat.OpenXml
Assembly Version: 2.0.5022.0
Win32 Version: 2.0.5022.0
CodeBase: file:///C:/temp/Analyzer/DocumentFormat.OpenXml.DLL
WindowsBase
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.5011 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/WindowsBase/3.0.0.0__31bf3856ad364e35/WindowsBase.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.

More
21 Jun 2013 09:20 #1176 by o.bouhaj
o.bouhaj replied the topic: Saving report from analyzer = unhandled exception
Hello enichols,

Which version of the Analyzer/Management Console do you use? (you can check that in the window titles).
Hoping to hear from you soon. Thanks,

Regards,

Omar.

Please Log in to join the conversation.

  • enichols
  • enichols's Avatar Topic Author
21 Jun 2013 15:17 #1186 by enichols
enichols replied the topic: Saving report from analyzer = unhandled exception
4.0.42.1556 Express

Already tried copying Template.docx (attached) from C:\Shares\VSIshare\_VSI_ManagementConsole to C:\Shares\VSIshare\_VSI_Binaries\Analyzer

Please Log in to join the conversation.

More
26 Jun 2013 14:31 #1212 by o.bouhaj
o.bouhaj replied the topic: Saving report from analyzer = unhandled exception
Hi Eni,

I suggest updating the bits with the latest patch (4.0.2); www.loginvsi.eu/download/VSI40/LoginVSI402Patch.exe
PS, a backup before you upgrade to be sure is good.

Let me know.

Thanks,

Omar

Please Log in to join the conversation.

  • enichols
  • enichols's Avatar Topic Author
26 Jun 2013 15:47 #1218 by enichols
enichols replied the topic: Saving report from analyzer = unhandled exception
We were already at 4.0.2 patch. Re-applying the patch did not change the version number of the analyzer. Maybe you or another forum member could be so kind as to export the two reports for us? The data might be useful to others, we ran two tests, one on VMWare View and the other on XenDesktop.

You will see that the createprofile workload txt file exists but that the medium workload content is in there. This is because as per my previous post, this is the only workload we could get to work despite the documentation stating that the medium workload should work.

Please Log in to join the conversation.

What our customers are saying

Michael Cooper - Citrix

"We use Login VSI as a level set. If we are looking at a system that we are putting on brand new hardware or that we are putting in the cloud, we may see those environments completely differently but the end result is: is the user going to have a good solid happy user experience? And what Login VSI provides us on all three platforms is fairly consistent apples-to-apples comparison: is the user happy?"

Michael Cooper, Director of Solutions Architecture and Global Alliances at Citrix Systems


Eduardo Molina - RoundTower Technologies

"Login VSI support is fantastic. I had one issue, things were not working. I sent an email, got a call the next morning and the guy knew exactly what I was talking about and we just solved the issue in less than an hour. And that was one thing that was really, really great, the support that we get from Login VSI is fantastic."

Eduardo Molina, Virtualization and Cloud Architect at RoundTower Technologies


Andrew Mills - Nutanix

“Predictability is a key piece to VDI. It’s one of reasons that VDI has scared people away, but Login VSI solves that. If you’re going to do it, do it right. Login VSI really gives that rubber stamp on doing it right.”

Andrew Mills, VDI Alliances Manager at Nutanix

Login VSI, Inc.

300 Tradecenter

Suite 3460
Woburn, MA 01801

Phone: +1 844 828 3693

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200