 |
|
|
Joined: 11/24/2006
Posts: 4
|
|
|
Hi guys,
I've been having major problems (various errors at different stages of the install) trying to get 4.3.6 (and now....4.3.5) on Godaddy. I've read through numerous posts regarding Godaddy's issues with directory permissions, web.config modifications, etc...etc. I appreciate all the help everyone's given. One thing I have not been able to find though, is how do you go about getting the program to reinstall? It seems once I've failed an installation, I cannot install again, it just comes up with the same error again (lately it's been the server.createobject) ones. Is there one config file with one parameter that tells the program it's already been installed or to install again, etc?
So far, to reinstall, I had to turn back .net to 1.1, delete my directories, enable .net 2.0, and then recreate my directory (dnn) to get it to try again.
Am I missing a simple shortcut here?
Thanks in advance,
James
|
| |
|
|
 | |
|
|
Joined: 5/24/2006
Posts: 91
|
|
|
Hi, James --
A couple of thoughts.
To reinstall, make sure you have copied over the "\Install" branch of the files found within the DotNetNuke_4.3.5_Install.zip , into the \Install of your root directory files after you have had a failed install attempt.
You can conduct a liitle test to see if this is the issue:
(1) Take a clean, fresh copy of DotNetNuke_4.3.5_Install.zip and extract (unzip) it into any folder on your hard drive.
(2) Right click on its \Install folder, once unzipped. Take note of Properties. It will probably be >350 KB in size.
(3) Do an install attempt on your host. (assume failure)
(4) Navigate to the same \Install folder on your root directory structure.
(5) You will find that after failure it is only about 45 KB. If you find this to be the case, then you must copy the entire \Install folder from that freshly unzipped copy of install.zip, into over and on top of the \Install on your dnn directory, to return that folder to size of about 350 KB.
(6) Then the next time you invoke the Install.aspx you should get a fresh install start.
Just one more thing. I've been using GoDaddy shared hosting for two DNN sites for several months, [b]and both sites were installed using the Value Applications auto-install option.[/b] I've figured out a way to do everything that I would want to do at other less-restrictive hosts, and in fact I have decided that it is easier than attempting to manually install DNN on GoDaddy in the first place. This would include: access to all my root installation directory files; upload/download/remotely alter those installation directory files; accessing the database; backing up the database; query the database, and, just today (yes!) a maneuver to copy the entire site, database and portal files and all, and recreate the live site in its entirety on my home computer web server. And then make changes to the site "offline" on my home web server, then upload those changes at once into my live, functional GoDaddy site. I am going to start making instructional web pages at my commonmancomputing website explaining how to do all of these things. (The set of instructions will work on any hosting provider.)
Thanks,
Travis
|
| |
|
|
| |
|
|
Joined: 11/24/2006
Posts: 4
|
|
|
Travis,
Thanks for the reply. Well I guess I'm already confused about something on Step 2. After I unzip the DotNetNuke_4.3.5_Install.zip and extract everything (am I supposed to extract all files???)....when I check the properties of the "Install" folder, it contains 41 files and it's something like 2.2 megabytes.
The Intall\Module directory has a number of zips in it which are the majority of the 2.2 megabytes.
Am I missing something here?
James
|
| |
|
|
| |
|
|
Joined: 5/24/2006
Posts: 91
|
|
|
jja28 wrote . . .
After I unzip the DotNetNuke_4.3.5_Install.zip and extract everything (am I supposed to extract all files???)....when I check the properties of the "Install" folder, it contains 41 files and it's something like 2.2 megabytes.
The Intall\Module directory has a number of zips in it which are the majority of the 2.2 megabytes.
James, Looks like you have step 1 correct. The \Install subfolder, of the DotNetNuke_4.3.5_Install.zip is a folder of size 2.21 MB. It is that entire folder, which you need to copy over, to the root directory of your DNN installation after a failed attempt to install. In other words, you will be copying the \Install (2.21 MB) onto the \Install of your GoDaddy root directory, or wherever the \Install folder appears on your FTP GoDaddy. To confirm this, I installed DNN 4.3.5 on an empty GoDaddy shared hosting site that I happen to have available. After installation (or after a failed installation) the \Install folder is written over, and now contains only 37.66 KB. So you'll need to copy over as described above, thus returning the \Install folder at your GoDaddy root directory to a folder of size 2.21 MB. Then you'll be able to reinstall attempt without needing to denominate down to ASP 1.1 and back up to ASP 2.0. Thanks, Travis
|
| |
|
|
| |
|
|
Joined: 11/24/2006
Posts: 4
|
|
|
Travis,
Thanks for all the help. I've just about got it. I've been able to get both 4.3.5 and 4.3.6 going (both with a couple of small hickups....but nonetheless...they both work).
My biggest problem from what I gather is that during the install process I would get an error at the installation of the SQLDataProvider (step 3 or 4 in the install process). It seems after that, I would end up getting about 10 errors overall and a failed install. Well after going through the DotNetNuke.Schema.log file.....I found this:
"System.Data.SqlClient.SqlException: Invalid column name 'IsSuperUser'.
Invalid column name 'IsSuperUser'."
I checked the tables and it was there, along with the column and all, so I wasn't sure why it was bombing out. Finally it hit me... I have a few other tables in my Godaddy database for another app, and one of them is called "Users"...When dnn installs......it creates another table called "Users". Granted they both have different owners. However, during the above step, when the query is made, my old table is being queried so the columns don't match up...thus the error. I didn't need my old table right (plus it's small, so easy to redo), so I deleted it. Sure as ****, the next install attempt of dnn went through....with only 1 error.
That came at the upgrade to 3.2.3. I get this:
"System.Data.SqlClient.SqlException: There is already an object named 'GetProfilePropertyDefinitionID' in the database."
During that step, it never checks to see if that function already exists, so it tries creating another one (by the same name)..and it would error. Anyays.....it goes through the rest of the upgrades.....3.2.4.....3.2.5.....up to 4.3.5 w/o any more errors. Is it same to assume that if it gets through the rest of them that my install is OK? I would think so, but figured I'd ask anyways.
Finally, I see what you mean about the Install directory and what is is after the install attempt. At first I didn't get what you meant by that, but after looking more carefully, I understood.
Thanks again for all the help,
James
|
| |
|
|
| |