Legacy SSRS reports after upgrading Azure DevOps Server 2020 to 2022 or 25H2
We are currently planning an upgrade from Azure DevOps Server 2020 to Azure DevOps Server 2022 or 25H2, and one of our biggest concerns is reporting. We understand that Microsoft’s recommended direction is to move to Power BI based on Analytics / OData. However, for on-prem environments with a large number of existing SSRS reports, rebuilding everything from scratch would require significant time and effort. Since Warehouse and Analysis Services are no longer available in newer versions, we would like to understand how other on-prem teams are handling legacy SSRS reporting during and after the upgrade. Have you rebuilt your reports in Power BI, moved to another reporting approach, or found a practical way to keep existing SSRS reports available during the transition? Any real-world experience, lessons learned, or recommended approaches would be greatly appreciated.
SSRS group adding
Hi everybody, I have an SQL server with SSRS. The reports work fine, but the reports are only available with the administrator profile. So I thought I would like to add another "profile" which is only for reading data. I created a new AD group, which is 'DOMAIN\users_test' but when I want to add the group on SSRS webpage I've got the following error message: "The user or group name 'DOMAIN\users_test' is not recognized." I have no idea what should I do. Can you give me some advice? Thank you. PN
SSRS log missing Report ID
In the SSRS ReportingServicesService log I see this when one of our reports failed for a data source issue. What I am wondering is why there is no Report ID. The log entry references a Report with ID but there is no ID. Report with ID=. Is this a bug with logging. I see this same behavior on multiple installations we have. processing!ReportServer_0-1!1e4!09/06/2024-08:31:02:: i INFO: DataPrefetch abort handler called for Report with ID=. Aborting data sources ...SharePoint 2019 and SSRS
Hi All, I know SSRS SharePoint integrated mode is not supported with SharePoint 2019 anymore. I have a situation where SharePoint was migrated from 2016 to 2019 using the database attach method. They had SSRS reports in a document library. While the reports are still working in 2019 and usable, we are no longer able to update any subscriptions. So we need to know 2 things: 1. is there a way to find the subscriptions so we can document them? 2. is there a way to easily migrate these RDL files out of SharePoint and into SSRS?Scheduled refresh issue with pbix report that connects to Access DB data source in PBIRS
This article discusses about the error “The login failed for data source ‘Unknown’ that occurs with scheduled refresh of pbix report that uses Access database as the data source and the solution to get the refresh to work. Error message: Data source error: The login failed for data source ‘Unknown’ Clicking on in the status, would give you details of the error: Error details: SessionID: f94a2716-08e8-47a3-87e8-668c92d4cae2 [0] -1055784932: DataFormat.Error: Unspecified error. ADB.accdb. ;Unspecified error. The exception was raised by the IDbCommand interface. Though the test connection to data source succeeds, the refresh fails with the above-mentioned error. How to get the refresh to work ? For any pbix report that connects to Access db data source, you need to make sure the following steps are done to get the report refresh to work: Step 1: Make a note of the account used in the “User name” section of “Credentials” (Credentials required to connect to Access DB data source) of the pbix report for which the refresh failed. From the screenshot below, “abc” account is used to connect to the data source for my report. Step 2: Note down the service account used by PBIRS from “Service Account” section of Report Server Configuration manager of PBIRS From the screenshot below, “Virtual Service account” is my PBIRS service account Step 3: The account used to connect to the data source in pbix report (“abc” account obtained from step 1) needs to be provided permissions mentioned in the next step on the folder security of the “Temp” folder associated with the PBIRS service account (“Virtual Service account” obtained from step 2). If you have a built-in-account configured as the service account for PBIRS (such as Virtual Service, Network Service, Local System), you should look for Temp folder in the following location on PBIRS Server: C:\Windows\ServiceProfiles\PowerBIReportServer\AppData\Local\Temp If you have a domain account configured as the service account for PBIRS, you should look for Temp folder in the following location on PBIRS Server: C:\Windows\Users\<domain account> \AppData\Local\Temp Step 4: Provide the following permissions to the data source credential account “abc” in the folder security of PBIRS service account’s (Virtual service account) temp folder as shown below: Read & Execute List folder contents Read Write After implementing the steps mentioned above, you should see the refresh working successfully for the pbix report. Why is providing permission to PBIRS Service account’s Temp folder for the data source account, required? When performing scheduled refresh for reports that use Access DB as the data source, the Mash up process performs impersonation using the account provided in the data source credentials section and hence checks the PBIRS Service account’s folder security to validate if the data source credential account used in the report has the necessary privileges. This validation decides the success/failure of the report refresh. Following is a screenshot from Process Monitor (Process Monitor - Windows Sysinternals | Microsoft Docs) trace that explains the behaviour: Hope this article helps you in fixing your report refresh issue! Author: Uma S M – Technical Advisor, SQL Server BI team, Microsoft Reviewer: Kane Conway – Escalation Engineer, SQL Server BI team, Microsoft
Publishing Reports to Sharepoint Site
Hi all, I'm looking for some advice in regards to the best approach to publishing reports to our Sharepoint online sites. Currently we use an old version of SSRS we want to replace with an alternative or update to a newer version, ideally something that can integrate with our Sharepoint online instance. Reading the documentation of MS Docs, it sounds like we will need a new version of SSRS (https://docs.microsoft.com/en-us/sql/reporting-services/report-server-sharepoint/reporting-services-report-server-sharepoint-mode?view=sql-server-2016), does anyone have any advice as to what version, or the best approach to doing this? Thanks Steve
SSRS et SharePoint Thumbnail image
Bonjour à tous Je rencontre actuellement un problème lorsque je souhaite ajouter une image miniature SharePoint dans un rapport SSRS. L'image miniature s'affiche correctement dans la Preview de Visual Studio (l'image d'origine s'affiche également correctement), mais lorsque que je génère le rapport via SharePoint, l'image miniature ne s'affiche pas (par contre si j'utilise l'image d'origine cela fonctionne). Image d'origine : /Images/Toto.jpg Image miniature : /Images/_t/Toto_jpg.jpg Une idée pour palier à ce problème ? --------------- Hi everyone I experiencing an issue with SSRS and SharePoint thumbnail image. The thumbnail image is display on Visual Studio Preview (the original image works too), but when I generate the repport with SharePoint thumbnail is not display (the original image displayed correctly). Original image : /Images/Toto.jpg Thumbnail image : /Images/_t/Toto_jpg.jpg Any idea?
