In a testing environment, a client had no issue in setting up a connection to a supported LDAP environment through User Profile Synchronization. In an identical copy of this environment, however, the client kept running into an error message displaying “Unable to process Create message”. This error is accompanied with an Event Log entry with the most important part “Retrieve schema failed”:
As a reminder for me, from http://vspug.com/wkkf/2007/05/09/changing-recipient-of-access-request-for-a-site-emails/
By default SharePoint 2007 automatically configures the access requests for a particular site to go to the person who created the site. This is not always what you want and you may find yourself receiving “Access request for a site” emails for sites you setup, but don’t actually manage. You can change this by doing the following:
Change the Send all requests for access to the following e-mail address: to the proper address.
- Navigate to the site in question
- Navigate to People and Groups > Site Permissions > Settings > Access Requests
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? …
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. Windows SharePoint Services (WSS) does not have any features to really move sites, and so the advised way to move sites within and over WSS 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 WSS web farm goes somewhat like this:
stsadm.exe -o export -url http://mysharepoint/site/subsite -filename subsite.bak
Importing this site back into your WSS 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? …
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.