DavidWSnow wrote ...I had a running site hosted at Godaddy that was running 4.3.5. I did a couple of localhost installs on my test system and decided that it was time to update GoDaddy, becassue I was about to take that site live.
I maintiained the same directory protections on my /dnn directory as before, created a fresh database, ftp'ed up the install kit with the release.config file renames as web.config and edited for the correct connection string(s). I seem to get one of three errors when I try the install:
- The yellow screen of death - telling me that I should have a custom error page. BTW - does anyone have one of those?
- A black and white error that the assembly version of the database doesn't match the real one, and therefore no database access.
- The web browser spins FOREVER displaying "connecting" but never connects nor does it timeout. I waited an HOUR.
I went back and reinstalled the Install Kit for 4.3.5 and all worked well.
Anybody got an idea, or seen similar behavour.
I just now looked at the "upgrade" instructions and they don't seem to address how one upgrades from 4.2.5 to 4.3.6 but focus on the 3.0 to 4.0 upgrade. Anybody got a pointer to a simple upgrade.
Regards,
/dave snow
Dave,
I hope I can offer some help. I'm in the same boat as you are, in terms of goals. I operate two GoDaddy shared-hosting sites which are using DNN 4.0.2 . I want to remove the current install structure (which was put in my place by GoDaddy at the time of their creation) and in their spot, put my own-handed install of 4.3.5. In my case, these sites have been live for months so I am moving cautiously here on my local Cassini Web Server as a practice field.
A few things from your comments:
First, it is version 4.3.6 which is causing the one particular error where the web browser spins forever. It is caused by a bug in 4.3.6. It has a fix which is detailed at the URL after this sentence. Nonetheless, because of this, personally I am going to stick with a 4.3.5 install during my practice runs. Bug fix is described and corrected here: ( http://tinyurl.com/va3vt ) and (( http://tinyurl.com/yj8c7p )).
Second, after you do get DNN installed on GoDaddy (whether you use your own-handed install, or if you use their auto-installer for DNN 4.3.5 thing) you can create your own custom error messages, and in fact change anything you want about your install, using Web Explorer Lite. You can deploy an ASP.NET 2.0 application called Web Explorer Lite to your root user folder on GoDaddy. Then, you can use Web Explorer Lite to get to any and all of your root DNN installation folders and files, remove them, replace them, etc. Web Explorer Lite is pretty much like Windows Explorer, it simply let's you navigate your DNN root folders, which you otherwise cannot reach. It's an FTP-like client with a nice graphical interface. If you need help deploying Web Explorer Lite on your website, just ask. You can also ask me directly on my forums at commonmancomputing. c o m . *Note: This refers to DNN files, not database tables.
Third, your database error. Just to be sure (although you likely know this) if you install DNN using their auto installer for DNN, your real database is located on a virtual server not accessible by you. Therefore any database you make through the GoDaddy Control Panel, won't really be the database which is in use by DNN in this scenario.
Four, I have an extra "empty" shared hosting (paid, full featured, Deluxe hosting plan) site with GoDaddy that we can mutually fiddle with if this would be beneficial to you. It seems our goals are essentially the same, except that I would want to play with 4.3.6 and include its bug fixes as we go.
Thanks,
Travis commonmancomputing. c o m