I'm fairly new to reporting services. I have set up a timed subscription to run a report and write it to a file though the report manager. I can see that the report ran but I see the following error.
"Failure writing file FIRM_LIST : The report server has encountered a configuration error."
Any ideas to get more specifics on the error?
Check in the application log on the reports server.
If there is nothing in there check in the reporting services LogFiles directory (something like C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles), these tend to give you quite a bit of info.
In my experience the main problem with scheduling reports to write to a folder are permissions issues. Make sure the user you are using to run the report has write/delete access into the folder you are trying to save to
Related
I'm running SQL Server 2016 and have local reporting services running.
I can run my SSRS reports up fine and display them to screen.
I can also export them to PDF or to CSV but if I try to export to Word, PP or EXCEL I get:
Reporting Services Error
An error occurred during rendering of the report. (rrRenderingError)
An error occurred during rendering of the report.
The type initializer for 'MS.Utility.EventTrace' threw an exception.
Requested registry access is not allowed.
the same report works fine on other peoples machines in the office so I know it's not to do with the report itself.
I've tried
Has anyone else had this issue or know how I can shift it?
I just spent hours troubleshooting this in a fresh install of SSRS 2019 using an updated database from a prior version.
I'm using an execution account with low permissions and did not want to make it a full Local Admin permanently but I tried adding it, unsuccessfully.
I removed the account from unattended execution in Report Services Configuration Manager and suddenly was able to export to XLSX. I was not sure what the fallout would be for existing reports, so I was not satisfied with this solution either.
Elsewhere I saw a recommendation to use Process Monitor (procmon) to watch for registry key access denials, you can download it here procmon.
It was difficult to search all of the output but you can filter by registry key access, then look for the RS executables or the result ACCESS DENIED.
In my case, it was HKU\%service account sid%\Software\Microsoft\Avalon.Graphics, and granting the execution account (not the account that runs the service) Read access to this key resolved the issue.
I got the same issue. Check in the URL (once you click on excel) whether the format is EXCELOPENXML. If yes change it to EXCEL.
Then it will download and work correctly.
You can enable it to 'EXCEL' by default by changing the 'rsserverconfig' file under reporting services. It will download in 'xls' format not 'xlsx'
NOTE: This solution is a common workaround when rendering extensions fail to work due to your deployment configuration or environment.
RSServerConfig
C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\rsreportserver.config
Look for the Render section, enable or disable the export formats that you want your users to have access to. see Rendering Extensions Overview on SQLDocs for more information on individual extensions.
<Render>
<Extension Name="WORDOPENXML" Type="Microsoft.ReportingServices.Rendering.WordRenderer.WordOpenXmlRenderer.WordOpenXmlDocumentRenderer,Microsoft.ReportingServices.WordRendering"/>
<Extension Name="WORD" Type="Microsoft.ReportingServices.Rendering.WordRenderer.WordDocumentRenderer,Microsoft.ReportingServices.WordRendering" Visible="false"/>
<Extension Name="EXCELOPENXML" Type="Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.ExcelOpenXmlRenderer,Microsoft.ReportingServices.ExcelRendering" Visible="false"/>
<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering" Visible="true"/>
…
<Render>
I had the same issue in SSRS2016 on a clean install of Windows Server 2016 & SQL 2016 with SSRS with all SP's & CU's and windows updated applied.
To confirm my fix, the execution account was not a member of the local administrators group on the SSRS server, once added and stop/start of SSRS, I am now able to export to Excel & Word, not the most secure way of getting it working but better than enabling the depreciated Excel 2003.
I had the same issue in SSRS 2019, and the fix was quite easy.
In Report Server Configuration Manager > Service Account, I had it set to "Use built-in account" = "Virtual Service Account".
I changed to "User another account", and selected a local users who is part of the Administrators group.
NOTE: This is NOT the Execution Account. This is for the Service Account.
You could be getting this error in Excel because the maximum number of rows that can be put in an excel sheet is 65536. If your data has more rows than that it will throw that error.
I got this issue on one of my machines when I installed MSSQL Server 2016 with SSIS, SSAS and SSRS.
SSIS and SSAS is working fine but SSRS does not.
After the installation, I opened the Reporting Services Configuration Manager and leave everything to default. This usually the end of it, but for some reason when opening the Portal, I got this:
When I check the log, the error is
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
What is Invalid PBI Configuration? And how do I identify the problem?
Thank you in advance.
Took a while to sort this out, but it's a simple fix.
Open SQL Server Reporting Services Configuration Manager
Click on Web Service URL menu and make sure that the URL's match the ones located in Web Portal URL menu.
If they're different, open the rsreportserver.config file (C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer) and remove any entries not listed in Web Service URL.
Open your web portal ie. http://localhost/Reports and see if it's resolved. If so, all done.
If not, click the Encryption Keys menu, in the "Delete Encrypted Content" section, click "Delete".
Open your web portal again and see if it's resolved.
Locate and update your datasource credentials.
I have report solution file with one project and one report.I have designed rdl report using BI in SSDT tools. After creating report successfully build is success and preview is ok. No problem did not arise when i did create report.
Now, I want to deploy this report to my remote reporting server. I gave a url like this www.plumeria.arvixe.com/Reports into Target server url. when i press deploy then need username and password, i gave that. after certain time it appears a errors like this.
Many times i have tried but not get a proper solution step by step deploy rdl report to remote server.
Is there any solution? Thanks.
"like this www.plumeria.arvixe.com/Reports into Target server url" is not correct. What you are referring to is the Report Manager.
You have to correctly specify:
Target Dataset folder
Target Data Source Folder
Target Report Folder -->From your project
Target Server URL-->Get it from Reporting Services Configuration Manager
Target Server version.
You may need elevvated permissions in SSDT.
My target url used in my book is as follows:
http://HODENTEKWIN7/Report_Server_Kailua
The instance name of SQL Server is Kailua and it is native mode.
This is a comprehensive book covering SQL Server 2012 both native mode and SharePoint
I'm working on integrating a report into a browser, and I get this error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'dsFederatedSample_SurveyLevel_STG'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Does this have to do with SQL vs Windows authentication?
First thing I would try is to get a bit more information on the error - that's a pretty generic message.
You could enable remote errors as per the error message and replicate the error for more information.
Or check the Report Server error logs to see what error was logged.
%programfiles%\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles\
The next step would be to connect as the Data Source user to the database, run any code/stored procedures that the report is using with the same parameters you're using when running the report, and see if any errors occur. Make sure the account you are using has permission and that you have entered the name and password correctly in the Data Source.
In SQL Server 2008 in addition to the above two options you have a third option to make this setting through SQL Server Management Studio.
1.Start Management Studio and connect to Report Server Instance (make sure you select 'Reporting Services' server type).
2.Right click on the ReportServer and Select Properties
3.Click Advanced
4.In EnableRemoteErrors, select True.
5.Click OK.
I had the same issue "Cannot create a connection to data source...Login failed for user.." on Windows 8.1, SQL Server 2014 Developer Edition and Visual Studio 2013 Pro. All solutions offered above by other Stackoverflow Community members did not work for me.
So, I did the next steps (running all Windows applications as Administrator):
VS2013 SSRS: I converted my Data Source to Shared Data Source (.rds) with Windows Authentication (Integrated Security) on the Right Pane "Solution Explorer".
Original (non-shared) Data Source (on the Left Pane "Report Data") got "Don't Use Credentials".
On the Project Properties, I set for "Deployment" "Overwrite DataSources" to "True" and redeployed the Project.
After that, I could run my report without further requirements to enter Credentials. All Shared DataSources were deployed in a separate Directory "DataSources".
In my case, this was due to using Integrated Windows Authentication in my data sources while developing reports locally, however once they made it to the report manager, the authentication was broke because the site wasn't properly passing along my credentials.
The simple fix is to hardcode a username/password into your datasource.
The harder fix is to properly impersonate/delegate your windows credentials through the report manager, to the underlying datasource.
The issue is because your data source is not setup properly, to do that please verify your data source connection, in order to do that first navigate to Report Service Configuration Manager through
clicking on the start -> Start All -> Microsoft SQL Server ->Configuration Tool -> “Report Service Configuration Manager”
The open Report Manager URL and then navigate to the Data Source folder, see in the picture below
Then Create a Data Source or configure the one that is already there by right click on your database source and select "Manage" as is shown below
Now on the properties tab, on your left menu, fill out the data source with your connection string and username and password, after that click on test connection, and if the connection was successful, then click "Apply"
Navigate to the folder that contains your report in this case "SurveyLevelReport"
And Finally set your Report to the Data Source that you set up previously, and click Apply
if you use null values in your stored procedure, you will need to set the parameters to accept null values. That worked for me.
In my case I had in one report many different datasets to DB and Analysis Services Cube. Looks like that datasets blocked each other and generated such error.
For me helped option "Use single transaction when processing the queries" in the CUBE datasource properties
I had a similar problem, and being the newbie that I am it took me a while to figure out but I learned the user must have a login in SSMS. I created the logins with the following parameters:
Under Server Roles - check sysadmin
Under User Mapping - I selected the database and the report server. For each I checked datareader and datawriter
Under Securables - I checked anything that would allow the user to connect to the database and view anything
I also found that one of the existing logins had denydatareader and denydatawriter checked. Once I removed these it worked.
I'm not saying this is the best way to do it, just what worked for me. Hope this helps
More information will be useful.
When I was faced with the same error message all I had to do was to correctly configure the credentials page of the DataSource(I am using Report Builder 3). if you chose the default, the report would work fine in Report Builder but would fail on the Report Server.
You may review more details of this fix here:
https://hodentekmsss.blogspot.com/2017/05/fix-for-rserroropeningconnection-in.html
I had the exact same issue.
The cause could be different but in my case, after trying several different things like changing the connection string on the Data Source setup, I found that this was the infamous 'double hop' issue (more info here).
To solve the problem, the following two options are available (as per one of the responses from the hyperlink):
Change the Report Server service to run under a domain user account, and register a SPN for the account.
Map Built-in accounts HTTP SPN to a Host SPN.
Using option 1, you need to select 'Windows' credentials instead of database credentials to overcome the double hop that happens while authentication.
I'm trying to use team foundation server power tools to add project reports to an existing team foundation server 2010 install. Here's the command I'm running with the output...
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>
tfpt addprojectreports /c ollection:https://SERVERNAME:8080/tfs/Projects /teamproject:SANDBOX / processtemplate:"MSF for CMMI Process Improvement v5.0" /validate
The project collection does not have reporting configured. Therefore,
reports cannot be added to projects in the collection.
The error message seems to indicate that reporting services has not been set up for the whole project collection. If I log into the TFS server and run the TFS admin console, hit Reporting under the application tier, each area (warehouse, analysis services and report server) indicate that everything is configured and enabled.
Also, if I point a browser to the report server configured within the admin console I get a directory listing with two data sources listed (Tfs2010OlapReportDS, Tfs2010ReportDS) and a directory called TfsReports. In the TfsReports dir there is a Projects directory and further a directory within the projects directory which contains what I'm assuming are the default reports for a project. If I drill all the way down to an actual report Build -> Build Summary, it runs just fine.
So, it seems like reports are configured for one of the team projects, but I'm not sure how this was accomplished since I'm not able to do this for other projects. If I run the previous command and use the name of the project that already has reports for it, I get the same error message.
I don't think I have the collection URL incorrect because if I totally fudge this I get a TF31002 error indicating unable to connect to TFS.
Any thoughts? Thanks a lot.
In the TFS Administration console, go to the project collection and in the Reports Folder tab ensure that you have set the Default Folder Location.
If the tab isn't showing (because you haven't closed the admin console since you configured reporting), click the refresh button at the top of the window and it should appear.