This is going to be fun. I’ll start with the latest and start working my way back through a long list of failures. Some I have fixes for and some I have workarounds for while others are a mystery.
Latest: “can’t fetch an item that has been previously fetched by another user”
Cause: We had changed the default home page assignment for a site to another page that was unpublished.
Fix: We put the home page for the site back to the previously published page. I’ve had similar failures around renaming the default home page that resulted in us having to delete the site and recreate in another location. I don’t think this is one of those scenarios but wasn’t willing to break anything else today.
I will update you on what happens when the new page gets published and assigned as the new default home page.
I’ll have to dig through my deployment failure notes to confirm the error we were getting when renaming the default home page.
Tags: MOSS, SharePoint, TJ
The content deployment failure that occurs when we were renaming some of the default home pages was: the page already exists.
Something to do with the GUID being the same but the name was different when compared to the destination site. We tried putting the original back and no go. We tried deleting the site on the source and destination farms and then starting with the defaults. Still it failed.
We had to recreate in another arm of the tree to get it to work. Who doesn’t love Content Deployment?