Travis,

So far so good....although it's only been a day...haha.   One thing I should clarify is that I don't have both 4.3.5 and 4.3.6 installed at the same time.  I never tried that and don't know whether or not you can?   Although they would reside in 2 different directories, my first concerns/questions would be the database.  If each version were to create their own set of tables, sprocs, views, etc..then I could see it possibly working.  However with a host like Godaddy (or any other ones that work MS SQL the same way) where you only get 1 database  (unlimited tables, etc I think, but not sure) I think it would cause problems.  If you  have access to 2 different databases, with 2 different log in credentials that you could pass in the web.config file, then I'd bet you could probably run both versions.  This is just a wild guess though on my part.  I've only been messing with this software over the holiday weekend so I'm definitely NEW to this!

At the moment, I'm not too concerned with backing up the dnn installation.....yet.   I have a feeling I'll mess with 4.3.6 for a few days..then dump it and try 4.3.5 again for a few days and see what I like/don't like about each, etc.  One thing I have noticed in 4.3.6 though is that sometimes it seems to just "hang"....and you have to wait for the next screen to come up, for an update to take place, etc.   I know the issue is not with godaddy's site in general, because while the system is sitting there spinning its wheels, I can still go over to godaddy and mess with my site, access it, change stuff, etc.  So I think the problem is more in 4.3.6, but who knows.  Do earlier versions have issues like this?

So far I noticed one error with a user account.  I had created a user and then at some point down the road, I tried to update his profile, etc....well this system just hung there for a bit...and I can't remember if I tried hitting the back button on my browser or what....but it somehow screwed up the record.  From that point on I couldn't even update or delete it, I kept getting an error message (although I did not write it down).  I ended up logging into the database through Godaddy's site and deleting it there.

I have not made a set of instructions, but to be honest, it's pretty straight forward (as strange as that may sound), and goes along with what I've read in other threads on this site...they were correct.   Basically what I did was:

1) Logged into godaddy's site and changed my .net to 2.0...waited a bit til the change took place....etc...
2) Created a directory (dnn, dnn35, dnn36, etc..etc..while I was tesing...lol) and gave it the 4 permissions (all but browse)...then waited a bit til the change took place....etc...
3) Unzipped the original installation zip file into a directory (dnn, dnn35, dnn36, etc) on my local  hard drive.
4) Renamed the web.config to orig-web.config.
5) Made a copy of Release.config and then renamed that copy to web.config.
6) Made the two changes to the SQL 2000 entries to reflect my database connection string starting with the "Server=" part up to the semi-colon at the end. (Server, database, uid,  pwd).
7) Comment out the original connection settings for SQL Express.

On 6 and 7 above, you have to watch the comment thingamabobs <-- and -->.  Make sure you scroll all the way to the right and see if there's one at the end, if it needs to be there, etc.

Mine looks like this (less the x'd out stuff)

  </configSections>
  <connectionStrings>
    <!-- Connection String for SQL Server 2005 Express
    <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />  -->
    <!-- Connection String for SQL Server 2000/2005  -->
    <add
      name="SiteSqlServer"
      connectionString="Server=whsql-v02.prod.mesa1.secureserver.net;Database=DB_xxxx;Uid=xxxx;Pwd=xxxx;"
      providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules  
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>  -->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules  -->
    <add key="SiteSqlServer" value="Server=whsql-v02.prod.mesa1.secureserver.net;Database=DB_xxxx;Uid=xxxx;Pwd=xxxx"/>
    <add key="InstallTemplate" value="DotNetNuke.install.config" />

I included the line above and the line below to show you where I started/stopped.


8) Changed the CustomErrors to Off........scroll down a bit and you'll find this.....

    </compilation>
    <!-- permits errors to be displayed for remote clients -->
    <customErrors mode="Off"/>
    <!-- Forms or Windows authentication -->
    <authentication mode="Forms">


9) I ftp'd the entire directory structure from my drive to godaddy's site (dnn to dnn, dnn35 to dnn35, etc)
10) pointed my browser to the dnn, dnn35, dnn36 (depending on which try this was...lol) directory...and waited for the install to begin.  It takes a couple minutes for it to start doing anything.


When I first started this thread I was having issues with errors and "re" starting the installation process.  After the failed attempts, I ended up ftp'ing the entire directory over to godaddy again and starting from scratch.   I probably could have done just the Install folder since that's where all the zips resided, but after doing it so many times, I said what the heck.

Other than the issue I had with the table named "Users".....the other problem was that since I already have some other tables and data in that database, I cannot just drop it and start over.   So I had to go and drop every view, stored procedure, and table relating to dnn.  That was a pain in the *** at first.  I tried using the "uninstall.sql" file or whatever it was called.  It said to find/replace the dbo owner and qualifers, etc...but it seemed even after doing that, there would always be 3 or 4 errors (missing tables, missing sprocs, etc) that would cause it to bomb out and not work.

What I ended up having to do was from godaddy's sql manager page, I brought up the tables...then highlighted everything....copied and pasted into excel.... used a few formulas such as (find, left, concatenate, etc) to create my own drop statements for everything that existed in MY database.  It was kind of a pain, but afterwards it worked pretty good.  The issues I had with that were 3 or 4 tables that had primary key/foreign key relationships that I had to go in and manually delete before dropping the table.  I could have (and should have just dropped those constraints too, since they were in the "uninstall" file, but I passed on it.   Anyways...that's how I had to go about getting rid of dnn from my database  unfortunately.  If your database is empty, you're good to go, since you can just delete the database, create a new one and go from there.

Ok, that's enough typing for now....lol   I'll keep you posted on how it goes.   Let me know if you find anything, good or bad.

Thanks,
James