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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to Place Database on a Separate ServerHow to Place Database on a Separate Server
Previous
 
Next
New Post
10/9/2006 4:43 PM
 

Installing DNN from scratch to a separate server is definately a sure way to go. There are a few other things that DNN refers to that can affect operation when you are moving the application around.

web.confg
<connectionStrings.SiteSqlServer> <appSettings.SiteSqlServer>
<appSettings.InstallationDate>
<system.web.machineKey.validationKey> <system.web.machineKey.decryptionKey>
<DotNetNuke.providers.SqlDataProvider.objectQualifier>
Generally not used, but very effective in a shared hosting environment with a single shared SQL database.

I would purposely use Build|Publish Web Site and Website|Copy Web Site to separate test locations and compare the results with your working site. When I reread you post, I have three more quesitons.

1) Are you using Visual Studio 2005 Express Edition?
2) What was the error message in the first place?
3) Can you display the Admin|Log Viewer to see the error(s)?

I would really like to resolve this puzzle and either make it work or put it to rest for a reason.


Dwayne J. Baldwin
 
New Post
10/14/2006 4:31 PM
 

Dwayne,

I am sorry to reply late.  I have some critical issues to handle.  I hope I can help to make this product better.  These errors only occur if I ues "Build|Publish Web Site" -- Scenario 1.  Everything is fine if I use Scenario 2.  But first I create the DNN web site on Machine A with SQLServer on the same machine.  The connectionString is "Server=machinea;Database=DNN;uid=dnn;pwd=dnnpass;".  Things work fine on Machine A.

Scenario 1:  Build|Publish Web Site.  I publish the web site to Machine B.  This method gives error.

Scrnario 2:  On Machine C, create a web application in IIS.  Using Windows browser, copy all the file for DNN from Machine A.  Give "NETWORK SERVICE" the "Full Control" to this folder.  I can run http://localhost/dnn on Machine C without error.  I guess I could use "Website|Copy Web Site" too.

1) Are you using Visual Studio 2005 Express Edition?  VS 2005 Professional
2) What was the error message in the first place?  See below
3) Can you display the Admin|Log Viewer to see the error(s)? 
See below

Error for 2):  Login as host on Machine B with http://localhost/dnn.  Click on Users in the Common Tasks.

An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Value cannot be null. Parameter name: format ---> System.ArgumentNullException: Value cannot be null. Parameter name: format at System.String.Format(IFormatProvider provider, String format, Object[] args) at DotNetNuke.UI.WebControls.PagingControl.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Error for 3):  From 2) above, click Back in the browser.  Click Admin|Log Viewer

An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Value cannot be null. Parameter name: format ---> System.ArgumentNullException: Value cannot be null. Parameter name: format at System.String.Format(IFormatProvider provider, String format, Object[] args) at DotNetNuke.UI.WebControls.PagingControl.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

 
New Post
10/15/2006 1:04 AM
 

On machine B using IIS manager, select the properties of the virtual website and check the ASP.NET tab settings. What version does say? Also check the default web site Home Directory, and look for web.config in that local path.

There is obviously something odd about machine B.  Have you tried Build|Publish on machine C?

I see nothing to do with the database yet, it looks more like a .NET issue. Running aspnet_regiis may fix it, or the Build|Publish mechanism is simply not publishing all the files correctly.

 


Dwayne J. Baldwin
 
New Post
10/15/2006 12:59 PM
 

Dwayne,

  1. Verson:  All three machines have 2.0.50727.
  2. Build|Publish to Machine C has the same result as to Machine B.  Both have same errors.

Does this have to be a website on machines B and C?  I have been using a virtual directory under an existing website.  But copying files gives no problem.

 
New Post
10/15/2006 3:51 PM
 

Virtual directories are fine, as long as the web.config in the root website does not conflict with the web.config in the virtual directory.

A quick way to check this is to rename the root to web.configx and hit the virtual site to see if the errors are different. Then rename web.configx back to web.config in the root. This is a known issue with IIS and parent web.config files.

If copying files is no problem, then you must have something turned off (not to publish). The only thing you can do is build/publish then compare it to the files that should have been copied.

Sorry I don't have a better answer, it's really difficult to diagnose from here (along with a broken thumb).


Dwayne J. Baldwin
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to Place Database on a Separate ServerHow to Place Database on a Separate 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