MOSS: Render Failed Error for Custom View

I recently created a custom view in MOSS with a column using the Checkbox (Yes/No) data type. The view was filtering on that column (is equal to Yes).

I later changed the data type to Choice and provided Yes and No values. The view failed to render and displayed the error:



I modified the view (the filter was changed to "is equal to 1") to change the filter to Yes again and that fixed the issue.

I've never seen the render error before, so here you have it.

Building My MOSS Farm: Part 1

Few months ago, I bought a serious Intel Core 2 Quad (4 cores, that is) with 2.83Ghz and 8GB of ram. It's a 64 bit machine with 120GB of 10,000 rpm for the C drive (makes all the difference, believe me) and additional 500GB drive. The plan? Not a nuclear bomb, but to build out a 4-server MOSS farm.

In these series, I'll chronicle the build and configuration process.

1) I will be using my MSDN subscription for the software.
2) I decided on installing Windows 2003 Enterprise Edition R2 (64 bit, of course).
3) I am going with SQL Server 2008 Enterprise edition.
4) MOSS 2007 SP1 + February update.
5) I will be using VMWare to host my farm. So why not Virtual PC 2007?

Reason 1: Although it's free, I was so disappointed that 64-bit guest machines are not supported. Are you kidding me?!
Reason 2: VMWare just rocks. You'll see why soon.

Approach

1) Build a base machine with all updates and patches + .NET framework 3.5 SP1.
2) Clone this machine for the 4 servers in the farm.

MOSS Farm

Server 1: App server, i.e central administration + indexing role
Server 2: Database server
Server 3: Web server 1 + query role
Server 4: Web server 2 + query role

To be continued...

Search request was unable to connect to the Search Service

The search request was unable to connect to the Search Service.

Resolution: make sure the correct ports are open between server if you have your index and query servers on different boxes within your MOSS farm. Also, the correct roles need to be selected for each of these servers in the central administration.

MCMS Migration to MOSS: Telerik RadEditor Content Appears as Decoded HTML

If you use RadEditor from Telerik in MCMS, and you migrated your content to MOSS, you will notice that your HTML tags are stored in a decoded format. "~LT~" and "~GT~" are especially noticeable as they represent the "<" and ">" characters.

Some have suggested running a script against the MCMS database to resolve the problem but I highly advise you against this approach; your support agreement with Microsoft would become void.

An alternative would be to format the custom fields' content on the MOSS site after the migration. Gary Lapointe provides sample code for custom commands to use with the STSADM tool to do just that.

A word of caution: Gary uses regular expressions, and so you need to be aware of some of nuances, such as escaping the "~" with "\".

MOSS 2007 Enterprise Search: Metadata Property Mappings

When adding a new Managed Property under Search Settings in a Shared Service Provider (SSP), you may encounter the ambiguous error:

The settings could not be saved because of an internal error: name

This could occur if you have spaces or underscores in the name. Remove all spaces and you should be good to go!