SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSRS configuration vs Report Builder configuration


SSRS configuration vs Report Builder configuration

Author
Message
pietlinden
pietlinden
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: General Forum Members
Points: 42392 Visits: 16084
is there an article (or whatever!) that details the differences between configuring Report Builder and configuring SSRS? I can get ReportBuilder to publish just fine. SSRS doesn't doesn't want to play. (They both connect to the same data sources etc... it's just the publishing settings in my instance of SSRS that are totally screwed up.)

I'm just trying to fix an improperly configured instance of SSRS 2016
Sue_H
Sue_H
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47625 Visits: 12323
pietlinden - Friday, February 2, 2018 11:32 AM
is there an article (or whatever!) that details the differences between configuring Report Builder and configuring SSRS? I can get ReportBuilder to publish just fine. SSRS doesn't doesn't want to play. (They both connect to the same data sources etc... it's just the publishing settings in my instance of SSRS that are totally screwed up.)

I'm just trying to fix an improperly configured instance of SSRS 2016


I don't think so. The publishing is configured more client side unless you are having some kind of permissions issue.
What are the problems and errors you get? And is this just with Report Builder or are you also using SSDT?

Sue



pietlinden
pietlinden
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: General Forum Members
Points: 42392 Visits: 16084
Sue,
If I use Report Builder, I can create and publish reports just fine. I connected to the same database just to keep the results as close as possible.

What's the best way to diagnose what's going wrong with SSDT? I'm sure my SSDT/SSRS instance isn't configured properly, because I can't publish. Should I look at the Execution Log? Which? (where even is it?)

Thanks!
Sue_H
Sue_H
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47625 Visits: 12323
pietlinden - Friday, February 2, 2018 3:37 PM
Sue,
If I use Report Builder, I can create and publish reports just fine. I connected to the same database just to keep the results as close as possible.

What's the best way to diagnose what's going wrong with SSDT? I'm sure my SSDT/SSRS instance isn't configured properly, because I can't publish. Should I look at the Execution Log? Which? (where even is it?)

Thanks!


Okay...that really sounds like it's SSDT then. The execution log views won't do you any good - they are really more for the report execution.
You can try looking in the Reporting Services trace log - that one I mentioned the other day. Should be in the following on whatever drive where you installed:
Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
Those files in there are what are often called the Reporting Services logs. MS often refers to them as the trace logs. Anyway...with SSDT it's often VS shell that can cause issues or in configuration manager, things are messed up. I was reading about a lot of problems and known bugs with one of the recent versions. It's like they all have different bugs...irritating as H. I recently just uninstalled mine as it was pissing me off too much. Here are a couple of deploy issues for one of the buggier versions:
Unable to deploy SSRS report
SSDT - Deploy Report To RS Gives "The given key was not present in the dictionary."

I would try downloading another version - that's what I was doing when I hit bugs. The bugs almost seem like they change on different releases. So you learn to live with the ones that don't mess up your work. Those ones usually if you restart you are fine. But a problem with deploying isn't one to live with.
Are you getting any specific errors when it won't deploy?

Sue



pietlinden
pietlinden
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: General Forum Members
Points: 42392 Visits: 16084
Which versions are okay? I have these... Not sure which are buggy, but I've read a couple of versions of SSDT were wonky as hell.
Microsoft Visual Studio 2015 Shell (Integrated)
Version 14.0.23107.0 D14REL
Microsoft .NET Framework
Version 4.7.02556

Installed Version: IDE Standard

Microsoft Visual Studio Tools for Applications 2015 00322-10000-00000-AA908
Microsoft Visual Studio Tools for Applications 2015

Visual Basic 2015 00322-10000-00000-AA908
Microsoft Visual Basic 2015
Visual C# 2015 00322-10000-00000-AA908
Microsoft Visual C# 2015


SQL Server Analysis Services 14.0.514.48
Microsoft SQL Server Analysis Services Designer
Version 14.0.514.48

SQL Server Data Tools 14.0.61704.140
Microsoft SQL Server Data Tools

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 14.0.500.272

SQL Server Reporting Services 14.0.514.48
Microsoft SQL Server Reporting Services Designers
Version 14.0.514.48

When I try to publish the report from within SSDT, I get this not so helpful message:
Build complete -- 0 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Deploy fails, but there are not error messages other than that.
Sue_H
Sue_H
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47625 Visits: 12323


This one is a little newer and might be worth a try. I haven't found one without bugs, they've all just had different ones. And if you're on a home laptop, Windows 10 updates and those issues aren't helping:
Download SQL Server Data Tools (SSDT)

The last time I got that same error it was me not setting it right in configuration manager that you have to change for deploying. From memory, in configuration manager go to the build tab and select Deploy option. I think that's what it was. But usually for normal people, it ends up being something with the TargetServerURL so double check that setting.

Sue



pietlinden
pietlinden
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: General Forum Members
Points: 42392 Visits: 16084
What configuration property is the Target Server URL supposed to match? (That's the part that doesn't make sense to me... if I wrote blogs, I'd write one about that and have the Configuration stuff on one side of the page and the SSRS config stuff in a page next to it...) Maybe I'm dense, but the way MS does this boggles my mind.
Sue_H
Sue_H
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47625 Visits: 12323
pietlinden - Friday, February 2, 2018 5:02 PM
What configuration property is the Target Server URL supposed to match? (That's the part that doesn't make sense to me... if I wrote blogs, I'd write one about that and have the Configuration stuff on one side of the page and the SSRS config stuff in a page next to it...) Maybe I'm dense, but the way MS does this boggles my mind.


Use the Web Service URL - it's on the Reporting Services Configuration Manager.
You used the defaults so it should be http://localhost/reportserver or http://YourPC/reportserver

Are you actually expecting MS to make sense? Smile It is sad though as documentation used to be one of their strengths. They've gone the opposite way. It's like a continual cycle of spastic feature releases without much regard for stability or documentation.

Sue



pietlinden
pietlinden
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: General Forum Members
Points: 42392 Visits: 16084
If I attempt to go to ReportServer (http://desktop-6p4std8/ReportServer), instead of getting a web site, I get

desktop-6p4std8/ReportServer - /

and then a list of files. (So it's like the SSRS report server isn't acting like a server at all.
Sue_H
Sue_H
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47625 Visits: 12323
pietlinden - Friday, February 2, 2018 5:53 PM
If I attempt to go to ReportServer (http://desktop-6p4std8/ReportServer), instead of getting a web site, I get

desktop-6p4std8/ReportServer - /

and then a list of files. (So it's like the SSRS report server isn't acting like a server at all.


That's how it will look. You won't have reports with that URL - it's just the for the Web Service. You deploy to that one. And then the YourPC/Reports (not ReportServer) will have the reports.

Sue



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search