I think I have tracked down the error. At least part of it !!
ASP.NET2 extends the CodeAccess level permisions required to
manage/load the various configuration settings of the web.config
file.
By default in .NET 1.1, an application could load the configuration
nodes (providers section) under Medium Trust. In .NET 2 under
Medium Trust it checks a requirePermission attribute on the
configuration section declaration - the section at the top of
web.config. For example:
<section name="data" requirePermission="false"
type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler,
DotNetNuke" />
<section name="logging" requirePermission="true"
type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler,
DotNetNuke"/>
If they are declared as above then acces to the "data" provider section
is allowed but access to the logging section is not (under Medium
Trust).
By default in .NET 2 the requirePermission is set to true, therefore we
will need to add the requirePermission="false" attribute to the element.
This is not documented in msdn at all - in fact if you add the node
intellisense tells you it is not a valid attribute for the element.
Charles Nurse
Keydance Computer Services
Langley, BC, Canada