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 Uploading DNN 5.4.4 to Production Web HostError Uploading DNN 5.4.4 to Production Web Host
Previous
 
Next
New Post
7/31/2010 4:23 PM
 
I am having an issue uploading a new DNN 5.4.4 site from my development server to the production web host. 

I created the site on my development server and created all the pages/forums/skins/etc.   The development server is Windows 2003 with IIS6 and Sql 2008 Developer.   I had this working using localhost, as well as over the network with a machinename alias.  Once I got everything the way I wanted it, I created aliases for the production Url's for the portal and proceeded to upload the content to the web host.

On the web host, I created the database (SQL2008 Express) and synchronized my local DNN database with the web host database using a Sql compare utility, which synchornizes both the structure and the data.  Once the synchronization was complete, I recompared the databases and they were identical.  I then uploaded the entire web folder via Ftp.  I then changed the connection strings in the web.config to point to the web host's database instance.  Then, I went to the web host control panel and set Network Service to have Read/Write permissions and replaced permissions from the root folder down.

In my opinion, this should've worked.  However, when I went to run the site, I received the following error:

DotNetNuke Error

An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Framework.DefaultPage.InitializePage() at DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at DotNetNuke.Framework.PageBase.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Any ideas what I did wrong, or what may be causing this error?
 
New Post
8/1/2010 6:06 AM
 
did you provide new domain name as additional portal alias (either via UI prior to the move or directly in PortalAlias table in the database)?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/1/2010 5:41 PM
 
Yes, I mentioned that in the first paragraph "I created aliases for the production Url's". 

I'm still having the problem.  I decided to try copying it locally to another database and another local Url, and I have the exact same problem locally on the new Url (still working on the original Url).   The error (Object Reference not set) is occurring in the DotNetNuke.Library\Framework\PageBase.vb class file on line 443 of the Overrides Sub OnInit method.  It's throwing the error on MyBase.OnInit(e).  I've stepped it through the debugger, and I can't tell what object it's complaining about.  None of the objects in that method are null.
 
New Post
8/1/2010 6:28 PM
 
I have verified the Url several times.  Although, it looks like for some reason this may be causing a problem.  I copied the site to my local machine to run it under debug.  I have narrowed it down to the InitializePage method in Default.aspx line 154.  Must've misread the stack trace before.  It's still running fine on the original development server I loaded DNN on, but I am able to reproduce the error on my local development box after replacating the database and adding the portal alias.  I am using a local Sql Server 2008 instance, have the web.config updated appropriately, and copied the production website on top of the development source code install.  

It is trying to loop through the PortallSettings.ActiveTab.BreadCrumbs (which is null/nothing), which gets the error.  I have re-checked that the alias is in the PortalAlias table in the database.  I have re-checked it several times.  Right now, I'm using the portal alias of  "localhost/DotNetNuke_Community".   I copied/pasted the Url from the PortalAlias table to the web browser, in case I typed it wrong and didn't see it.  Got the same error.  The PortalSetting.ActiveTab isn't null, but most of the elements look like default settings (either empty strings, Nothing, -1, etc.).

I also just tried setting the virtual directory name to the original virtual directory that I set it up under on the other server (localhost/domain), and am getting the same error, so I don't see how it can be portal alias related.
 
New Post
8/1/2010 8:20 PM
 

Okay, I figured out my problem.  I tracked it down in the code to the PortalInfo object not getting loaded, and further tracked that to the stored procedure that was supposed to load the object (GetPortal).  GetPortal was returning zero rows.  When evaluating why this occurred, I found that the PortalLocalization table did not have any rows in it. 

I guess this is my fault, as I haven't used Redgate's SQL Data Compare much.  When it ran, it told me there were 10 tables it couldn't compare.  I just thought that was because they didn't have any rows, and ignored it.  No, that wasn't the reason it couldn't compare.  It can't compare tables that don't have a primary key.  Evidently, there are a few tables in DNN that SQL Data Compare won't handle due to this issue.  Once I loaded the PortalLocalization and TabSettings tables (there were a few more tables it couldn't compare in the forum section), it started working.

Wow, I can't believe DNN has tables with no primary key.  It looks like these tables could be made to have a primary key.  It appears that PortalLocalization could have PortalId and LocalizationCode as the primary key, and it appears the TabSettings could have TabId and SettingName set as the primary key.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error Uploading DNN 5.4.4 to Production Web HostError Uploading DNN 5.4.4 to Production Web Host


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