SSRS Data Source is not responding error as The report server is unable to access encrypted data

The report server is unable to access encrypted data

Issue:


As we all know we have to plan for Disaster Recovery (DR) for our SharePoint environment we do a trail run on every year. We have performed the DR for this year also but during the practice we have encountered the below error while rendering SSRS reports. The error coming was: The report server is unable to access encrypted data.

The report server is unable to access encrypted data
The report server is unable to access encrypted data

Why is this issue?



We have restored all the below set of application DB from PROD to DR server and it has overwritten the reporting service DB also.

  • UserProfileService_ProfileDB
  • UserProfileService_SocialDB
  • UserProfileService_SyncDB
  • ReportingService
  • ReportingService_Alerting
  • ReportingServiceTempDB
  • SearchService_Admin
  • SearchService_Admin_AnalyticsReportingStore
  • SearchService_Admin_CrawlStore
  • SearchService_Admin_LinksStore
  • SecureStoreService

The issue here is PROD FARM has configured with one security key and DR server got configured with some other security key.

Solution:


Create all the data sources in DR server to fix this issue. As soon as we create the new data source for SSRS report everything went seamlessly.

Hope this helps.


You May Also like the Following SharePoint Online Tutorials:

About Krishna Vandanapu

I am Krishna.Vandanapu a SharePoint architect working in IT from last 12 years, I worked in SharePoint 2007, 2010, 2013, 2016 and Office 365. I have extensive hands on experience in customizing SharePoint sites from end to end. Expertise in SharePoint migration tools like Sharegate, Doc Ave and Metalogix. Migrated SharePoint sites from SharePoint 2007 to 2010 and 2010 to 2013 several times seamlessly. Implementing CSOM with Microsoft best practices. Spent quality time in configuring SharePoint application services like User Profile, Search, Managed Meta data services etc. Now exploring SharePoint Framework and SharePoint 2019

View all posts by Krishna Vandanapu →