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 ...Error trying to install 3.2.2 on Windows 2003 ServerError trying to install 3.2.2 on Windows 2003 Server
Previous
 
Next
New Post
12/30/2005 1:17 PM
 

I tried to install DotNetNuke 3.2.2 on a Windows 2003 Server PC, using instructions contained in book entitled "Professional DotNetNuke ASP.NET Portals," and ended up hitting an error (see below). Any ideas as to what could be wrong? One issue that may be related, and I mention it just in case, is the fact that when I went to assign rights to the C:\Websites\DotNetNuke folder, I never saw the user mentioned in the book on page 38. I only had the following choices:

Account Unknown(S-1-5-21- etc.), Administrators (OMEGA2003\Administrators), CREATOR OWNER, Everyone, SYSTEM, Users (OMEGA2003\Users).

I just assigned Full Control rights to Everyone to try to get it to work and got the following error:

Server Error in '/DotNetNuke' 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:

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.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName) +379
   DotNetNuke.Data.DataProvider.CreateProvider() +19
   DotNetNuke.Data.DataProvider..cctor() +15

[TypeInitializationException: The type initializer for "DotNetNuke.Data.DataProvider" threw an exception.]
   DotNetNuke.Data.DataProvider.Instance() +0
   DotNetNuke.Common.Globals.GetUpgradeStatus() +307
   DotNetNuke.Common.Global.CheckVersion() +103
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +320
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

 
New Post
1/2/2006 12:22 AM
 
The account which requires the permissions is whichever account the Application Pool is using in IIS... however the "Everyone" should take care of that.  The reference to a "reflection" error seems more like a trust issue ( as defined in either web.config or machine.config )...

Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
1/2/2006 7:22 AM
 

Hi guys,

I am getting exactly the same error. In my case however I am using IIS 5 on a XP machine. I have followed the installation guide and believe that the security on the DotNetNuke folder is correctly set.

Resolution to this issue will be highly regarded.

Thanks in advance.
Ash


Small Business Solutions www.mywebjunction.com
 
New Post
1/3/2006 2:15 AM
 

OK, here's the deal. While thinking, reading, thinking, reading, watching TrainCert video on installation, etc., I did the following:

1) corrected the SQL Server login info in the release.config file.

2) renamed the release.config file to web.config (this step wasn't in the Professional DotNetNuke ASP.NET Portals book that I was using, but was in the installation DOC I checked after).

3) moved the SiteUrls.config file from the Config foldre to the root DotNetNuke folder (prior to doing this, got message about not being able to find this file).

4) redid the setting of permissions on the DotNetNuke folder by ADDing a user (clicking on Add button) called "Network Service" and giving them FULL CONTROL, removing FULL CONTROL rights from EVERYONE.

After doing all this, VOILA...it worked!

 
New Post
1/4/2006 10:39 AM
 
BobRoyAce wrote

2) renamed the release.config file to web.config (this step wasn't in the Professional DotNetNuke ASP.NET Portals book that I was using, but was in the installation DOC I checked after).

3) moved the SiteUrls.config file from the Config foldre to the root DotNetNuke folder (prior to doing this, got message about not being able to find this file).

4) redid the setting of permissions on the DotNetNuke folder by ADDing a user (clicking on Add button) called "Network Service" and giving them FULL CONTROL, removing FULL CONTROL rights from EVERYONE.



These are the important points - steps 2 and 3 are NEW requirements since v3.1 (which was released after the Book)., and step 4 is how you add a new "User" to the NTFS security settings.

Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error trying to install 3.2.2 on Windows 2003 ServerError trying to install 3.2.2 on Windows 2003 Server


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