Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Following 9.5 upgrade - Some Reports won't run via Web, fine via Report Write

I have a few custom sql reports that stopped working via the webpage following 9.5 upgrade...following error occurs:

System.ArgumentNullException: Value cannot be null. Parameter name: s at System.IO.StringReader..ctor(String s) at System.Xml.Linq.XDocument.Parse(String text, LoadOptions options) at System.Xml.Linq.XDocument.Parse(String text) at SolarWinds.Orion.Web.Reporting.OrionReport.ApplyLayoutGroupingSort(String grouping, String& sort) at SolarWinds.Orion.Web.Reporting.OrionReport.BuildQuery(IC1QueryProxy c1host, String orderBy, String grouping, String filter) at SolarWinds.Orion.Web.Reporting.OrionReport.BuildQuery(String orderBy, String grouping, String filter) at SolarWinds.Orion.Web.Reporting.ReportRunner.WorkerProc()

....any ideas? When I run report via Report Writer they still run without issue.

Find more posts tagged with

custom_report

Accepted answers

FormerMember

This was indeed corrected in SP2.

All comments

bshopp

Have you opened a support ticket to look into and resolve?

brian_duvall

I called into support and opened case #99226. Support stated this is a known problem but he wasnt aware if the fix would be included in SP1. He had me open the reports that had issues in Report Writer and attempt a Save. When I tried to save it errored that a particular field was missing..so I added that field "NodeID" for my reports and set it to be a hidden field. After doing this on all my reports with issues I still get the same error via the web. Hopefully the bug will be fixed soon because these are my most critical reports.

Karlo.Zatylny

We have a temporary work around for this where you can remove the Grouping from the report in Report Writer and instead have an ORDER BY statement in the SQL.

Please let me know if this works for you.

Thanks

brian_duvall

To confirm the workaround...removing the Grouping from the report allowed the report to run via the web.

I assume this will be corrected via a service pack?

FormerMember

This was indeed corrected in SP2.