You're getting «HRESULT: 0x80070005 (E_ACCESSDENIED)» when you try to create subwebs using a custom site definition programmatically?

For a quick work-around, just add this to your Assembly.info.cs file, re-compile and re-deploy:

using System.Security;

...

[assembly:AllowPartiallyTrustedCallers]

Signing and making your code trusted should also work, but if you're on a tight spot, this code will probably get you some air to breath

Hope this helps someone out there

Florin just emailed me requesting to help on letting the word out on with the solution for this problem he was facing, so here it is, on his own words:

«If you upgrade from WSS 2.0 to Wss 3.0 and configure WSS 3.0 with anonymous access, you might get the following error while trying to create websites:

Error: File not found.

 

Looking at the Verbose Logfiles, you might get the following Error message:

Application error when access /_layouts/newsbweb.aspx, Error=A aplicação Web não foi encontrada em http://www.myportal.com/blogs/2a.

Verifique se escreveu o URL correctamente.

Se o URL tiver de fornecer conteúdo existente, o administrador do sistema poderá ter de adicionar um novo mapeamento do URL do pedido à aplicação de destino.

em Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)

em Microsoft.SharePoint.Administration.SPNativeConfigurationProvider.LookupSite(String requestUrl, Int32 iisInstanceId, String& siteUrl, Int32& zone, Guid& appId, Guid& siteId, Guid& databaseId, String& databaseServer, String& databaseName, String& databaseUsername, String& databasePassword, Boolean& useHostHeaderForSiteName) ........

 

Resolution:

 

1. ISA 2004 Web Publishing Rule (additional configurations over  the default rule):

    A. Forward the original host header instead of the actual one

    B. Requests appear to come from the original client

 

2. WSS 3.0 Configuration:

    In SharePoint 3.0 Administration page -> Operations -> Go to Managed Paths (Mapeamentos de Acesso Alternativos)

    Set the Internet Url equal to the public FQDN of the website used by ISA 2004 to publish the your portal, e.g. www.myportal.com.

 

3. IIS Configuration:

    Add the public FQDN as Host Headers in IIS for the website extended with WSS 3.0, e.g. www.myportal.com.

 

I hope that this can help someone.

 

Greetings!
Florin Zamfir»

Cool, eh?

Both me and Daniel Pereira just did 70-630. Instead of bragging about it, let's just say it's done, with style

Three or four weeks ago I did this during a weekend (yes, had no sleep...)

Basically, I integrated the Timeline from SIMILE (Semantic Interoperability of Metadata and Information in unLike Environments) into a SharePoint web part which consumes event itens from a SharePoint Calendar list.

I really fancy on how I might be using this in the future

Great news!

Just got this by email (which I have negleted to read and reply to properly lately with all the fuss which is going on) from José Silva:

This workaround helps us all to deal with the fact that the ability to update SharePoint lists from Office Excel 2007 is deprecated in favor of publishing and synchronizing lists using Office Access 2007, so now you can use the Excel 2007 SharePoint List Synchronizing Add-in to update SharePoint lists from Office Excel 2007.

I still think deprecating this feature was not a very happy decision. Being able to play from Access 2007 is great, but loosing Excel functionaly? ... C'mon guys!!

SPException ...

Pedro Santana just shared this with me ...

Now, who had the idea of translating the role ID for full control on MOSS 2007 pt-PT ?

... naughty you!