Hi All,
I wonder if someone can help me...I have DNN 2.1.2 running at www.instantbi.com using MS Access.  I am going to upgrade to 3.0.13 and sql server.

I have created a subdirectory under www.instantbi.com called /dnn3013 and I have turned on 'web application' in this directory. When I type www.instanbi.com/dnn3013 to try to initialise the dnn 3013 database I get the following message...

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: Exception creating section handler.

Source Error:

Line 4: <configSections> Line 5: <sectionGroup name="dotnetnuke"> Line 6: <section name="data" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" /> Line 7: <section name="logging" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" /> Line 8: <section name="scheduling" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />

However, this is the config file for dnn2.1.2 not 3.0.13 ??  I don't know how it got back to the root directory for the site instead of staying at /dnn3013 directory.....

I'm trying to install it as a dub directory first so that I can do the rebuild of the site on the remote server and then just reload DNN 3.0.13 to the remote server and have my new site up with a minimum of disruption.

ANyone have any ideas what is happening?

Thanks

Hi All,
I've still been trying to get my site running underneath my current site just to be able to 'build in place'..

I had another idea...in the install guide it says:

Give the ASP.NET worker process the appropriate Security access to the folders of your

website. In Windows 2000/IIS5 this is the {Server}\ASPNET User Account, while in

Windows 2003/IIS6 this is the NT AUTHORITY\NETWORK SERVICE User Account. To

enable this use File Explorer to locate the physical folder you used in (1) above. Rightclick

on the folder, and select “Properties”, and choose the Security Tab. The required

permissions are as follows:

• Root (and all child folders) – Read Access

• Root – Write Access (and Modify Access if expecting to create child portals)

However, I have no access to the file manager on my remote web server...I have just set the directory as a 'web application'.....could this be the problem?

I'm thinking the problem is something like DNN goes back up to the root directory of the site that is being passed in as the site to install in and is finding the web.config file there...

Any and all ideas welcome....I'm not keep to remove my current web site while I re-write it in DNN 3...

Thanks in Advance...

First, I would wait until 3.1 comes out.. that might eliminate a couple of upgrade problems that others have experienced upgrading to 3.0.13.

I would suggest setting up a test server on your local machine that is identical to your 2.0.12 site. I don't think you can get around the root web.config problem. Plus, installing DNN 3.0.13 on a sub directory probably isn't the same as installing it in the root directory. Then go through the proper upgrade process (RTFM) on your test server. If that works, make one more backup of the production server and upload the test server.

Hi Alex,
thanks for this.......

On upgrading.....I initially installed on MS Access (being as newbie and not knowing any better) and there is no good 'upgrade path' from access to sql server as far as I can find out. So I am just going to rebuild my site in 3.0.13.......the next problem is my host provider (discountasp.net) does not provide the ability for me to backup->restore an sql server database from my laptop to the host.....that's why I was trying to put 3.0.13 underneath the root directory. So I can edit the web site in place on the host server while not removing my current site.....

I believe you are correct in thinking DNN is just not going to go into a sub directory underneath another older DNN....

I shall have to find another way of doing this....all ideas welcome... :-)  

The problem is that you are installing a copy of DNN in a subdirectory of an existing DNN directory.  ASP.Net cascades web.config files and will try to use the web.config in the root and the web.config in the sub-directory.  If the setting is in both file the sub-directory setting is used, but if the setting is only in the root it will also use those settings.  Try installing this to a directory that is not a sib-directory of an existing DNN site.

Hi smehaffe,
thanks for the tip....I didn't know that.....(I'm pretty new to .net).

I don't have another site on my host I can use, unfortunately. (I installed 3013 on my laptop 'first time' no problems.....) 

I tried building a DNN on SQL Server on one laptop database and moving it to another via DTS but it seems that the constraints, sequence numbers, GUIDs etc do not transfer so well......maybe there is just something I don't know about moving a DNN SQL Server database from one place to another.....discountasp.net are reluctant to do a restore of the database and charge for that service...but that doesn't help anyway because I am sharing the database with my forums and a product I am developing.......maybe I should just try to rename the web.config in the root directory while I try the install...?? I'll let you know if this works...

Hi All,
I thought it worth sharing my findings.....
1.  I created my new portal on my laptop, just the 'bare bones' and sent it to discountasp.net using SQL Server EM DTS. It seems to send it 'first time' ok in 3.0.13...??? Perhaps it is only updating the target database it cannot do??? I have not played with 3.0.13 databases before...

2. In my root directory I renamed web.config to web.config.sav (which breaks the app in the root directory of course)

3. I edited the portal alias table to add www.instantbi.com/dnn3013 as an alias.

4. I then entered www.instantbi.com/dnn3013 in my browser and horray, it came right up!!!!

5. If I rename the web.config in the root directory back to web.config the 3013 version does crash and burn with config problems.

So, now, at least, I can just renamed web.config to web.config.sav effectively taking my site 'offline' while I edit the new 3.0.13 version underneath....I am (of course) assuming that when the time comes to actually do the 'upgrade' I will be able to replace my 2.1.2. directories with 3.0.13 dircetories and it should work...he says hopefully....

So, if anyone is looking at doing an upgrade like this.....these steps work...it does make me wonder though that if I did all my editting on my laptop might the initial transfer from laptop to hosting database work again if I deleted all the stored procedures, constrtaints, tables etc??? I'd be interested to know....I don't want to take the chance myself as it will take so long to build the site and try it out!!!

Hope this helps someone else.. ;-)