We as a company migrated from TFS 2013 to AzureDevops 2019 Server(On-Prem) and had to move old reports to the new report server. To do so we used a powershell script that uses /ReportServer/ReportService2005.asmx web service to create folders and reports. We couldn't do it manually because we have lots of collections and projects under them.
We have realized that the projects created after the migration had problems with the reports. Reports we use include default CMMI reports and some custom ones we have created. Most of these by default uses a SQL system function called [GetProjectNodeInfoFromReportFolder] that is located in warehouse database. This function returns the project guid and project name based on the current path of the report folder. This function uses the table DimTeamProject under the warehouse database and the column 'ReportPath' to determine which report is triggered against.
The problem we have is that the newly created projects after the migration all have NULL values in this ReportPath column, which fails our reports.
I couldn't seem to find where this ReportPath column is being filled upon so I couldn't find the core of the problem.
Based on research I've tried rebuilding the warehouse database in the administration console but it doesn't change anything. I've also checked in the administration console that the Default Report Folder path is set correctly for all the collections.
I've also tried uploading reports manually on the ssrs web portal.
As a side note, when I check the project in the visual studio Team Explorer I cant see the Reports tab. I can for the older projects. So I believe there should be something wrong in the project configuration.
I appreciate any feedback, thanks.
I've fixed the issue by following the steps below:
Connect to the server that devops is installed on.
Open Azure Devops Server Administration Console
Select Application Tier > Team Project Collections
Select the desired collection and click 'Edit Default Folder Collection'
Enter the folder path on the pop up and press OK. In my case it was already set but I was still having the problem mentioned in the question. (/TfsReports/DefaultCollection)
After 2-3 minutes setting the value in the last step, the warehouse db got updated and all the null values got replaced with the correct information.
**NOTE: This process needs to be repeated after a new project is created, otherwise the newly created project will still have a null value on reportpath
Related
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.
I'm trying to deploy a report from SpagoBIStudio 5.2.0 on a SpagoBI Server v5.1.0.
The report works perfectly in SpagoBIStudio (locally in my computer), and I successfully created the data source and the data sets using the web interface of SpagoBI Server.
Nevertheless when I click on the "Deploy" option of my ".rptdesign" file, I see the following dialog and the "Finish" button is always disabled.
For some reason I can select the correct Datasource but the Dataset dropdown list is empty and disabled. I guess this could be the problem.
The data source is a JDBC-Hive connection to Cosmos and the Datasets are defined as HQL queries in both Studio and Server.
Does anybody know why the datasets aren't listed in the deploy document wizard of SpagoBIStudio?
Thanks in advance.
you cannot finish the deploy not because of dataset but because you did not select any functionality on the tree on the right.
You don't have any functionality on server where to store your document, so you should go to server with and administrator user role,
then with the menu on the right, on the profile section, select the "functionalities management" menu and create a folder that is child of the root. Give it the permissions you need
After this operation try again the deploy and you should be able to select one funcitonality and so have finish button enabled
greetings
the dataset selection is disabled because a Birt Report is not linked to dataset that way.
There are two ways of using datasets in Birt:
- Birt embedded datasets, that can be of several types provided by Birt (SpagoBI has no role with that)
- SpagoBIServer type dataset; these are linked to SpagoBIDataset by providing label, but this association is written inside template, during template definition.
Hope this fix your problem, I would suggest you also to take a look at SpagoBI wiki page for further informations
greetings
Giulio
You don't have to select the dataset. Your finish button is not enabled because you haven't select the path from the functionalities tab. After selecting it will be enabled and your report will be deployed. After deployment you need to create Analytical drivers for the parameters through which your report will run.
NOTE: You must have a Active server configured under resources under SpagoBI project folder.
I have changed the SSRS report names in my reporting server projects. I have four reports and four linked reports in this projects. The linked reports are being called by an action setup on a column value where the parameters are being passed to the linked reports. After renaming all the report names I have made similar changes in the Action property in order direct the parameters to the changed report name. I have also saved the changes and re-built the project and have not got any errors. All the four main reports are working fine but the linked reports are trowing the following error while running the reports using preview options in MS Visual Studio 2010
An error occurred during local report processing. Object reference not set to an instance of an object.
I have deployed this to my local report server and on browser I getting the following error
The item '/Unit Reports/OLDREPORTNAME' cannot be found. (rsItemNotFound)
Here you can see that it is still trying to locate it to the old report name not the new changed one.
I have clean, built and deployed the project several times but still getting these errors
Please let me know if I need to make changes in any other files to avoid this error.
Thanks
Within the .rdl search for "OLDREPORTNAME" and replace with "NEWREPORTNAME"...
Take a backup first :-)
I have noticed that when I implement the Action property on the report field, it automatically set-up the same Action property of that text box where the field was defined.
I have found that the text box Action property was still pointing to the old report. I have changed text box Action property to point it to the new report and now my linked reports are working absolutely fine.
Thanks
Yogesh
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.