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 ...After installing Starter Kit, compile gets Object reference not set to an instance of an object. After installing Starter Kit, compile gets Object reference not set to an instance of an object.
Previous
 
Next
New Post
8/4/2006 9:02 AM
 

Sorry for the long subject, but basically I started a new web site with the Starter Kit.  I used CTRL-F5 to compile and install, but when my browser opens, all I get is

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.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


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42  

Any ideas?

 
New Post
8/4/2006 2:49 PM
 
Are you using VWD or VS 2005 to do the initial install?

Do you already have the database setup, file permissions, user and connection settings already configured?


 
New Post
8/7/2006 1:02 PM
 
what has to be done in the database setup?
 
New Post
8/7/2006 8:29 PM
 
I'm bumping this thread as I'm having the same problem.

I've created a new db on my SQL server which has a user account with data read/write and securityadmin properties flagged.

I grabbed the DNN starter kit, loaded up a new website in VS2005, dropped in the DNN content, adjusted my web.config to point to the correct SQL provider with the appropriate credentials, selected the 'Publish website' option from VS2005's build menu, published it to a local directory, then copied the contents across to my web server.

Then on the web server I opened the security tab of the site parent directory and added 'NETWORK SERVICE' and granted it full access.

Then I dropped into IIS and created a new website (using a virtual site failed completely with an 'access denied' error page, and its our current policy to use distinct websites), within the new website I pointed it to the directory containing the DNN content (previous set with the security permissions), I flagged it as having read/write/execute abilities, left anonymous access enabled/windows authentication enabled/ and activated digest domain authentication for my domain. Then I made sure I set the ASP version to 2.0.

Saving all that I closed IIS Manager and switched back to my workstation. I opened up an IE window and pointed it to the web server machine and port. The initial install process kicked off (better than the previous attempt with 'permission denied') and appeared to run correctly until it reached the point where the output reads "Creating superuser" or similar. Following that it spat out the standard format error message underneath complaining about custom error mode.

So I then dropped straight into the web.config on the deployed edition sitting on the web server and changed the custom error mode from its default of "RemoteOnly" to "Off". Hitting the address again in my browser after making the change now gives me the same error message as the initial post.
 
New Post
8/7/2006 10:10 PM
 
I think I may have located the cause of the problem. I made the mistake of dropping the starter kit into a new website I had created, but the thing I overlook was that I usually work in C#. So the site language is flagged as thus; DNN on the other hand is made for VB, not C#. So when you build it/publish it the site just won't work correctly.

After creating a new site, this time with it's language set to VB instead, the DNN template showed up correctly in the templates selection. Creating a site with it also correctly displayed the welcome page.

Now after changing the web.config sql connection string information to be accurate and deploying the whole shebang to my web server, it successfully ran right through the install process and opened up onto what appears to be the default portal page (an empty block with date, register/login, search, and a short footer).

So, night_day, I think you may have compiled the site in the wrong language. Try recreating it again, making sure when you do that you have Visual Basic flagged as your site language. You should have more success once you have.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...After installing Starter Kit, compile gets Object reference not set to an instance of an object. After installing Starter Kit, compile gets Object reference not set to an instance of an object.


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