So you’ve set up yourself a nice farm of production, testing and acceptance SharePoint servers, and you want to build a new test server.
You make a backup through the Central Administration website, and on your soon to be testing server, you restore the backup.
And then you want to connect the restored Content database, only to discover that SharePoint claims that this database does not contain any sites… Oops? …
When you have rolled out your Microsoft Office Sharepoint Server or Windows Sharepoint Services together with Microsoft Search Server, you probably want to be able to search all sites through any search field on any site. But you still only see “This Site” as the only scope to select.
This is not fun.
If you’re like me, you sometimes play with SharePoint. In the last SharePoint Services 3.0 installation I noticed that the search function did not give back results, and I went out to scout what the problem was.
The Windows SharePoint Services Search is configured on the Central Administration website, Operations tab and Services on Server section. There, you can select which server’s services you want to see, and see their running state and if necessary stop them.
I stopped the Windows SharePoint Services Search services, and that was a Bad Idea.
Suppose you have just finished installing a SharePoint Services 3.0 installation in a multi-domain environment, and the installation should be available from a multiple other domains. Suppose you also configured a Web Application that links to http://mysite/.
In your own domain, this will work without a glitch. But not in the other domains!
