December 1, 2017 at 11:57 am
We have an Enterprise vendor application for student system.
We have our some customized pages that using SSRS reports.
It is in an HTML put into powerschool site, but has an iframe that hosted a report viewer that connects to a SSRS report in our own SSRS server.
Recently we get a message for a user,
INC0097853 - Access violation screen is the report. It has been logged into Powerschool log.
I checked the report on SSRS server, it runs fine on the server, the security looks good, and there is no any timeout or error.
I run this OK on the powerschool site too. so cannot reproduce it.
Some of the users has the same problem, but after they logged off and logged in, it runs OK.
But for just this one user, even logged off and log in still not work for her.
I suspect it is a Powerschool problem, it looks like it has not reached so far to run the report.
Any suggestions to troubleshoot?
Thanks
December 1, 2017 at 12:15 pm
I'd agree with you in that in looks more like a Powerschool issue - or maybe something with the Report Viewer. From what you describe, I doubt it's an SSRS issue. Nonetheless, you could check the Reporting Services log files to see if there is something in there. Not likely but best to check anyway.
Does Powerschool do any logging?
Other than that, I'd probably check all of the servers involved for any dump or minidump files as those would typically name the module involved. Or you could run it through WinDbg.
I'd check the event logs on all of the servers involved as well.
Sue
December 1, 2017 at 2:25 pm
I did check the SSRS log, qurey ReportDB tables, no warning and error of any kind.
Powerschool log has the same message as in my first post. Nothing else.
We logged in as the same user, and was able to duplicate the error.
The strange thing is we navigate to another report, run the report, and later come back to the problem report, then runs fine.
But everytime the user has to do this work around.
The user has permissoions correct setup an any other user.
I suspect it is the html page that hosted the reports viewer, the two reports above they on same powerschool html page, but the report viewer
shows different reports.
December 1, 2017 at 2:50 pm
sqlfriends - Friday, December 1, 2017 2:25 PMI did check the SSRS log, qurey ReportDB tables, no warning and error of any kind.
Powerschool log has the same message as in my first post. Nothing else.We logged in as the same user, and was able to duplicate the error.
The strange thing is we navigate to another report, run the report, and later come back to the problem report, then runs fine.But everytime the user has to do this work around.
The user has permissoions correct setup an any other user.
I suspect it is the html page that hosted the reports viewer, the two reports above they on same powerschool html page, but the report viewer
shows different reports.
That is weird. Is that with Active Directory accounts or a application, program login? Or is it some kind of mapping between Powerschool and Active Directory or something like that?
From how you describe it, I wonder if its not something with verifying that users credentials or permissions. You could possibly find something in the security logs on the Powerschool server. And check the security logs on the PC after reproducing that issue.
Did you check the security and application event logs on whatever server is hosting the report view control? There have been weird errors with that control before - seems a fair amount related to the web config files. And iframes but I thought most of those had been resolved.
Shot in the dark and not likely but do you have a test or dev environment with all of this? I was just wondering about trying out different versions the ReportViewerControl. Any way you can check which version you are using?
Sue
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply