[BUG]

[RobCarlton]

Component

Full Dashboard

Performance Monitor Version

2.2.0

SQL Server Version

SQL 2022Standard Edition

Windows Version

Windows Server 2022

Describe the Bug

I get an error when trying to view the dashboard monitor graphs

Steps to Reproduce

1. Open the dashboard
2. Click on the server being monitored

Expected Behavior

To see the server resources in graphs

Actual Behavior

Error

Error Messages / Log Output

When I double click on the server name to view graphs, I get the following:
[2026-03-13 12:33:56.038] [INFO] === Application Starting ===
[2026-03-13 12:33:56.049] [INFO] Version: 2.2.0.0
[2026-03-13 12:33:56.050] [INFO] OS: Microsoft Windows NT 6.3.9600.0
[2026-03-13 12:33:56.051] [INFO] .NET Runtime: 8.0.25
[2026-03-13 12:33:56.051] [INFO] Log Directory: C:\Users\RCarlton\AppData\Local\PerformanceMonitor\Logs
[2026-03-13 12:34:21.729] [INFO] RefreshNocHealthStatusAsync starting for LWSQL001
[2026-03-13 12:34:21.811] [INFO] Connection opened for LWSQL001
[2026-03-13 12:34:21.850] [INFO] Blocking status: 0 blocked, longest 0.000000s
[2026-03-13 12:34:21.879] [INFO] All NOC queries completed for LWSQL001
[2026-03-13 12:34:21.881] [INFO] NOC status for LWSQL001: CPU=23%, Blocked=0, LongestBlock=0.000000s
[2026-03-13 12:34:25.990] [INFO] Connectivity check passed for server 'LWSQL001'
[2026-03-13 12:34:26.221] [ERROR] Unhandled Dispatcher Exception
Exception: XamlParseException
Message: The invocation of the constructor on type 'ScottPlot.WPF.WpfPlot' that matches the specified binding constraints threw an exception.
StackTrace:    at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
   at PerformanceMonitorDashboard.ServerTab.InitializeComponent() in D:\a\PerformanceMonitor\PerformanceMonitor\Dashboard\ServerTab.xaml:line 1
   at PerformanceMonitorDashboard.ServerTab..ctor(ServerConnection serverConnection, Int32 utcOffsetMinutes) in D:\a\PerformanceMonitor\PerformanceMonitor\Dashboard\ServerTab.xaml.cs:line 87
   at PerformanceMonitorDashboard.MainWindow.OpenServerTabAsync(ServerConnection server) in D:\a\PerformanceMonitor\PerformanceMonitor\Dashboard\MainWindow.xaml.cs:line 505
   at PerformanceMonitorDashboard.MainWindow.LandingPage_ServerCardClicked(Object sender, ServerConnection server) in D:\a\PerformanceMonitor\PerformanceMonitor\Dashboard\MainWindow.xaml.cs:line 831
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Screenshots

Additional Context

No response

[erikdarlingdata]

Thanks for reporting this, Rob! The log output is very helpful.

The crash is a XamlParseException wrapping a failure in ScottPlot's SkiaSharp native rendering library. ScottPlot 5 uses SkiaSharp under the hood, which requires native Skia binaries to be present at runtime.

One thing I noticed in your log: the OS is reporting as Microsoft Windows NT 6.3.9600.0, which is the kernel version for Windows 8.1 / Server 2012 R2 — not Windows Server 2022 (which should report 10.0.x). That could indicate the app is running under a compatibility shim, or there's something non-standard about the environment that's preventing SkiaSharp from loading the correct native libraries.

A few things to try:

1. Make sure the Visual C++ Redistributable (x64) is installed — SkiaSharp's native libs depend on it
2. Check if the app is running in compatibility mode — right-click the exe → Properties → Compatibility tab, make sure nothing is checked
3. Try running the app as Administrator once to rule out permissions issues loading native DLLs

On our side, I'm adding better error handling around the chart initialization so if this does happen, you'll get a clear error message pointing to the likely cause instead of a raw exception. Will be in the next release.