Exception always occurs after the app runs for a day or two

[willow_techie]

First of all, thanks for such a useful program.

I do, however, get this error after leaving the application open for a day or two. It happens if I click on the production server in the server group from the tree list. Once this happens, I can't view any server properties anymore.

I am running Windows 2008.


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

************** Exception Text **************
System.ArgumentException: The min value of the axis range (6/1/2008 9:52:09 AM) should be less than its max value (5/30/2008 3:11:40 PM).
at DevExpress.XtraCharts.AxisRange.CheckRange(Object minValue, Object maxValue)
at DevExpress.XtraCharts.AxisRange.set_MinValue(Object value)
at LogShippingMonitor.ucDisplayTrend.DisplayTrend(ServerConfig server, TrendInterval trendInterval, TrendData trendData, Boolean showDate)
at LogShippingMonitor.ucServerSummary.Display(ServerConfig server)
at LogShippingMonitor.frmMain.DisplayData(Int32 groupID, Int32 serverID, Boolean alwaysUpdateAlerts)
at LogShippingMonitor.frmMain.tvGroups_AfterSelect(Object sender, TreeViewEventArgs e)
at System.Windows.Forms.TreeView.OnAfterSelect(TreeViewEventArgs e)
at System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
at System.Windows.Forms.TreeView.WmNotify(Message& m)
at System.Windows.Forms.TreeView.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.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
LogShippingMonitor
Assembly Version: 1.0.1.0
Win32 Version: 1.0.1.0
CodeBase: file:///C:/logshippingmonitor/LogShippingMonitor.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
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.1434 (REDBITS.050727-1400)
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.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
DevExpress.XtraCharts.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.XtraCharts.v6.3.DLL
----------------------------------------
DevExpress.XtraCharts.v6.3.UI
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.XtraCharts.v6.3.UI.DLL
----------------------------------------
DevExpress.Utils.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.Utils.v6.3.DLL
----------------------------------------
DevExpress.Data.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.Data.v6.3.DLL
----------------------------------------
DevExpress.XtraEditors.v6.3
Assembly Version: 6.3.3.0
Win32 Version: 6.3.3.0
CodeBase: file:///C:/logshippingmonitor/DevExpress.XtraEditors.v6.3.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
-xudwyjn
Assembly Version: 1.0.1.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
glxfvbda
Assembly Version: 1.0.1.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
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.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.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.

[Jason Cook]

Hi Willow,
Thank you for reporting this to us. I've passed the information on to the developer of the tool who should resolve it in a future release.

Unfortunately, because it's a 'labs' tool, I don't have an estimation to when such a release would occur, but we will announce it here if one becomes available.

Thanks,
Jason