How to upgrade from 2.1.1 to 2.1.2?
I have 2.1.1 wokring fine and I have spent a lot of time making it just right but I want to make sure I have the latest & greatest so I am trying to get 2.1.2 to work so I can upgrade.
When I try to set-up 2.1.2 I get a few errors such as:
Could Not Load Skin: ~/Portals/_default/Skins/_default/admin.ascx Error: C:\WINDOWS\Microsoft.NET\Framework\v2.0.40607\Temporary ASP.NET Files\dnn212\295dc47c\1861dacc\3z6nxty1.0.vb(159): error BC30560: 'admin_ascx' is ambiguous in the namespace 'ASP'.
Is there a simple way to upgrade from 2.1.1 to 2.1.2?
Iff you have not made any cha...Version 2.1.1 to 2.1.2 upgrade
I upgraded from 2.1.1 to 2.1.2 last night.
In case anybody wants it, I created a ZIP file containing the changed RUNTIME files - all you need to do is extract and ftp over the top of your 2.1.1 install - assuming you've NOT MODIFIED anything yourself... ;)
Get the ZIP file here.
Hope someone finds it helpful.
joelblogs.co.uk...Never done upgrade before. Have a 2.1.2 site w/many custom (purchased) modules, some of which are no longer supported. Don't see *any* info in 3.1 install docs for 2.1.2 upgrade?
I'm about to try something very scary, and I've spent the last 5 or so
hours reading DNN 3.1 docs and doing searches here (sure which the
search worked better, like allowed sort by date??). Anyway, I
don't see *any* info on updating a 2.1.2 site to a 3.1 site. The
only examples all have machine key stuff and other stuff that's not an
issue (or is it?) w/2.1.2
Here's the situation:
1 I have localhost access to the site via remote desktop
2. I have disconnected backed up data and log files and reconnected
3. I have made a copy of the virtual folder.
No...Having problems loging in after upgrading from 2.1.2 to 3.1.1
Ok i have done the upgrade from 2.1.2 to 3.1.1 the installer did its magic and i got the click here to access your portal/site which means the upgrade went well... but now i get this error on my homepage
A critical error has occurred.Multiple controls with the same ID 'ctr' were found. FindControl requires that controls have unique IDs.Can some one help me out and explain what this means???? Has any one seen that before ??? ... The other thing i cannot log into the site either ... when i login it takes me back to the home page and i dont have the control panel or anythin...Bug DNN 3.1.1 Upgrade from 2.1.2 -> 3.1.0 ->
Somewhere along the process, (I missed when) a portal upgrade created a problem with portal creation. The site is created fine, but the password for the admin is never correct. I have to use host to correct it. Anyone faced this ?Do you know the truth when you hear it?
are you using the same hash keys in your web.config? this got me one time-DarrenNeese.com-DNN ROCKS!-DeveloperSchool.com
Thanks, this helped me narrow it down and realize it was possibly the upgrade from DNN2 to DNN 3. Since there are no hash keys in DNN2 because it uses an encryption key, how did you solve it?Do you know ...Upgrade from VirtualBox 2.1.0 to 2.1.2 vboxdrv issue
Hey everybody, I've already posted on the Vbox forums, but I want to
post here to diversify. Here's the situation:
OpenSuse 11.1 host. Vbox 2.1.0 was installed from binary. Upgraded to
2.1.2 earlier today (tried several times using rpm command-line and
Yast). Yast doesn't report errors, but rpm on cli does. Error on install
is "Stopping VirtualBox kernel module failed (Cannot unload module
vboxnetflt: no symbol version for SUPDrvLinuxIDC
vboxnetflt: Unknown symbol SUPDrvLinuxIDC
VirtualBox boots, but if I attempt to start a VM I...DNN 2.1.2 to 3.1.2 upgrade, skin probs
OK, we'll I've had a good read around here, and I've read Charles great install doc. But I'm still stuck.In fact I've had to restore my old db and files - and have got back to 2.1.2.My problem is that upon upgrading, I get a light blue 'skin'? appearance on the all the modules. The 2.1.2 sites (six of them) do not have that "appearance" - and that's the way I'd like to keep it. I have tried 'resetting' the skins (in that Admin section they all show as 'not installed' (or whatever it is)). It doesn't seem to help. I get several 'container file not found' type mes...Help!!! After upgrading DNN 2.1.2 to 3.1.1 FTB Error
I keep on getting this error after upgrading a DNN 2.1.2 to DNN 3.1.1 (Windows 2k with SQL Server 2000). The Text/HTML module when in edit comes up with error as follws;
Basic Text Box
Rich Text Editor
An error has occurred.DotNetNuke.Services.Exceptions.ModuleLoadException: The data at the root level is invalid. Line 1, position 1. ---> System.Xml.XmlException: The data at the root level is invalid. Line 1, position 1. at System.Xml.XmlTextReader.ParseRoot() at System.Xml.XmlTextReader.Read() at Sys...iManager 1.2.2 to 2.0.2 Upgrade
I've been running GW 6.5 WebAccess on the following system configuration:
Netware 6.0 SP4
eDirectory 8.7.3 SP2 IR
JVM 1.4.1 SP6
Novell Enterprise Web Server
Yesterday I made the following change:
Upgraded iManager to v2.0.2 and Tomcat to v4.0.
This change broke GW WebAccess.
I'm getting the following error when I try to get into GW WebAccess.
It appears to pop up as it tries to bring up the login page.
This server has encountered an internal error which prevents it from
fulfilling you...Auto Upgrade from 2.1.2 w/ Access to 3.1.1 w/ SQL?
Just wondering if the install script and the Auto Upgrade of 3.1 is able to upgrade the Access database of a DNN 2.1.2 local site to a SQL database for 3.1 - and if so, do I need to create a SQL database first? I would assume so since one must create a SQL database for a clean install.Or are users of DNN 2.1.2 using the Access dataprovider hosed on the upgrade to 3.1? Thanks for any help.
It seems there isn't a way to "upgrade" from an Access 2.1.2 database into the 3.1 SQL database. That being said.... Anyone know of a way to port the old Access database into some ...Upgrade 1.0.10 to 2.1.2
I am preparing to upgrade a site from DNN 1.0.10 to 2.1.2
The site is hosted on a remote server using a SQL database and when I originally installed the 1.0.10 version I did a search/replace on all of the database install scripts - removing [dbo]. and dbo. This seemed to be the only way that DNN would install smoothly.
When I view the remote database using enterprise manager it seems that the tables and stored procedures are owned by either my user 'pkoanui' or 'dbo'
I foresee this being a problem when upgrading to 2.1.2. I have since performed fresh installs of other DNN 2.1.2 sit...Upgrading from 2.1.2 to 3.1.00
I am upgrading a DNN site from version 2.1.2 to 3.1.00. Now, I did read the "DotNetNuke Installation Guide.doc" ! (Ya Sure, You Betcha!) And, what I get is the error "The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist." no matter what I do.In the What went wrong? Section of the 3.1 Docs you find a siminlar error message "Could not find stored procedure 'dbo.GetPortals' " and it talks about issues with the objectqualifier and dnn.config ! I've never used the objectqualifier previously, thus the value is set to a blank string and the dnn.config says...Upgrading from 1.0.8 to 2.1.2
Im upgrading a friends site who hosts 3 parent portals.
I made a quick backup and gave this a go (ie putting overwriting the old source)
however it did not seem to recognise the old information
I will give it another go this weekend and just wondered if you guys have any tips or tricks to look out for.
I've done several upgrades from 1.x versions to 2.1.2, and the main thing I run into are third party modules crashing. The way I've gone about it is to copy the database, change the web.config to point to the database, and drag and drop...Upgrade 2.1.2 to 3.1 PLAN
Just wanted to throw my plan out there for upgrade. Allow smarter folks to tell me where I will run into trouble. I have a 2.1.2 site on a rented server. I have a 2.1.2 development site using Access on my local machine. I have recently installed and configured SQL Server 2000 locally and a DNN 3.1 local website which works fine. I also have custom modules I've written (poorly but they work) and many third party modules on my server side production site. My plan to upgrade the server site is:1. Update my custom modules to work with DNN3 (by testing th...