SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

Blog

FIXED – DeleteElementAddToMyColleaguesURL People Search

If you ever see the below People Search error go double check your indexed User Profile Properties.   I saw this recently and the root cause was a missing “Indexed” checkbox.   Enabling the Indexed checkbox for Account Name and crawling again fixed the issue.   Thanks to Puneet for the tip on this one.

System.NullReferenceException: Object reference not set to an instance of an object. at System.Xml.XmlNode.RemoveChild(XmlNode oldChild) at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.DeleteElementAddToMyColleaguesURL(XmlNode result) at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.CreateXmlDocument() at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.SortBySocialDistance() at Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart.GetXPathNavigator(String viewPath)

image

Create Scopes & Managed Props with code #DevAdmin

Yesterday I found some great articles on how to create SSP search scopes and SSP Managed Properties via code.   This isn’t for developers.   This is for administrators!   If you need to repeat something with high quality a console EXE in Visual Studio is a great way to script against SharePoint 2007 (no offense to PowerShell in 2010).

Bundling these up as Console EXE that take in paraneters like args[0] allows you to easily build CMD files that can run many commands (even across many farms).   Excel fill down is my favorite way of doing this … then you just copy/paste over to CMD!  

Open-mouthed

 

image

DevAdmin = Best job title!

Admins and Devs seem different.  They often argue, yet can learn from each other.  I’ve done both and neither is the complete picture.   Below is an idea for scripting, scaling, and growing by learning both.  “DevAdmin” is a role with incredible potential.   Please leave a comment, email me, or send a tweet.   I’d really like to hear your feedback.

Dev   Admin
  • Says “yes”
  • Goal = More features
  • Liberal approach
 
  • Says “no”
  • Goal = More stability
  • Conservative approach

Above is my stereotype of both groups.  While not perfect it’s a useful frame of reference.  When speaking to one group (or the other) keep their unique perspective in mind to communicate more clearly.  Below is an outline for mixing both to create a more balanced IT worker:

DevAdmin
  • Says “maybe” and listens
  • Goal = Stable features
  • Liberal on features, Conservative on process
  • Knows both sides, actively works on both
image

RDP sucks at scaling.  But it’s great for small tasks.  How do you admin 300 servers?  Hmm … that’s a bunch of windows to juggle! 

Confused

   I developed a working concept called the “grid” script that would place real-time configuration on a single page.  Each machine/server is a vertical column.   Each configuration point is a row.   On a single page I can tell exactly what settings are missing, where changes are needed, and ensure high quality with lower costs.   I must be a DEV to code this tool.   I must be an ADMIN to read and use it.

http://spdash.codeplex.com/

I’ve reserved the URL above to place my code and EXE once complete for all to enjoy.   More to come soon …

image

image

image

The technology environment will only grow more complex.   ADMINs must learn some DEV (script, powershell, dot net, etc.) to remain marketable.   DEVs must learn some ADMIN (performance, capacity, uptime) to know how to scale up their application and ensure stable delivery to end users.

Related Posts

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲