They can start with this little chestnut which no one else has ever heard of. It affects site membership links, profile updates and Jed knows what else.
[cid:[email protected]] ProfSynch: Exception attempting to enumerate site f9ad433c-0f15-4dce-b350-b795d2d31913 for ContentDB 1326e9df-61fd-4e10-924f-9b48e0558d35: Microsoft.Office.Server.UserProfiles.ProfileSynchronizationInternalException: ProfSynch: The site with ID f9ad433c-0f15-4dce-b350-b795d2d31913 cannot be synchronized due to an unprovisioned root web. at Microsoft.Office.Server.UserProfiles.SiteSynchronizerCollection.GetSynchInfoForSite(SqlDataReader dr, SynchInfo info) at Microsoft.Office.Server.UserProfiles.SiteSynchronizerCollection.<get_Elements>d__0.MoveNext() Just what the Fred is an "unprovisioned root site" and how does one go about provisioning one?! From: [email protected] [mailto:[email protected]] On Behalf Of Paul Turner Sent: Tuesday, 3 November 2009 9:08 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing You should be sent to MS in Redmond so you can tell them all about it... I'll leave it to Dan to organise :-) Regards, Paul Turner Senior Solutions Specialist M: 0412 748 168 P: 08 8238 0912 F: 08 8234 5966 A: 66 Henley Beach Road, Mile End SA 5031 E: [email protected]<mailto:[email protected]> W: www.dws.com.au<https://webmail.dws.com.au/owa/UrlBlockedError.aspx> Error! Filename not specified. ADVANCED BUSINESS SOLUTIONS LTD This email and any files transmitted with it are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient you have received this email in error and are requested to delete it immediately. Any opinion expressed in this e-mail may not necessarily be that of DWS Pty Ltd. Please consider the environment before printing this email. ________________________________ From: [email protected] [[email protected]] On Behalf Of Paul Noone [[email protected]] Sent: Tuesday, 3 November 2009 8:38 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Brilliant. As for presenting to SPUG, I keep telling you, unless the title of my presentation is "101 SharePoint Bugs That Only I Seem To Have", I really have nothing of value to say. :D From: [email protected] [mailto:[email protected]] On Behalf Of Daniel W. Brown Sent: Tuesday, 3 November 2009 8:59 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Haha, normally I'd jump on it, but I'm a bit under the hammer at the moment :( I'll make you a deal.. come down and present at the user group and I'll write it :P However on a more serious note. I will add it on to my "todo list" and publish it up codeplex 1 day. From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 3 November 2009 8:32 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing And you would be just the man to write it, yes? ;) From: [email protected] [mailto:[email protected]] On Behalf Of Daniel W. Brown Sent: Tuesday, 3 November 2009 8:56 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing LOL Paul :P You're a man full of ideas. It may be possible to create a page, which allows you to reparent a content type. It would just need a custom page and some code :) From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 3 November 2009 8:28 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Agreed, agreed! And there should be an easy way to either lock them down or reparent them in the event they become orphaned through misadventure! From: [email protected] [mailto:[email protected]] On Behalf Of Daniel W. Brown Sent: Tuesday, 3 November 2009 8:52 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing > For future reference, the predicament you currently find yourself in is > precisely why Site Columns should always be used for these purposes. Their early should either be functionality to create a content type from a list .. or my preference get rid of the ability to even HAVE "free range" column. Content Types should be just how it's done :P From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Tuesday, 3 November 2009 8:22 AM To: ozMOSS Subject: RE: Content Types - Exporting and importing Mike, if you're not that keen on coding you can grab SPSource<http://spsource.codeplex.com/> to suck down the columns as XML schema definitions for re-use in a Site Column feature<http://blogit.create.pt/blogs/andrevala/archive/2008/03/26/SharePoint-2007-Deployment_3A00_-Site-Column-Features.aspx>. Writing a site column feature is a good first step to developing in MOSS as it's fairly straightforward. If SPSource seems a little too geeky then you can do the same thing with SharePoint Manager<http://www.codeplex.com/spm>. Just drill down to the fields in the list, switch to schema view and copy out the XML to an elements manifest. For future reference, the predicament you currently find yourself in is precisely why Site Columns should always be used for these purposes. Regards, Paul Online Developer, ICT CEO Sydney From: [email protected] [mailto:[email protected]] On Behalf Of MacDonald, Mike Sent: Tuesday, 3 November 2009 2:46 AM To: ozMOSS Subject: Content Types - Exporting and importing I created a list with A LOT of columns - now I want to save it as a content type so that the fields are accessible when creating new content types at the top level on other sites. Is that possible ?
<<inline: image001.jpg>>
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
