English

The STSADM.exe is command-line tool for administration of Office SharePoint Server (SharePoint 2007, SharePoint 2010). It is installed on the same location as SharePoint Products and Technologies location: %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin (for SharePoint 2007) or %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin (for SharePoint 2010). You must be Farm Administrator to be able to run the tool.

By default, the STSADM.exe must be executed locally since it will access SharePoint Object Model. It is also necessary for the tools to connect to the SQL Database using credential of the user who executes it. Therefore, normally the Administrator must remote-login to the SharePoint server before he/she can run the tools.

Remote execution of STSADM.exe using PowerShell Invoke-Command cmdlet faces double-hop challenges. This occurs when SQL Database for the farms is installed on different machine than the SharePoint server. The credential in theInvoke-Command session can not pass through to the SQL Database without configuring delegation in the WinRM services.This module solve double-hop problem without configuring CredSSP.

Download the module here:
http://code.msdn.microsoft.com/Remote-StsAdm-in-6fec24b8

English:

In SharePoint, there is SPPropertyBag which can stores arbitrary key-and-value pairs into configuration database. And this is very good location compared with web.config. Moreover we can also create our custom class from SPPersistedObject to persist it state in a permanent store and retrieve it for later usage. (see MSDN refence SPPersistedObject)

But don’t be so happy – the SPPropertyBag can only store primitive types such as strings, integers, and GUID; and collection of above. The main keyword to understand is SPPropertyBag can only store primitives type and not arbitrary key-and-value pairs.

When you try to store complex object, you’ll unstablize configuration DB. And most of the time, you will not be able to install WSP, or perform anything related with SPPropertyBag operation. For example the timer job will stops to work, any component that reads SPPropertyBag will suddenly stuck. All because SharePoint will try to retrieve any persisted object from configuration DB and it fails. It will then show you and error message like this,

The platform does not know how to deserialize an object of type [TYPE]. The platform can deserialize primitive types such as strings, integers and GUID; other SPPersistedObjects or SPAutoserializingObjects or collections of any of the above. (..more..)

The visual error will be something like this,

So how to troubleshoot this issue?

IMPORTANT! 
1. Please backup configuration DB before proceeding with following procedure.
2. This procedure will modify configuration DB directly , and is un-supported by Microsoft.

TROUBLESHOOT.

1. Remove offending assembly from GAC (C:\Windows\Assembly) store.

2. Open Query Manager in SQL Management Studio, and connect to SharePoint content DB. Check that you have all reference to the offending property bag.

3.  Offending property bag can be found in “Properties” field of Objects table. If you dig into the content you will find something like

<object type=……>
…<fld type=”[YOUR TYPE]”></fld>..
</object>

where [YOUR TYPE] is the one causing problem. Once you have sure that you have all rows selected, then you can do clean up.

4. Replace SELECT [Fields] statement with DELETE statement.

And voila, I have saved you from big trouble.

English

Before you continue reading this post, I hope you have read the basic task to start using lambda expression in SOM here.

A.  Find any Event list in site.

SPWeb spWeb = SPContext.Current.Web

var lists = spWeb.Lists.OfType<SPList>().Where(
             l => l.BaseTemplate == SPListTemplateType.Events);
  foreach (SPList list in lists)
{
       Console.WriteLine("{0} {1}", list.BaseTemplate.ToString(), list.Title);

  }

B.  Find any list based on custom list definition with Type=20080

SPWeb spWeb = SPContext.Current.Web

var lists = spWeb.Lists.OfType<SPList>().Where(
             l => (int) l.BaseTemplate == 20080);
  foreach (SPList list in lists)
{
       Console.WriteLine("{0} {1}", list.BaseTemplate.ToString(), list.Title);

  }

C. Find any “Daily” alert in the site

SPWeb spWeb = SPContext.Current.Web

var alerts = spWeb.Alerts.OfType<SPAlert>().Where(
                                  a => a.AlertFrequency == SPAlertFrequency.Daily);

  foreach (SPAler alert in alerts)
{
      // Do something with alert

  }

D.  Find any user which are Domain group

SPWeb spWeb = SPContext.Current.Web

var users = spWeb.SiteUsers.OfType<SPUser>().Where(
                              u => u.IsDomainGroup );

  foreach (SPUser user in users)
{
      // Do something with alert

  }

English

For anybody who works with SharePoint Object Model (SOM), you might have read these articles  :

• Common Coding Issues When Using the SharePoint Object Model
• Using Disposable Windows SharePoint Services Objects

If you have not read those articles, I suggest to spend your 10 minutes to read them. It was posted 1 year ago, but still relevant if you’re actively develop or do code quality control in SharePoint development.

I’ve been working with team that are new to SharePoint and even tough we have a brief explanation and code standards; they tends to miss at some points. I usually use the list from Roger Lamb (SharePoint 2007 and WSS 3.0 Dispose Pattern by Example) for my reference to do sampling check on our controlled sources.

But, thanks to Pandrew – who made SharePoint Dispose Checker . With this tool, I would never do visual sampling check again. It will just make our quality control job easier. Run the tools and go grab the line in the source code to see if it is truly undispossed or just false positive.

Bahasa

Bagi rekan-rekan yang bekerja dengan SharePoint Object Model (SOM),  dua artikel ini mungkin sudah pernah Anda baca  :

• Common Coding Issues When Using the SharePoint Object Model
• Using Disposable Windows SharePoint Services Objects

Jika Anda belum sempat keduanya, cobalah untuk meluangkan sedikit waktu untuk membaca artikel tersebut.  Meskipun sudah cukup lama ditulis, namun tulisan itu masih relevan untuk rekan-rekan yang aktif mengembangkan aplikasi dengan SharePoint.

Biasanya saya menggunakan daftar yang dibuat oleh Roger Lamb (SharePoint 2007 and WSS 3.0 Dispose Pattern by Example) untuk melakukan pengecekan terhadap hasil code rekan-rekan dalam satu tim. Caranya adalah dengan mengambil sampling dari semua code yang telah dibuat.

Tetapi pekerjaan itu sekarang menjadi jauh lebih mudah dengan adanya  SharePoint Dispose Checker , yang dibuat Pandrew dkk. Dengan utility ini, tidak perlu ada lagi pengecekan acak. Cukup dengan menjalankan utility dan memverifikasi ulang method yang dilaporkan “bermasalah”.  “Bermasalah” belum tentu benar-benar tidak melakukan dispose – tetapi bisa jadi hanya interpretasi berbeda dengan SPDisposeChecker; namun ini sudah cukup membantu kita untuk melakukan pengecekan secara langsung hanya pada baris-baris yang dicurigai saja.