Archive for September, 2010

Sweden SharePoint User Group (SSUG), Meeting in October

September 24th, 2010 by Tobias Zimmergren

Author: Tobias Zimmergren
http://www.zimmergren.net | http://www.tozit.com | @zimmergren

Introduction

After a long and well deserved vacation we’re now back with new strength!
It’s time for our first SSUG meeting for the fall!

Please do remember; This is a FREE event – we never have and never will charge anyone for loving SharePoint and sharing the awesomeness :-)

Meeting details

Let’s meet up at Microsoft HQ for our first SSUG meeting this fall! You will have the possibility to mingle around with SharePoint MVPs, folks from Microsoft and of course all our splendidly cool members!

We will of course have snacks and beer/beverages at hand, just like we always do.

Please see the following sections for details about the meeting!

Location

Microsoft AB, the Swedish Microsoft HQ.

Microsoft AB
Finlandsgatan 36
KISTA

Find it:
http://www.hitta.se/ViewDetailsPink.aspx?Vkiid=FRfzEz0DKh9ofdUqflCH4g%253d%253d&vad=Microsoft

Time and Date

October 5th, 2010.

We’ll meet up at 17:30 at Microsoft HQ and sessions will start around 18.00 – so there’s plenty of time for making acquaintances before we begin.

Session agenda

  • 17:30: – Doors open at Microsoft HQ
  • 18:00: Session 1;
    • Lync/OCS 14: Pontus Haglund from Microsoft AB
  • Break
  • 19:00: Session 2;
    • Visio 2010 + SharePoint 2010: Wictor Wilén, Connecta AB

Sign up for the meeting!

As we still haven’t finalized the new membersite for the SSUG group (hold your breath, we’re soon to be finished); you can sign up for the meeting by e-mailing info@ssug.se with the subject “Oktobermöte”.

If you know of anyone interested in attending, please feel free to forward this information!

Summary

A lot of questions have popped up in regards to what’s going on with the member-site, and we’ll shortly announce some news about that – but for now, let’s focus on making this meeting rock as always :-)

Cheers!

Author: Tobias Zimmergren
http://www.zimmergren.net | http://www.tozit.com | @zimmergren 

Introduction

I’ve been getting some questions lately about modifications to web.config files and SharePoint 2010 – is it possible to automate so that the administrator don’t have to manually edit those files on each WFE?

Yes, that’s the easy answer. This was possible in SharePoint 2007 as well.

In this article I’ll quickly demonstrate how you (using a Web Application feature) can make modifications to web.config automatically.

Please note that this is just a getting-started point which you’ll have to work deeper into to tweak it to your likings for updates and removals from the web.config file.

Automatic web.config changes using a SharePoint 2010 feature

Basically, if you want to get some type of change into the web.config, it oftentimes has to do with adding custom settings or values that you’ll later reference in your applications.

In this scenario, we’ll add the following key into web.config using a Feature Receiver, so we don’t have to do it manually after/before deploying our solutions:

 <add key= "isAwesome " value= "1 " />

So, in order to achieve this programmatically without actually editing the web.config by hand – you could utilize the class called SPWebConfigModification something like this:

 public  override  void  FeatureActivated(SPFeatureReceiverProperties  properties)
 {
     var  value = 1; // We want to set the key isAwesome to the value "1" 

     var  webApp = properties.Feature.Parent as  SPWebApplication ;
     var  mySetting = new  SPWebConfigModification 
     {
         Path = "configuration/appSettings",
         Name = string.Format("add [@key='isAwesome'] [@value='{0}']", value),
         Sequence = 0,
         Owner = "Zimmergren.SP2010.WebConfigModifications.Awesomeness",
         Type = SPWebConfigModification.SPWebConfigModificationType.EnsureChildNode,
         Value = string.Format("<add key='isAwesome' value='{0}' />", value)
     };

     webApp.WebConfigModifications.Add(mySetting);
     webApp.Update();
     webApp.Farm.Services.GetValue<SPWebService>().ApplyWebConfigModifications();
 }

By executing this cute snippet of code you will actually add the setting called isAwesome to the web.config of your web application. (This will be persisted to all the WFE’s of course).

Please note: You will need to tweak your code quite a lot to make the sweet SPWebConfigModification class behave the way you want on activation/deactivation of the feature. This should at least give you a starting point :-)

Summary

In this short introductory article about web.config modifications I’ve talked a bit about how you can automate the process of altering your web.config files without actually opening them on the file system.
Nothing fancy, but a good starting point for those of you who requested some info on the topic.

Enjoy!

Author: Tobias Zimmergren
http://www.zimmergren.net | http://www.tozit.com | @zimmergren

Introduction

In SharePoint 2010, you’ve got some new capabilities for error reporting and logs. One of the most noted features for me as a developer is that whenever you bump into an error message – you’ll be presented with a correlation ID token.

In this article I will try to explain how you can fetch that token from SharePoint, and also provide a small snippet of code to be able to build your own “Log Searcher Web Part” for your administrators.

Correlation ID, what’s that?

In SharePoint 2010, you get a Correlation ID (which is a GUID) attached to your logs/error messages when something happens. This ID can then be used to lookup that specific error from the logs.

This Correlation ID is used per request-session in SharePoint 2010, and if you are in the process of requesting some information from SharePoint and bump into some problems along the way – your Correlation ID will be the best starting point for searching for what went wrong along that request!

You might get an error message like this in SharePoint 2010 (don’t worry, if you haven’t seen one like this one yet – just hang in there, sooner or later you will.. Winking smile)

image

Search for the log messages based on the Correlation ID token

So if you’ve gotten such an error message and want to find out more information about the actual error and don’t have the time to go around poking in the logs and searching – there’s a few methods you can do this rather easily, as described below.

Using PowerShell to lookup a log message based on Correlation ID token

One of the quick-n-awesome ways to do this is to simply hook up a PowerShell console (SharePoint 2010 Management Shell) and then just write the following command (replace the <GUID> with the Correlation Id):

get-splogevent | ?{$_Correlation -eq "<GUID>" }

This will give you the details about your specific error like this in the console:

image

You might want to be more precise and get more specific details out of your query, then you can try something like this:

get-splogevent | ?{$_.Correlation -eq "<GUID>"} | select Area, Category, Level, EventID, Message | Format-List

This will give you the details about your specific error like this with some juicy details:

image

Finally if you would want these messages to be put into a text or log file instead, you could just add the classic “> C:Awesome.log” after the command like this:

get-splogevent | ?{$_.Correlation -eq "<GUID>"} | select Area, Category, Level, EventID, Message | Format-List > C:Awesome.log

image

On MSDN they have an overvoew of using SP-GetLogEvent which I would recommend!

Using SQL queries to find log message based on Correlation ID token

You can utilize the SQL logs database to fetch the specific error message based on Correlation id as well. In your logging DB (usually called WSS_Logging, but can be called something else if you’ve changed it) there is a view called ULSTraceLog which you can query with a simple SQL query and fetch the results.

I’ve created a query to fetch the items from the logging database like this:

 select 	[RowCreatedTime],  [ProcessName],  [Area],  
 		[Category],  EventID,  [Message] 
 from  [WSS_UsageApplication].[dbo].[ULSTraceLog] 
 where  CorrelationId=< pre>'B4BBAC41-27C7-4B3A-AE33-4192B6C1E2C5'

This will render your results in the SQL Query window like this:

image

This can of course be implemented in a Web Part for your convenience as well (I’ve created a bunch of diag. and logging web parts that I’ve got deployed to Central Admin) that could look like this (this way you don’t need physical access to the ULS logs all the time, but can do a quick lookup from the web part):

image

Get the current Correlation ID by using code

I got this piece of code from my good friend Wictor’s blog post. Thanks Wictor – this made my Logging-project more satisfying!

With the following code you can fetch the current Correlation Id of a request.

Create a method (in my case called GetCurrentCorrelationToken()) to wrap up the functionality of returning the current token like this:

 public  class  CorrelationId 
 {
     [DllImport ("advapi32.dll")]
     public  static  extern  uint  EventActivityIdControl(uint  controlCode,ref  Guid  activityId);
     public  const  uint  EVENT_ACTIVITY_CTRL_GET_ID = 1;

     public  static  Guid  GetCurrentCorrelationToken()
     {
         Guid  g = Guid .Empty;
         EventActivityIdControl(EVENT_ACTIVITY_CTRL_GET_ID, ref  g);
         return  g;
     }
 }

Then from wherever in your code you can simply call it by using this approach:

 protected  void  Button1_Click(object  sender, EventArgs  e)
 {
     Label1.Text = CorrelationId .GetCurrentCorrelationToken().ToString();
 }

(Normally you might want this in a try/catch statement or something like that)

image

Summary

This article should give you (administrator and developer) an insight in how you easily can track the specific errors your users encounter in their/your application(s). If a user gets an error message in SharePoint 2010, they’ll also see the Correlation ID.

If you can train your users to write down that Correlation ID along with a few simple steps on how the error might have been occurring, you’re going to have a much easier way to find the details about that specific error than ever before.

Enjoy!