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 ...Wait! A different Wait! A different 'Object reference not set to instance of an object' error! :)
Previous
 
Next
New Post
4/6/2006 12:55 PM
 

Ok. I am still attempting to install 4.0.2 with SQL 2K, on IIS 6.0 and W2K3 Server.  BTW, If someone is trying to use a different database than SQLExpress, make sure you check *exactly* where the comment lines start and end.  I would suggest that in future release.configs, that the comment start and end tags are in completely different lines...for the connection string info at least--this is very easy to overlook, even for seasoned programmers. I bet by separating out the comment lines, less people would make the *bonehead* mistake I did. :)

I am now receiving an obvious permissions related problem:  I've checked the last 500 threads, and have not seen this specific error mentioned.  I don't get any null reference or source dump.  The whole of the error is as below:

DotNetNuke Configuration Error

Object reference not set to an instance of an object.

DotNetNuke has extensive file upload capabilities for content, modules, and skins. These features require custom security settings so that the application is able to create and remove files in your website.

Using Windows Explorer, browse to the root folder of the website ( C:\DotNetNuke by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to Enable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions.

If using Windows 2000 - IIS5
- the {Server}\ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website

If using Windows 2003 - IIS6
- the NT AUTHORITY\NETWORK SERVICE User Account must have Read, Write, and Change Control of the virtual root of your website

---------------------------------------------------------------

Now, this should be easy to fix, right?  Well, the problem is, I have placed my c:\websites\DNN4\ folder and ALL sub folders and files with NETWORK SERVICE having COMPLETE CONTROL.  Heck, I have even placed my inetpub/wwwroot with NETWORK SERVICE WITH FULL CONTROL--since it's the 'localhost' root.

But even though it appears that every file and subfolder has NETWORK SERVICE with complete control, I still get the above error message?  I deleted the dnn_version database table (so I know the database access is working), and it still happens.  Deleted cookies--still get the same error.  I wish I could attach a picture so I could show everyone that my virtual directory root DOES have permissions for NETWORK SERVICE.

Could someone show this dufus what he's doing wrong?  I used to have no problems installing DNN.  Now it seems, that while I can install it using the starter kit and SQLExpress, and can install all versions of 3.x--I cannot install 4.0.2.  Any help appreciated!  Hoolie?  Can you hit me on the head with the obvious places to look besides the folder permissions?

 
New Post
4/7/2006 3:07 PM
 

Well, I decided to download 4.0.3, since I had never had such problems installing a version of DotNetNuke in the almost two years I'd been working with it.

4.0.3 installed in like 5 minutes for SQL2K5.  No problems at all.  Seems to me there are issues w/4.0.2 and installing it with *any database* other than SQLExpress.

My advice is for everyone (and there are a LOT OF THEM!) to download 4.0.3...and read the installation instructions!  And don't forget to look for the <--  and --> comments to see what's enabled and what's disabled.  Here's a valid connection string (for both SQK2K and 2K5, that should help):

    <add name="SiteSqlServer" connectionString="Server=(local);Database=dATABASENAME;uid=USERNAME;pwd=PWORD;" providerName="System.Data.SqlClient" />

If you are using a NAMED INSTANCE:

    <add name="SiteSqlServer" connectionString="Server=MACHINENAME\INSTANCENAME;Database=dATABASENAME;uid=USERNAME;pwd=PWORD;" providerName="System.Data.SqlClient" />

But by all means, stop tearing your hair out trying to install the source install for 4.0.2 for SQL2K or SQL2K5.  Just use the following link and download 4.0.3 Source Install...

http://prdownloads.sourceforge.net/dnn/DotNetNuke_4.0.3_Source.zip?download

It's been running now for a day, and appears to be a very solid version.  I've checked the logs and there are no worrisome error messages, and I've been installing modules all day, and compiling and such.

One other thing to note.  If you want to use the DotNetNuke project, and you did NOT use the default DotNetNuke_2 Virtual Directory, you need to change the .sln file and the web.vbproj file and change DotNetNuke_2 to whatever is the virtual directory you named in IIS.  Be a good idea to do this BEFORE you open of VS.NET or VWD...

Hope all this helps some people out there.  Get 4.0.3!!!

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Wait! A different Wait! A different 'Object reference not set to instance of an object' error! :)


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