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 ...Moving from local Vista host to Web Host - problems!Moving from local Vista host to Web Host - problems!
Previous
 
Next
New Post
11/20/2008 9:16 AM
 

hi all, first time poster....long time reading!

I had installed a portal on my local machine which is Vista ultimate. got everything going eventually (made virtual directory into Application on IIS7), updated the site, no problems.

I then copied the contents of the dotnetnuke folder (one that virtual directory was pointing to) into a new folder in the wwwroot of my new web host.

i have tried the following web.config connection strings but all give the same errors as below:

Provider=sqloledb;Data Source=<dbserver>.hosting.local;Initial Catalog=<dbname>;User Id=<userid>;Password=<pass>;

Data Source=<externalIPAddr>;Network Library=dbmssocn;Connection Timeout=15;Packet Size=4096;Integrated Security=no;User ID=<username>;Encrypt=no;

server=<dbserver>.hosting.local;database=<dbname>;uid=<username>;pwd=<pass>;

Which one would be correct?

If i access the site via the web hosts own address i get the following message. only the one web.config file exists in the folders. i am unable to access the host to set the site to "application" like i did in Vista.

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:

 

Source File: D:\CustomerData\webspaces\webspace_00106938\wwwroot\cottage2\web.config    Line: 60

 


If I look at the site through its dot com address i get the following error which is different to the above. it does look like a connection string error but i don't know enough about dotnetnuke to say otherwise. any help would be appreciated:

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:

 

Stack Trace:

 

 


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

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


Show Additional Configuration Errors:

 
 

 
New Post
11/20/2008 12:18 PM
 

Some of the post seems to be missing. I used version 4.8 at the time. as i said when i access the site via the dot com address i get the following errors:

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:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Common.Utilities.Config.GetConnectionString(String name) +47
   DotNetNuke.Common.Utilities.Config.GetConnectionString() +38
   DotNetNuke.Data.SqlDataProvider..ctor() +83

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +103
   System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +268
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
   DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +582
   DotNetNuke.Data.DataProvider.CreateProvider() +47
   DotNetNuke.Data.DataProvider..cctor() +13

[TypeInitializationException: The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.]
   DotNetNuke.Common.Globals.GetUpgradeStatus() +67
   DotNetNuke.Common.Initialize.CheckVersion(HttpApplication app) +147
   DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +413
   DotNetNuke.Common.Initialize.Init(HttpApplication app) +125
   DotNetNuke.Common.Global.Global_BeginRequest(Object sender, EventArgs e) +50
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving from local Vista host to Web Host - problems!Moving from local Vista host to Web Host - problems!


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