SharePoint Feature Receiver Error ‘The EXECUTE permission was denied…’

15 03 2010

I got this error this morning when trying to activate a web feature in a site collection. It turns out that this is because the application pool running the web application (in my case ‘Network Service’) does not have the required permissions to run some SharePoint SQL stored procedures within the configuration database.

In order to fix this error you will need to give the application pool database role WSS_Content_Application_Pools ‘Execute’ rights on the following stored procedures:

  1. proc_PutObject
  2. proc_putClass
  3. proc_dropObject
  4. proc_getNewObjects

Once you have granted this role the correct permissions you will be able to activate the feature/perform the operation you were attempting before.

Hope this helps!

Opening InfoPath form in SharePoint ‘Requested registry access is not allowed’

8 12 2009

This is another gotcha that I’ve run into today – when I went to publish an InfoPath form to my SharePoint site I spotted an error in the design checker ‘Invalid Form Template’. I ignored the error and carried on but when I tried to create a new form based on the template in the document library, I received the following error –

Requested registry access is not allowed. at System.ThrowHelper.ThrowSecurityException(ExceptionResource resource) at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable) at Microsoft.Win32.RegistryKey.OpenSubKey(String name) at Microsoft.Win32.Registry.GetValue(String keyName, String valueName, Object defaultValue) at Microsoft.Office.InfoPath.Server.Runtime.FormServer.<>c__DisplayClass1.b__0

I did some research and came accross this blog post from Joel Oleson (@joeloleson) which helped me fix the problem –

The steps I took to fix the error were slightly different from Joel’s (see below) but his blog post helped to point out the registry keys on which the access was failing.

The application pool account for my SharePoint web application was running as ‘Network Service’, I did try and add this account to the ‘Distributed Com Users’ group but this did not fix the problem.

Initially I changed the application pool account for the web application to a domain account and this fixed the problem, then I changed it back to Network Service and gave that built in account read permission on the registry key –


and that also worked! So there are two options in case anyone runs into the same problem.

Hope this helps 🙂

How to: Install SharePoint 2010 ‘Standalone’ on Windows 7

23 11 2009

SharePoint 2010 Logo Since getting my hands on the Beta 2 version of SharePoint 2010 and SharePoint foundation I’ve read countless guides and blog posts about how to install it on Windows 7.

The problem is finding one that gives you the correct install procedure and this often means trawling through the comments to see if it is a reliable source. Because of this I’ve decided to post my own tutorial of the steps I used to create a reliable and fully functional SharePoint 2010 environment on a single machine (client OS).

Keep in mind that this blog post only walks through installing SharePoint 2010 in ‘Standalone’ mode (aka default configuration). This does not give you as much flexibility nor does it replicate a server farm environment. But this does work well for small dev work or to simply play around with SharePoint 2010.

*RAM Requirements: Be aware that if you are planning to install SharePoint Server 2010 you will need a lot of RAM. The recommended minimum from Microsoft is 6GB. SharePoint 2010 will install on a machine with 4GB of RAM but this will not be enough for a development environment.*

1. Install the Pre-Requisites for your operating system listed in the following MSDN guide –

2. Install the ‘WCF Hotfix’ (KB976462) for Windows 7/Server 2008 R2 which is available here –

3. Extract the SharePoint installation (.exe) that you downloaded, you can do this by typing at the command line the following –

c:\SharePoint\SharePoint2010.exe /extract:c:\Temp

4. Next we need to edit an xml file and add an attribute that will allow you to install SharePoint on a workstation OS. If you try and run the setup without performing this step then it will display an error message that the OS is not supported.

SharePoint 2010 Setup Error

Open the ‘config.xml file located at ‘c:\Temp\files\Setup\config.xml’ (where Temp is the folder that contains your extracted files from above).

Add the following line inside the <configuration> tag:

<Setting Id="AllowWindowsClientInstall" Value="True"/>

Save and close the file.

5. Run the SharePoint 2010 setup (setup.exe).

6. When asked what type of installation you wish to perform select ‘Standalone’. This will install an instance of SQL Express and the default configuration. This will allow you to use local windows accounts.

SharePoint 2010 Installation Type


7. Once the wizard has completed it will prompt you to run the ‘SharePoint Products Configuration Wizard’ (aka Psconfig). Do Not run the wizard and exit.

8. Install SQL Server 2008 cumulative update package 2 –


9. When the above update has finished installing, execute the ‘SharePoint Products Configuration Wizard’. Ignore the warning telling you that installing SharePoint 2010 on Windows 7 or Vista is unsupported. You also need to click ‘OK’ to the message explaining that IIS will be reset as part of the installation.



The wizard will now configure SharePoint 2010 so you can sit back and relax! (Hopefully this step goes smoothly and you don’t see any errors).

10. When the wizard is complete, click ‘Finish’. An IE window should now popup and display a SharePoint page asking you to select the template you would like for your first SharePoint 2010 site collection.

SharePoint 2010 Central Administration

11. Success – the installation is now complete and you have a full working copy of SharePoint 2010 Beta! 🙂