Odd Search Results

Odd Search Results

This question is answered

I just upgraded and virtualized my 2003R2 environment to Windows Server 2008 R2.  I then contacted Telligent to upgrade my existing CS Version 3.0.20611.960 and was given the following files:

  • CS2007.1_3.1.20917.1142.web.zip
  • CS_2007.1_SP2.zip

I setup a webserver virtual machine (WEB) and a sql server virtual machine (SQL).  I then took a backup of my existing database and restored it on the SQL VM.  I created a custom sql logon and gave it dbo permission to my database.  I then followed the instructions in the downloads above and ran the appropriate sql scripts, doing the 'web' script first and then the 'sp2' script second.

Next, I made a new website on the WEB VM from the web directory in the 'web' download from above.  I changed the app pool to classic and then copied all the 'sp2' files over top of the existing files.  I then merged my original files (configs, themes, photos, blog files etc) using WinMerge and everything works fine except for searching.

If I search for anything longer than 2 characters I get:

Sorry, we were unable to find any results using your search terms. Please change your search terms and try again.

If I search for '*' (just an asterisk) I get what looks like all results, many many pages.  If I search for 'a' I get what looks like all results plus all a's are highlighted.

I checked the CS logs from the admin menu and the event viewer on both machines and I'm not seeing any clues.  Anyone have any ideas?

Matt Williamson Bunker Hollow
Verified Answer
  • The upgrade instructions say to run the following scripts only if you're upgrading from .NET 1.1 to 2.0.

    • cs_ASPNET2_Membership_Schema_Update.sql
    • Reset_SearchIndexes.sql

    After trying everything else I decided to start over and try these scripts.  The first failed since I was already using .NET 2 and all the objects already existed, but the second script ran successfully.  Then, after starting the website and waiting 20 minutes for all the Jobs to run, searching worked again, woohoo!

    So, if you've upgraded/restored/moved your Community Server site and search isn't working, run the following SQL script and then wait 15 minutes for the search barrel jobs to kickoff and searching should work again!

    Truncate table dbo.cs_SearchBarrel
    Update dbo.cs_Posts set isIndexed = 0

    Matt Williamson Bunker Hollow
All Replies
  • The upgrade instructions say to run the following scripts only if you're upgrading from .NET 1.1 to 2.0.

    • cs_ASPNET2_Membership_Schema_Update.sql
    • Reset_SearchIndexes.sql

    After trying everything else I decided to start over and try these scripts.  The first failed since I was already using .NET 2 and all the objects already existed, but the second script ran successfully.  Then, after starting the website and waiting 20 minutes for all the Jobs to run, searching worked again, woohoo!

    So, if you've upgraded/restored/moved your Community Server site and search isn't working, run the following SQL script and then wait 15 minutes for the search barrel jobs to kickoff and searching should work again!

    Truncate table dbo.cs_SearchBarrel
    Update dbo.cs_Posts set isIndexed = 0

    Matt Williamson Bunker Hollow
  • This worked.

    Matt Williamson Bunker Hollow