Skip to main content

Microsoft SQL Reporting Services FIX

Scenario

MS SQL 2005 Reporting Services on Windows Server 2003. App based on MS SQL Reporting services web service failing.

Error "System.Configuration.ConfigurationErrorsException: The RSA key container could not be opened"

Trouble shooting steps I followed.

  1. Check IIS, how are you authenticating?
  2. Check permissions on the sql database, ensure the web server HOSTNAME$ is db owner. If IIS is anonymous then NETWORK SERVICE must have db permissions too.
  3. Check permissions on your web services via the admin interface usually something like this http://HOSTNAME/Reports$DBINSTANCENAME/Pages/Folder.aspx
  4. Check you can access the web services from a workstation to ensure the service is "exposed"
  5. Check you can access the web services from the web server, you should be able to enter the web service required variables and return data.

If the site is running in the "Network Service" context then it is possible that the access to key store was removed. To reassign permissions to allow Network Service account access to the key store run the following command from the .net Framework folder.

%WINDOWS%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -pa "NetFrameworkConfigurationKey" "Network Service"

This seems to occur sometimes with SUS security updates but I haven't completely figured it out, will update once I do.

Popular posts from this blog

Mac OS X "SOE" Day 7

Page Redirection> continued from day 6...

In summary, here is my method for creating a Mac OS X 10.7.3 Standard Operating Environment "SOE" Image.


Overview The goal is to create a "MASTER" non-booted SOE that can be used with multiple models and it multiple sites with different local requirements.

My intention is to use this "MASTER" image in a manual restore procedure due to the fact netboot facilities cannot be made available to all the sites I support however the DMG files are netboot compatible.

RequirementsLion Recovery Disk Assistant v1.0"TARGET" workstation. A compatible workstation that will be used to install Mac OS X 10.7.3 and capture a DMG image(s)."ADMIN" workstation. A workstation with Disk Utility that you will use to capture your DMG image(s).External storage such as a USB HARD DISK. SetupDownloaded the Lion Recovery Disk Assistant v1.0 and followed the instructions to setup an external Recovery D…

Mac OS X "SOE" Day 6

Page Redirection> continued from day 5...

Continuing on from the "firstboot" phase setup we need to script our "localiser" options.

I previously set my build phase to autologin and run the firstboot script, the localiser phase essentially sits there and waits for you to run it.

In my case I have an applescript GUI wrapper that requests some info to use in the localisation. I request a TAG number which is an organisational internal number and I also request a user name that will be set as the OWNER.

NOTE : I ordered these specifically...not just because it makes sense logically but also technically. For example, setting the Language actually zaps a plist file (.GlobalPreferences) which you need to write to for Locale and Country info.

This stuff is going to be totally dependant on your environment, as an example here is what I do.

So what's the minimum we need in the "localiser" phase? Depends on how many sites you support, I support over 50 si…