SSRS configuration vs Report Builder configuration

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.)

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,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?)

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\LogFilesThose 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 reportSSDT - 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?

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 D14RELMicrosoft .NET FrameworkVersion 4.7.02556

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.

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.

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.

Are you actually expecting MS to make sense? 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.