Wednesday, November 25, 2009

MOSS Migration woes

I have been involved in a MOSS 2007 migration over the last few months. The migration has been from an externally hosted MOSS 2007 instance to an internally hosted virtualized MOSS 2007 instance. The original MOSS 2007 instance has the following 2 server configuration -

Single MOSS Server
  • Windows 2003 R2 SP2 (Enterprise Edition)
  • Intel Xeon CPU 5140 2.33 GHz 4 CPUs (8GB RAM)
  • WSS version - 12.0.0.6318 (SP1 + Cumulative Update)
SQL Server
  • Windows 2003 R2 SP2 (Enterprise Edition)
  • Intel Xeon CPU 5140 2.33 GHz 4 CPUs (8GB RAM)
  • SQL Server - MS SQL Server 2005 Standard Edition Build 9.00.2047.00

The new MOSS instance hosted internally has the following configuration -

MOSS WFE Servers (2)
  • Windows 2008 (Enterprise Edition) x64
  • VMWare VM (2GB RAM)
  • WSS version - 12.0.0.6318 (SP1 + Cumulative Update)
MOSS Index Servers
  • Windows 2008 (Enterprise Edition) x64
  • VMWare VM (2GB RAM)
  • WSS version - 12.0.0.6318 (SP1 + Cumulative Update)
SQL Server (Clustered for fail-over with 2 nodes)
  • Windows 2008 (Enterprise Edition) x64
  • VMWare VM (2GB RAM)
  • SQL Server - MS SQL Server 2005 Standard Edition Build 9.00.2047.00
The main content database and SSP database were backed up off the live site and copied over to the new DB server cluster. After MOSS 2007 was installed, the default content database was removed from MOSS and the migrated content database was attached through MOSS Central Admin. Next the SSP database was attached. A few modifications were required to the search settings etc as the new server was hosted (temporarily) on a different URL. A full crawl on the content sources were also obviously required. I also regenerated the audiences that were in use.

We encountered one particularly puzzling issue related to search. When a search is performed on the new site from a default search page, the search returns the expected results. However, if there are multiple pages of results, attempting to go to another page in the result set brings back the following error -
"Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information."

Also, other static searches done through a URL querystring also fail if the IsDocument property or v=date settings are used.
at

1 comment:

  1. @binarybrewery3:10 PM

    Have you all considered dumping the index and re-indexing the results keeping the settings in place (i.e. keeping the content sources, scopes, etc.)?

    ReplyDelete