SharePoint Dragons

Nikander & Margriet on SharePoint

Monthly Archives: February 2013

Top 10 SharePoint Blogs

From now on, we’re going to do the SharePoint 10 blogs differently. We’re going to do it once every 3 months and try to get more community participation. In +/- 2 weeks a Sticky Thread will appear in the SharePoint forums where people can vote on the Top 10 blogs. This voting process will be repeated quarterly. The top 10 will be placed on the popular TechNet Wiki SharePoint 2013 Best Practices page and will appear on the TechNet Wiki Ninja Blog Spot.

Advertisements

Working with .BLG files

When doing performance analysis, we routinely record .blg files using perfmon to inspect the various servers involved in the SharePoint farm. We were looking for a library or piece of .NET code to read such .blg files but eventually came to the conclusion that there are only two workable solutions:

$result = import-counter .\sample.blg
$result | export-counter -path .\output.csv -FileFormat csv

For more info on SharePoint related perf counters and the related get-counter cmd, check out http://gallery.technet.microsoft.com/PowerShell-script-for-59cf3f70

SharePoint 2013 Feature Overview

And another SharePoint 2013 feature comparison overview: http://www.apps4rent.com/sharepoint-2013-features-comparison.html

It’s the SharePoint Flavored Weblog Reader again!

 

We’ve released SFWR v1.3.

What is it?

“The IIS logs are an invaluable way to get to know your web application and your end users once it’s in production. Therefore, having a tool to analyze IIS logs is in invaluable asset in your bag of tricks. Especially if this tool has a certain SharePoint flavor added to it…”

What’s the update?

“Not everybody has the same IIS logging settings, that’s why SFWR uses the DLR to support this. Nevertheless, there were certain reports that threw exceptions and caused processing to halt because they expect certain data to be present (mainly bytes sent and bytes received). v1.3 uses a little Aspect Oriented Programming (AOP) to make sure all report calculation errors are handled.”

Where to  get it?

http://gallery.technet.microsoft.com/The-SharePoint-Flavored-5b03f323

GhostDoc – Way of the Samurai

Or was that movie called Ghostdog? Anyway, we haven’t looked at this tool for years, and retried it again recently: GhostDoc. If you don’t know it, take a look at it ( http://submain.com/products/ghostdoc.aspx ). It’s a nice tool for auto generating comments. The reason we didn’t like it that much originally, was because we didn’t think the auto generated comments were very helpful. Check out this example and you know what we mean:

/// <summary>
/// Gets or sets the delay in seconds.
/// </summary>
/// <value>
/// The delay in seconds.
/// </value>
public int DelayInSeconds { get; set; }

The reason we fell in love with it this time is because pressing CTRL+A (to select everything, a standard shortcut) followed by CTRL+SHIFT+D (GhostDoc specific) sets up a nice start that allows you to fill in missing information and make the comments more valuable, while saving a lot of keystrokes. On second view, this tool is actually quite handy!

PressurePoint Dragon for SharePoint 2013

When you apply enough pressure, every application you or somebody else builds has a point where it breaks. I call this point the pressure point. PressurePoint Dragon for SharePoint 2013 will help you find this point, the follow-up of the generic PressurePoint tool: http://gallery.technet.microsoft.com/PressurePoint-Dragon-for-87572ee1

CAML Designer 2013

Page Rank Checker

Check the page rank of your web site at: http://www.prchecker.info/ At the time of writing, ours was 3 and we weren’t able to find a SharePoint blog with a page rank higher than 4, so that seems to be the limit for our “niche”.

Most Revised Article Award

Couldn’t resist the quote:

“The article to receive the most revisions this week is SharePoint 2013 Best Practices by wiki legend and TNWiki Community Council member Margriet Bruggeman

Read http://blogs.technet.com/b/wikininjas/archive/2013/02/09/top-contributors-awards-mega-busy-week-technet-wiki-also-exchange-server-2013-windows-root-certificates-sharepoint-2013-and-more.aspx for a complete overview of Wiki activity.

SharePoint 2010 Recycle Bin Blues

Let’s do a recap of the SharePoint 2010 Recycle Bin functionality. There are two stages, the site recycle bin and the site collection recycle bin. When the end user throws away content, it first is thrown into the site recycle bin (where, by default, it stays for 30 days). After this retention policy causes the deletion of content from the site collection bin, its added to the site collection recycle bin, where only site collection admins can restore it. Both recycle bins are enabled by default.

Check the recycle bin settings by doing this:

Controleer eerst de thresholds en settings voor beide recycle bins:

1. Open SCA

2. Go to Application Management > Manage Web Applications

3. Select the web application your interested in

4. In the ribbon, click General Settings

5. Check the recycle bin settings

If you can’t find an item in the site recycle bin, pay attention to a couple of things:

  • The end user who has deleted the content will see it in the site recycle bin, other end users won’t. The site collection admin will see all deleted content.
  • If you delete a folder, it will show up in the recycle bin. Individual sub items located in that folder won’t, and you can’t navigate thru that folder to find them.
  • Be careful, the content may have been renamed or relocated instead of deleted.

When the content is not there, a couple of things may have happened:

  • An administrator used SCA to turn off the recycle bins which causes the deletion of all recycle bins (and may even have turned it back on again, which makes no difference).
  • A recycle bin threshold has been reached which caused the automatic deletion of content.
  • An administrator deleted the content permanently from the site collection recycle bin.

When the content has been deleted permanently, there’s only one way to get it back: get it from an old back-up. This goes something like this:

1. Create a back-up of the current environment.

2. Restore the old content.

3. Export the content that is deleted in the current environment to the file system.

4. Restore the back-up of the current environment.

5. Upload important files.

Of course, you can only do this in production if there’s a time slot that allows for this, and it’s usually better to restore the content in another environment. The following blog post describes an interesting variant on the back-up/restore scenario: http://blogs.msdn.com/b/modonovan/archive/2007/09/14/how-to-recover-sharepoint-document-once-deleted-from-recycle-bin.aspx

If you don’t have access to old back-ups, you’re in a dark place where unfortunately you won’t be able to restore the lost files. One last thing, be aware that end users may be confused by the fact that deleted items may still show up in searches. This confusion will go away eventually after indexing as taken place.