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 ...Situation: New Install, SQL2K5,Named Instance,W2K3, DNN 4.0.2, Install Source CanSituation: New Install, SQL2K5,Named Instance,W2K3, DNN 4.0.2, Install Source Can't Install
Previous
 
Next
New Post
4/5/2006 9:00 PM
 

Hello all.  Well, I cannot seem to get 4.0.2 to install on SQL2K5, named instance (though that really isn't an issue), using the source install. This is a new install, not an upgrade, with IIS 6.0.

Here's *exactly* what I did.  If someone could tell me what I did wrong, I will write up exact steps to Install using the above configuration (so we don't have a zillion threads asking the same thing. .  I spent the last 1 1/2 hours looking for a similar thread, went back 300 threads--and nothing about the above scenario, so I figured I'd start a thread and finish it with something useful for others).

1. Downloaded 4.0.2 Install Source.

2. Unzipped the file to C:\websites\DNN\ folder I created

3. Went to IIS 6, created a Virtual Directory under the Default Web Site, pointed to C:\websites\DNN\website\.

4. In IIS, Allowed Read access and execute 'Scripts and Executables'. 

5. In IIS, Changed to ASP.NET 2.0

6. In IIS, Named the application DNN4Test

7. Went to the c:\websites\DNN\ folder.  Right clicked on the folder and selected 'Security'.  Selected 'Advanced' and 'Find Now' to get a list of all roles.  Selected 'NETWORK SERVICE' as this is a W2K3 Box (all the latest updates), gave complete control to the NETWORK SERVICE (just to be sure...I read the documentation, at least twice.  Not easy going back and forth from 4.0 instructions to 3.x instructions, but I've installed many 3.x apps, so perhaps not as difficult for me as for someone new to DNN), to the DNN folder and ALL children.

8. Opened SQL2K5 Management Studio, created a new database.  Called it DNN4.  Added a user and gave it ownership if the DNN4 database.

9. Opened release.config.  Added object qualifier of 'doodoo' (not really, but I gave it a name ).  Removed the two references to SQLExpress connection and added this connection string:

    <!-- Connection String for SQL Server 2000/2005
    <add
      name="SiteSqlServer"
      connectionString="Server=MACHINENAME\INSTANCE;Database=DNN4;uid=UserX;pwd=PWXXXX;"
      providerName="System.Data.SqlClient" />

and here:

    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=MACHINENAME\INSTANCE;Database=DNN4;uid=UserX;pwd=PWXXXX;"/>

That's it.  Went to http://localhost/DNN4Test/ and got the following error:

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 above, from my experience, tells me I have a permissions problem, but I followed the docs, EXACTLY.  Yet, I cannot get DNN 4.0.2 to install.  Can someone tell me what step I must have missed?  Thanks...

 
New Post
4/5/2006 11:48 PM
 

Well, I've discovered some strange things occurring, that I think have to do with anyone trying to install using anything *but* the SQLExpress database.  Though I *completely* removed any references to the SQL Express database in my web.config before I ran the default app, and before I set up IIS Virtual Directory, I noticed that when I opened the VD in IIS and clicked on the ASP.NET tab, it was pointing to a SQLExpress database connection!  And there was no info at all on my MSSQL 2005 (also tried 2000) connection string.

So I thought, 'hmm, it obviously MUST be getting this SQLExpress connection info from somewhere else'.  I looked in the website folder, and there's a development.config file.  I have no clue what it's for, since it's not mentioned in the docs, so I made a backup copy and changed that file also, exactly like the web.config.  Ran again.  Now I get an error stating that I need to change my folder permissions to add the NETWORK SERVICE (um, which is already set as FULL CONTROL on wwwroot (what the heck! right?), and on the C:/websites/DNN4 folder and ALL childe folders--so I do not understand that message at all. 

But anyway, there appears to be some issue with 4.0.2 looking at the development.config file for the connection string...this is perhaps why if someone just used the SQLExpress database, um, it would work.  And there sure seem to be a lot of threads asking the same types of questions here.  I don't see how any mods can possibly help ANYONE, if we all just start a new thread, without looking to see if there's another thread asking the same question.

But that's besides the point.  Has anyone heard of a bug w/4.0.2 concerning the development.config and using anything *but* the SQLExpress database?  As soon as I fixed that file, it *did* create database files in the MSSQL 2K5 database...

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Situation: New Install, SQL2K5,Named Instance,W2K3, DNN 4.0.2, Install Source CanSituation: New Install, SQL2K5,Named Instance,W2K3, DNN 4.0.2, Install Source Can't Install


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