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

"Refresh" and "Printable Version" buttons not working on Syslog page

I have upgraded to version 8.5. Searching through the Syslog page works fine for a while, but if you perform a query that takes a long time to complete, the page just clears all of your search specs. After this happens, the refresh and printable version buttons take you to a generic 404 "The page cannot be found" page. This renders the Syslog page useless.

It appears that when this happens, the page posts to /servername/orion/Syslog.asp instead of /servername/NetPerfMon/Syslog.asp.

I am able to resolve this issue by performing a "Clear Web Cache"...until I try another query that takes "too long". I have installed Hotfix 1 with no change.

Any ideas?

Find more posts tagged with

Accepted answers

All comments

tdanner

Could you check the browser's location bar when it is in this state? See if the path looks like /Orion/Proxy.aspx?... That could cause this behavior. Proxy.aspx is part of the glue we're using to connect the old ASP and new ASP.NET parts of the website. We try to hide it, but sometimes it leaks out and causes problems like this.

derek.taylor

When it works... http://servername/NetPerfMon/SysLog.asp

When it fails... http://servername/orion/Syslog.asp

If I use the back button in IE...http://servername/orion/proxy.aspx?path=/NetPerfMon/Syslog.asp

Thanks for the quick response.

derek.taylor

Mr. Danner, any further ideas on this problem?

Thanks

tdanner

Proxy.aspx is definitely the cause. A workaround would be to hit Back until you get to the version of the page that doesn't have Proxy.aspx in the URL. The next service release will have some extra tricks to fix some cases that are exposing Proxy.aspx.