June 21, 2018 at 9:58 am
Hi,
I have a test SSRS server that currently only has one report on it, I can see the report when I connect on the actual report server however when I connect to the report server on my laptop and try to view the report I get the following error message:
I have already tried deleting then republishing the report but that has not solved the issue.
Any suggestions?
P.S. this has worked as recently as a few weeks ago and as far as I'm concerned I have not made any changes to the report server or the report itself.
June 21, 2018 at 11:32 am
mharbuz - Thursday, June 21, 2018 9:58 AMHi,I have a test SSRS server that currently only has one report on it, I can see the report when I connect on the actual report server however when I connect to the report server on my laptop and try to view the report I get the following error message:
- An error has occurred during report processing. (rsProcessingAborted)
- Cannot create a connection to data source 'AdventureWorksDW'. (rsErrorOpeningConnection)
- For more information about this error navigate to the report server on the local server machine, or enable remote errors
I have already tried deleting then republishing the report but that has not solved the issue.
Any suggestions?
P.S. this has worked as recently as a few weeks ago and as far as I'm concerned I have not made any changes to the report server or the report itself.
It doesn't look like the issue is the report or the report server. The error is for the data source and not being able to connect.
Did you check the Reporting Services log as well as the data source?
Sue
June 22, 2018 at 2:23 am
Sue_H - Thursday, June 21, 2018 11:32 AMIt doesn't look like the issue is the report or the report server. The error is for the data source and not being able to connect.
Did you check the Reporting Services log as well as the data source?Sue
Hi Sue,
How can I see the Reporting Services log and what am I looking for?
Sorry if this is a simple questions but I am new to SSRS and I am using this test server to learn more about how it works and what I can achieve with it.
Matt
June 22, 2018 at 10:49 am
mharbuz - Friday, June 22, 2018 2:23 AMSue_H - Thursday, June 21, 2018 11:32 AMIt doesn't look like the issue is the report or the report server. The error is for the data source and not being able to connect.
Did you check the Reporting Services log as well as the data source?Sue
Hi Sue,
How can I see the Reporting Services log and what am I looking for?
Sorry if this is a simple questions but I am new to SSRS and I am using this test server to learn more about how it works and what I can achieve with it.Matt
Sure...no problem. With working on learning how SSRS works, knowing about the log can really help.
To find the log, the default path will be along the lines of Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
The log files are named using this naming convention: ReportServerService_MM_DD_YYYY_HH_MM_SS.log. It gets the date and time from when the log is created, reporting services starts up. You'll want to look through there and understand what's "normal" and what isn't. Most of the entries are informational and you can see them categorized with <date time> INFO followed by the action. You can see the entries when starting up as those have: INFO: Initializing. Here is a link for the documentation of the SSRS log:
Report Server Service Trace Log
When you have any issues, errors with SSRS, check the log as most issues will have some information in the log. Things will be logged sequentially and the issues with be categorized with ERROR (instead of INFO). It usually gives a decent amount of information - often enough to track down the issue, much more verbose then whatever error is thrown when using the portal/report manager. So go check that and look for the errors. If you can reproduce the error, go ahead and force it and then check the log. The errors would be at the end of the log (less to sort through).
And for the data source issue, check the data source in the portal, see if the properties look correct and do a test on the connection.
Checking those will give you more information on the errors.
Sue
June 25, 2018 at 4:36 am
Sue_H - Friday, June 22, 2018 10:49 AMmharbuz - Friday, June 22, 2018 2:23 AMSue_H - Thursday, June 21, 2018 11:32 AMIt doesn't look like the issue is the report or the report server. The error is for the data source and not being able to connect.
Did you check the Reporting Services log as well as the data source?Sue
Hi Sue,
How can I see the Reporting Services log and what am I looking for?
Sorry if this is a simple questions but I am new to SSRS and I am using this test server to learn more about how it works and what I can achieve with it.Matt
Sure...no problem. With working on learning how SSRS works, knowing about the log can really help.
To find the log, the default path will be along the lines of Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
The log files are named using this naming convention: ReportServerService_MM_DD_YYYY_HH_MM_SS.log. It gets the date and time from when the log is created, reporting services starts up. You'll want to look through there and understand what's "normal" and what isn't. Most of the entries are informational and you can see them categorized with <date time> INFO followed by the action. You can see the entries when starting up as those have: INFO: Initializing. Here is a link for the documentation of the SSRS log:
Report Server Service Trace Log
When you have any issues, errors with SSRS, check the log as most issues will have some information in the log. Things will be logged sequentially and the issues with be categorized with ERROR (instead of INFO). It usually gives a decent amount of information - often enough to track down the issue, much more verbose then whatever error is thrown when using the portal/report manager. So go check that and look for the errors. If you can reproduce the error, go ahead and force it and then check the log. The errors would be at the end of the log (less to sort through).
And for the data source issue, check the data source in the portal, see if the properties look correct and do a test on the connection.
Checking those will give you more information on the errors.Sue
Hi Sue,
Thanks for this I think I have managed to find out why I was getting this error, in the portal it was trying to connect to the data source using the logged in users credentials instead of the administrator credentials.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply