tag:blogger.com,1999:blog-5495217247354866797.post1438131321598778350..comments2023-03-24T16:40:55.122+01:00Comments on Antoine.MOSS2007: How To Delete an “Orphan” Content Type?Antoine Pichothttp://www.blogger.com/profile/15190228901796083769noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-5495217247354866797.post-62533665721951925312017-07-19T03:10:13.066+02:002017-07-19T03:10:13.066+02:00Excellent!!! This has helped me a great deal. Th...Excellent!!! This has helped me a great deal. Thank you for writing this!Affiliate Rookiehttps://www.blogger.com/profile/15039947384825144875noreply@blogger.comtag:blogger.com,1999:blog-5495217247354866797.post-36029073048174370802014-03-12T21:40:38.241+01:002014-03-12T21:40:38.241+01:00Very good blog poѕt.I certainly love this site. Ke...Very good blog poѕt.I certainly love this site. Keep it up!<br /><br /><br />my ѡeblog: vegetable smoothie diet - <a href="http://greatfitnessideas.com/smoothie-diet/" rel="nofollow">greatfitnessideas.com</a>,Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5495217247354866797.post-84922778601541193162010-10-05T02:30:53.202+02:002010-10-05T02:30:53.202+02:00"Update [SharePoint - 27235].[dbo].[ContentTy..."Update [SharePoint - 27235].[dbo].[ContentTypes] set [IsFromFeature] = 0 where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x0101EF0201%')"<br /><br />This Amount to database editing , which will put your database in to Unsupported state ,Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5495217247354866797.post-2461451544289741842010-09-24T16:56:28.144+02:002010-09-24T16:56:28.144+02:00Brilliant. Allowed me to correct a content type e...Brilliant. Allowed me to correct a content type error for a MOPS 2007 upgrade to 2010. I was stuck on the sql for specifying the exact rows by contentTypeId - this was the ticket. Thanks!Scottnoreply@blogger.comtag:blogger.com,1999:blog-5495217247354866797.post-7881646192319889262010-06-11T10:45:53.954+02:002010-06-11T10:45:53.954+02:00THanx this worked for me!THanx this worked for me!Unknownhttps://www.blogger.com/profile/09782831073735058153noreply@blogger.comtag:blogger.com,1999:blog-5495217247354866797.post-42267816251768469462010-02-25T11:06:12.614+01:002010-02-25T11:06:12.614+01:00You're right, but you also assume there is no ...You're right, but you also assume there is no bug in SharePoint :-)<br />For me these missing id's are the consequence of a bug un SharePoint. Normally, when the error management is well done, such bad entries never exist in the DB. That's why there is no other possiblities (even with the object model) to remove these entries than removing them directly from the DB.Antoine Pichothttps://www.blogger.com/profile/15190228901796083769noreply@blogger.comtag:blogger.com,1999:blog-5495217247354866797.post-58688587771814516462010-02-23T23:08:10.456+01:002010-02-23T23:08:10.456+01:00You can't really call this a solution, as dire...You can't really call this a solution, as directly modifying the db is explicitly prohibited if you want to maintain Microsoft support of the SharePoint product. I'm still looking for a way to get rid of these... Perhaps the object model could let you modify these properties?Jon Badgetthttps://www.blogger.com/profile/16735238142710317155noreply@blogger.com