Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Editing web.config before installing 4.3.4Editing web.config before installing 4.3.4
Previous
 
Next
New Post
8/28/2006 3:53 PM
 
Hi!

After deleting web.config and renaming release.config to web.config, I edited it like this, but I'm getting an error at the end of installation (thread, object reference, etc):

<connectionStrings>
    <!-- Connection String for SQL Server 2005 Express -->
    <add name="SiteSqlServer" connectionString="Data Source=(local)\SQLExpress;Database=dotnetnuke;uid=nukeuser;pwd=xxxxxx;" providerName="System.Data.SqlClient" />

<appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=(local)\SQLExpress;Database=dotnetnuke;uid=nukeuser;pwd=xxxxxx;" />


Is this right?

IIS,  database and folder permissions are apparently configured correctly. I'm using Windows 2000 Server and SQL Express.

Thanks in advance!
 
New Post
8/28/2006 7:16 PM
 

Can you please provide more detail on the error?  Why did you have to delete the web.config and create another anyway?  Did you already try to run a previous install before this one?  Copy the whole error page please.

 

Thx

 

 

 
New Post
8/29/2006 9:08 AM
 
I deleted it because it's explained in DotNetNuke Installation Guide.pdf . The error message appears when I do a clean install and it appears faster when I retry an installation. Sometimes the error is the following, sometimes it talks about thread something.

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:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +125
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +83
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +5768
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64



 
New Post
8/29/2006 1:39 PM
 

So you had a bad install previously.  Whenever this happen I always delete not just the web.config but also the database and files within the directory to ensure a clean install.  During some failed installs in the past, I would just type in the url

(1.) http://domain.com/install/install.aspx?mode=upgrade

(2.) If that didnt work I deleted the entire directory and unzipped a fresh DNN source and create a NEW database with new usernames etc. 

Let me know if these two change anything for you and repost any error or stacktrace.

 
New Post
8/30/2006 10:08 AM
 
I've tried various clean installations now. The last method was deleting a lot of modules (except for html and help), but I couldn't get it to install.

Maybe the problem lies in SQL Server Management Studio Express.

In the login properties for the login I created, in "Users mapped to this login", after selecting the database dotnetnuke, should I choose [dbo] or [db_owner] in Default Schema?

I should also set this user as db_owner in "Database role membership", right?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Editing web.config before installing 4.3.4Editing web.config before installing 4.3.4


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out