Many of the Windows-based websites in the Tux Reports Network are based on Community Server product developed by Teligent. Beta 2 of the Community Server 2.0 was released on Friday December 16, 2005. Two files are available for download, a new Windows-based installer and a Web-based installer. The installation on the Windows 2003 server involved running a Beta 1 to Beta 2 upgrade script available in the Web-based installer zip file. This script is run through the Query Analyzer by opening the file, checking the database name, and pressing F5.
Unfortunately, the upgrade script failed with numerous messages and the websites no longer loaded. After eight hours, the basics of the websites were back online. However, many features were tossing errors, including our favorite feature of blog posting with ink was not working. The purpose of this post is to explain how the upgraded database was synchronized with a new installation database in order to fix the failing features, except ink (Ink is fixed in a new build to be provided by Teligent sometime soon).
Step One: Backup Database and Files
Make a backup of your upgraded database (db1). This database is named CommunityServer by default. If you have access to Enterprise Manager, right click on the database name | All Tasks | Backup Database. Add the date to the name of the backup file so that you can distinguish your backup file. For example, name the backup CommunityServer backup 12292005.
Copy all of the CS files you presently use to a backup location.
Step Two: Prepare New Database
Use the .msi download file to create a fresh install and new database with a different name from CommunityServer. I used the name CommunityServerBeta2, CommunityServerNEW, etc. Verify this new installation works. Double check Enterprise Manager and check that you have one good database (db2) and the upgraded database (db1).
Step Three: Web.config
Edit your web.config file so that the connection string points to the original database (db1). You may need to change the Trusted_Connection to no.
Step Four: Synchronize
Use SQL Compare from Red Gate to compare the two databases, db1 and db2. Uncheck everything that is different (use the blank checkbox in the toolbar) and pay attention to the direction of the arrows. Check one box at a time and sync the databases so that db1 is fixed. Watch the screens to make sure you have the correct database being synch’d. On TRN, there were seven tables and 14 stored procedures out of synch.
Viola. You have a working site. Now, we are waiting for the new build with the ink blog posting fixed. This fix was completed yesterday. Until this new build is installed on TRN everyone is welcome to use the forums to post in ink.
Hope this helps anyone else having trouble. Best of luck.