dnn 3.0.7

Greetings ...

Successfully running dnn 2.1.2 (MS Access database) but get 'runtime error' when trying dnn 3.0.7

Has anyone had success with dnn 3.0.7using discountasp.net?

Thanks.

Roy
www.haygood.com (ok)
www.haygood.com/beta/default.aspx (problem)


Post Edited (haygoodcom0) : 12/11/2004 7:29:44 PM GMT

 

Server Error in '/beta' Application.


Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Exception creating section handler.

Source Error:

Code:

Line 4:      <configSections>
Line 5:          <sectionGroup name="dotnetnuke">
Line 6:              <section name="data" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
Line 7:              <section name="logging" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
Line 8:              <section name="scheduling" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />

Source File: E:\web\haygoodcom0\htdocs\web.config Line: 6



Version Information:Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032 <!--
[TypeLoadException]: ?
at System.Type.GetType(String typeName, Boolean throwOnError)
at System.Web.Configuration.HttpConfigurationRecord.GetFactory(String configKey)
[ConfigurationException]: Exception creating section handler. (E:\web\haygoodcom0\htdocs\web.config line 6)
at System.Web.Configuration.HttpConfigurationRecord.GetFactory(String configKey)
at System.Web.Configuration.HttpConfigurationRecord.GetFactory(String configKey)
at System.Web.Configuration.HttpConfigurationRecord.Evaluate(String configKey, SectionRecord section)
at System.Web.Configuration.HttpConfigurationRecord.GetConfig(String configKey, Boolean cacheResult)
at System.Web.HttpContext.GetConfig(String name)
at System.Web.Configuration.HttpConfigurationSystemBase.System.Configuration.IConfigurationSystem.GetConfig(String configKey)
at System.Configuration.ConfigurationSettings.GetConfig(String sectionName)
at DotNetNuke.Framework.Providers.ProviderConfiguration.GetProviderConfiguration(String strProvider)
at DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectNamespace, String ObjectAssemblyName)
at DotNetNuke.Data.DataProvider.CreateProvider()
at DotNetNuke.Data.DataProvider..cctor()
[TypeInitializationException]: The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.
at DotNetNuke.Data.DataProvider.Instance()
at DotNetNuke.Services.Upgrade.Upgrade.AutoUpgrade()
at DotNetNuke.HttpModules.AutoUpgradeModule.Init(HttpApplication application)
at System.Web.HttpApplication.InitModules()
at System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers)
at System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context)
at System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
--><!--
This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.-->

 

Running DNN 2.1.2 successfully under theroot directory.No problems at all.

Trying toconfirm/checkout DNN 3.0.7 separately under /beta folder. Did a fresh install directly to /beta.

Thanks for the help. Sounds like what I trying to do simply won't work.

Roy

 

Discovered that fact shortly after reporting problem.

Looks like I'll stick with dnn 2.1.2, and Access, for awhile longer.

Thanks for the post.

 

Hi,


You know that DNN 3.+ doesn't supportAccess?


It only supports SQL. You have to have a SQL-enabled account.


You no longer have to change the data provider in the web.config file, just your connection string to point to your SQL database and the correct user account &amp; password. Must also give that user dbo permissions in your SQL DB.