In my project I've a general folder for all my reports. I want to run these report for 2 different systems, (same server, different databases, same store procedure)
after I deploy I created 2 folder and I moved the DataSource and the report into them and update the connection string for each database.
I've 2 issues:
In one the report runs ok but when I tried to edit my DataSource I got the error "An internal error occurred on the report server."
In second folder I can edit the DataSource to change the connection string but the report show values in 0
I'm guessing that I don't need to create Data Source in each folder, Am I in the right way to do that?
I would recommend creating two different projects within a solution. This will let you set the deployment settings for each project. You can do all the copying on your local machine after you modify a report and then deploy.
Related
Visual Studio 2019, SSIS project.
Whenever I drop a new Destination Assistant into a Data Flow I am required to create a new Connection Manager to our SQL Server instance.
Presently, there are 4 identical Data Connections (except the index appended on the name) and none of them show up in the list of "Select connection managers." TBH this is driving me nuts. It is the same behavior for both Package and Project scoped Connection Managers.
Any ideas? Everything I see everywhere just shows the Database connection managers listed as expected - but they don't show up for me.
Don't use the assistants. Not to be flippant but I don't find that they add any value. I know whether I'm pushing/pulling from a flat file vs OLE DB so why do I want to make clicks here versus just dragging the thing I want onto my palette?
Whenever I start SSIS work on a new machine, I remove the suggested favorites of source/destination assistants and add in what I use day-in and day-out.
I have an ssrs server that is not allowing me to create subscriptions for some reports. There are 20+ reports in a folder which all use the same data source: /Data Sources/MyDataSource. The credentials are stored in the data source. I can add subscriptions to most of the reports, but there are a few which throw the following error:
An Error Has Occurred:
Subscription can't be created or edited because
the credentials used to run the report are not stored, or if a linked
report, the link is no longer valid.
I have tried deleting the report and re-uploading them, deploying the whole bit from the project and adding another data source with the same stored credentials. However, I still get the same warning triangle on the subscription button. There are a batch of new reports I have added, some have this issue and others do not. Restarting the SSRS service did not help.
Any other ideas for troubleshooting this?
Bonkers! Looks like the issue was a case sensitivity one. In the project, all of the reports referred to a shared data source. However, sometimes the reference to the shared data source was spelled "mySharedDataSource" instead of "MySharedDataSource"
I found a hint of this in the logs, which complained about the first version of the spelling which did not exist on the report server. Fixing that and deploying the report corrected the issue and now I can create subscriptions.
Might be a 2017 thing, I have these reports both on a 2016 and 2019 instance and they have not complained.
Do not seem to be able to find any place in the portal or Report Builder where I can actually edit the connect string & creds.
Report Manager shows the XML, but that really is it.
Disk files (from the looks of it) are no longer present in high versions (using SQL 2016/2017).
Is there a known location anywhere in GUI, or maybe direct edits in the SQL Server repository?
I can't even delete a shared source anymore, only view or test the connection.
If anybody could post a screenshot, it'll be highly appreciated.
EDIT: Just found out - when I create a new Data Source, it's editable; the imported data sources are not.
There are two ways of doing this. You can set the 'overwrite datasource' option in the project properties.
Or, you can got to the report portal , show hidden items in the view menu and there is a folder called "data sources". Open this and you will see all data sources, from there you can edit and save changes. All reports that use that datasource will be affected.
My error is below:
The report server cannot process the report or shared dataset.
The shared data source 'XXX' for the report server or SharePoint site is not valid.
Browse to the server or site and select a shared data source. (rsInvalidDataSourceReference)
Right. I've checked all 3 data sources and they connect fine. I've deleted the report and data sources and deployed them again but still the error. I've used Notepad++ to check for the reference XXX in any of the files and still nothing.
These options are both checked.
Always run this report with the most recent data
Do not cache temporary copies of this report
Under Snapshot Options > Allow report history to be created manually I get a warning of Credentials used to run this report are not stored. Could this be a reason?
My data sources are setup like:
I have read other similar posts but no luck.
Thanks
A restart of report server resolved this particular issue for some annoyingly odd reason
Go to your Datasets and check the Data Source being used if it's pointing to the correct data source
I've created a new SSRS project, and added a shared data source. When I run the project, I get the expected result succesfully.
However, when I try to deploy the report I get:
Error: Cannot deploy the report because the shared data source '/Data Sources/DataSource1' that the report references does not exist on the report server.
I'm guessing I am missing something very simple and critical because I am a complete beginner.
What am I doing wrong?
First, deploy the data source:
Then, deploy any necessary shared datasets:
Now, you'll be able to deploy or run your report.
If trying to deploy dataset but still getting this error...
I have discovered that if you change the name of the shared data source after you have already created a corresponding shared dataset, then the "DataSourceReference" property in the dataset does not change accordingly, is not be editable via the wizard, and it will throw this misleading error.
On the shared dataset, right-click and go to "Open With..." --> "XML (Text) Editor".
There you will see the raw configuration file. Make sure the <DataSourceReference> node has the proper value...
Scenario: You've decided to use a Shared Dataset on your report but you haven't used it. Make sure to select the proper datasets for this issue.
Answer with steps:
On the Report Data tab on your SSDT double click the Datasets(not the one with the folder sign). It'll open the Dataset Properties.
- when the Dataset properties is open make sure to select a Dataset that your report is suppose to use.
-press OK.
-Solved]1