Steven Van de Craen's Blog

Thank you so much, a very useful tool indeed and a big thank you for the source code too it.

Thanks a lot for this. I've been struggling with this issue for a couple days now. Very much appreciated!

This was huge. Helped me get past my issue with this. /me tucks this tool away in my toolbox.

Steve, you're the man. Thank you for the tool & code!!!

Great tool! Fixed the problem. Thanks

I have finalized the Contact Form. From now on you can contact me using the contact.aspx page ;)

Hi Steven - I have run your tool and it works great ! - however, I have a problem - your tool reports an invalid feature at a web which not the root web eg :- http://myweb.com/thisweb and I cant remove it using stsadm as suggested as it says you must remove it from the root site - which I did - but your tool still reports the error in the sub site Nigel

Hi Nigel,

I did some testing and it was not possible using STSADM. I have released a newer version of the tool that should let you delete the features instantly. Be careful ! This tool will delete *any* feature you select, also working ones.

Steven

I've been researching this 'Object reference not set to an instance of an object' error when I try to deploy my Webpart via Visual Studio 2005 for over a week now. This tool has been the only helpful item I've found anywhere on the web relating to this issue. I ran the tool, removed the corrupt feature, and the deployment worked for the first time in a week.

Hi Steve, I can't backup my site after I installing some feature and almost getting upset about it. Your post so helpful. Really thanks ^^

Hi Steven, thanks for this great tool. I was completely stuck developing my own tool for exporting SharePoint content using SPExport. I could never have quessed that a faulty feature was the reason that I got the "Failed to compare two elements in the array" exception. I will add this to my toolbox, and drink a beer on your health tonight!! Serge

Great little tool. Simple, Straightforward, no gimmicks - Problem Solved!!! Thank you!

Thanks a bunch for your post and your utility, Steven. This was exactly my problem and saved me a bunch of head-scratching.

Hi Steven, this sounds like a great tool. I'm trying to run it on my local SharePoint install but am getting the infamous "Request for the permission of type 'Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' failed" error. I tried setting the trust setting in web.config for my virtual server to "Full" and did an iisreset, but I still see the error. Is there something else I need to do at the server or SharePoint level to get rid of this error? Thanks!

Well, just answered my own question. I was running this tool from a network drive. As soon as I moved it to the local C: drive, it works fine (with "Full" trust access).

Hi, I have exactly the same problem, run your tool and voila! errors gone. Thanks a lot G

Hi steve! when i ran your tool and there were a lot of error feature. TUrns out there were enterprise feature but we are running on standard edition. the site was migrated to our standard edition. however, when i removed the feature and run the export tools again, there were still error main because the site perhaps may be using the features i uninstalled. any thoughts on what i should do now?

Mela, I don't know what other causes this exception could have, but if it is not solved by removing the features I can't really help you any further. Does the tool still give you errors on certain (site collection or site) features ?

hi steven! one of the features that the tool recognized as an error was IPFSWebFeatures (i knew what the feature was after searching that GUID on google). i tried to uninstall it, but when i exported again, it is now looking for this feature also. i tried to install this feature again but again i am again having the error: Failed to compare two elements in the array.

thanks a lottttt

Hi Steven, Thank you very much! I am glad to hear from you. Yes, I have some interesting stuff lined up, and I am excited about it. Mostly I will publish small tips that would be helpful to the developer community. Thanks once again. Regards, S.S. A p.s I am sorry I couldn't find a link on your blog to send you an email, therefore, I am adding this comment.

Excellent that you made this tool!! Exactly what I needed and saved so much time.

This tool worked great for me, my only concern is that I deleted features that I need - would that be true? Is it safe to assume that any errors removed would not be working anyway and being currently used in a production environment?

I think most of the erroneous features are leftovers from B2TR upgrades or incorrect removed development features. I couldn't see how one of the OOTB features would be corrupted (unless someone deleted the folder in \FEATURES). You could always reactivate the current set of features so that any (hidden) feature dependencies are loaded again just to be safe.

Great tool but I got this on export: Feature 'a0e5a010-1329-49d4-9e09-f280cdbed37d' for list template '10102' is not installed in this farm. The operation could not be completed. Better than before but now what? Ideas welcome. PB

Great tool.It was creating error (Object reference not set to an instance of an object) when I try to deploy my Webpart via Visual Studio 2005 . After removing the particular feature by using this tool the problem has been solved.I think it's the only tool to solve this kind of "Life Hell" error. Thanks

Thanks so much, bailed me out of an important migration task. Love it when Googling the problem takes you right to solution!

Seriously- Good job buddy.

Great tool. Helped me resolve export issues with sites that had been migrated from a MOSS Enterprise environment to a MOSS Standard environment. One minor issue - the tool only seemed able to remove one feature at each scope (i.e. 1 SPSite-scoped feature and 1 SPWeb-scoped feature or one of either) at a time, even though I had multiple features selected. Is this by design, or a bug?

HI, and thanks for all your work. I ran into a export fatal error though after removing the invalid features: "FatalError: Feature 'a0e5a010-1329-49d4-9e09-f280cdbed37d' for list template '10102' is not installed in this farm. The operation could not be completed." I am now afraid I may have screwed something up, maybe to do with a customized list that was developed for us? Any ideas how to correct? Thanks

The tool should be able to remove multiple features at a same time and if it doesn't it is probably a bug.

Barry, If you have the custom list solution/feature I suggest you try to force reinstall it. Or if you don't need it anymore you could remove all the bits (like the list template) manually yourself.

Awesome tool, Steven! Thanks for sharing! Barry, I ran into the same problem. a0e5a010-1329-49d4-9e09-f280cdbed37d corresponds to the IPFSWebFeatures on my server. I reinstalled it using the following command: stsadm -o installfeature -name IPFSWebFeatures -force and I was able to export my sites. I hope this helps you. I was initially trying to create a site template of my sites without the content - this was what led me to using the stsadm export function. I was getting "Failure decompressing data from a cabinet file" errors when I attempted to do this via the SharePoint site interface. Well, I was able to fix this problem also using the Faulty Feature tool. Thanks, Shola Salako

Hi Steve, cool Blog. I am facing exactly this Problem. My question is now: Will the name of the Feature be empty -> like... Feature: 11cda100-5a8c-4f39-a149-0fd3f86b5e98() or is it something like -> Feature: 11cda100-5a8c-4f39-a149-0fd3f86b5e98(CTypes) or (NoCodeWorkflow) ? Thanks for your Help Sam

I've fixed the issue where only 1 checked feature would be deleted. Now you can delete multiple checked features at once ! @SAM: Normally each feature has a name. If the feature doesn't exist it will still give you the GUID but also an error notification.

Hey Steve, How wonderful tool it is. I have struggled a lot to get rid of this error. It was fortunate that I could find this. I could remove all the ERROR READING FEATURE features from the subwebs (sub sites) and could export the bugging site collection.

qeewvqrc voopamnr http://jsyivjep.com gflqmrwg mromgbwf [URL=http://puakoilo.com]jyavpkur[/URL]

mupqyiyb http://gdfhorxp.com aeuevvwj yigsiinc [URL=http://jaycqhda.com]dqrupkoq[/URL] npmugjij