The Frog Pond of Technology

Ripples of Knowledge for SharePoint and Other .Net Technologies

News

Subscribe to this blog

Grab this badge here!

About Me

Name: Brian T. Jackett
Location: Columbus, OH
Company: Microsoft

Find me on...

Twitter

BrianTJackett @officeovereasy I'll see if @ScriptingGuys can talk to the product team about adding bacon and gamification to PowerShell :) @ferringer about 1 minute ago

BrianTJackett @MonGinder Newer OSes automatically take care of defrag and clean up without you having to manually kick them off as frequent. about 2 hours ago

BrianTJackett @DavidGiard I'm donating money to a different charity each week. I like to do something proactive rather than give up something. about 2 hours ago

BrianTJackett @ferringer PowerShell is awesome. If only could use it to automate making bacon... (starting new side project) @usher @TashasEv @mrackley about 2 hours ago

BrianTJackett Hotel internet isn't fast enough to play #SWTOR, sad face :( reading more Game of Thrones on kindle which makes happy face :) about 14 hours ago

BrianTJackett @ghurlman I assumed that's what you meant, just clarifying. Agreed that you should run through build/deploy process sans VS. about 1 day ago

BrianTJackett @ghurlman Do you include a dev server where you are developing the SharePoint solution? about 1 day ago

BrianTJackett I won the Air Freshener achievement in Bug Village (WP) for 39 trueachievement points - http://t.co/3vravh0v about 3 days ago

BrianTJackett @WonderLaura Doesn't SPD copy current item action save to a variable which you can then query? about 5 days ago

BrianTJackett @JDWade Watched 50/50 last night and had a joke about Doogie Howser which a young char didn't get, makes ME feel old @spmcdonough @TashasEv about 5 days ago

Post Categories

Syndication:

RSS
ATOM

December 2011 Entries

Fixing “Failed to create field: Field type <field name> is not installed properly” Error on SharePoint 2010 List

Upgrading a SharePoint farm can reveal hidden issues that may not be causing any visible consequences in your current environment. This was especially the case in a recent customer visit to assist with an upgrade from SharePoint 2007 to SharePoint 2010. During the upgrade we encountered the error “Failed to create field: Field type <field name> is not installed properly” while attempting to upgrade hundreds of SharePoint lists and document libraries. The issue my customer faced related to a...