Unfortunately, like many programs, installing the Community Server 2007 in my remote hosting was not an easy task.  It was not because the software was buggy or the installation methods didn't work, but mostly it was because of my hosting compay GoDaddy.  GoDaddy offers Community Server 2.1 through their Metropolis community.  After playing with it for a while, I chose to buy the full version so I will not have any restrictions; here is when the trouble started.

Background

Before paying for the software, I tried out the older version of the Community Server 2.1.  This free version allowed me to pretty much do the same that 2007.  However, it had a restriction on the number of pictures that I can download, number of blogs, etc.  So finally, I paid my $99 and got my own license key; time to upgrade to 2007.

Installation of 2007

First, I tried the upgrade option, when that didn't work, I tried to delete it and start a complete installation.  After spending too many days of calling Community Server and GoDaddy, finally gave up because I was not able to install it.  So I decided to re-install the version 2.1 again.  After so many little issues, I was able to make it to work (so far). 

Upgrading the Database

There are few things that GoDaddy won't let you do:  One, you cannot use your own copy of SQL Server 2005 to run the upgrade script.  They don't allow you to remote to their SQL servers.  So you will use their version of the query analyzer online.  Unfortunately, it works different.  If you open up the upgrade script, you will find out that the script is 29,000+ lines of code; that's a hint that for a web program, it is going to time out.  So you will need to run the script in pieces.  Secondly, the online query analyzer didn't like comments, print statements, and long string values (with this hint, I just saved you one day of debugging).  Open up your text editor to replace any comments (--) with blanks.  Next, delete all the Print statements; this include all the "else" statements that only has print statements.  Lastly, check for string values that are too long.  This took me a while, because you will notice that the online query analyzer does not have horizontal scroll bars, so long strings will be broken into the next line and so you will have unclosed string values.  For long string values, break them up and 2 (or 3) strings and concatenate them with pluses (+).  One more last thing, if you are upgrading the database then commented out the sample and static data that the script has.  Close to the end of the script, you will have records that are being inserted to some tables, comment these records out.  I did some spot checking and it seems that the these tables already the records.  Done, if you are lucky and didn't delete too much, you should have a working script.  I was able to copy-and-paste about 5000 lines of code and run them in parts.

Upgrading the Web Files

These is the easy part, just replace the web files from the Web installation.  Copy the files using the current structure and the proper directories will get replaced/added the files.

Running the Installer

I found different instructions on how to run the installer.  The Community Server documentations shows that you will need to add the connection information to the Web.config after you finish with the installer and that's not true.  Apparently the installer will do it for you.  But let me back up a little; when running the installer, I noticed that I didn't have any databases showing on the dropdown after you entered your information (Server host, login and password).  I open up the Default.aspx file on the installer folder and noticed that it is trying to go to the "Master" database and get all the available databases.  GoDaddy will not let you do that.  So you will need to modify the page's code.  Since I am upgrading, that means that you already know the database name.  So make the following changes:

•  On function Validate_SelectDb_ListDatabases:  Comment out the calling of the databases and just add the name of your database to the list  For example: db_name_list.Items.Add( "JURA00235" );
• On functions IsSchemaExisting and IsForumsSchemaExisting: Make sure to override the value of variable returnValue to false.

Since you are upgrading and already ran the SQL query for the upgrade, you don't want override your sql server work.  Now you are ready to run the installer successfully.

 Done, your Community Server should work now.  Good Luck.