sqlskills-logo-2015-white.png

Backup your Reporting Services Encryption Key

  • Jonathan Kehayias
  • March 21, 2019

If you run SQL Server Reporting Services, part of your DR plan needs to include a backup of the encryption key for SSRS. This sadly is an all to often overlooked part of the solution, even though it is incredibly easy to do. If you don’t have a backup of the encryption key during a restore, the report server will never be able to decrypt the encrypted content (connection strings, passwords, etc) stored in the database, and your only recourse would be to delete the encrypted content and recreate it manually or through a redeployment of datasources.

https://docs.microsoft.com/en-us/sql/reporting-services/install-windows/ssrs-encryption-keys-back-up-and-restore-encryption-keys?view=sql-server-2017

For those that are into Powershell, Microsoft has provided a simple function Backup-RsEncryptionKey that can be utilized for this as well:

https://www.powershellgallery.com/packages/ReportingServicesTools/0.0.0.2/Content/Functions%5CAdmin%5CBackup-RsEncryptionKey.ps1

Make sure that you’ve covered all your bases with backups of other keys and certificates as well. Even if you think you’ve got your bases covered, now is a great time to verify, especially for anyone using Transparent Data Encryption for a database. One of the worst emails we’ve ever gotten from someone in the community was that they had backups of their database but not the certificate used for encryption and they couldn’t restore the database or access the data, and there is absolutely nothing anybody can do to help you if this happens.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

Other articles

Do you need trace flag 460.

For most people that are reading this post, I’d venture to guess that you have no idea what Trace Flag 460 is or when you

Event exceeds the number of allowable bound actions

Did you know that there is a limit to the number of actions you can add to a single event in Extended Events? While I

SQL Server 2022: Measuring Extended Events Performance Impacts

Have you ever wondered if Extended Events is affecting the performance of your workload? I have written a lot about Extended Events and have been

What’s New in SQL Server 2022: GENERATE_SERIES()

I’ve been doing a lot of work with SQL Server 2022 lately and one of my absolute favorite new features that I just came across

Logging Database Scoped Configuration Changes

The introduction of DATABASE SCOPED CONFIGURATIONS in SQL Server 2016 enabled different configuration settings at the individual database level. However, there is no logging of

SqlClient Configurable Retry Logic – ICYMI

While I was doing some research for a client on how to accomplish a specific task, I happened across a BOL topic that caught my

Imagine feeling confident enough to handle whatever your database throws at you.

With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.

SSRS unable to backup encryption key

jasona.work

Points: 50060

More actions

February 19, 2015 at 1:13 pm

I'm beginning the process of migrating a customer to a new SSRS server, and to save everybody work, I want to migrate their Reporting Services database.

I've done this before a year or so back, so I know the process is fairly straight-forward.

1. Backup the encryption key on the existing SSRS instance

2. Backup the Reporting Services DB (in this case I don't need the Reporting Services TempDB)

3. Configure SSRS on the new server

4. Restore the encryption key to the new SSRS instance

5. Restore the DB

6. Point the SSRS instance to the restored DB

The problem is, step 1. On both the existing QA and production SSRS servers, when I try to backup the encryption key, after entering the path, password, and hitting OK, I get "windows has encountered a critical problem and will restart." I'm trying to save the key file to my desktop on the server, so it shouldn't be an NTFS permissions issue.

I've done some Google searching, and not found this. We did just recently go through a security audit, so some GPO settings may have changed (which I would have no knowledge of or insight to)

My next step at the moment is going to be to try starting the SSRS Config Manager using the "Run As Administrator" option, although I'm not too confident in that.

Has anyone run into something like this, and if so, how did you resolve it?

I've already warned the customer that we / they may need to re-upload all their reports and schedules on the new server, as well.

Update 1: Before you ask, no, I don't have a copy of, or easy access to a copy of, the original encryption key backup. I could likely get one from our backup admin, but they'd need to go to the off-site tapes, plus I'd have to track down when the migration happened (one is easy, the other more work)

Update 2: A peice of good news in the MS article on migrating Reporting Services. They suggest and link to several methods to just migrate content from one instance to another, so that might make things a little less painful if I can't resolve this...

https://msdn.microsoft.com/en-us/library/ms143724(v=sql.110) .aspx

Points: 323503

February 19, 2015 at 1:24 pm

jason i only did this once, and it was a two or more years ago, for a 2005 instance.

there's away to backup the key via powershell, and avoid the gui which seems to be crashing;

i cannot find the exact article i found, but this was the first link i found that had something similar:

http://www.pertell.com/sqlservings/archive/2011/12/backing-up-ssrs-encryption-key-with-powershell/

and of course googling for "powershell backup ssrs encryption key" gets a lot of other examples.

Lowell -- help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

February 19, 2015 at 5:58 pm

Lowell, thanks for the pointer. I hadn't even thought about seeing if there was a way to get the key out with something like Powershell, I'll be giving that a try tomorrow!

February 20, 2015 at 7:00 am

So I tried tweaking the method that Lowell provided for a one-off, without the SQL DB / Table holding the password for the file. Looks like either I'm typo'ing something, or MS changed something, or they've got the systems so locked down it's preventing the method from working...

Regardless, thanks Lowell for the pointer to a possible solution!

(And I do think it's the third option above, I'm seeing audit failures in the OS Security Event log when I try to run the backupencryptionkey part, despite me being a local Admin on the box, and having done "Run As Administrator" for the Powershell session)

February 20, 2015 at 7:17 am

Jason running this specific example on my local machine, as well as on another server, this worked correctly for me:

http://webcache.googleusercontent.com/search?q=cache:GQgjJjIxFmsJ:codetempest.blogspot.com/2009/08/powershell-reporting-services-rskey.html+&cd=8&hl=en&ct=clnk&gl=us

it has to run locally, since it's effectively calling a command line to RSKeyMgmt.exe:

#####################################################################

# SCRIPT NAME: Backup-RSKeys.ps1

# PURPOSE: Generate the .bat file to backup the Reporting

# Services RSKeys and delete the old ones after 30 days.

# the .bat file creates a RSKey backup file with a filename

# like RSKey_MYSERVERNAME_200908052329.snk.

# Parameters:

# $RSKeysFolder -> directory to write to and delete from - will NOT be recursive!

# $DaysBackToDelete -> Files older then N days to be deleted

# $RSKeyFilePwd -> Actual RSKey encryption file password

# Example Usage

# to delete from 15 days back

# ./Backup-RSKeys.ps1 "\\SERVERNAME\ShareFolder\SQLBackups\RSKeys" "-15" "FlibbertyGibbet77"

# to run from DOS command or from Task Scheduler:

# powershell -command "& {./Backup-RSKeys.ps1 'E:\TargetFolder' '-30' 'FlibbertyGibbet77'}"

# Change History:

# 08/04/2009 10:33 AM - gmilner: Created.

######################################################################

param( $RSKeysFolder = "C:\Data" , $DaysBackToDelete = -30, $RSKeyFilePwd)

# populate the variables.

# the date before which you delete old files.

$DeleteFromDate =((Get-Date).AddDays($DaysBackToDelete))

# Get the name of our machine

$ServerName = get-content env:computername

$RSKeyFilePwd ="MyS3cr#tPa55w0rd!"

# Formats now date and time to go in a filename like 200909142304

$DateString = (get-date (get-date) -uformat %Y%m%d%H%M)

# build the target path and filename

$TargetPathAndFileName = $RSKeysFolder + "\RSKey_" + $ServerName + "_" + $DateString + ".snk"

# we need a file to feed it the "Y" when the RSKeyMgmt.exe asks for it

"Y">y.txt

#note the redirection operator to bring in the Y from y.txt ("an old DOS trick")

$DOSCommandString = "RSKeyMgmt.exe -e -f """ + $TargetPathAndFileName + """ -p"+ $RSKeyFilePwd + " < y.txt"

# write the command out to a batch file. NOTE: If you done use -encoding the batch will error

# on a unicode related error.

$DOSCommandString | out-file -file "BackupRSKeys.bat" -encoding ASCII

# Now run the batch file

.\BackupRSKeys.bat

#---------------------------------------------

# Delete files older than x days if extension = .snk

Get-ChildItem "$RSKeysFolder" -include *.snk |

where { $_.LastWriteTime -le $DeleteFromDate } |

remove-item

February 20, 2015 at 10:47 am

Looked like a great solution, except it generates the same OS error as trying to backup the key in the SSRS Config manager.

I really do think one of the things that got locked down / changed for the recent security audit is the culprit...

Once again, Lowell, thanks.

Now for some good news (for me at least.) Turns out on the QA server (where I've been trying these tips) there's a backup of the key (for QA, but to simplify the Devs life I'm hoping / betting it's the same between QA and Prod) sitting on the filesystem! So I've got that out to the new server, and am working on getting things configured.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Notes on SQL

Random articles from a puzzled dba.

reporting services backup encryption key

SSRS – Backup Encryption Key Error

July 23, 2021

When attempting to back up the key, within Reporting Services Configuration Manager, it fails and provides a less than helpful error message.

As part of an upgrade (from SQL Server 2012 to SQL Server 2017) I discovered that the installation of SQL Server 2017 will remove SQL Server Reporting Services (SSRS). SSRS is now a separate installation, much like SQL Server Management Studio (SSMS).

The SQL 2017 upgrade process advises you to backup your current SSRS encryption key, which can then be used when you install the new SSRS software and will recover the existing SSRS reports and setting.

However, in my case this produced an error message. The solution was quite simple, but with so many things in the world of IT – it is only simple once you find out what it is.

Reporting Services Configuration Manager

First of all – load the ‘Reporting Service Configuration Manager’ and select the ‘Encryption Keys’ option from the menu:

Figure 1: SSRS Configuration Manager

reporting services backup encryption key

Pressing the ‘Backup’ button will produce a dialog screen that requires a filename and location, as well as a password to use, in order to secure this file. This password is not the password that the certificate might have been created with; it is a new password that is just used to secure this backup file.

Figure 2: Specifying the filename and associated password

reporting services backup encryption key

Pressing the ‘OK’ button didn’t produce an immediate, helpful error message, but at the bottom of the screen a red cross and the message ‘Creating Encryption Key Backup’ was shown.

Clicking on the link ‘Tell me more about the problem and how to resolve it’, certainly tells you more about the issue, but gives no details on how to resolve it

Figure 3: Error Message

reporting services backup encryption key

The full error text is:

“Microsoft.ReportingServices.WmiProvider.WMIProviderException: Exception from HRESULT: 0x800708C5 at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.ThrowOnError(ManagementBaseObject mo) at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, SecureString password) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, SecureString password)”.

Although not the most helpful message, it does make several references to ‘password’ – so there is something about the password that it doesn’t like.

The exception code of ‘0x800708C5’ is a fairly general code that doesn’t really help.

Further Digging

Several articles pointed to an issue with the supplied password. Effectively the password does not match the password requirements of the Windows environment. However, I tried this method on out live servers, with the same password, and it worked perfectly well. So I assumed that the password requirements would be the same (or stronger) for the live environment than they would be for the development environment that I was currently playing with.

To quote one of the favourite movies of my wife – big mistake, huge mistake.

One article suggested switching off the password validation requirements for the server, long enough to work around this issue. So, before I made this request from our support people, I thought I had better look at the password policy, so it at least looked like I knew what I was talking about.

Finding the Windows Password Policy

Even if you don’t have the required permissions to change the password policy, you might well be able to see what they are.

From the ‘Run’ command – type either gpedit.msc or secpol.msc and press enter, which will launch the Group Policy Editor.

Once that loads, go to ‘Security Settings’ and then ‘Account Policies’ and then ‘Password Policy’. This screen shows what are the password requirements are for this Windows installation.

reporting services backup encryption key

From this screen you can see the ‘Password must meet complexity requirements’ option is enabled. The interesting information for my issue, is that the ‘Minimum password length’ is 12 characters, whereas in my live environment it is 8 characters. So, my 8 character password worked fine in live but failed here.

Once I changed my password to 12 characters (including the other usual complexity requirements – upper/lower case/numeric/special character) it worked perfectly fine.

Upgrading Reporting Services

Share this:

3 thoughts on “ ssrs – backup encryption key error ”.

  • Pingback: Upgrading A SQL 2012 AG to 2017 Without Downtime | Notes on SQL

' src=

We are trying to back up our Encryption key but I’m not finding the file do I have to change the Encryption key to have one to backup so that we can upgrade the server?

' src=

The encryption key isn’t a seperate file – it’s stored within SSRS and using the backup option within SSRS Configuration Manager is the way to back it up and restore it. Oddly enough, we have recently just recreated a new key, due to a strange error message that we were seeing. Creating a new key still allowed access to the existing reports, which I thought would have failed. Unfortunately I’m no expert in SSRS and the documentation is less than perfect.

Leave a comment Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed .

Create a website or blog at WordPress.com

' src=

  • Already have a WordPress.com account? Log in now.
  • Subscribe Subscribed
  • Copy shortlink
  • Report this content
  • View post in Reader
  • Manage subscriptions
  • Collapse this bar

Change the SQL Server Reporting Services Service Account

By: Satnam Singh   |   Comments (6)   |   Related: > Reporting Services Administration

Recently, we received a request where we needed to change the service account for SQL Server Reporting Services to a new account. We wanted to use a new account, because it would only be applicable for this particular instance. The Service Account that we used earlier was common for all production SQL Server instances which we wanted to eliminate.

In order to change the SQL Server Reporting Services (SSRS) Service Account, we need to perform the following steps:

  • On the SSRS Home Page, click on the Site Settings and Folder Settings and ensure that the New Service Account has been provided the appropriate role.
  • Ensure that the New Service Account has access to the Data Sources.
  • At the SQL Server level, ensure the new Service Account has the RSExecRole inside the ReportServer and the ReportServerTempDB databases.
  • Issue a full backup of all the databases along with the ReportServer and ReportServerTempDB database on the SSRS SQL Server instance.
  • Create a backup of the Encryption Key using the steps below.

Create Backup of Reporting Services Encryption Keys

  • Open Reporting Services Configuration Manager on the server.
  • Click on the Encryption Keys as shown in the screen capture below.

sql server reporting services manager

  • On the right side, click on the Backup button and a new window opens. Specify the location and the name of the Encryption Key Backup file. The extension of the Encryption Key Backup file will be *.snk.

ssrs backup encryption key

  • Enter a Password for the encryption key file and press the OK button.

Specify the Location and the Password of the Encryption Key.

  • The Encryption Key backup gets created as shown below.

Encryption Key gets Created.

Once the Encryption Key Backup is created successfully, the next step is to change the Service Account.

  • In the Reporting Services Configuration Manager, click on Service Account as shown below.
  • Enter the new Service Account and Password and then press the Apply button.  As soon as you click the Apply button, the system will create a backup of the Encryption Key then change the Service Account and then Restore the Encryption Key automatically.

ssrs change service account

  • Once the above step is performed, run services.msc and find the service for SQL Server Reporting Services and verify that the new account is being used for SQL Server Reporting Services.
  • Restart the SQL Server Reporting Services service.
  • Open the SSRS Home Page and ensure that the Folders and Reports are displayed properly.  Once the change happens successfully, the Folders should be shown properly on the SSRS Home Page.

ssrs home page

  • Inside the Folders on the Home Page, ensure the Reports are there and it doesn't ask for a User Name and Password. If everything looks good then it means everything has gone smoothly.

As discussed above, the system automatically backups and restores the Encryption Key, but in some cases an error is encountered. In such cases, we will need to manually restore the Backup of the Encryption Key as shown below, this is why we created a backup in the beginning of the tip.

Manually Restore the Reporting Services Encryption Key

  • If the Encryption Key needs to be restored manually, in the Reporting Services Configuration Manager click on the Encryption Keys and click on the Restore button as shown below.

ssrs restore encryption key

  • A new window opens as shown below.  Specify the File Location of the Encryption Key along with the Password. The password should be the same as specified during the creation.

Specify the Location of the Encryption Key along with the Password. Password should be the same as we have specified during it

  • Once the above step is completed then restart the SQL Server Reporting Services service and you should be able to view all the reports successfully without any issues.
  • In some cases, I have seen that the SSRS Reports writes data onto a particular location. Before the change, ensure the new Service Account has the necessary access to that particular file location.

Important Point of Consideration

If you do not create a backup and restore the Encryption Key, but instead directly update the SSRS Service Account, when you try to view the SSRS Home Page you will get the following error message:

In such cases, I have seen people delete the Encryption Key to try to make it work which is never successful. Instead you get the following screen. This is a pretty messy situation and it could be avoided if the operation is performed as per the steps above.

In case if things dont work well then we see this situation which is pretty messy.

  • Changing a SSRS Service Account is possible only when implemented accurately otherwise there can be situations where a restore of the ReportServer/ReportServerTempDB database is needed which shouldn't be the case.
  • Check out these other Reporting Services tips .
  • Check out the SQL Server Reporting Services Tutorial .

sql server categories

About the author

MSSQLTips author Satnam Singh

Comments For This Article

Related articles.

Connection denied by Geolocation Setting.

Reason: Blocked country: Russia

The connection was denied because this country is blocked in the Geolocation settings.

Please contact your administrator for assistance.

  • SAP HANA ABAP
  • Data Virtualization
  • ASP.NET Visual Studio
  • Purble Place

How to back up the reporting services encryption key to a text file

Reporting Services uses encryption keys to secure credentials, connection information, and accounts that are used in server operations. Encryption keys are created during setup. If you ever need to repair a Reporting Services installation due to changes in computer name, instance name, or user account values, you can apply the key to make the report server database operational.

Reporting Services provides the rskeymgmt utility that you can use to extract a copy of the encryption key from the report server database. The utility writes the key to a file that you specify, and then scrambles the key using a password that you provide. For lated use you should not forget the password and keep the destination file where the key is exported in a safe place.

To extract the encryption key from reporting services database to a text file, follow the below steps:

Log on to the server locally where the Reporting Services is installed.

Open the command prompt and navigate the current directory to the folder where the RSKeyMgmt.exe file exists. With default installation RSKeyMgmt.exe is placed in the " C:\Program Files\Microsoft SQL Server\80\Tools\Binn " folder.

Path of executable : C:\Program Files\Microsoft SQL Server\80\Tools\Binn <pwd> : MyPassword <file> : c:\ReportingServicesDBKey.txt

Sample command line prompt for rskeymgmt.exe to extract reporting services database key.

For more information on report server encryption keys check the following link Managing Encryption Keys MSDN article

SQL Server 2019 Installation download SQL Server 2019 download SQL Server 2017 download SQL Server 2016 download SQL Server 2014 download SQL Server 2012 MacOS ve SQL Server 2019

SQL Resources

SQL Server Tutorials SQL Server 2012 SQL Server Tools SQL Server SSIS

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

TF400981: Failed to backup the Reporting Services encryption key.

TF400981: Failed to backup the Reporting Services encryption key. You can try using RSKEYMGMT command to backup the encryption key Completed Verify Backup Encryption Key Operation: Warning

SQL Server Reporting Services A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports. 2,727 questions Sign in to follow

Hi @Pratik Makwana Has your issue been resolved? If you have any questions, please feel free to let me know. If the answer is helpful, please click "Accept Answer" and upvote it. Best regards, Aniya

Hi @Pratik Makwana According to your error message, you can try to use rskeymgmt.exe to backup the encryption key. Here is an example that you can use as a reference:

For more details, you can refer to this link: ssrs-encryption-keys-back-up-and-restore-encryption-keys .

p<password> Which password i need to put.

255004-image.png

TF401002:The SQL Server database Engine failed to save the database backup to path , Please grant SQL Serice account read write access to that folder

IMAGES

  1. SSRS 2017 Backup and Encryption Key Maintenance

    reporting services backup encryption key

  2. Backup SQL Server Reporting Service encryption key

    reporting services backup encryption key

  3. How to backup EFS encryption key in Windows 11/10

    reporting services backup encryption key

  4. Secure Microsoft’s SQL Server Reporting Services with SSL/TLS

    reporting services backup encryption key

  5. SQLCoffee

    reporting services backup encryption key

  6. SQLCoffee

    reporting services backup encryption key

VIDEO

  1. Encryption with Control-M Managed File Transfer

  2. SQL Server 2022: Handle encryption

  3. How to Keep Your Devices and Data Secure While Traveling

  4. How To Turn Off Encrypted Backup On WhatsApp

  5. Turn Off End to End Encryption Backup

  6. Understanding "Backup Validation": A Key to Data Security

COMMENTS

  1. Back Up and Restore Reporting Services Encryption Keys

    Back up encryption keys -Report Server Configuration Manager (Native Mode) Restore Encryption Keys See Also Applies to: SQL Server 2016 (13.x) and later versions An important part of report server configuration is creating a backup copy of the symmetric key used for encrypting sensitive information.

  2. Configure and Manage Encryption Keys (Report Server Configuration Manager)

    Back Up and Restore Reporting Services Encryption Keys Explains how to back up encryption keys and restore them to recover or migrate a report server installation. Store Encrypted Report Server Data (Report Server Configuration Manager) Describes encryption on a report server.

  3. Backup and restore operations for Reporting Services

    Back up the encryption keys Back up the configuration files Back up data files Related content This article provides an overview of all data files used in a Reporting Services installation and describes when and how you should back up the files.

  4. SQL Server Reporting Services Encryption Key

    Solution This tip is intended to encourage everyone to be sure to backup their SSRS keys, potentially often. SSRS uses symmetric and asymmetric keys which are generated from the Windows OS. If your SSRS setup uses a farm approach with multiple instances, then every instance must use a copy of the symmetric key.

  5. Backup your Reporting Services Encryption Key

    March 21, 2019 If you run SQL Server Reporting Services, part of your DR plan needs to include a backup of the encryption key for SSRS. This sadly is an all to often overlooked part of the solution, even though it is incredibly easy to do.

  6. SSRS 2017 Backup and Encryption Key Maintenance

    Backing up (and restoring the key) can all be done from the SQL Server 2017 Reporting Services Configuration Manager. Clicking on the Backup button allows for the creation of the SSRS Key file.

  7. Back up the SSRS Encryption Key

    In the Reporting Services Configuration Manager, click Encryption Keys in the left pane. In the Backup section, click Backup. In the Backup Encryption Key screen, complete these fields. File Location: - Select the directory where you want to store the Encryption Key backup. Password: - Enter the password that protects the Encryption Key backup ...

  8. Backup SQL Server Reporting Service encryption key

    Backup SQL Server Reporting Service encryption key Mohamed Radwan - DevOps 18.3K subscribers Subscribe Subscribed 11 Share 9K views 9 years ago Migrating TFS and SharePoint 2013 Databases How...

  9. Backup Encryption Key (Reporting Services Configuration)

    To open the Backup Encryption Key dialog box, click Encryption Keys in the navigation pane of the Reporting Services Configuration tool, and then click Backup. This dialog box also appears when you update the service account using the Service Account page in the Reporting Services Configuration tool. Options File Location

  10. SSRS unable to backup encryption key

    The problem is, step 1. On both the existing QA and production SSRS servers, when I try to backup the encryption key, after entering the path, password, and hitting OK, I get "windows has...

  11. SSRS

    Overview When attempting to back up the key, within Reporting Services Configuration Manager, it fails and provides a less than helpful error message. Background As part of an upgrade (from SQL Server 2012 to SQL Server 2017) I discovered that the installation of SQL Server 2017 will remove SQL Server Reporting Services (SSRS).

  12. Change the SQL Server Reporting Services Service Account

    Open Reporting Services Configuration Manager on the server. Click on the Encryption Keys as shown in the screen capture below. On the right side, click on the Backup button and a new window opens. Specify the location and the name of the Encryption Key Backup file. The extension of the Encryption Key Backup file will be *.snk.

  13. scheduled job for backing up reporting services encryption key

    0. I want to backup reporting services encryption key daily using SQl server agent job. I will be using the following syntax. rskeymgmt -e -i <> -f <> -p<password>. but when run on cmd it prompts me "are you sure you want to extract encryption key from report server". Only after typing "y" and pressing enter it lets me finish the task.

  14. Delete and Recreate Encryption Keys (Report Server Configuration Manager)

    You can use the Reporting Services Configuration tool or the rskeymgmt utility to reset the symmetric key and encrypted data. For more information about how the symmetric key is created, see Initialize a Report Server (Report Server Configuration Manager). How to recreate encryption keys (Reporting Services Configuration Tool)

  15. SQLCoffee

    Backup Reporting Services Encryption Key Applies to: Microsoft SQL Server 2008 Standard Edition SP2, Team Foundation Server 2010.

  16. SSRS Encryption Key

    SQL Server Reporting Services (SSRS) uses encryption to protect sensitive data with an encryption key. The encryption key used by SSRS is separate from the database and must be backed up separately. If you move the ReportServer database you must restore the encryption key before SSRS can function. The encryption key only needs to be backed up ...

  17. Missing Encryption Key when migrating Reporting Services from SQL

    Unfortunately we don't have the Encryption Key. Because the service is down I can't even take the back up now, its too late. I tried backing up the ReportServer and ReportServerTempDB databases and then restoring those to the new servers. Restore went well, I even changed the database from the reporting services configuration manager.

  18. How to back up the reporting services encryption key to a text file

    Log on to the server locally where the Reporting Services is installed. Open the command prompt and navigate the current directory to the folder where the RSKeyMgmt.exe file exists. With default installation RSKeyMgmt.exe is placed in the " C:\Program Files\Microsoft SQL Server\80\Tools\Binn " folder. Syntax : RSKeyMgmt -e -f<file> -p<pwd>. Code.

  19. SSRS Encryption Keys

    In Reporting Services, an initialized server is one that can encrypt and decrypt data in a report server database. ... in which case you may be required to apply a backup key or delete the encrypted data if a backup key is unavailable or not valid. For more information about encryption keys used by a report server, see Configure and Manage ...

  20. reporting services

    Comparing Report Server Configuration Manager on each, whilst obviously server name, service account and passwords will be different, everything else is the same except the Backup button on the Encryption Keys page is greyed out on the problematic installation.

  21. Encryption keys backup option is disabled

    I just installed Reporting Services (2005) in a "distributed installation" mode. ... When I get to the Encryption Keys page, it has a blue exclamation icon next to its icon in the left pane. ... it displays a green checkmark next to "Deleting Encryption Content". But the Backup and Change buttons are still disabled and the Initialization page ...

  22. TF400981: Failed to backup the Reporting Services encryption key

    Oct 19, 2022, 6:46 PM Hi @Pratik Makwana According to your error message, you can try to use rskeymgmt.exe to backup the encryption key. Here is an example that you can use as a reference: rskeymgmt -e -f d:\rsdbkey.snk -p<password> For more details, you can refer to this link: ssrs-encryption-keys-back-up-and-restore-encryption-keys.