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.

Labels:

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. Requirements Lion 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. Setup Downloaded the Lion Recovery Disk Assi...
more...

IIS looks normal, but site won't load.

Someone updated .Net Framework on Win2003 server (required for another app). Unfortunately didn't check existing IIS sites and their requirements so it broke a custom c# web site. Uninstalled without error in the OS, but website still 404ing, reboot and iisreset didn't fix it. "%systemroot%\Microsoft.NET\Framework\ VERSION \aspnet_regiis.exe" –i Then iisreset. All good :) Read about it here http://msdn.microsoft.com/en-us/library/k6h9cz8h(v=vs.80).aspx
more...

Mac OS X "SOE" Day 3

Page Redirection > continued from day 2... Ready to copy my scripts over, as previously mentioned I am thinking of having 3 phases; build - preps the image for dmg capture. firstboot - runs anything I can't do in build ie, writing to byhost files etc that require UUID or Macaddress. Basically machine/model specific settings. localise - runs localisation scripts such as language, locale etc etc. Basically a set of dynamic scripts in case you are an admin for multiple offices, multiple countries. So what's the minimum we need in the "build" phase? Disable the Setup Wizard. Disable the Registration Wizard. Create a local admin user(s) and set autologin for the firstboot phase. Enable root (set the password). Enable SSH Access Enable VNC Access Enable ARD Access Disable softwareupdate automatic updates "schedule" Cleanup/Minimise the dmg where possible. Set a firstboot loginhook for the second phase. What are some other n...
more...