is there a log where ssrs errors are recorded?

Question

hi we run 2014 enterprise. whenever i see the error below i wonder how the error can be seen without enabling remote errors and without running the report right on the report server itself. is there a log somewhere where ssrs errors are recorded?

Answer 1

Hi @db042190 ,

You can open the remote errors, and find logs atC:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles

About how to enable the remote errors:

how-to-enable-remote-errors-in-ssrs.html

Best Regards,
Isabella

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

thx isabella. i think you mean rdp to the report server and find that file? I was hoping to get an answer that didnt involve enabling remote errors. and i dont really know what opening remote errors means.

Answer 3

Hi db042190-2983,
Thanks for your reply.

I was hoping to get an answer that didnt involve enabling remote errors. and i dont really know what opening remote errors means.

I’m afraid we have to enable remote errors through SSMS. Enabling remote errors ensures that the SSRS log file can include external error information (for example, error information about report data sets) with the error messages that are returned for users who request reports from remote computers.
Currently, the error message is too ambiguous to analyze.
And please make sure that the account that the SSRS reports run under has sufficient permission to access dataset. Please take a look at this similar thread.

Best Regards,
Amelia

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

isabella and amelia, both your links show how to do something simple but neither explains what to expect. are you saying that if i follow the simple instructions to enable remote errors, that previously ambiguous messages will now show where they usually do at report rendering time, in my client browser but they will be more clear? I don know what "open remote errors" means nor do i know what to tell my dba to expect resource wise if we turn this on for ssrs. there must be a reason why by default its off. and i think its fair to ask if the content in the log will be clearer too?

lets say i rdp to that ssrs server and peek at the log on the "c" drive and look at an error that resulted at the same time an exec proc permissions problem occured. then i enable , reboot etc. does the content of the log also get clearer for the same type of error or just what displays on my local browser in place of what is now a very ambiguous/general error ?

what if i raise an error in the proc? does the log entry look the same before and after the enabling/reboot exercise? and does my message from the raise error start showing (after enabling) in that same spot in my browser where the ambiguous error used to show?

Answer 5

i found our logs.

my conclusion so far is that if i raise an error of 10 severity the accompanying message doesn't show in the log and the proc isn't interrupted.

severity of 18 shows my message clearly in the log but as i think amelia and isabella are saying, the displayed message in my browser remains that small font ambiguous message.

we are going to enable remote errors and see where this takes us. i'll post answers to some of the mysteries here.