while installing dotnetnuke 4.0.3 i m facing following error
steps that i followed to install dotnetnuke 4.0.0
1)Using SQL 2000 : created database having name DotNetNuke4
2)Created folder having name Dotnetnuke_2 with subdirectory Website
3)unzip install package in Website folder
4)Rename relase.config to web.config
5)written database server name uid and password
6)delete tag <data
defaultProvider="SqlDataProvider">
<providers>
<clear/>
<add
name="SqlDataProvider"
type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
connectionStringName="SiteSqlServer"
upgradeConnectionString=""
providerPath="~\Providers\DataProviders\SqlDataProvider\"
objectQualifier=""
templateFile="DotNetNuke_template.mdf"
databaseOwner="dbo"/>
</providers>
</data>
because i am using SQL Server 2000 and not express
7)created virtual directory
8)change asp.net framework setting from IIS property to 2.0.50727
9)run from IE version 6.0
Installing DotNetNuke
Server Error in '/DotNetNuke_2' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. |
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +465
DotNetNuke.Data.DataProvider.CreateProvider() +39
DotNetNuke.Data.DataProvider..cctor() +13
[TypeInitializationException: The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.]
DotNetNuke.Entities.Portals.PortalSettings.GetProviderPath() +14
DotNetNuke.Framework.Install.InstallApplication() +1189
DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +376
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
|
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42