Custom reports and limitation problems

I wrote this report, which lists active advanced alerts, along with information about the host and such. Whenever I atttempt to view this through an account with a limitation applied, I get the following: Incorrect syntax near the keyword 'Where'

select NODES.CAPTION, NODES.STATUSLED, NODES.PRIMARY_ROLE, ALERTDEFINITIONS.ALERTNAME, ALERTSTATUS.OBJECTNAME, ALERTSTATUS.TRIGGERTIMESTAMP, interfaces.interfacename, interfaces.interfacetypedescription, interfaces.interfacespeed, interfaces.statusled, interfaces.interfaceicon, interfaces.inpercentutil, interfaces.outpercentutil

From (alertdefinitions INNER Join alertstatus on (alertdefinitions.alertdefid = AlertStatus.AlertDefID) inner join interfaces on (interfaces.interfaceid = AlertStatus.activeobject) inner join nodes on (interfaces.nodeid = nodes.nodeid))

where alertdefinitions.objecttype = 'interface'

I cannot use basic alerts, and cannot handle how little information is given by default of the advanced alerts. I need to have a summary page that can show relevant information about advanced alerts.

does anyone have any suggestions on how I can accomplish this?

Thanks

Steve

Find more posts tagged with

advanced_alerts

sql

summary_page

interface

custom_report

Accepted answers

All comments

thurgoodj187

Bump<?>

FormerMember

Bump. I'm having the same issue with a custom sql report. Runs fine in the report viewer, runs fine on the web as admin, but bombs out with a limited account. All the devices being spit back in the report, this account should have access to.

Any ideas where I should start looking?

Thanks!

thurgoodj187

I didn't... basically I build the main pages with "where" filters, but the users have rights to see whatever they want if they know how to get to it (say top 10 lists, search, etc). We are 1 company, not really worried about keeping things separate. It would be nice to be able to use some of the canned stuff out of the box, instead of recreating 4,5,10 versions of each report for all of our various groups. I have pretty much given up on any form of support from solarwinds, other than updates. I never did call them on this one. My past experiences were painful.

Good luck

Steve

FormerMember

thurgoodj187,

I'm sorry to hear that you've had poor experiences with Support. We did go through a period in early 2007 where we were very short-staffed. That problem was cleared up a long time ago, so if you're having problems, please open a ticket.

Rangertdc,

Please note the original post was in September of 2007, probably about v8.5. There have been many releases since then, so it's likely that your problem is different from the original problem reported, even though the symptoms are nominally the same.

dcl