We are working on migrating our SSRS from SQL Server 2008 to SQL Server 2014. After brining the reports over I have a set of reports that will execute just fine but when I try to perform a standard export to excel from the 2014 Server I get a message box saying: > We found a problem with some content in ACM Consolidated > Invoie_2014.xlsx. Do you want us to recover as much as we can? > If you trust the source of this workbook, click yes. However, I do not receive the same message when exporting to Excel from the 2008 server. I believe the problem is related to some Numeric fields that are coming back with a value of 0.0000000000000000000. Has something changed with the excel export function between these two versions?

Our data is loaded daily. My report can be run, using a parameter, for any number of sites (100 is the total number of sites) and I want it to cache a temporary copy of the report and expire it on a schedule - a schedule that is triggered at the end of our daily load. This is simple. Where it gets complicated is I have a cache refresh plan to pre-load the cache for all 100 sites. I need to make sure the cache expires before this plan runs - a plan that is tied to a schedule I want to trigger at the end of our load. If I trigger the jobs, in order, at the end of the load, they are effectively triggered together, so I would like to understand what happens on the system level when SSRS expires a cache so that I can ensure the refresh occurs after the expiration. Is there a value in one of the ReportServer tables that is changed or a row deleted? For what it's worth, this is what I am seeing in my testing (the cache is successfully pre-loaded), but I would like to understand the technical architecture to give myself a better comfort level before using this in production.

I have a separate reporting server and a separate database server. Now on the Reporting server site settings I could see there are some roles and users. Suppose a User BOB has ‘POWER USER’ role assigned and the user can create and deploy report. Now the confusion lies here as I want to remove some database logins does BOB needs to have database level permission (example execute permission and database reader ) on the database and also on the report server database or the permission assigned to the role on SSRS will be good enough. Does SSRS report user needs database level permission or the login that is used on the data source will only need database level permission.

We have a production environment running SQL Reporting Services 2014. The service is running as a group managed service account domain\SSRSProdSvc$ We are now trying to change our test environment to use managed service accounts for SSRS, however I can't change it. If I go into Reporting Services Configuration Manager and try and change the service account I get an error > Setting Windows Service Identity to Windows Account > > The Windows account information used to run the Windows service has failed to update. Previously designated settings are being used instead. If I go into Windows Services I can change the account to domain\SSRSTestSvc$ and the service starts, however in the Reporting Services Configuration Manager it still comes up with the previous domain account. I'm not sure how it was configured on Live, but when I look at the Reporting Services Configuration Manager it's service account is domain\SSRSProdSvc$ Any ideas how to fix test?

I’m a bit confused on how I move the reporting database (and the temp one) from prod to test. I know after moving DBs I need to export its encryption key, but I would like to not cause any report to be sent by mistake to prod clients. Is there a way to clean the subscription table for example, without breaking the reporting service?

I have a requirement for a third party vendor application which requires SSIS and SSRS. The vendor had suggested this 3 server model, and my management is going ahead with the same. Three VMs are being provisioned, one each for SQL Server, SSIS, and SSRS. I want to know in what ways I can configure SSIS and SSRS to work with the SQL Server. Also, what would be the best way to create SSIS packages? Because, if the packages have to be created on the dedicated instance, I still need to create a local instance of the database engine on the SSIS server. I need some guidance as to how I can configure SSIS and SSRS in conjunction with the SQL Server instance in the third VM. I am fairly new to these two areas. I am going through these two links: 1. Configuring SSIS 2. Configuring SSRS Please let me know if another URL would provide detailed step by step information. Also, would the three servers have to be in the same cluster? The system is spread across continents hence we expect a lot of users in the long term. The way it was planned was to have separate instances of SSIS and SSRS, and they point to a database in an Always On setup which stores the reporting information.

I am looking to find a solution for the SSRS 2014 server redirects to http url instead of https for all the subreports and other report parts like subscription , security , datasources etc .  What I have done so far 1. On the rsreportserver config file changed the value for from 0 to 3 , SSRS does not work when this value is set to anything other than 0 . 2. Added the url to rsreportserver config file to contain the https:// version of my report server 3. Added a registry entry to have DisableLoopbackCheck with value 1 and restarted the server (Tried this solution already https://dba.stackexchange.com/questions/163016/ssrs-bug-using-ssl-https) 4. Our SSRS does not have an IIS , its managed in the Reporting services configuration manager where we have bound the ssl certificates with https: url port 443 I have also tried removing http: with port 80 on the Web Service manage and Report server url .  This problem is taking a lot of time and is affecting a lot of production user when they get redirected to sub reports they will have to manually key in https: on the address every time when the report is run .  Let me know if you require any detail and help me fix the problem .  Thanks in Advance

I am new to SSRS and I have been tasked to copy the SSRS reports(from PROD) to another Server(QA). I found many documentations that show how to migrate the reports by Restoring ReportServer, ReportServerTempDB and encryption key. I just want to confirm. After doing above, my main environment(prod) will remain intact and operational?Please confirm. I'm creating a QA environment that I am copying from PROD and I cannot afford for anything to happen to PROD.

I need assistance getting labels to print from SSRS 2014 to a Zebra GK420D direct thermal label printer. The labels show up when running the report but when I print them to the label printer, all that comes out is a blank page. If I export to a PDF and then print, it works fine, but this isn't a viable option for our end users. I've set the printer to the correct label size as well as changing the page size in the report to match and I've changed the printer settings to "Always use driver settings" and to print directly to the printer (bypassing the spooler) which were the two recommendations I found thanks to googling. Any assistance is greatly appreciated.

Whenever we apply a patch (recently with CU5), end users need are prompted for administrator credentials to print. In googling, I see many different suggestions, but nothing seems to work. I have tried adding the SSRS server to the trusted sites list. Also, I have checked the active X permissions and they seem to be set correctly under Security Settings. Does anyone know the necessary configuration to avoid this prompt with future SQL Server updates on our SSRS server? I've followed the Microsoft [directions for RSClientPrint](https://learn.microsoft.com/en-us/sql/reporting-services/report-server/enable-and-disable-client-side-printing-for-reporting-services?view=sql-server-ver15&redirectedfrom=MSDN&viewFallbackFrom=sql-server-2014) - in looking at the users Internet Security settings, they appear to be in line with those recommendations.

I have a table that I'm trying to report out on in SSRS-2014. A cut down version of the table:- ~~~ TABLE_NAME FEE_NAME FEE_VALUE PDE 1st year 100.00 PDE 2nd year 120.00 PDE 3rd year 130.00 PDE 4th year 140.00 PDE 5th Year 150.00 PGB 1st year 500.00 PGB 2nd year 520.00 PGB 3rd year 530.00 PGB 4th year 440.00 PGB 5th Year 850.00 PUS 1st year 100.00 PUS 2nd year 120.00 PUS 3rd year 130.00 PUS 4th year 140.00 PUS 5th Year 150.00 PCA 1st year 100.00 PCA 2nd year 120.00 PCA 3rd year 130.00 PCA 4th year 140.00 PCA 5th Year 150.00 PJP 8th year 600.00 PJP 10th year 820.00 PJP 11th year 40.00 PJP 12h year 140.00 PJP 14th Year 750.00 ~~~ How can I display the data so that it's :- ~~~ Table Name 1st year 2nd year 3rd year 4th year 5th year 6th year 7th year 8th year 9th year 10th year 11th year 12 year 13th year 14th year PDE 100.00 120.00 130.00 140.00 150.00 PGB 500.00 520.00 530.00 440.00 850.00 PJP 600.00 820.00 40.00 140.00 750.00 ~~~ And so on. The year columns will range from 1 to 20 and there wont always be a value for every year. I've tried using :- ~~~ =Lookup(ReportItems!Textbox3.Value, Fields!FEE_NAME.Value, Fields!FEE_DIS1.Value, "Fees") ~~~ to use the year in the header row of the SSRS table to lookup the FEE_NAME from the dataset, but I get a row for every entry in the dataset but each row shows the same (correct) value. I've tried using CASE in the SQL :- ~~~ CASE WHEN FEES.FEE_NAME = '3rd year' THEN FEE_VALUE END AS [3rd year], ~~~ Again, I get the value I want and then empty rows for the rest of the TABLE_NAME rows. I also looked at Pivot (SQL) and a Matrix (SSRS) table but I just want to return the corresponding fee value and display it in the relevant year column whereas from what I've read so far Pivot and SSRS need an aggregate. Hopefully this makes sense. Cheers.

Just wondering if anyone has come across this scenario and can provide some advice. We have a vendor application that only runs on SQL Server Reporting Services 2014. However, all of our other applications support SQL Server 2017. Can I setup SSRS 2014 on a separate server, but have the database residing on the SQL Server 2017 server? Cheers Phil

Our SSRS instance has several Shared Data Sources that hit Oracle databases. Whenever we do patching or the server restarts, these Data Sources seem to break. Any reports hitting them come up with the below error message:

Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.

This has been happening for years, and the weird part is, to fix it, the DBAs have been removing the password from the Data Source, and recopying it, and then it works fine. So it's not like something isn't installed, like the error message claims. It is almost like the server is not storing the passwords correctly. We do have several Data Sources that use SQL Server accounts, but they don't have any trouble. Has anyone dealt with something like this before?

It is straightforward to change the TCP port of SSRS using the GUI (Reporting Services Configuration Manager) but I am trying to fully script the installation and config of our SSRS servers. Is it possible to change the TCP port of the SSRS web service via command line? I have looked through this SSRS documentation from Microsoft , but don't see the option to change the TCP port. **UPDATE:** There is still no facility that I can find - as of SQL Server 2014 - to programmatically change the port of SSRS's web service. As per Microsoft , "You must write custom code that makes calls into the Report Server WMI provider. There are no command line utilities or script templates for configuring the URLs." And even then, the port cannot be changed. I tried editing the rsreportserver.config file and changing the port in there, but that resulted in "This page can’t be displayed" errors. Bah!

I'm trying to print labels on a Zebra printer in SSRS 2014 and the orientation is coming out wrong. In report builder, I set the page size to 4.15 x 1.15 with correct margins. Also, in report builder, if I print it will typically come out the correct orientation (landscape), but occasionally I have to go into Page Setup, change the Orientation from Portrait to Landscape & back again to get it to print correctly (Not sure why it requires a Portrait orientation to print in Landscape in Report Builder. However, when I try to print from SSRS directly, it comes out in portrait and prints across several labels. I've done some research and saw recommendations to change the printer to print directly and bypass the print spooler, which I've attempted to no avail. Any assistance is greatly appreciated.

I am using the below query for accessing the Users who are using the Application Reports. SSRS 2014 gives the Service Account(IIS Account used for Application) as User Name instead of Actual User name. USE ReportServer; GO SELECT el2.username, el2.InstanceName, el2.ReportPath, el2.TimeStart, el2.TimeEnd, el2.[Status], isnull(el2.Parameters, 'N/A') as Parameters FROM ExecutionLog2 el2 GO Can you please let me know why I am not able to see exact username who accessed the Report instead why I am seeing the Service Account in the place of User Name exactly. There is only one DISTINCT RequestType which is Interactive. Where as when we read IIS logs using Log parser it does contain the User Name individually Thanks

We recently upgraded our test database servers from SQL 2014 SP2 CU3 to 2014 SP2 CU10. Most of the servers are fine, but on 2 of them we are getting the following error when connecting to the reporting services website: sorry, it didn't scale well, the message reads : > "The version of the report server database is either in a format that > is not valid, or it cannot be read. The found version is '163'. The > expected version is '164'. (rsInvalidReportServerDatabase)" Having a look at the log files I can see this error: > library!WindowsService_0!4cc!02/26/2018-12:47:43:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "Latin1_General_CI_AS_KS_WS" in the equal to operation. Cannot resolve the collation conflict between "Latin1_General_CI_AS_KS_WS" and "Latin1_General_CI_AS" in the equal to operation. After that we get a number of entries about the database version being incorrect: > library!DefaultDomain!1bf0!02/26/2018-12:49:42:: e ERROR: Throwing Microsoft.ReportingServices.Library.InvalidReportServerDatabaseException: , Microsoft.ReportingServices.Library.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '164'.; I'm assuming it's something to do with Collation, but everything I can see is set to Latin1_General_CI_AS. I'm not sure where it's getting the other collation from or how to fix it. Any ideas on who to get the database to upgrade to the new version?

I'm moving SSRS reports from a 2008R2 server to a 2014 server. I've moved all the RDLs with a 3rd party tool only to find none of the permissions exist on the target. I'm attempting to copy the permissions over with Powershell but the script errors when attempting to set the policy with .SetPolicies. The object members appear to be incompatible between 2008 R2 and 2014. Is it possible to move the perms from 2008R2 to 2014 via Powershell? $ReportServerUriSource = 'http://my2008Source/ReportServer/ReportService2010.asmx?wsdl ' $ReportServerUriTarget = 'http://my2014target/ReportServer/ReportService2010.asmx?wsdl ' $InheritParent = $true $rsProxy = New-WebServiceProxy -Uri $ReportServerUriSource - UseDefaultCredential $rsProxyTarget = New-WebServiceProxy -Uri $ReportServerUriTarget - UseDefaultCredential $SourceItems = $rsProxy.ListChildren("/MyReports", $true) | ` SELECT TypeName, Path, ID, Name $targetFolder = $rsProxyTarget.GetPolicies($SourceItem.Path, [ref]$InheritParent) foreach($SourceItem in $SourceItems) { $Policies = $rsProxy.GetPolicies($SourceItem.Path, [ref]$InheritParent) if($InheritParent -eq $false) { $Policy = $rsProxy.GetPolicies($SourceItem.Path, [ref]$InheritParent) $rsProxyTargetPath = $rsProxyTarget.GetPolicies($SourceItem.Path, [ref]$InheritParent) if($rsProxyTargetPath) { $rsProxyTarget.SetPolicies($SourceItem.Path, $Policy) } } } Error: > Cannot convert argument "Policies", with value: "Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1er_ReportService2010_asmx_wsdl.Policy[]", > for "SetPolicies" to type "Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy3er_ReportService2010_asmx_wsdl.Policy[]": "Cannot convert the > "Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1er_ReportService2010_asmx_wsdl.Policy" value of type > "Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1er_ReportService2010_asmx_wsdl.Policy" to type > "Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy3er_ReportService2010_asmx_wsdl.Policy"." > At line:21 char:15 > + $rsProxyTarget.SetPolicies($SourceItem.Path, $Policy) > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + CategoryInfo : NotSpecified: (:) [], MethodException > + FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument

We have a SQL server 2014 and SSRS 2014 instance set up on two different 2012 R2 servers. This has been our setup for years, and everything has worked fine. We did an in place upgrade of the SQL server from 2014 to 2016 with no issues, but when I tried an in place upgrade of SSRS 2014 to 2016, it completed the setup with errors. The error we initially recieved on setup is “Index was out of Range. Must be non-negative and less than the size of the collection. Parameter name: index”. Now we are unable to start the SSRS instance. These errors appear to be an authentication issue. When I try starting the instance, I receive the following errors: > “Starting report server “ReportServer$NVSLDS2T080SSRS on NVSLDS-2T080. > The Task Failed. > > “System.InvalidOperationException: Cannot start service > ReportServer$NVSLDS2T080SSRS on computer 'NVSLDS-2T080'. ---> > System.ComponentModel.Win32Exception: Access is denied --- End of > inner exception stack trace --- at > System.ServiceProcess.ServiceController.Start(String[] args) at > System.ServiceProcess.ServiceController.Start() at > ReportServicesConfigUI.Panels.ConfigurationPanelWithErrors.StartOrStopServiceTask(Boolean > start, String serviceName)” The Event Viewer is also saying: - Event ID 7000 “The SQL Server Reporting Services (NVSLDS2T080SSRS) service failed to start due to the following error: Access is denied.” - Event ID 64, “Certificate for local system with Thumbprint 89 91 b4 e0 3a 96 cf ea a2 75 8f aa b6 41 e4 e5 c2 d3 69 aa is about to expire or already expired.” - Event ID 16 “The access history in hive \??\C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT was cleared updating 0 keys and creating 0 modified pages.” I haven't found many clear articles on the issue. The closest I have gotten is an article about the KB 2677070 update, which I don't believe to be the issue. https://support.microsoft.com/en-us/help/2745448/you-cannot-start-sql-server-reporting-services-after-you-apply-the-upd An issue with ASP.net: https://support.microsoft.com/en-us/help/332215/fix-system-argumentoutofrangeexception-index-was-out-of-range-error-oc . Please advise.

Is there any incompatibility with reports developed in SQL Server SSRS 2014, and then exported to .RDL files that will be imported into SQL Server 2008?