My IT Experiences

We had an issue with our Index server running out of disk space. The server was old and didn't have slots available to add more storage. The approach I took had a disadvantage that I had to do a Full Crawl again. Here are the steps I followed: 1. Setup MOSS server with all pre-requisites; do not add server to farm Note: It is important not to install .NET Framework 3.5 SP1 on this server, please read my previous blog post for more details. It can be installed after setting up search. 2. Reset all crawled content from Central Admin. We may choose to remove the existing Index server from farm if required 3. Run PS Config wizard on new Index server and add the server to farm. If you have done a complete installation of MOSS the Web Application service and Incoming Email service would have started. Before configuring search we may choose to stop these services. 3. Start search service from Services on Server page of Central Admin - Operations and do the configuration. 4. Navigate to S

While trying to configure Search Settings in my new Index Server, I received this error when I clicked "Search Settings" from SSP: In my farm I was planning to run both Index and Query services on same server. I did some research and found that this could be because of corrupted SSL for the Office Web service. The reason it seems to be .NET Framework 3.5 SP1 !! Yes it seems if we enable search service or configure Index server on a box which has .NET Framework 3.5 SP1 the SSL of the Office web service in IIS would go corrupted. I had a similar situation; I was replacing the Index server in my MOSS farm version 12.0.0.6219 I brought up this new server with same OS and framework patch level as the existing index server. That was a mistake because my existing Index server was setup in 2008 and that time there was no .NET Framework 3.5 that time. It got installed later during a patching window. But in my case when I made the patch level same on my new server I installed all frame