If you’re toying around with SharePoint and want to move a site to another location, you might run into what I’ve run into: broken Lookup field links.
SharePoint Server 2003 and Windows SharePoint Services 3.0 feature 20 server templates you can integrate within your SharePoint infrastructure with the command line utility stsadm.exe.
This command line utility also allows you to move sites. SharePoint does not have any features to really move sites, and so the advised way to move sites within and over SharePoint web farms is to use stsadm.exe export and import operations to export a given site, and import it on another location.
For instance, exporting a site from your SharePoint web farm goes somewhat like this:
stsadm.exe -o export -url http://mysharepoint/site/subsite -filename subsite.bak
Importing this site back into your SharePoint web farm goes like this:
stsadm.exe -o import-url http://mysharepoint/subsite -filename subsite.bak
You now have moved your subsite to the root site. Or did you? Continue reading ‘Moving stuff breaks stuff’
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.
Continue reading ‘Search Scopes not visible in Search dropdown’
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.
Continue reading ‘Stopped the WSS Search? D’oh!’
If you ever run into one of those messages “The current time on the computer and the current time on the network are different” when trying to log on, you will probably try to log on on the domain controller and try to assess in which amount the time got desynchronised in your domain or between domains in your forrest. As you might know, Active Directory is picky about time, because the Kerberos authentication does not accept timestamps that differ more than 5 minutes between the machine that is trying to host the login and the domain controller.
Continue reading ‘Be mindful of the Current Time’
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!
Continue reading ‘SharePoint redirects, DNS confused’
