Archives | May 2009

One would think that SharePoint would prevent you from loading up a SharePoint backup on a new domain with conflicting SIDs and usernames, but it actually allows you to do so without too much grief. I recently had to do this for a client who was having serious problems with WSS search and after a few trials and tribulations with STSADM I was able to get it up and running on my test virtual machine in a matter of minutes. Obviously my test VM isn't on the client's domain nor does it share and SIDs with the original hosting environment. Disclaimer!!!  The notes below are just that: notes that...

---

Problem When you open a page in SharePoint designer it complains that there is a conflict and that the placeholder for the master page is missing. Explanation This occurs when a user modifies a master page. The master page no longer contains that objects that the derived page expects, so SharePoint Designer gives an error (note that SharePoint will still recover gracefully from this, so some users simply switch between valid and invalid master pages instead of addressing the problem directly. Cause User used SharePoint designer to delete or comment out a placeholder. Resolution Use...

---

By far the most common mistake is to forget to specify the proper columns to tell SharePoint how to join the lists Looking up data on an empty column. If this happens make the lookup column required SharePoint Designer workflows are not portable between servers, lists, libraries, or farms. If you need to develop code in a dedicated development environment consider writing Visual Studio workflows. Problem You don't understand how to lookup data between lists in a SharePoint Designer workflow or you're not getting data when you lookup information between lists; usually you lookup...

---