March 26, 2017 at 10:12 am
This may sound as silly question but here's my situation:
I'm a newcomer in my work, where we use a server named "DWH" and we currently upload our reports from SSRS to Reporting Server, where our customer can reach them. I've got an idea we can use Report Builder and Mobile Report Publisher instead, but when I log in through remote desktop on our physical server and run SQL Server Configuration Manager, I see the address for report server as "http://dwh:80/Reports" which does not work in RB. I've tried any possible variantions as dwh/reports, /ReportingServices, dwh, ... but with no success.
Any advice would be appreciated. Thanks in advance.
March 26, 2017 at 12:27 pm
It should be the report server web service URL that you connect to (ex: http://dwh:80/reportserver). In order to use that you need to confirm the following:
- The reporting services web service has been configured for that instance of SSRS
- You have the correct URL for the web service. You should be able to get this from the admin managing your SSRS instance
- The account that you are using has rights to upload reports to the location you are trying to upload to
I am guessing you are using a stand-alone version of Report Builder? Another thing you could try would be to get with the admin of the SSRS instance and see if the Report Builder click-once app is configured. If so you could open Report Builder from within your SSRS instance and it would automatically be connected to the right URL.
What do you get when you try and connect now?
Joie Andrew
"Since 1982"
March 27, 2017 at 1:42 am
Thanks for your reply.
Despite writing correct address http://dwh:80/ReportServer in this thread, I lost the second "/" behind "http:/" in connection string within Report Builder.
However, when I want to publish report parts, the process fails.
Further, when I run a report it retrieve back an error "Failed to preview the report. The definition of this report is not valid or support by this version..." I tried to change TargetVersionServer to "2008 R2, 2012 and 2014" and Default Deployment Server Version to 10.0 and opened the report from bin/Debug folder, but the issue still persists.
Any help would be appreciated.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply