Todo Sharepoint

SharePoint Software Factory

2012-02-25T03:54:00.001-08:00

Nueva versión de la extensión de Visual Studio para ayudarnos a programar en Sharepoint. http://spsf.codeplex.com

NUEVAS FEATURES:

Menu "List And Doc": Linq to SharePoint (imports the schema of several lists to LINQ classes)
Menu "BCS": Simple BCS Model
Menu "BCS": Import BCS Model from Database
Menu "BCS": Model BCS Model with classes
Menu "BCS": Quick Deploy BCS Model (undeploys/deploys BCS model via powershell)
Menu "Security": Minimal CAS, Medium CAS, recipes for single CAS Policy Items etc.
Menu "ASP.NET": WCF Webservice
code snippets added, partly from http://spcodesnippets.codeplex.com Thx to Ayman El-Hattab (http://aymanelhattab.com)
Added custom FxCopDictionary to allow project specific exclusions for abbreviations, keyword, acronyns etc. Dictionary will be automatically used in Realase build configuration.

MEJORAS

ParametersDefault.msbuild sets RestartIIS to false by default
ParametersDefault.msbuild updated sample structure to allow easy setup of multiple deployment environments
In selection form of fields or content types the group is displayed (e.g. for field "Title" there are 6 results and no difference)
SharePointVersions.xml with current version numbers
Added BCS extensions (DBML, BDCM) to function "IsExcludedExtension" to avoid that model layout is saved to the WSP file
Change default.aspx in site defition Team Site and Blank Site to version 2010
In feature selection dialog a existing feature of allowed scope is selected by default
StartDeploy.bat: Made verbosity for ULSLogger configurable (previously it was always diagnostic)

Ver algunos ejemplos: http://geeks.ms/blogs/lmanez/archive/2011/10/21/sharepoint-plantilla-para-visual-studio-sharepoint-sw-factory.aspx

Más info:

http://geeks.ms/blogs/lmanez/archive/2012/02/23/sharepoint-2010-liberada-nueva-versi-243-n-de-la-sharepoint-software-factory.aspx

Incrementar el tamaño máximo de template de listas

2012-02-25T03:32:00.001-08:00

Si intenta guardar una lista como una plantilla de lista, puede ver el siguiente error, debido a que la lista sea demasiado grande:

“The list is too large to save as a template. The size of a template cannot exceed 10485760 bytes.”

Puede aumentar el tamaño máximo de una plantilla de lista del sitio, ejecute el siguiente comando (tenga en cuenta que 500 MB es lo más grande que puede setear):

stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 50000000

PDF Files en SharePoint Online

2012-02-25T02:01:00.001-08:00

Ahora se puede abrir archivos PDF directamente en Adobe Reader - y el archivo PDF se mantendrá conectado a SharePoint Online. También puede editar y guardar los cambios a SharePoint Online desde el escritorio. Y además, ahora se puede utilizar control de versiones (check-in y check-out) con los archivos PDF para una mejor gestión y revisión.

Para aprovechar las ventajas de esta actualización, siga los siguientes pasos.

Espere por la actualización de SharePoint Online
Actualice Adobe Reader a la versión 10.1.2 de cliente.
Añade su sitio web de SharePoint Online a la zona de seguridad Sitios de confianza en InternetExplorer (por ejemplo, https://contoso.sharepoint.com).
Marque el Recordar mi contraseña en la casilla al iniciar sesión en un sitio de SharePoint Online.

Privilegios elevados en código de Sharepoint

2012-02-25T01:57:00.001-08:00

SharePoint utiliza impersonation de ASP.Net para personalizar la plataforma basado en el usuario actual autorizado. Objetos de SharePoint son conscientes de la identidad del usuario y muchas partes de SharePoint sacan provecho de esta capacidad. Por ejemplo, cuando llegue a las listas en un sitio a través de la API, que sólo ven los que el usuario actual tiene acceso.

Si utiliza la autenticación de Windows y el código llama el modelo de objetos de SharePoint a partir de un proceso de trabajo de IIS, la solicitud debe suplantar la identidad del usuario que realiza la llamada. Sharepoint Foundation configura ASP.NET para suplantar al usuario que llama de forma automática, pero su código puede funcionar inesperadamente, o no, si se suspende la suplantación. Más info: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsite.aspx

Cuando usar RunWithElevatedPrivileges y cuando no

RunWithElevatedPrivileges is a great way to solve the database connection problem, but often it can become somewhat of a Pandora’s box. It can become a go-to tool for every permission error encountered in SharePoint code. However, there are some issues that can occur with overuse of this style of programming, not least of which is that you lose some core SharePoint functionality inherent with impersonating the user.

A StackOverflow discussion about the pitfalls of RunWithElevatedPrivilges is a good summary and starting point for reading on the subject. Also, I’ve included below 3 good references for further reading on the topic.

A veces para suspender la impersonalización de usuario, es posible usar “SPSecurity.RunWithElevatedPrivileges”.

RunWithElevatedPrivileges es una gran manera de resolver el problema de conexión de base de datos, pero a menudo puede llegar a ser algo así como una caja de Pandora.Puede convertirse en una herramienta de go-to para cada error de permiso encontrado en el código de SharePoint.Sin embargo, hay algunos problemas que pueden ocurrir con el uso excesivo de este estilo de programación, no menos importante de los cuales es que se pierde la funcionalidad de SharePoint básico inherente a suplantar al usuario.

Mejores prácticas en el uso de RunWithElevatedPrivileges

Evite usar SPSecurity.RunwithElevatedPrivilege para acceder al modelo de objetos de Sharepoint. Use SPUserToken para impersonalización con SPSite.
Si usas SPSecurity.RunwithElevatedPrivilege, has un dispose de todos los objectos en el delegate. No pases objectos de SharePoint fuera del método RunwithElevatedPrivilege.
Sólo use SPSecurity.RunwithElevatedPrivilege para hacer llamadas externas bajo la identidad del app pool. No lo uses para elevar los privilegios de objectos de Sharepoint.
Siempre usa el constructor SPSite con una instancia de SPUserToken para crear un contexto de seguridad con privilegios elevados. Para impersonalizar el sistema, usa la propiedad SystemAccount.UserToken del actual contexto SPSite, ej:
var site = new SPSite(SPContext.Current.Site.ID, SPContext.Current.Site.SystemAccount.UserToken);
Evitar pasar objetos de Sharepoint entre diferentes contextos de seguridad (SPSiteinstances), con exception de SPUserToken. Un objeto SPUSer creado en un SPSite A no puede pasarse a un SPSite B. Esto puede ser fuente de oscuros bugs.
Restring que assemblis pueden usa privilegios elevados corriendo en minimal trust, evita el uso de la GAC, y has auditoria de cualquier CAS policies deployada.

Algunos código útiles:

   1:  SPUserToken sysToken = SPContext.Current.Site.SystemAccount.UserToken;

2:

   3:  using(var systemSite = new SPSite(SPContext.Current.Site.ID, sysToken))

   4:  {

   5:      using (var sysWeb = systemSite.OpenWeb(SPContext.Current.Web.ID))

   6:      {

   7:          // Perform elevated actions here

   8:      }

   9:  }

---------------------------

   1:  private static void impersonateTest()

   2:  {

   3:     string siteStr = "http://mysharepointsite/";

   4:     SPSite tempSite = new SPSite(siteStr);

   5:     SPUserToken systoken = tempSite.SystemAccount.UserToken;

   6:     using (SPSite site = new SPSite(siteStr, systoken))

   7:     {

   8:         using (SPWeb web = site.OpenWeb())

   9:         {

  10:             //right now, logged in as Site System Account

  11:             Console.WriteLine("Currently logged in as: " +

  12:                                web.CurrentUser.ToString());

  13:             switchUser(web, siteStr, "BlackNinjaSoftware/MatthewCarriere");

  14:             switchUser(web, siteStr, "BlackNinjaSoftware/ShereenQumsieh");

  15:             switchUser(web, siteStr, "BlackNinjaSoftware/DonabelSantos");

  16:         }

  17:     }

  18:  }

19:

  20:  private static void switchUser(SPWeb web, string siteStr, string user)

  21:  {

  22:     //impersonate somebody else

  23:     SPUserToken userToken = web.AllUsers[user].UserToken;

  24:     SPSite s = new SPSite(siteStr, userToken);

  25:     SPWeb w = s.OpenWeb();

  26:     Console.WriteLine("Currently logged in as: " +

  27:                       w.CurrentUser.ToString() +

  28:                       "(" + w.CurrentUser.Name + ")"

  29:                      );

  30:  }

---------------------------

   1:  protected static SPUserToken GetSystemToken(SPSite spSite)

   2:  {

   3:      SPUserToken res = null;

   4:      bool oldCatchAccessDeniedException = spSite.CatchAccessDeniedException;

   5:      try

   6:      {

   7:          spSite.CatchAccessDeniedException = false;

   8:          res = spSite.SystemAccount.UserToken;

   9:      }

  10:      catch (UnauthorizedAccessException)

  11:      {

  12:          SPSecurity.RunWithElevatedPrivileges(delegate()

  13:          {

  14:              using (SPSite elevatedSPSite = new SPSite(spSite.ID))

  15:                  res = elevatedSPSite.SystemAccount.UserToken;      // (***)

  16:          });

  17:      }

  18:      finally

  19:      {

  20:          spSite.CatchAccessDeniedException = oldCatchAccessDeniedException;

  21:      }

  22:      return res;

  23:  }

Fuente:

http://tomresing.com/blog/Lists/Posts/Post.aspx?ID=53

http://daniellarson.wordpress.com/2008/06/06/best-practices-for-elevated-privilege-in-sharepoint/

http://dotnetfollower.com/wordpress/2011/03/sharepoint-how-to-get-systemaccount-token/

Más información:

http://www.arboundy.com/2011/02/sharepoint-run-with-elevated-permissions-vs-impersonate/

Algunos códigos de idioma ID (LCID) de configuración regional

2012-02-21T18:50:00.001-08:00

Identificador de configuración regional (LCID) : valor A 32 bits definido por Microsoft Windows que consta de un identificador de idioma, ordenar ID y bits reservados que identifican un idioma determinado.

Inglés EE.UU.
1033 (& H409)

Español (tradicional)
1034 (& H40A)

Portugués (Brasil)
1046 (& H416)

Fuente:

http://support.microsoft.com/kb/221435

Encontrar todos los archivos desprotegidos (check out) de un sitio

2012-02-21T16:54:00.001-08:00

El siguiente código de powershell permite recorrer un sitio y subsitios que devuelve una lista de archivos desprotegidos.

   1:  function GetCheckedOutFiles($web)

   2:  {

   3:  Write-Host "Processing Web: $($web.Url)..."

   4:          foreach ($list in ($web.Lists | ? {$_ -is [Microsoft.SharePoint.SPDocumentLibrary]})) {

   5:              Write-Host "`tProcessing List: $($list.RootFolder.ServerRelativeUrl)..."

   6:              foreach ($item in $list.CheckedOutFiles) {

   7:                  if (!$item.Url.EndsWith(".aspx")) { continue }

   8:                  $hash = @{

   9:                      "URL"=$web.Site.MakeFullUrl("$($web.ServerRelativeUrl.TrimEnd('/'))/$($item.Url)");

  10:                      "CheckedOutBy"=$item.CheckedOutBy;

  11:                      "CheckedOutByEmail"=$item.CheckedOutByEmail

  12:                  }

  13:                  New-Object PSObject -Property $hash

  14:              }

  15:              foreach ($item in $list.Items) {

  16:                  if ($item.File.CheckOutStatus -ne "None") {

  17:                      if (($list.CheckedOutFiles | where {$_.ListItemId -eq $item.ID}) -ne $null) { continue }

  18:                      $hash = @{

  19:                          "URL"=$web.Site.MakeFullUrl("$($web.ServerRelativeUrl.TrimEnd('/'))/$($item.Url)");

  20:                          "CheckedOutBy"=$item.File.CheckedOutByUser;

  21:                          "CheckedOutByEmail"=$item.File.CheckedOutByUser.Email

  22:                      }

  23:                      New-Object PSObject -Property $hash

  24:                  }

  25:              }

  26:          }

  27:  foreach($subWeb in $web.Webs)

  28:  {

  29:  GetCheckedOutFiles($subweb)

  30:  }

  31:          $web.Dispose()

  32:  }

33:

  34:  $web = get-spweb $args[0]

35:

  36:  GetCheckedOutFiles($web)

./GetCheckedOutFiles http://urltoweb | Format-Table url | out-file output.txt -width 500

Fuente:

http://www.thorntontechnical.com/tech/powershell-tech/powershell-tip-find-all-checked-out-files

Detrás de escenas de una consulta de search en Sharepoint 2010

2012-02-21T13:43:00.001-08:00

En los siguientes artículos encontrará una descripción de los pasos que se ejecutan detrás de una consulta de search en Sharepoint 2010.

http://blogs.msdn.com/b/russmax/archive/2012/02/15/guide-to-walking-a-sharepoint-2010-search-query-behind-the-scenes.aspx

http://blogs.msdn.com/b/russmax/archive/2010/04/23/search-2010-architecture-and-scale-part-2-query.aspx

En resumen:

1. A search is performed by a user

2. The WFE serving the call uses the associated search service application proxy to connect to a server running the Query and Site Settings Service also known as the Query Processor. It uses WCF for this communication.

3. The QP will connect to the following components to gather results merges\security trims and return results back to WFE:

Query Component - holds entire index or partition of an index

Property Store DB – holds metadata\properties of indexed content

Search Admin DB – holds Security Descriptors\Configuration data

4. WFE displays search results to the user

Resetear la “Farm Passphrase”

2012-02-21T13:35:00.001-08:00

Se debe ser miembro del rol SharePoint_Shell_Access de la base de datos de configuración de SharePoint. Ver Get-SPShellAdmin y Add-SPShellAdmin.

Abrir SharePoint 2010 Management Shell como administrador

Ingresar lo siguiente:

$passphrase = ConvertTo-SecureString -asPlainText –Force

El sistema preguntará por un string , ingresa la nueva passphrase y presiona enter.

El prompt aparecerá de nuevo, ingresa lo siguiente:

Set-SPPassPhrase -PassPhrase $passphrase -Confirm

Te preguntará de nuevo por la passphrase, ingresala y presiona enter.

Más información:

http://iedaddy.com/2011/01/sharepoint-2010-reset-the-farm-passphrase/

Al activar la feature “Document Id” en la site collection me lanza “Acceso denegado“

2012-02-21T13:22:00.001-08:00

Una vez que se activo la feature “Document ID” a nivel de site collection se desea modificar el prefijo del id de documento generado de forma automática.

Si embargo, al presionar OK lanza el error de “Acceso denegado”

Este error es generado porque el permiso “Create Subsite” ha sido removido de la web application actual.

Pasos para resolver:

Central Administration->Manage Web Applications->Web Application name ->User Permission.
Dentro de la categoría “Site Permission” activar el checkbox de “Create Subsites”.

Más información:

http://sharepoint.mindsharpblogs.com/Brian/archive/2012/02/19/%E2%80%98Access-Denied%E2%80%99-Error-When-Activating-Document-ID-Site-Collection-Feature.aspx

Microsoft IT Showcase para SharePoint Server 2010

2012-02-21T12:48:00.001-08:00

Microsoft IT documenta y publica un conjunto de recursos conocidos como Microsoft IT Showcase, que describe la manera en que se diseñaron e implementaron varias tecnologías y productos de Microsoft.

Fuente:

http://blogs.msdn.com/b/sharepoint_sp/archive/2012/02/20/191-c-243-mo-lo-hace-microsoft-it-compruebe-estos-recursos-de-it-showcase-para-sharepoint-server-2010.aspx

Conocer el tamaño y la cantidad de documentos de una content database

2012-02-21T05:27:00.001-08:00

Ejecutar la siguiente consulta contra la content database deseada:

--"count" and "size" of all docs in your SP2010 contend DB
--run script against your SharePoint 2010 wss_Content..... db
SELECT 
COUNT(*) AS 'Count',
(SUM(CONVERT(bigint,Size))/1024) AS 'Size in kbyte',
((SUM(Size)/1024)/COUNT(*)) AS 'AVG Size per Doc. in kbyte'
from dbo.AllDocs WITH(NOLOCK)
WHERE ID IN 
(
SELECT tp_DocID FROM dbo.AllUserData WITH(NOLOCK)--comment this clause out if you also want include the SP systemfiles
)
AND Size is NOT NULL
AND Extension != '000'
--"count" and "size" of all docs in your SP2010 contend DB group by fileextension
--run script against your SharePoint 2010 wss_Content..... db
SELECT 
COUNT(ID) AS 'Count',
(SUM(CONVERT(bigint,Size))/1024) AS 'Size in kbyte', --covert because of an "int" overflowrisk in a lager db
Extension AS 'Filetype',
((SUM(Size)/1024)/COUNT(*)) AS 'AVG Size per Doc. in kbyte'
from dbo.AllDocs WITH(NOLOCK)
WHERE ID IN 
(
SELECT tp_DocID FROM dbo.AllUserData WITH(NOLOCK) --comment this clause out if you also want include the SP systemfiles
)
AND Size is NOT NULL
AND Extension != '000'
GROUP BY 
Extension 
ORDER BY 'Size in kbyte' DESC

Fuente:

https://www.nothingbutsharepoint.com/sites/itpro/Pages/COUNT-and-SIZE-of-all-your-documents-in-SharePoint-2010.aspx

Tips to optimize SharePoint performance

2012-02-21T05:25:00.001-08:00

Les dejo algunos tips para optimizar la performance. Podrán extender la lectura en las fuentes de los posts:

Tip 1: Separate user and database traffic

But SharePoint places a tremendous amount of demand on SQL -- each request for a page can result in numerous calls to the database, not to mention service jobs, search indexing and other operations.

Tip 2: Isolate search indexing

In order to prevent search and user traffic from conflicting, an additional server may be added to the farm, which is dedicated solely to servicing search queries (in smaller environments, the index server may also serve this function). The farm administrator would then configure the search service to perform crawls only against this dedicated server. This configuration may reduce traffic to the Web front-end servers by as much as 70% during index operations.

Tip 3: Adjust SQL parameters

One quick way to avoid future headaches is to provision the major SharePoint databases on separate physical disks (or LUNs if a storage-area network is involved). This means one set of disks for search databases, one for temporary databases and still another for content databases. Additional consideration should be given to isolating the log files (*.ldf).

Another technique is to proactively manage the size and growth of individual databases. By default, SQL grows database files in small increments, either 1MB at a time or as a fixed percentage of database size (usually 10%). These settings can cause SQL to waste cycles constantly expanding databases, and prevents further data from being written while the databases are expanding. An alternative approach is to pre-size the databases up to the maximum recommended size (100GB) if space is available and set auto growth to a fixed size (e.g. 10MB or 20MB).

Tip 4: Defragment database indexes

SQL Server maintains its own set of indexes for data stored in various databases in order to improve query efficiency and read operations. Just as with files stored on disk, these indexes can become fragmented. It is important to plan for regular maintenance operations, which includes index defragmentation

Tip 5: Distribute user data across multiple content databases

Site collection with thousands of subsites is storing the bulk of the user data from every list in every site in a single table in SQL.

This can lead to delays as SQL must recursively execute queries over one potentially very large dataset. One way to reduce the workload is to manage the mapping of site collections to content databases.

Tip 6: Minimize page size

Tip 7: Configure IIS compression

SharePoint content consists of two primary sources -- static files resident in the SharePoint root directories (C:\Program Files\Common Files\Microsoft Shared\12 for 2007 and \14 for 2010) and dynamic data stored in the content. At runtime, SharePoint merges the page contents from both sources then transmits them inside an HTTP response to the requesting user. Internet Information Server (IIS) versions 6 and 7 both contain various mechanisms for reducing the payload of HTTP responses prior to transmitting them across the network. Adjusting these settings can reduce the size of the data transmitted to the client, resulting in shorter load times and faster page rendering.

Tip 8: Take advantage of caching

Much of the content requested by users can be cached in memory, including list items, documents, query results and Web parts.the SharePoint Object Cache can significantly improve the execution time for resource-intensive components, such as the Content Query Web Part. For example, large objects that are requested frequently, such as images and files, can also be cached on disk for each Web application to improve page delivery times.

Tip 9: Manage page customizations

When customization occurs with Sharepoint Designer, the entire page content, including the markup and inline code, is stored in the database and must be retrieved each time the page is requested. This introduces relatively little additional overhead on a page-by-page basis, but in larger environments with hundreds or even thousands of pages, all that back-and-forth to the database can add up to significant performance degradation.

SharePoint Performance Optimization In 10 Steps for the IT Professional

View more presentations from Joel Oleson

Fuentes:

http://www.networkworld.com/news/tech/2010/052410-tech-update.html

http://www.slideshare.net/joeloleson/sharepoint-performance-optimization-in-10-steps-for-the-it-professional

Agregar servidores de bases de datos a una farm existente

2012-02-21T02:57:00.001-08:00

En algunos escenarios es recomendable que las bases de datos de contenido estén alojadas en servidores de BD separados, el mismo caso se cumple para las BDs de Aplicaciones de Servicio como por ejemplo las BDs del servicio de búsqueda.

En este post explica cómo agregar un servidor de bases de datos a una farm existente: http://geeks.ms/blogs/marchena/archive/2012/02/15/a-241-adir-servidores-de-base-de-datos-a-una-granja-existente.aspx

Paso a describir el procedimiento:

1. Primero debemos instalar un servidor de SQL Server 2008 R2 que disponga de las mismas actualizaciones del servidor de BD que aloja nuestra de BD de configuración (Verificar las actualizaciones). Este servidor debe estar unido al dominio.

2. Una vez que tenemos el servidor listo debemos dar los permisos de dbcreator y securityadmin a las cuentas administradores de la granja (Cuenta de instalación sp_install y cuenta de la granja sp_farm).

3. Habilitar el acceso al puerto 1433 desde el firewall del nuevo servidor de SQL.

4. Verificar la conexión desde el servidor de SharePoint 2010.

5. Configurar el Alias para SQL.

6. Crear una nueva aplicación web.

7. En la sección de Database Server por defecto se mostrará el servidor empleado durante la instalación de la granja.

8. Debemos especificar el alias del nuevo servidor de SQL.

9. Si no hemos dado permisos a las cuentas anteriormente especificadas (sp_install y sp_farm) obtendremos el siguiente mensaje de error:

10. Una vez especificados los permisos de manera correcta, podremos crear la aplicación web sin problemas.

11. Se mostrará el nuevo servidor agregado.

12. La BD se habrá creado sin problemas en el nuevo servidor de SQL.

Fuente:

http://geeks.ms/blogs/marchena/archive/2012/02/15/a-241-adir-servidores-de-base-de-datos-a-una-granja-existente.aspx

Más información:

http://technet.microsoft.com/en-us/library/cc262781.aspx

Añadir servidores de base de datos a una granja existente

2012-02-17T17:27:00.001-08:00

En SharePoint 2010 se administran una gran variedad de bases de datos. Tenemos la BD de Configuración, BDs de Contenido y BDs para las aplicaciones de servicio.

El procedimiento para agregar nuevos servidores de BD a la granja lo obtuve del siguiente enlace:http://technet.microsoft.com/en-us/library/cc262781.aspx

Paso a describir el procedimiento:

3. Habilitar el acceso al puerto 1433 desde el firewall del nuevo servidor de SQL.

4. Verificar la conexión desde el servidor de SharePoint 2010.

5. Configurar el Alias para SQL.

6. Crear una nueva aplicación web.

7. En la sección de Database Server por defecto se mostrará el servidor empleado durante la instalación de la granja.

8. Debemos especificar el alias del nuevo servidor de SQL.

9. Si no hemos dado permisos a las cuentas anteriormente especificadas (sp_install y sp_farm) obtendremos el siguiente mensaje de error:

10. Una vez especificados los permisos de manera correcta, podremos crear la aplicación web sin problemas.

11. Se mostrará el nuevo servidor agregado.

12. La BD se habrá creado sin problemas en el nuevo servidor de SQL.

Fuente:

fuente:

http://geeks.ms/blogs/marchena/archive/2012/02/15/a-241-adir-servidores-de-base-de-datos-a-una-granja-existente.aspx

Creating a Web Part with Custom Properties

2012-02-17T17:05:00.001-08:00

Create a Visual Web Part project in Visual Studio. In the file VisualWebPart1.cs, add your custom properties:

The Personalizable attribute is what tells is the Web Part framework to store this property in the database. The WebBrowsable attribute is what tells the Web Part framework to make this property visible in the Edit Web Part properties pane. The WebDisplayName attribute changes the display name visible within the Edit Web Part properties pane. In this case, if we did not alter the display name, it would appear as CustomProperty. Since we have now altered the display name to include a space, these two words will not run together. The Category attribute will change what section of the Edit Web Part properties pane this setting will appear in. If not specified, the custom property will appear in a Miscellaneous section.

In the file VisualWebPart1UserControl.ascx.cs, add a property to store our custom web part.

Now, back in the VisualWebPart1.cs file, alter the CreateChildControls() method to pass this web part into our user control.

Now, in the VisualWebPart1UserControl.ascx.cs file, update the code to display the value entered for our custom property in a label we have added to our VisualWebPart1UserControl.ascx file.

Now deploy your web part and add it to your page. When we go to edit our web part, we see there is a section called Custom Settings which contains our property.

Upon entering text into this field, hitting OK, and saving the page, we will now see our text appear in the label for our web part.

Fuente:

http://www.thesharepointblog.net/Lists/Posts/Post.aspx?List=815f255a-d0ef-4258-be2a-28487dc9975c&ID=105

Más información:

http://blog.concurrency.com/sharepoint/create-a-custom-web-part-for-sharepoint-2010/

http://allaboutmoss.com/2010/04/05/webpart-development-part-4-creating-custom-web-part-properties/

URL path length restrictions (SharePoint Server 2010)

2012-02-17T16:57:00.001-08:00

There is no limit to encoded URLs in SharePoint Server 2010. The limitations are the following:

260 Unicode (UTF-16) code units – the characters in a full file path, not including a domain/server name.
256 Unicode (UTF-16) code units – the characters in a full folder path, not including the file name and the domain/server name.
128 Unicode (UTF-16) code units - characters in a path component, that is, a file or folder name.
260 Unicode (UTF-16) code units – the characters in a full path, including a domain/server name for use with Office clients.
256 Unicode (UTF-16) code units – the characters in a full path including the domain/server name, for use with Active X controls.

Internet Explorer URL length limitations

Internet Explorer also has limitations that are separate from those in SharePoint Server 2010. Even though you make the SharePoint Server 2010 URL path shorter than the limitations, you might experience an Internet Explorer URL length limitation because of added parameters and encoding of the URL. You must use the most restrictive limitation as a guideline for planning URL lengths.

Both Internet Explorer 7 and Internet Explorer 8 have a maximum URL length of 2,083 UTF-8 characters and a maximum path length of 2,048 UTF-8 characters. However, in Internet Explorer 7, under certain circumstances, the effective URL length limitation is 1024 UTF-8 characters, not 2083 UTF-8 characters. For more information about the URL length limits in Internet Explorer, see Microsoft Knowledge Base article 208427, Maximum URL length is 2,083 characters in Internet Explorer (http://go.microsoft.com/fwlink/p/?LinkId=195568&clcid=0x409).

Important:

Unless all of the browsers in the environment are Internet Explorer 8, use the effective limit of 1024 UTF-8 characters.

Resolving URL length problems

There are several ways that you can resolve or mitigate URL length problems in the SharePoint Server 2010 environment. The following list provides suggestions:

Upgrade all the end-user browsers to Internet Explorer 8, which has a longer URL length limit.
Use shorter names for sites, folders, and documents and control the depth of the site and folder structures to reduce the lengths of URLs.
If possible or allowed, use ASCII names for sites, folders, and documents. This will avoid situations where the URL will be lengthened by being encoded.
To reduce the risk that the SharePoint Server 2010 end-users will encounter problems because of URL length limitations, we recommend that you apply the following effective limits in the deployment:
- 256 Unicode (UTF-16) Code units - the effective file path length limitation, including a domain/server name
- 128 Unicode (UTF-16) Code units - the path component length limitation

Más información.

http://technet.microsoft.com/en-us/library/ff919564.aspx

Content DB has been deleted from SQL Server but still get an error 'A SharePoint database named ‘….. ‘ already exists'

2012-02-17T16:54:00.001-08:00

This happened to me after I tried to restore few sites with their content databases from CA. The restoration failed but the content DBs were created in SQL Server but were not displayed in CA. I simply deleted those databases from SQL Server. Unfortunately, this caused me not being able to create a new content DB with the same name from CA. The error message was

'A SharePoint database named ‘….. ‘ already exists'

The solution to this problem was to run the following script on the SharePoint_Config database

Delete FROM Objects WHERE Name = 'name of the ghost db'

Instalar REST en Sharepoint 2010

2012-02-17T14:55:00.001-08:00

wanted to use the new REST services in SharePoint 2010. But when I navigated to the ListData.svc service. I got the following error:

First I checked if there was a System.Data.Services entry in the Global Assembly Cache (GAC). There was one with version 3.5.30729.1. So it wasn’t a case of a missing file.

Searching the web on the error

Could not load type ‘System.Data.Services.Providers.IDataServiceUpdateProvider’ from assembly ‘System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′.

does not provide many hints to what is causing this error. Most sites suggest to install ADO.NET Data Services v1.5 CTP2, but I already had.

I finally found the page REST and SharePoint 2010 Quick Start Guide by Scott Currier. He suggests to install the ADO.NET Data Services Update for .NET 3.5 SP1. As it runs out, this is the final release of the ADO.NET Services v1.5!

The update comes in two flavors.

Download the ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2.

After installing the version of the System.Data.Services.dll file is 3.5.30729.5004.

Download the ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 2000, Windows Server 2003, Windows XP, Windows Vista and Windows Server 2008.

After installing the version of the System.Data.Services.dll file is 3.5.30729.4466.

After I installed the update I browsed to the ListData.svc service.

The service description of a SharePoint 2010 Team Site as atom feed.

Fuente: http://blog.hompus.nl/2010/03/26/could-not-load-type-idataserviceupdateprovider-when-using-rest-with-sharepoint-2010/

Más información:

http://fabiangwilliams.wordpress.com/2010/07/06/errorresolution-could-not-load-type-system-data-services-providers-idataserviceupdateprovider-from/

http://blah.winsmarts.com/2010-4-WCF-ADONET_Data_Services_-_Could_not_load_type_'SystemDataServicesProvidersIDataServiceUpdateProvider'.aspx

Obtener un term de metadata Sharepoint 2010

2012-02-17T14:52:00.001-08:00

Obtener una referencia al término “Newsfeed”

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Taxonomy")
$site = Get-SPSite http://portal.sharepoint.com
$session = New-Object Microsoft.SharePoint.Taxonomy.TaxonomySession($site)
$termStore = $session.TermStores["Connection to: Managed Metadata Service"]
$group = $termStore.Groups["MyTerms"]
$termSet = $group.TermSets["Features"]
$terms = $termSet.GetTerms(100)
$term = $terms | ?{$_.Name -eq "Newsfeed"}

SharePoint Configuration Cache

2012-02-17T14:49:00.001-08:00

1.What is SharePoint Configuration Cache?

The config cache is where we cache configuration information (stored in the config database) on each server in the farm. Caching the data on each server prevents us from having to make SQL calls to pull this information from the configuration database. It is full of XML files containing configuration objects. The SharePoint configuration cache is where configuration information from the SharePoint configuration database is stored on each server in the farm. Caching the data from the config database as XML files on the web front ends and application servers prevents multiple calls to SQL Server thus improving performance. This is a feature in WSS & MOSS 2007 as well as SharePoint 2010.

There is a timer job called “Config Refresh” that updates the cache on SharePoint servers in the farm. Like any other cache, config cache becomes stale over time. Therefore, clearing the cache is needed to get all the SharePoint servers up to date on the latest farm information

Sometimes this cache can become corrupted. This issue can come up when developing timer job definitions . These definitions use this cache, so everytime you deploy new versions of the assemblies, you’ll have to clear the cache. Also, when the cached data becomes out of sync with what’s in the configuration database, timer jobs may start failing. This will occur if the contents of the file system cache on the front-end servers are newer than the contents of the configuration database, so after you perform a system recovery you may have to manually clear the file system cache on a server as well. Another of the reasons your cache could be out of sync is if the Timer service on your servers was stopped or failed unexpectedly.

If you are experiencing issues with WSS/MOSS/SharePoint timer jobs failing to complete or you are receiving errors trying to run psconfig, clearing the configuration cache on the farm or a problem server is a possible method for resolving the issue.

2.How to clear SharePoint Configuration Cache?

a)     Stop the SharePoint 2010 Timer service on ALL of SharePoint servers in the farm.
b)     Log into your Index server.
c)     Navigate to the directory: C:\ProgramData\Microsoft\SharePoint\Config\GUID.
d)     Delete all the XML files from the directory.
CAUTION: DELETE ONLY THE .XML FILES, NOT THE .INI FILE. IF YOU DELETED THE .INI file, see item 3.
e)     Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
f)      Start the SharePoint 2010 Timer service on the Index server and wait for XML files to reappear in the directory.
g)     After you see XML files appearing, repeat steps c, d & e on each query server (one server at a time).
h)     After all of the query servers have all been cleared, repeat steps c, d & e on each of the WFE and application servers in the farm (one server at a time).
Once you are done, go into Central Admin and check your timer job status. You should see a timer job for “Config Refresh”. Verify that this job shows a status of succeeded.

3.I deleted the entire configuration cache directory. Now What?
a)     To recreate the directory, you need to know the directory name (which is a GUID). You can find this GUID in the registry entry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14\Secure\ConfigDB. Copy the GUID from Id attribute and create the new directory: C:\ProgramData\Microsoft\SharePoint\Config\GUID.
b)     In the directory you just created, create another file called cache.INI. Open the file using Notepad and enter the number “1″ without the quotes. Save and close the file.
c)     Start the SharePoint 2010 Timer service on the Index server and wait for XML files to reappear in the directory.

Fuente:

http://blog.christophermichaelwebb.com/windows/clear-the-sharepoint-configuration-timer-cache/348/

http://latenightsp.wordpress.com/2011/03/16/sharepoint-config-cache/

Más información:

OnPostRestore error might be caused by SharePoint Cache

Host header for Web application Sharepoint 2010

2012-02-17T13:10:00.001-08:00

Host header (aka domain names or host names) let you assign more than one site to a single IP address on a IIS Web server. In SharePoint context, may you need individual host-named such as http://thuansoldier.net instead of http://thuansoldier/.

When you create new Web application and then create new site collection, you will make difficulties for end user. They don’t want complicated URL with port number. In this post, I will configure host header via DNS and IIS 7.5. in order to facilitate URL of Web application. All of them are visual but you can use Windows PowerShell to do this rapidly.

Create new Web application

Open Central Administration > Application Management > Manage web applications (under Web Applications). Click New in Ribbon.

I will select Classic Mode Authentication because I haven’t configured Kerberos yet for fully configuring Claim-based Authentication. Under Name, you can type name of Web application. You should name it simply to remember and manage. Please notice under Port and Host Header. Because I want to facilitate URL for end-user thus I select port 80. I continue to type URL: portal.ict24h.net.

At Security Configuration settings, I will keep by default all. Under URL at Public URL, I delete port 80 and keep so as below image.

I use exist application pool. Under Database Name at the Database Name and Authentication, I reduce name of Content database because GUID is so complicated. This make you manage content database effectively.

Now, you can select service application connection and then click OK to create new Web application.

Register the host header in DNS Server

In my DNS server, I create new host A.

Type host name under Name and IP of Web server. Click Add Host.

Configure host header for a Web application

Above all, you check Web applications in Central Administration or IIS Website. Because I will do configuration in IIS thus I will check exist Web application in IIS.

In IIS Manager, right click in Web application that needs to be configured host header and then click Edit Binding. In Site Bindings dialog box, click Edit. At IP address option, select IP address of DNS Server. UnderHost name, type your host name. My domain name is ict24h.net thus I want to use my SharePoint site with this domain name. Click OK.

Open Central Administration > Application Management, under Web Applications , click Configure alternate ccess mappings. Verify that the URL for the default zone is set correctly.

However, when you open portal.ict24h.net whether in Internet Explore 8 or Mozilla Firefox 3.5, you will encounter 404 Page Not Found error. What’s up? Yes, you haven’t created Site collection in your Web application yet. Thus you will encounter this error.

At Central Administration, click Application Management > Create site collections (under Site Collections). Please notice your Web application that you just created namely portal.ict24h.net.

Then configure some information. Open your site collection with URL portal.ict24h.net.

Fuente:

http://thuansoldier.net/?p=1323

Copiar los items de una lista a otra Sharepoint 2010 Server Object

2012-02-17T12:24:00.001-08:00

Más información:

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splist.aspx

Copiar una libreria de SharePoint library usando PowerShell

2012-02-17T12:18:00.001-08:00

Export-SPWeb -Identity http://sp.christianazcon.com.ar -Path "D:\Backup\Libreriabak.dat" -ItemUrl "/Shared%20Documents"
Import-SPWeb -Identity http://sp.christianazcon.com.ar/Test -Path "D:\Backup\Libreriabak.dat"

Determinar que proceso del w3wp es un servicio de Sharepoint

2012-02-17T11:55:00.001-08:00

SharePoint runs its service applications on IIS application pools, which in turn creates multiple w3wp processes running on your servers. When looking at Task Manager, you will see a long list of w3wp processes. Similar to

As you can see in my example above, most of my w3wp processes are using unique accounts, so I can quickly look at this list and know what process belongs to which service account. Per Microsoft’s recommendations for installing SharePoint, using a unique account per service is preferred, and this is one of the benefits.

If we didn’t use a unique account per service, this list would show all the w3wp processes using the same account. Exceptionally uninformative.

What happens if one w3wp processor is pinning the processors? Or if one is taking up apparently large amount of RAM? How do we determine which process belongs to which application pool and which application pool belongs to which SharePoint service application or SharePoint site?

Unfortunately there is easy direct method of finding this out. We utilize a few different tools to get it done.

First, let’s get the PID for each process. This is simple through Task Manager.

Select the View menu, then select Choose columns.
Check off PID.
Click OK.

Your process list will now have a PID column.

Now we need to match up the PIDs to the IIS application pools. Open a command prompt window and go to c:\windows\system32\inetsrv by typing in

cd c:\windows\system32\inetsrv

Next type in

appcmd list wp

This will return a list of all application pools running, with their PIDs.

You’ll see in the list the name of each application pool and their PID. The name will match up to the name in IIS Application Pools. Some of these names should be obvious, as they are similar to your web applications. There are a bunch that are uniquely named using a GUID. These ones are the service applications.

Now let’s find out what GUID belongs to which service application.

Open SharePoint 2010 Management Shell (Start > All Programs > Microsoft SharePoint 2010 Products), and type in

Get-SPServiceApplicationPool | select Id, Name

This will return all service applications and which GUID they are using.

This GUID will match the application pool GUID that we previously saw.

TA DA!

You may also notice that not all of the service applications are being represented in the Task Manager. This is because the services themselves are asleep, and are not running. For example, my Word Automation service isn’t listed in the Task Manager, and since I haven’t used it, it isn’t running. If I were to go in and use it, it would then start up.

Fuente:

http://sp365.co.uk/2012/02/determining-which-w3wp-process-goes-to-which-sharepoint-service/

Using a SharePoint List as a Data Source in SQL Server Reporting Services 2008 R2

2012-02-17T11:50:00.001-08:00

Create a Data Source

When building a report that uses data in a SharePoint list, the Data Source Connection String property must be set to the URL of the SharePoint site or subsite that contains the list you want to use in your report. Right click on the Data Sources node in Report Data and select Add Data Source from the popup menu. Fill in the Data Source Properties General tab as shown below (specify the URL in the Connection string for your SharePoint site or subsite):

Click on Credentials and fill in the dialog as shown below:

Create a Dataset

Once you have a Data Source that points to the URL of a SharePoint site or subsite, the next step is to create a Dataset based on the Data Source. Right click on Datasets in Report Data and select Add Dataset from the popup menu. Fill in the dialog as shown below (select the Data Source created above):

Click on the Query Designer button to display the SharePoint lists in the SharePoint site specified in the Data Source. Select a list and some fields from the list as shown below (I chose an Announcements list):

Note that you can only select fields from one list. Click OK and you will be returned to the Dataset Properties dialog which is now complete:

The Query is displayed as XML and it shows the name of the list and the fields selected.

Más información:

http://www.mssqltips.com/sqlservertip/2068/using-a-sharepoint-list-as-a-data-source-in-sql-server-reporting-services-2008-r2/

Clase SPSiteDataQuery

2012-02-17T11:45:00.001-08:00

Represents a query that can be performed across multiple lists in multiple Web sites in the same Web site collection.

You can use an instance of this class to retrieve data from selected lists or from all lists in the current site collection. Specify the scope of the query by setting the Websproperty. Specify the lists to participate in the query by setting the Lists property and the fields to return by setting the ViewFields property. Control data selection and order by setting the Query property.

To execute the query, pass the SPSiteDataQuery object to the GetSiteData(SPSiteDataQuery) method, which returns a DataTable object containing rows of data that represent the result of the query. Each DataRow object in the DataTable.Rows collection represents a single item that satisfies the query. Each DataColumn object in theDataTable.Columns collection represents a field that is requested in the ViewFields property, and the column name equals the value of the Name attribute for that field. In addition, the data table contains a column named WebId, which identifies the Web site that contains each item, a column named ListId, which identifies the list that contains each item, and a column named ID, which identifies each item.

Importante:

The enumeration value for Contacts is 105.

using System;
using System.Data;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;

namespace SampleWebParts
{
   public class ContactViewer : WebPart
   {
      private GridView grid;

      protected override void CreateChildControls()
      {
         base.CreateChildControls();

         // Add an instance of the grid control.
         this.grid = new GridView();
         this.Controls.Add(this.grid);
      }

      protected override void RenderContents(HtmlTextWriter writer)
      {
         SPWeb web = SPContext.Current.Web;
         SPSiteDataQuery query = new SPSiteDataQuery();

         //Ask for all lists created from the contacts template.
         query.Lists = "<Lists ServerTemplate=\"105\" />";

         // Get the Title (Last Name) and FirstName fields.
         query.ViewFields = "<FieldRef Name=\"Title\" />" +
                            "<FieldRef Name=\"FirstName\" Nullable=\"TRUE\" Type=\"Text\"/>";
        // Note that setting the Nullable attribute to TRUE
        // causes an empty value to be returned for lists that
        // do not include the FirstName column. The default is 
        // to skip a list that does not include the column.

         // Set the sort order.
         query.Query = "<OrderBy>" + 
                           "<FieldRef Name=\"Title\" />" + 
                       "</OrderBy>";

         // Query all Web sites in this site collection.
         query.Webs = "<Webs Scope=\"SiteCollection\" />";

         DataTable dt = web.GetSiteData(query);
         DataView dv = new DataView(dt);

         // Set up the field bindings.
         BoundField boundField = new BoundField();
         boundField.HeaderText = "Last Name";
         boundField.DataField = "Title";
         this.grid.Columns.Add(boundField);

         boundField = new BoundField();
         boundField.HeaderText = "First Name";
         boundField.DataField = "FirstName";
         this.grid.Columns.Add(boundField);

         this.grid.AutoGenerateColumns = false;
         this.grid.DataSource = dv;
         this.grid.DataBind();

         this.grid.AllowSorting = true;
         this.grid.HeaderStyle.Font.Bold = true;

         this.grid.RenderControl(writer);
      }
   }
}

Una recomendacion final es no abusar de SPSiteDataQuery para realizar todo tipo de consultas, 
recuerda que SPSiteDataQuery realiza la consulta en toda una coleccion de sitio, si solamente 
requieres buscar sobre un mismo nivel de sitio es mucho mas recomendable utiliza SPQuery.

Más información: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spsitedataquery.aspx

http://geeks.ms/blogs/haarongonzalez/archive/2007/10/03/spsitedataquery-que-belleza.aspx

http://sadomovalex.blogspot.com/2011/02/problem-with-spsitedataquery-and.html

Crear una página custom de error Sharepoint 2010

2012-02-17T02:33:00.001-08:00

Locate and copy the error.aspx file in Layouts folder of the 14 Hive (%PROGRAM FILES%\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS).

Create a new folder in the Layouts folder (ex. CustomError) and then paste the copied error.aspx file more the next content.

Set-SPCustomLayoutPage -Identity Error -RelativePath “/_layouts/CustomError/error.aspx” -WebApplication <webappURL>

The perform un iisreset.

At any point, you can set the error page back to the default by running the following command and then IISRESET:

Set-SPCustomLayoutPage -Identity Error -WebApplication <webappURL> -Reset

Más información:

http://www.tcscblog.com/2012/02/10/custom-error-page-with-log-support-ticket-link-for-sharepoint-2010/

Obtener el lenguaje de la UI via jquery o javascript

2012-02-17T01:58:00.001-08:00

alert(_spPageContextInfo.currentLanguage);

Setear el lenguaje para un usuario:

<button onclick="OnSelectionChange(1036)"> French </button>
<button onclick="OnSelectionChange(1033)"> English </button>

Más información:

http://techtrainingnotes.blogspot.com/2010/10/sharepoint-2010-playing-with.html

Sharepoint 2010–Orden correcto de instalación

2012-02-17T01:45:00.001-08:00

SharePoint 2010 RTM + SP1 (slipstreamed)
Configure Farm using PowerShell
Office Web Apps RTM + SP1 (slipstreamed)
Run SharePoint Config Wizard (PSConfig) on all severs
SharePoint 2010 Server Language Pack RTM + SP1 (slipstreamed)
Run SharePoint Config Wizard (PSConfig) on all servers
Install OCT 2011 CU (or current recommended CU)
Run SharePoint Config Wizard (PSConfig) on all servers

Additional Note: Sometimes after installing CU’s I’ve noticed errors when trying to run the SharePoint Products Configuration Wizard (PSConfig), like in the screenshot below. In my case the PSConfig wizard was complaining about missing language packs and the CU files, which I could confirm had been installed properly and there before installing the CU. To fix this, I simply forced PSConfig through PowerShell – avoiding the GUI – and it worked like a charm!

psconfig.exe -cmd installcheck -noinstallcheck

There's also IISRESET and rebooting your servers as potential fixes too.

Fuente:

http://sharepoint.jsturges.com/2012/02/correct-installation-order-for-sharepoint-server-2010-farms/

Más información sobre el error:

http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/e4cd8263-26b3-4259-afdf-620acb23dfde

Enable folder creation on a list in Sharepoint

2012-02-17T01:42:00.001-08:00

PS > $spWeb = Get-SPWeb http://sp01/site
PS > $spList = $spWeb.GetList ("http://sp01/site/Lists/MyList")
PS > $spList.EnableFolderCreation = $true
PS > $spList.Update()

Más información:

http://blog.falchionconsulting.com/index.php/2009/07/setting-list-properties-using-stsadm/

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splist.enablefoldercreation.aspx

http://bytes.com/topic/net/answers/867481-trying-create-folder-programatically-doc-library-sharepoint-site

Word Web App cannot open this document for viewing because of an unexpected error (Word Web App no puede abrir este documento por un error inexperado)

2012-02-17T01:37:00.001-08:00

I encountered this error on a newly created site collection

Word Web App cannot open this document for viewing because of an unexpected error. To view this document, open it in Microsoft Word.

One look in SharePoint log files with ULS viewer did not reveal much:

w3wp.exe (0x1A74) 0x22F4 Office Web Apps Office Viewing Architecture b4vn Medium Conversion response received: CantFindSourceDocument 41e96340-f0a6-4b66-b471-83b9d2026d61

The problem was that service account which is used for Office Web Apps, in particular Word Viewing Service Application did not have proper permissions (db_owner) on the content database where the site collection is stored.

After setting the permissions, I got another cryptic error which fortunately I encountered before and was an easy fix

Word Web App encountered an unexpected error

To fix this, just close all browser sessions on the client computer and start over again.

Cause of this error was actually end user interaction. User opened Internet Explorer 9 and accessed a site where documents were stored. After that, user opened same site from the same computer using Firefox 7 and Chrome 14, but with different user account. I guess this somehow messed up credentials on the client computer and Office Web Apps couldn’t display office documents. At the same time, users were able to access same document using Office Web Apps from other computers. Simple client computer restart solved the issue.

Fuentes:

http://sharepoint.tejic.com/2012/02/15/how-to-fix-word-web-app-cannot-open-this-document-for-viewing-because-of-an-unexpected-error/

SharePoint Server 2010–Todas las versiones hasta el 02/12

2012-02-17T01:33:00.001-08:00

Microsoft SharePoint Server 2010
Release	Version	KB	Download
RTM	14.0.4762.1000	n/a	n/a
June 2010 CU	14.0.5114.5003	n/a	n/a
Aug 2010 CU	14.0.5123.5000	2352342
Oct 2010 CU	14.0.5128.2003	2394320
Dec 2010 CU	14.0.5130.5002	2459257
Feb 2011 CU	14.0.5136.5002	2475878
April 2011 CU	14.0.5138.5001	2512800
Service Pack 1	14.0.6029.1000	2460045
June 2011 CU	14.0.6106.5000	2536599	n/a
June 2011 CU (Refresh)	14.0.6106.5002	2536599
August 2011 CU	14.0.6109.5002	2553048
October 2011 CU	14.0.6112.5000	2596505
December 2011 CU	14.0.6114.5000	2597014

Logging in SharePoint

2012-02-17T01:31:00.001-08:00

SPDiagnosticsService.Local.WriteTrace(0, new

SPDiagnosticsCategory(“My category”,

TraceSeverity.Unexpected, EventSeverity.Error),

TraceSeverity.Unexpected, ex.Message, ex.StackTrace);

Your solution might have the minium log level set to higher than “Information” and your entry will not be written if your log level is set too low

If your application is running on one of the front-end Web servers in the farm, the property LOCAL returns an instance of the SPDiagnosticsService class. If an instance of the service does not exist, when you access this property, an instance is created on the local server and the change propagates to all servers in the server farm.

If you are not connected to a front-end Web server in the server farm, the property returns Nothing.

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spdiagnosticsservice.aspx

Identify and clean up orphan sites in sharepoint

2012-02-15T15:47:00.001-08:00

A continuación busco los sitios huerfanos que tengan PWA como URL:

select distinct a.Path, b.name as databasename,a.ApplicationId, b.id as dbid, a.Id

from

[SharePoint_Config].dbo.sitemap as a inner join

[SharePoint_Config].dbo.objects as b on a.databaseid=b.id inner join

[SharePoint_Config].dbo.objects as c on c.id=a.applicationid inner join

[SharePoint_Config].dbo.objects as d on b.parentid=d.id inner join

[SharePoint_Config].dbo.objects as e on d.parentid=e.id

WHERE b.name like '%PWA%'

Fuente:

http://social.technet.microsoft.com/wiki/contents/articles/how-to-identify-and-clean-up-orphan-sites-in-sharepoint.aspx

SharePoint SandBox Solution Execution process

2012-02-12T12:27:00.001-08:00

Sandbox Solutions == user solutions

It is a new feature introduced in SharePoint 2010

Sandbox is a secured wrapper and it has restrictions on code to run in SharePoint environment

Sandbox solution assembly (dll) will be deployed to content database

farm solution assembly (dll) will be deployed(Assembly target type) to GAC (Assemblies run with full trust by default. They are globally installed, so they will work in any Web application) or Web Application (bin – cas policies , tends to available in only one web app)

Physical location of GAC files click Start | Run and type in “c:\windows\assembly\

SandBox Sol can access only data within site collection

Can be uploaded by site collection administration, so no need of farm administrator to install the solution and they can view the resource utilization of each solution and can block if it consumes too much resources. Usually when sites working slow, developers complain the server is slow whereas site/server administrators blame on Develepor code/solutions.
Technically speaking SharePoint solutions run in seperate worker processes and not in w3wp.exe. So It doesn’t require IIS Reset or Application Pool Recycling. Without disturbing the SharePoint site, Sandbox solutions can be deployed. Only thing while deploying new version of Sandbox solution over existing solution, SharePoint will display No Solution found error in Sandbox Webparts on the page. However within seconds sandbox solutions getting deployed and it’ll start working.

User Code processes

SPUCWorkerprocess.exe - Sandbox Worker process service which is a Seperate Service Application which actually executes Sandbox code. It should be started in every farm to use Sandbox solutions.

SPUCWorkerProcessProxy.exe – Sandbox Worker process proxy which is working as a proxy for Worker process and takes care of Sandbox code execution. It can also serve to other farms if configured. Basically it helps site administrator for load balancing.

SPUCHostService.exe – Sandbox User Code Service takes care of user code in Sandbox amd it can be started in the farms where to use Sandbox solutions.

Steps involved in Execution process:

1 – Execution manager on SharePoint server decides which process to use w3wp.exe or SPUCWorkerProcess

2- control is passed to the SPUCHostService.exe process

3- UserCodeHostservice passes the code to sandbox worker process (SPUCWorkerProcess.exe)

Here untrusted code is validated against the limited available subset of object model

If it succeeds the operation is performed by the full, non sandbox object model

when u create a visual studio project, visual studio build process(compilation) is done using full object model,so if u used full object model namespace.. u can’t catch them during build process

Exceptions in sand boxed solutions :

Projects or item types which are used for more than one site or adds files to file system

Site Definition projects
Visual webpart ( in this user controls are deployed to file system)
BCS Models
Application pages
workflow with custom code
In code we cannot use SPFarm and SPServcie objects and cannot use spsite for accessing other site info by passing URL in constructor
No Security Elevation – RunWithElevatedPrivileges which runs the specified block of code in application pool account(typically System Account) context is not allowed in Sandbox code. SPSecurity class also not allowed to use in Sandbox.
No Email Support – SPUtility.SendMail method has been blocked explicitly in Sandbox, However .Net mail classes can be used to send mails. Additionaly sandbox won’t allow to read Farm SMTP address. So developers has to specify the SMTP address in code itself(may be some other workaround).
No Support to WebPartPages Namespace – Sandbox won’t allow to use Microsoft.SharePoint.WebPartPages namespace.
No Support to external Webservice – Internet web service calls are not allowed to ensure security in Sandbox solutions. Allow Partially Trusted code also can’t be accessed within Sandbox.
No GAC Deployment – Sandbox solutions are not stored in File System(Physical path) and assemblies can’t be deployed to Global Assembly Cache(GAC). But it’s available on C:\ProgramData\Microsoft\SharePoint\UCCache at runtime. Note the ProgramData is a hidden folder.
No Visual Webparts – Visual Studio 2010 by default won’t allow to create Visual Webparts to deploy as sandbox solution. But with Visual Studio PowerTools extensions(downloadable from Microsoft MSDN website) Visual Webparts can be developed and deployed as sandbox Solutions.

Benefits of sandboxed solutions

Can be uploaded ,deployed by Site collection admin and can be managed easily

Management of user solutions

By navigating to solution gallery – activate ,deactivate, upload, delete, can verify the resource usage

Fuente:

http://niranjanrao.wordpress.com/2012/02/08/sharepoint-sandbox-solution-execution-process-2/

Renombrar Servidor de Sharepoint

2012-02-12T12:15:00.001-08:00

1. Usar Rename-SPServer (http://technet.microsoft.com/en-us/library/ff607556.aspx)

2. Pero si se ha renombrado el server por eje: en el caso de máquinas virtuales clonadas

Solución:

1.Asegúrese de que usted es un miembro del grupoAdministradores local en el equipo local para poder ejecutar Stsadm.

2.En la unidad donde está instalado SharePoint Server 2010,vaya al directorio siguiente: %COMMONPROGRAMFILES%Microsoft sharedWeb server extensions14Bin.

3.Escriba el siguiente comando y, a continuación, presione ENTRAR: stsadm -o renameserver -oldservername <oldServerName> -newservername <newServerName>

Nota:
No se recomienda el uso de Rename-SPServer cmdlet, ya que no funcionará si el servidor en el que se almacena la base de datos de configuración que ya se ha cambiado el nombre.

And when you run PowerShell on your server you get the following error: The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.

Recordar cambiar Alternate Access Mappings

Más información:

http://technet.microsoft.com/en-us/library/cc261986.aspx

Display the sandboxed solutions service configuration settings

2012-02-12T12:06:00.001-08:00

You can use this procedure to display the tiers that have been configured for the sandboxed solutions service and to display the worker processes, application domains and other properties that are currently configured for each tier. You can append this script to the script in the previous procedure, or you can use it as a stand-alone script.

#Loop through and show the user what exactly has been created

$uc=[Microsoft.SharePoint.Administration.SPUserCodeService]::Local

Write-Host "The following tiers have been created"
Write-Host "***********************************************************"

foreach($tier in $uc.Tiers)
{      Write-Host "Tier Name: $($tier.Name)"      Write-Host "Tier MaximumWorkerProcess: $($tier.MaximumWorkerProcesses)"      Write-Host "Tier MaximumConnectionsPerProcess: $($tier.MaximumConnectionsPerProcess)"      Write-Host "Tier MaximumAppDomainsPerProcess: $($tier.MaximumAppDomainsPerProcess)"
     Write-Host "Tier PriorityPerProcess: $($tier.PriorityPerProcess)"      Write-Host "Tier ResourceMaxValue: $($tier.ResourceMaxValue)"      Write-Host "***********************************************************"
}

Más información:

http://technet.microsoft.com/en-us/library/hh230317.aspx

Esquema Regional Settings

2012-02-12T12:02:00.001-08:00

El esquema Regional Settings se usa para definir las zonas horarias, las configuraciones locales, los idiomas y las monedas de una implementación de SharePoint Foundation. Este esquema se expresa principalmente mediante dos archivos ubicados en el directorio de instalación, a saber, RGNLSTNG.XML (%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\1033\XML) y TIMEZONE.XML (%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\CONFIG).

Actualizar manualmente la definición horaria:

http://support.microsoft.com/kb/943663

Actualizar manualmente el período de horario de verano de una definición de zona horaria:

http://support.microsoft.com/kb/888253/es

Más información:

http://msdn.microsoft.com/es-es/library/aa979616.aspx

Remover base de datos de Servicios renombradas

2012-02-12T11:51:00.001-08:00

Renombrar bases de datos de servicios:

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=233

http://technet.microsoft.com/en-us/library/ff851878.aspx

Renombrar bases de contenido

http://blogs.technet.com/b/wbaer/archive/2008/06/16/renaming-content-databases.aspx

Renonbrar bases de Sharepoint

http://blogs.technet.com/b/seanearp/archive/2009/03/14/renaming-crazy-sharepoint-database-names.aspx

Cuando se han renombrado las bases de datos, pueden seguir apareciendo como bases de datos de Sharepoint pueden chequearse en http://central_admin_url/_admin/DatabaseStatus.aspx.

Para borrar esas bases de datos, puede hacerlo con powershell:

# check to ensure Microsoft.SharePoint.PowerShell is loaded

$snapin = Get-PSSnapin | Where-Object {$_.Name -eq

'Microsoft.SharePoint.Powershell'}

if ($snapin -eq $null) {

Write-Host "Loading SharePoint Powershell Snapin"

Add-PSSnapin "Microsoft.SharePoint.Powershell"

}

Get-SPDatabase | Where{$_.Exists -eq $false} | ForEach {$_.Delete()}

Instalación de Sharepoint–Cuentas locales

2012-02-12T11:45:00.001-08:00

Al instalar una instancia de Sharepoint y SQL Server en un mismo servidor, en el momento de la configuración con PSCONFIG, nos lanzará el siguiente error al agregar una cuenta de farm.

The specified user xxxx\yyy is a local account. (el usuario especificado es una cuenta local)

Local accounts should only be used in stand alone mode. (cuentas locales deben usarse en mode stand alone)

Solución:

New-SPConfigurationDatabase
Cargo los datos indicados

Posibles errores:

New-SPConfigurationDatabase: Could not load file or assembly ‘Microsoft.IdentityModel, Version 3.5.0.0. The Power Shell looks like the following when you’re running New-SPConfigurationDatabase to configure your SP database for the first time:

Could not load Microsoft.IdentityModel

The fix: Install Microsoft Identity Framework to address this problem.

New-SPConfigurationDatabase: The user does not exist or is not unique. You get to the point in the New-SPConfigurationDatabase command-let that asks you for the Farm Credentials. You didn’t fully qualify the username with the domain or computer name.

New-SPConfigurationDatabase - user does not exist

To fix this, simply make sure that the user account you are specifying for the Farm Credentials is fully-qualified with the domain-name or, if using local accounts, the computer name. Example: “macbookpro\gabe”.

New-SPConfigurationDatabase : Unknown error (0×80005000) At line: 1 char:20. + New-SPConfigurationDatabase <<<< + CategoryInfo : InvalidData

Unknown error when running New-SPConfigurationDatabase

Fuente:

http://sharepoint.microsoft.com/blogs/fromthefield/lists/posts/post.aspx?id=112

Enable ASP.NET Session State on SharePoint 2010 Application

2012-02-12T11:32:00.001-08:00

Hace un tiempo escribí un post del Objeto Session:

http://todosharepoint.blogspot.com/2012/01/sharepoint-2010-objecto-session.html

ASP.NET Session state is disabled by default in SharePoint 2010 installation. Although it may not require in typical SharePoint 2010 installations, there may be need in custom solutions & web parts built on top of SharePoint 2010 framework where developers required persisting information per user session.

How really ASP.NET Session State works in SharePoint?

As many of you are aware, ASP.NET allows persisting session states in three different medium – on server memory as a inproc which would require server & load balancer affinity, on SQL Server to persist session in database, or on Session State Server to persist session on dedicated server memory. Both SQL Server and Session State Server would support server farm environment and because SharePoint is the multi-server farm environment based on ASP.NET framework, by default, it can be enabled to use SQL Server and SqlSessionStateStore provider to persist session state.

Should I really worry if ASP.NET Session State is enabled on my SharePoint farm?

It depends on many factors like how many concurrent users will be accessing site or heavy vs. average vs. low usage of session objects. If you really need to persist user session information and if you can store them in other mediums like cookies, ASP.NET Session state may not be necessary. Since SharePoint is built on top of ASP.NET framework, ASP.NET Session state would be ideal place to persist user sessions. Since ASP.NET Sessions gets stored in the SQL Server, heavy usage of session state may require detailed database planning, regular truncating/maintenance/cleanup of expired session state data, or fine tuning of default 60 minute session expiration time. Great thing about this service is even though it’s enabled on whole farm, it’s not used unless specific application is activated to use session state and you have full control & visibility of how ASP.NET sessions gets stored in SharePoint.

How do I enable ASP.NET Session State in SharePoint?

ASP.NET Session state is available to the SharePoint environment by enabling “SharePoint Server ASP.NET Session State Service” service application on the SharePoint farm. You can’t enable this service application using central administration browser interface. You must enable it using PowerShell command.

Step 1: Enable ASP.NET Session State Service

To enable ASP.NET session state, log on the Central Admin Server using Farm Admin Account, and

Either Run PowerShell command “Enable-SPSessionStateService –DefaultProvision” to create service application with default state. By default, this will create service application database with “SessionStateService_<GUID>”, on the same database server where farm configuration database is located using windows credentials of the logged in user.
Or Run PowerShell command “Enable-SPSessionStateService -DatabaseServer YourDBServerName -DatabaseName YourDBName” to create service application with specific database name on non-SharePoint configuration database server. For more details and additional parameters, please visit Enable-SPSessionStateService http://technet.microsoft.com/en-us/library/ff607857.aspx.

By enabling Session State Service on your farm,

It would create database on specified server – SessionStateService_<GUID>

It would create SharePoint Server ASP.NET Session State Service in Manage Service Applications

It would add module in all web applications on farm – <add name=”Session” type=”System.Web.SessionState.SessionStateModule” />

It would add sessionstate entry in all web applications on farm

Step 2: Activate ASP.NET Session State on SharePoint Web Application

By enabling ASP.NET session state service in the SharePoint farm, every SharePoint web application in the farm ready to use ASP.NET session framework. To ensure SharePoint web application gets activated to persist ASP.NET sessions, you have to manually update Web.Config file for the specific SharePoint web application on all servers in the farm. - <pages enableSessionState=”true”

Step 3: Although this may not be necessary, performing IISReset on all the servers would help resetting all the sessions.

How would use ASP.NET Session State Service in Code?

This is straightforward. You can access ASP.NET session state object using HTTPConext.Current.Session and use the ASP.NET session state same as typically ASP.NET Session Management. Here is the sample code which would create new ASP.NET session object called “SampleSessionKey”, if it doesn’t exists.

if (HttpContext.Current.Session["SampleSessionKey"] == null) { HttpContext.Current.Session.Add(“SampleSessionKey”, “SampleSessionValue”); sessionVal.Text = “SampleSessionKey is added.”; } else { sessionVal.Text = “SampleSessionKey is already exists.”; }

After you run above code, this is what you would see in the ASP.NET Session State Service Application database. By default, it would create session for 60 minutes. If you want to increase or decrease session expiration, you have to pass “SessionTimeout” parameter while creating ASP.NET Session State Service using Enable-SPSessionStateService command.

Additional References

Session State Management in SharePoint – http://msdn.microsoft.com/en-us/library/ff648090.aspx
Using Session State in SharePoint 2010 – http://blogs.msdn.com/b/markarend/archive/2010/05/27/using-session-state-in-sharepoint-2010.aspx
How to enable Session State in SharePoint 2010 – http://moustafa-arafa.blogspot.com/2010/05/how-to-enable-session-state-in.html
Enable session state for SharePoint Server 2010 and Foundation – http://code-journey.com/2011/enable-session-state-for-sharepoint-server-2010-and-foundation/
SharePoint 2010 Session Management – http://blog.petercarson.ca/Pages/SharePoint-2010-Session-Management.aspx
SharePoint 2010 FBA and Sliding Sessions – http://blogs.msdn.com/b/scicoria/archive/2011/06/10/sharepoint-2010-fba-and-sliding-sessions.aspx
SharePoint 2007 – Improve ASP.NET Session State performance –http://blogs.technet.com/b/patrick_heyde/archive/2009/12/22/sharepoint-2007-improve-asp-net-session-state-performance.aspx

Fuente:

http://nikspatel.wordpress.com/2012/02/12/enable-asp-net-session-state-on-sharepoint-2010-application/

Funcionamiento de Client Object de manera gráfica

2012-02-11T03:26:00.001-08:00

Clases Sharepoint Development Server Object

2012-02-11T03:23:00.001-08:00

Algunas clases que deberías conocer para empezar a desarrollar soluciones del lado del servidor de Sharepoint.

Alias para el SQL SERVER

2012-02-10T14:29:00.001-08:00

The use of SQL Server names and/or addresses in difficult-to-alter SharePoint database connection strings is what makes this situation problematic.

You can get some protection and peace-of-mind for this type of scenario by utilizing SQL Server aliases on each of your SharePoint servers. Aliases act as an abstraction layer between your SharePoint servers and your SQL servers. So, instead of this:

SharePoint => SQL Server You end up with this: SharePoint => Alias => SQL Server

In this scenario, pointing your SharePoint member servers to a different back-end SQL Server is as simple as changing one or more SQL aliases. In effect, your SharePoint farm becomes decoupled from the SQL Server(s) it uses.

SQL Server aliases can be created and maintained easily using the SQL Client Network Utility (cliconfg.exe) or the SQL Server Configuration Manager which is installed with the SQL Client Tools.

To do this we should run the SQL Server Client Network Utility (which is installed on every SharePoint machine).

Start… Run..
Type cliconfg and click OK.
Click TCP/IP and then the Enable >> button.
Click the Alias tab.
Click the Add button.
Select the TCP/IP radio button.
Enter the alias you wish to use (e.g. SHAREPOINT) in the Server alias text box.
Enter the address of your instance (e.g. SQL1\SHAREPOINT) in the Server name text box.
Deselect the Dynamically determine port check box.
Enter the port of your instance (e.g. 1433) in the Port number text box.
Click OK to save the alias.
Click OK to save the configuration and close SQL Server Client Network Utility.

Fuente:

http://secretsofsharepoint.com/cs/blogs/tips/archive/2012/02/10/using-sql-aliases-in-your-sharepoint-farm-for-sharepoint.aspx

OSearch14 VSS Writer No aparece

2012-02-10T14:07:00.001-08:00

Cuando se ejecuta vssadmin list writers y no aparece OSearch14 VSS Writer hay que hacer lo siguiente:

1. Abrir regedt32.exe en el servidor

2. Ir a HKLM/System/CurrentControlSet/Services/VSS

3. Click derecho sobre la key VssAccessControl y agregar un Nuevo valor DWORD (32-bit)

4. Agregar domain\username de la cuenta del search como nombre, y setear el valor a 1

5. Click derecho sobre la key Diag y setear los permisos: agregar la cuenta de usuario del search y darle full control

6. En el CMD: net stop osearch14. Y después : net start osearch14.

Improving SharePoint’s Performance

2012-02-10T02:25:00.001-08:00

The database

The database is a common area where performance hits are most prevalent. SharePoint is database intensive, about 95% of SharePoint is stored in a SQL database: files, images, videos, pages, content, user profiles, etc. It’s important to have a happy and health SQL database running.

Things to do or check

Make sure databases are running on RAID5 or RAID10 partitions. These two RAID configurations provide the fasted throughput for constant read/write activities. If you’re on a RAID1, consider moving your databases.
Check your drive’s free space. Make sure you have several gig available. If it gets too small SQL still start acting funny, and slower. If it get to a gig or under it’ll stop working all together.
Check your content database size and growth properties in SQL Server Management Studio. If these are set too low, then SQL has to resize itself a lot and that can slow it down.

To check your database properties

Connect to the database server using Microsoft SQL Server Management Studio.
Right click your database and select Properties.
Go to Files on the left.
You should now see 2 rows for your database.
Select the one with a File Type of Rows Data.
- This represents your database file, where all the stuff is stored.
- Note the initial size. If this site is new and young and doesn’t have much on it, set that initial size to an estimated file size for the future. If it’s an existing content database with a load of data, don’t worry about the initial size. By setting this above and beyond, it’ll resize the database now, instead of later.
- Note the Autogrowth setting. Modify this to be 25%-50%, higher if the site will be loaded up with a lot of data coming soon. Again, this will resize the database once and cover a lot of data. The default property values requires SQL to resize frequently, and therefore imped performance of the server while it’s resizing.
Now select the File Type Log.
- This represents your transaction logs. As items are being written to and from the database file, the transaction log keeps a log of it, in the event of a database failure, you can technically restore back to the last transaction. This log can grow exceptionally large depending on traffic on your sites.
- Following the same rules as above, the initial size should be around 25% of the data file initial size.
- Set autogrowth to 25%-50%, again depending on amount data that will be loaded.
If possible, these two files should be on different physical disks, not just different logical disk partitions.
- This might be difficult as most servers have a single RAID container. In larger implementations, if you have additional drives available, separate the data and log files. Moving them onto their own physical disks or disk arrays, the drives can spin independent of each other, therefore improving performance.
Next, go to Options on the left
The Collation option should be Latin1_General_CI_AS_KS_WS (SharePoint’s preferred setting).
- This setting handles how the database treats some finer settings like case sensitivity. If the database was created by SharePoint, you’re fine. If a DBA or someone else made the database first, this might not be set correctly.
Click OK.
Expand System Databases on the left, and do the same as the above to the tempdb.
- The tempdb is a temporary location data is handled while it waits for other processes to finish. The tempdb prefers RAID10 over all.

Another consideration for improving database performance is RBS, I go into greater detail on RBS in this post.

SharePoint Logs

SharePoints logs are usually on the drive it was installed on, and in most cases that’s the C drive of the server. It’s recommended to moved these logs to another partition, and preferably different drives altogether.

Go to Central Administration > Monitoring > Configure Diagnostic Logging.
- Note the top part, Event Throttling. This specifies what SharePoint will log. If any of these have been changed from default, they’ll be in bold. Your ideal settings for all of them are
- Least critical event to report to the event log: Information
- Least critical event to report to the trace log: Medium
- In the next section, Event Log Flood Protection, make sure that’s checked.
- And in Trace Log section, feel free to move the logs to a different drive to either free up space on the current drive or to a unique drive. You may limit the amount of days or space the logs use per your preference.
- Click OK.

Large lists are slow

If you have lists that have several thousand records in them, those lists may run slow as you load views. Other lists which use your large lists in a lookup field may also slow down as it has to process all of the records.

You can enable indexing on your SharePoint fields within your lists to improve lookup speeds and page loads. Go to your list settings, then under the column list is a link Indexed Columns. Select your columns that you will be searching against, creating filtered views with or using in lookups.

Keeping it alive

This issue is less of an issue as it’s just how technology works. If SharePoint (rather the services running SharePoint: IIS) runs idle for a set amount of time, usually 20 minutes, the services will go to sleep and cache is cleared. As a result, when a user goes to access SharePoint, the services have to start up, and build the cache again. This can set an initial load to take several seconds, which to an end user can be forever. There’s a neat little application available athttp://spwakeup.codeplex.com/ which tickles your sites to keep them awake.

Funky Code

How many custom features are you using? Does it seem to slow down when they’re in use? This might be hard to determine as a highly used site might be hitting custom code left and right. If you’re a developer, or want to tell your developer something, check these out

Make sure all SPSite and SPWeb objects are disposed of cleanly. There is a free tool which will check your compiled solution for you, download SPDisposeCheck here http://archive.msdn.microsoft.com/SPDisposeCheck.
If you’re adding new items to a list that has thousands of records, don’t simply perform SPList.Items.Add(). This will actually load all your items into memory, then create a new record. Instead, do something like SPQuery qryEmpty = new SPQuery() { Query = “0″ }; SPList list = web.lists["Name"]; SPListItem newItem = list.GetItems(qryEmpty).Add(); This will load an empty results set first, then give you a new item. Also, check out the note above on Large lists are slow.
Check the status of workflows, ensure they aren’t looping. This is a common issue with developing custom workflows. If the workflow updates the item the workflow is running on, it’ll loop because it was updated again. And around and around you go. Make sure to include some validators in your workflow to ensure you want to perform the update, not just update it.
Check out http://bestofcyber.wordpress.com/2008/10/16/best-coding-techniques-to-improve-performance-for-sharepoint-applications/ for some more information on improving your code.

Fuente:

http://davidlozzi.com/2012/01/19/improving-sharepoints-performance/

Send email from Powershell with attachment SQL Server

2012-02-08T02:53:00.001-08:00

Este script puede ser útil para un SQL Server utilizado por Sharepoint

$emailFrom = "jvamvas@sqlserver-dba.com"
$emailTo = "jvamvas@sqlserver-dba.com"
$subject = "SQLServer-DBA.com: Powershell Function calling an SMTP server with attachment"
$body = "SQLServer-DBA.com : Send an email through SMTP in Powershell with attachment "
$smtpServer = "mysmtpserver"
$filePath = "C:\sql_server_health_sqlserver_jobs_2012-02.html"

Function sendEmail([string]$emailFrom, [string]$emailTo, [string]$subject,[string]$body,[string]$smtpServer,[string]$filePath)
{
#initate message
$email = New-Object System.Net.Mail.MailMessage
$email.From = $emailFrom
$email.To.Add($emailTo)
$email.Subject = $subject
$email.Body = $body
# initiate email attachment
$emailAttach = New-Object System.Net.Mail.Attachment $filePath
$email.Attachments.Add($emailAttach)
#initiate sending email
$smtp = new-object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($email)
}

#Call Function
sendEmail $emailFrom $emailTo $subject $body $smtpServer $filePath

Fuente:http://www.sqlserver-dba.com/

SharePoint 2010: Debugging Visual Studio 2010

2012-02-07T16:27:00.001-08:00

Method I:

Go to “Debug” and select “Attach to Process”
Make sure “Show processes in all sessions” checkbox is checked
Select all “w3wp.exe” processes and click on “Attach” button

If it does not work,

Go to “Debug” and select “Attach to Process”
Click on “Select…”.”Select Code Type” window will appear
Select “Debug these codes types” and check “Managed (v2.0, v1.1, v1.0)” only

Method II:

Write “System.Diagnostics.Debugger.Launch()” in the code where you want to attach debugger
When you run the code, a popup window will appear asking for attaching debugger.
Click “Yes” and guide to appropriate instance of Visual Studio

Method III:

Use third party software like:

Visual Studio 2010 extension for helping SharePoint 2010 debugging

Fuente:

http://farhanfaiz.wordpress.com/2012/02/07/sharepoint-2010-debugging-visual-studio-2010/

Site Collections vs Sites vs Web Applications

2012-02-07T01:44:00.001-08:00

Using separate Site Collections for your sites provides several benefits

Pros

Unique set of users and permissions
Unique and separated content databases are possible, which allow for multiple large (200GB+) sites
Unique set of workflows, site content types, site columns
Unique quotas
All farm services are shared
Upgrade to next version can be done in a phase approach

Cons

No out of the box solution to roll up data from site to site
If using separate content databases, increase farm administration tasks to backup each database/site
Navigation is tougher, no automatic hierarchy or inheritance between site collections
Solution management and deployment is harder as each site collection needs to be activated individually

Using a single site collection with Sub Sites has its share of benefits as well

Pros

Easier data propagation and collaboration, share data and content from site to site
Shared permission management across all sites
Single content database makes backing up easier
True site hierarchy and navigation

Cons

Single content database, could be a size issue down the road. MS recommended content database size is 200GB, however you can get away with much more
Permission management can get chaotic if the amount of users and sub sites are high
Restoring a content database will mean that the entire site is down
Potentially longer restore times as the database would be larger
When database size limitations are approached, moving a site to a new site collection is possible, however that means a new URL for the end user.

In addition to separating out site collections, you can also consider separating web applications. By using multiple web applications, you can separate site collections as well as other farm features

Pros

Services like User Profiles, Metadata, Business Data, etc. can be unique per web application
Separate authentication methods
Use of different security policies and user permissions
Other finer details like recycle bin retention, outgoing email server, resource throttling, etc.

Cons

Each web application uses additional memory
IIS management cost increases as each web application is a new website

Fuentes:http://sp365.co.uk/2012/01/initial-topology-planning-site-collections-vs-subsites/

SharePoint Dispose tool

2012-02-05T18:26:00.001-08:00

SPDisposeCheck is a tool that helps developers and administrators check custom SharePoint solutions that use the SharePoint Object Model helping measure against known Microsoft dispose best practices. This tool may not show all memory leaks in your code and may produce false positives which need further review by subject matter experts.[1]

Install SharePoint Dispose tracker tool.

Make sure you have installed Microsoft visual Studio 2010. Then run installer file SPDisposeCheck.exe.

After install successfully, you will able to find SPDisposeCheck Addin in Visual Studio 2010 Tools menu.

Configure the project what you analyze

Click SharePoint Dispose Check, get SPDispseCheck setting form.

Select the project what you analyze and treat problem type.

Check “Execute After Build” and the assemblies to analyze file.

Save it.

Analyze the code

Open the project, then check below code.

Build the project, the SPDispose Check tool will execute auto.

Go to View menu->Error List. You will see the error; this reason is in this code I did not disposed the objects properly.

Double click the error, you will locate to the incorrect code. Then you are able to correct it.

You also can get help to how to fix the error by select “Show Error Help” in right-menu of the error.

After click Show Error Help, will auto direct to the page(http://blogs.msdn.com/b/rogerla/archive/2008/02/12/sharepoint-2007-and-wss-3-0-dispose-patterns-by-example.aspx)

Fix above code according to the help.

Recheck the code, no error appear.

Index:

[1]. http://archive.msdn.microsoft.com/SPDisposeCheck

Fuente:

http://www.sharepointboost.com/blog/how-to-monitor-sharepoint-performance-issue/

Procedimientos recomendados para virtualización (SharePoint Server 2010)

2012-02-05T14:14:00.001-08:00

1. Usar la virtualización asistida por hardware

Si el procesador del equipo host admite la virtualización asistida por hardware (HAV), habilite esta opción. HAV ayuda a mejorar el rendimiento del software de virtualización y los tiempos de respuesta de la aplicación. En función de la carga de trabajo, HAV puede proporcionar un incremento del rendimiento igual o superior al 5%. Puede usar la herramienta de detección de virtualización asistida por hardware (http://go.microsoft.com/fwlink/?linkid=219550&clcid=0xC0A) de Microsoft para determinar si el procesador de un equipo admite HAV y si esta configuración está habilitada.

HAV se proporciona a través de la familia de procesadores con tecnología de virtualización de Intel (Intel VT) y la familia de procesadores con tecnología de virtualización AMD (AMD-V).

2. Habilitar hyperthreading en los procesadores que admiten esta tecnología

Hyperthreading es una tecnología que se encuentra disponible en los procesadores que admiten multithreading simétrico (SMT). Esta tecnología proporciona dos subprocesos para cada núcleo del procesador. El resultado final es el duplicado de los procesadores lógicos de cada núcleo.

Las pruebas de rendimiento en un servidor de 8 núcleos con hyperthreading habilitado mostraron un incremento de rendimiento, en promedio, del 16% en una carga de trabajo que no es específica de Microsoft SharePoint Server 2010.

Para obtener más información, vea Requirements and Limits for Virtual Machines and Hyper-V in Windows Server 2008 R2.

3. Configurar correctamente el acceso a memoria no uniforme

El acceso a memoria no uniforme (NUMA) es un diseño de memoria para equipos usado en los multiprocesadores para mejorar el rendimiento mediante la reducción de la latencia de acceso a memoria y el aumento del ancho de banda de memoria. Para obtener más información, vea el tema Descripción del acceso no uniforme a memoria(http://go.microsoft.com/fwlink/?linkid=164492&clcid=0xC0A) y el tema Cambios del kernel de Windows Server 2008 (http://go.microsoft.com/fwlink/?linkid=219551&clcid=0xC0A).

No obstante, si el tamaño de los límites de NUMA no se ajusta correctamente, el rendimiento puede verse reducido. Asegúrese de que a las máquinas virtuales de un servidor host que admite NUMA se les asigne la cantidad correcta de memoria en relación con el límite de NUMA. Para calcular el límite de NUMA, se divide la memoria del servidor host por el número de sockets del procesador. El rendimiento disminuye aproximadamente un 8% cuando la asignación de memoria de la máquina virtual es mayor que el límite de NUMA.

4. Configurar el host de Hyper-V para un rendimiento óptimo

Use las siguientes recomendaciones para configurar el servidor host de modo que el rendimiento sea óptimo.

Dedique el equipo host a Hyper-V. No ejecute aplicaciones adicionales en el host.
Instale y configure sólo los roles y servicios obligatorios.
No almacene los datos de la máquina virtual en las unidades del sistema. La partición raíz debe contener solamente el sistema operativo y Hyper-V.
Use más de un adaptador de red en el servidor físico y dedique un adaptador a la administración de Hyper-V Server. No enlace ninguna red virtual a este adaptador. Si las máquinas virtuales comparten un adaptador de red, supervise la latencia y el rendimiento para asegurarse de que no se sobrecargue el adaptador.

5. Mantener la compatibilidad de versiones de los servicios de integración

Para lograr un rendimiento óptimo, asegúrese de que el sistema operativo de administración y el sistema operativo invitado ejecuten la misma versión de los servicios de integración. Para actualizar los servicios de integración de un sistema operativo invitado a una versión más reciente, realice la actualización cuando la máquina virtual se esté ejecutando en la versión de Hyper-V que incluya la versión de los servicios de integración a la que desea actualizar. Para obtener más información, vea Version Compatibility for Integration Services.

No implemente en el mismo host máquinas virtuales que admiten servicios de integración junto con máquinas virtuales que no pueden usar servicios de integración.

6. Determinar las opciones de almacenamiento que se basan en cargas de trabajo y roles de máquinas virtuales

Hyper-V admite dos opciones de almacenamiento para máquinas virtuales: almacenamiento físico adjunto (también conocido como discos de paso a través) y discos duros virtuales (VHD).

Los discos de paso a través pueden ser de almacenamiento local o una red de área de almacenamiento (SAN). Estos son ligeramente más rápidos que los VHD. Si usa almacenamiento físico, desaprovecha las ventajas de los VHD, como la portabilidad, las instantáneas y el aprovisionamiento fino.

Nota:

Como procedimiento recomendado, no use instantáneas en un entorno de producción.

Se recomienda que use los discos de paso a través únicamente cuando el requisito de almacenamiento de una máquina virtual supera los 2 terabytes o cuando la aplicación de la máquina virtual es de entrada y salida. Un buen ejemplo es un servidor de bases de datos de SQL Server frente a un servidor front-end web.

De las tres opciones de discos duros virtuales (de tamaño fijo, de expansión dinámica y de diferenciación), se recomiendan los discos de tamaño fijo. Los discos de tamaño fijo proporcionan el mejor rendimiento global y reducen el riesgo de superar el espacio de almacenamiento físico cuando un VHD de expansión dinámica no se supervisa cuidadosamente.

Nota:

Únicamente instale el sistema operativo base en la unidad de arranque IDE. Use unidades de disco duro SCSI virtuales para el almacenamiento de datos y programas adicionales. Una máquina virtual (VM) configurada para usar un controlador SCSI le permite agregar unidades de disco duro sin necesitad de apagarla.

Para obtener más información acerca del almacenamiento de la VM, vea:

Planning for Disks and Storage
Rendimiento del disco duro virtual (http://go.microsoft.com/fwlink/?linkid=186519&clcid=0xC0A)

7. Establecer la configuración general de la máquina virtual para mejorar el rendimiento y la estabilidad

Configure las opciones generales y específicas de la VM para lograr un rendimiento y una estabilidad óptimos. Se recomiendan las siguientes configuraciones:

Inicio
Si las VM están configuradas para iniciarse automáticamente, use un retraso para reducir la contención en el host.
Apagado
No guarde el estado antes del apagado; permita que la VM se apague del mismo modo que un equipo físico.
Sincronización del reloj
No sincronice los relojes de la VM con su host. Muchas características de SharePoint Server 2010 usan trabajos del temporizador. Cualquier latencia en la sincronización de la hora entre una VM y el host afecta la confiabilidad de SharePoint.

8. No usar instantáneas en un entorno de producción

Las instantáneas de máquina virtual son instantáneas basadas en archivos del estado, los datos de disco y la configuración de una VM en un momento específico. No use instantáneas en un entorno de producción por los siguientes motivos:

Microsoft SharePoint Server usa trabajos del temporizador de manera intensiva; la latencia de las instantáneas afecta negativamente a las operaciones sujetas a limitación temporal y puede provocar que se pierdan o dañen los datos.

Importante:

No configure una VM de modo que guarde el estado durante el apagado, ya que esto también se ve afectado por la latencia.
Las instantáneas disminuyen el rendimiento de la VM e incrementan los requisitos de almacenamiento físico.

Para obtener más información, vea Hyper-V Virtual Machine Snapshots: FAQ.

9. Diseñar la topología virtual para un rendimiento óptimo

Diseñe la topología de la granja de servidores de SharePoint Server virtual en todos los hosts para maximizar el rendimiento general. Se recomienda lo siguiente:

Maximice le rendimiento general mediante la combinación de los roles del servidor de la granja en cada host. Por ejemplo, puede reducir la contención del disco si combina los servidores front-end web con los servidores de aplicaciones, ya que estos no suelen escribir en el disco al mismo tiempo.
Supervise el rendimiento de los servidores front-end web en un único host para garantizar que el incremento de la escalabilidad horizontal de las VM no provoque un rendimiento negativo o decreciente. En estos casos, incremente la escalabilidad horizontal mediante la implementación de VM adicionales en otro host.

Para obtener más información, vea Pruebas de rendimiento de Hyper-V (SharePoint Foundation 2010).

10. No sobrecargar el host de Hyper-V

Para evitar sobrecargar el equipo host de Hyper-V, realice una cuidadosa planeación a fin de garantizar que no se sobrecarguen los siguientes recursos de host principales.

Procesador
La relación de procesadores virtuales a procesadores lógicos es uno de los elementos determinantes al medir la carga del procesador. Cuando la relación de procesadores virtuales a procesadores lógicos no es 1:1, la CPU está sobrecargada, lo que implica un efecto negativo en el rendimiento.
Memoria
Las particiones raíz y secundarias requieren memoria suficiente para funcionar eficazmente. La partición raíz debe tener memoria suficiente (un mínimo de 512 MB) para proporcionar servicios, como virtualización de E/S, instantáneas y administración, para admitir las particiones secundarias. Un buen estándar para la sobrecarga de memoria de cada VM es 32 MB para el primer GB de RAM virtual más otros 8 MB para cada GB adicional de RAM virtual. Esto debe tenerse en cuenta en los cálculos de la cantidad de VM que se hospedarán en un servidor físico. La sobrecarga de memoria varía en función de la carga y cantidad de memoria real que se asigna a cada VM.

Planee detenidamente la configuración e implementación de la VM en función de la siguiente información:

Sobrecarga
Cumpla con los requisitos de memoria física y procesamiento del sistema operativo y de Hyper-V.
Alta disponibilidad
En un entorno de migración activo, todo host que forme parte del clúster debe contar con la capacidad de hospedar VM adicionales.
Incremento de la escalabilidad vertical o incremento de la escalabilidad horizontal
Es posible que sea necesario incrementar los recursos de una VM o agregar VM para solucionar problemas de rendimiento en los servidores de la granja de SharePoint Server.

11. No ejecutar trabajos con uso intensivo de recursos en las VM y el host de Hyper-V al mismo tiempo

Para garantizar un rendimiento coherente y óptimo, supervise detenidamente las VM y el host de Hyper-V para garantizar que no se ejecuten trabajos con uso intensivo de recursos al mismo tiempo. Por ejemplo, si ejecuta un programa de copia de seguridad en el equipo físico y en las VM al mismo tiempo, habrá contención de recursos.

Fuente: http://technet.microsoft.com/es-es/library/hh295699.aspx

Slide Show desde una librería de imágenes

2012-02-05T14:04:00.001-08:00

Step 1: Plugin Setup

Download the Easy Slider Plugin from http://cssglobe.com/lab/easyslider1.7/easyslider1.7.zip
Unzip the file and Upload easySlider1.7.js to a document library.

Step 2: Note down the List ID

Navigate to your Site Actions -> Site Settings
Under Site Administration, click Site libraries and lists
Click on your Picture Library name, to open it.
Note down the value of parameter List as displayed in Url window of your Internet explorer. It will be something like {26EC0E08-3D8A-4C67-ABF5-909D572B3030}
Add a content editor web part (CEWP) on your target page

Step 3: Set up Content Editor Web Part

On your target page, add a content editor web part (CEWP)
Paste the following code in Source Editor

<script type="text/javascript" src="http://TestServer/TestSite/js/easySlider.js"></script>

    function startSlider() {
        //Step 2 Replace {26EC0E08-3D8A-4C67-ABF5-909D572B3030} with the ID of your picture library
        var soapEnv =
            "<soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'> \
                <soapenv:Body> \
                     <GetListItems xmlns='http://schemas.microsoft.com/sharepoint/soap/'> \
                        <listName>{26EC0E08-3D8A-4C67-ABF5-909D572B3030}</listName> \
                         <viewFields> \
                            <ViewFields> \
                               <FieldRef Name='Title' /> \
                           </ViewFields> \
                        </viewFields> \
                    </GetListItems> \
                </soapenv:Body> \
            </soapenv:Envelope>";
        $.ajax({
            url: "//"+window.location.hostname+L_Menu_BaseUrl+"/_vti_bin/lists.asmx",
            type: "POST",
            dataType: "xml",
            data: soapEnv,
            complete: processResult,
            contentType: "text/xml; charset=\"utf-8\""
        });
    };
    function processResult(xData, status) {

//Uncomment the following line to see the raw xml received from lists.asmx
//$("#rawXml").text(xData.responseText);

$(xData.responseXML).find("z\\:row").each(function() {

            //Get relevant field values
            imageUrl="//"+window.location.hostname + "/" + $(this).attr("ows_FileRef").split(";#")[1];
            var description=getDescription( $(this).attr("ows_MetaInfo"));
            var title=$(this).attr("ows_Title");

            //Construct required HTML Markup
            var liHtml = "<li><h3>" + title + "</h3>" ;
            liHtml+="<IMG border=0 alt='" + title + "'src='" + imageUrl + "' >";
            liHtml+="<p>" + description + "</p>";
            liHtml+="</li>";

            //Add markup as line item in UL tag
            $("#imagesUL").append(liHtml);
        });

        //Start Slider
        //For full options, refer to http://cssglobe.com/post/4004/easy-slider-15-the-easiest-jquery-plugin-for-sliding
        $("#slider").easySlider({
            auto: true,
            continuous: true,
            controlsShow : false,
            speed : 800,
            pause : 4000
        });

        }
    function getDescription(metaInfo)
    {
        var description="";
        if(metaInfo!=null)
        {
            metaParts=metaInfo.split("\n");
            if(metaParts!=null && metaParts.length>0)
            {
                var i=0;
                do
                {
                    if(metaParts[i].indexOf("vti_description")>-1)
                    {
                        var descParts=metaParts[i].split("|");
                        if(descParts!=null && descParts.length>1)
                        {
                            description=descParts[1];
                        }
                    }
                    i++;
                } while (i<metaParts.length && description=="" );
            }
        }
        return description;
    }
</script>
<style type="text/css">
#slider{border-bottom:2px solid #ccc; background:#eee; padding:5px;    font-size:x-small;}
#slider h5{font:italic medium Georgia, Times, serif; color:#555; padding:3px; margin-bottom:-10px; background:#c6c6c6;}
#slider h5 span{text-transform:lowercase; padding:5px; font:x-small normal Arial, Helvetica, san-serif;}
#slider div {font-size: x-small; padding:3px;}
#slider ul, #slider li{margin:0; padding:0; list-style:none;}
#slider li{width:310;    height:400px; overflow:hidden; padding:0px;}
#controls2 {padding:3px 0 0 0; text-align:right; width:300;}
#prevBtn, #nextBtn{}
#nextBtn{}
#prevBtn a, #nextBtn a{font-size:x-small; background-color:#ccc; color:#444; padding:2px; text-decoration:none;}
#nextBtn a{}

</style>
    <div id="rawXml" ></div>
       <div id="slider">
        <ul id="imagesUL"/>
    </div>

Step 4: Update Code

Replace {26EC0E08-3D8A-4C67-ABF5-909D572B3030} by the List ID you got in step 2, above
Click OK, exit edit mode and Enjoy!

Notes:

This code is a sample code and you may need to change the styles section to match your site’s theme.
Please make sure all your images are of same size, if not, then please adjust the size in line 47 of source code.
This code assumes the size of images as 300×300 pixels, if you need to change it then update the relevant size at line 98.

Fuente:

http://www.sharepoint-insight.com/2012/02/05/quickest-way-to-create-slide-show-from-your-picture-library-in-sharepoint/

Notes Chapter 5 – Sharepoint 2010 Unleashed

2012-02-05T06:49:00.001-08:00

Migrating from Legacy Sharepoint to Sharepoint 2010

Microsoft provides for two out-of-the-box upgrade options: the in-place upgrade and the database-attach options.

The first and most straightforward option for upgrading to SharePoint 2010 is the in-place upgrade option. With this option, an existing SharePoint 2007 server is upgraded in place to SharePoint 2010. The advantage to this approach is that it is easy to perform and utilizes existing hardware and preserves custom farm settings such as Audiences or Search customization. The main disadvantage to this approach is that the hardware must be SharePoint 2010-capable and there is no going back when the migration starts.

The database attach upgrade process works off of a completely different concept. With this approach, you build the new SharePoint 2010 environment on completely different hardware and configure it to best practices. You have the option of completely rebuilding all farm aspects and can even have the new SharePoint environment serve as a farm target for multiple source farms of various versions (WSS, MOSS Standard, MOSS Enterprise). When the migration is ready to take place, it is done one content database at a time and is performed by attaching the database (or a restore of the database) to the new farm and upgrading it on that farm.

The significant advantage to this approach is that it is much more forgiving if there are errors, and it allows for easy fallback to the old farm if the migration fails.

The main disadvantage to this approach is that it migrates only content and does not migrate any farm settings, such as audiences or custom search settings.

This pre-upgrade check runs as an extension to the STSADM command-line tool, included in the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN folder on a SharePoint 2007 Server (either WSS or MOSS). When an environment is completely upgraded to SP2, this tool can be run without risk because it is read-only and makes no modifications to any of the files on the server.Run the pre-upgrade check by typing stsadm –o preupgradecheck

This farm passphrase is used for all new server additions to the farm, so be sure to store it in a safe place. The purpose of the passphrase is to avoid servers being added to the farm without prior consent of an administrator.

The database attach process is a much more risk-averse migration process and is subsequently more likely to be used for most environments. It has the significant advantage of

enabling SharePoint administrators to create new best-practice SharePoint 2010 environments and simply move the databases to a new farm and upgrade them there.

The exact syntax to use when upgrading is Mount-SPContentDatabase –Name DBNAME–DatabaseServer DBSERVER –WebApplication http://yourwebapp.companyabc.com (where DBNAME, DBSERVER, and http:// yourwebapp.companyabc.com are all names of your databases, servers, and webapps, respectively).

After migration, the site collection looks and feels exactly like a SharePoint 2007 site, assuming the option was chosen to keep the existing visuals temporarily during the

upgrade process. Site administrators need simply to click on Site Settings to see the new visual upgrade option available to them

Visual upgrade is not available when upgrading My Site. When upgraded, My Site immediately assume the new SharePoint 2010 visuals.

Use the in-place upgrade process only for those environments that are smaller than 30GB and for those environments without a large amount of customized web parts or other complexities.

Fuente:

http://www.amazon.com/Microsoft-SharePoint-2010-Unleashed-Michael/dp/0672333252

Notes Chapter 4 – Sharepoint 2010 Unleashed

2012-02-05T06:48:00.001-08:00

Advanced Sharepoint 2010 Installation and Scalability

The following list denotes the high-level steps that should be followed before architecting a SharePoint environment:

1. Define the business needs that should ideally be met by the project.
2. Map business needs to technical solutions in SharePoint 2010.
3. Define the number of farms required to satisfy business and technical needs and to provide for publishing and other features.
4. Define the number and scale of intranet versus extranet environments, using guidelines from Chapter 13, “Deploying SharePoint for Extranets and Alternate Authentication Scenarios.”
5. Define the physical architecture that will be required to deploy the technical solutions.
6. Define the security requirements, including number of service accounts and the rights they require.
7. Define the number of third-party and other MS solutions to properly secure and deploy.

The following high-level checklist should be used to continue the installation of an advanced SharePoint environment:

1. Create Web Applications required, configuring them for Kerberos, SSL, and Load Balancing (all best practices).
2. Configure Managed Paths and Content Database structure, based on the parameters defined during the design phase.
3. Configure My Site functionality.
4. Configure the SharePoint Central Administration Web Application as a loadbalanced, SSL, and Kerberos-enabled web application for performance, security, and
high availability.
5. Configure all service applications required for the farm, using either the web-based wizard or (preferably), PowerShell, as demonstrated in this chapter.
6. Configure the User Profile Service to pull information into User Profiles.
7. Configure inbound mail settings, and configure them to be load balanced for availability of the service.
8. Configure outbound mail settings for alerts and other messages to be sent from SharePoint.
9. Configure search (covered in more detail in Chapter 8, “Leveraging and Optimizing Search in SharePoint 2010,” including third-party iFilters such as PDF iFilters, and FAST Search if needed.

10. Configure backup (third-party, Microsoft DPM, or integrated backup.)
11. Configure edge security and antivirus (third-party or Microsoft Forefront products, covered in Chapter 14, “Protecting SharePoint with Advanced Antivirus and Edge
Security Solutions”).
12. Configure data and transport security options (covered in Chapter 17, “Safeguarding Confidential Data in SharePoint 2010”).
13. Configure SQL maintenance and optimization,
14. Configure third-party product functionality as necessary.
15. Test, test, and retest before deploying into production.
16. Migrate content into SharePoint using third-party tools (if necessary).

PowerShell is the only method that enables the creation of custom names for many of the databases created by SharePoint during the installation.

Script de PowerShell para crear un nuevo farm basado en el input del usuario: pag 78

PowerShell for Provisioning Service Applications: Pag 79

When deploying SharePoint, the primary concern for scalability is how many users will use the system.

In addition to total number of users, the following factors should be identified to more fully understand the load placed on a SharePoint server:

. Number of users
. Pages per user per work day
. Length of work day (hours)
. Type of work performed and level of office integration
. Size of document repositories

An understanding of how fast that content will grow is critical toward properly scaling an environment. Proper use of site quotas in SharePoint is an effective way to maintain control over the

size that a SharePoint database can grow to. Use of the Remote BLOB Storage API an help to keep the size of content databases under control by taking documents out of the database and storing them in other file formats.

SharePoint stores its data in SQL content databases but serves up access to that data via HTML and web services. The access to this data is served up to the user via the Windows Server Internet Information Services (IIS) service. IIS is composed of various logical structures known as websites, which are entry points to web content. Each website can be configured to point to various sets of information located on the web server or extended via SharePoint to be unique SharePoint web applications.

Use IIS websites mapped to SharePoint web applications to manage varying types of web-based access to SharePoint sites, such as SSL-encryption or different host headers.

Fuente:

http://www.amazon.com/Microsoft-SharePoint-2010-Unleashed-Michael/dp/0672333252

Notes Chapter 3 – Sharepoint 2010 Unleashed

2012-02-05T06:45:00.001-08:00

Installing a Simple SharePoint Server 2010 Farm

A server that will be running all SharePoint roles, including the database role, should have the following minimum requirements:

64-bit four core (minimum) processor
8GB to 16GB of RAM (8GB for evaluation or testing, 16GB for production)
80GB of drive space for the system drive (plus twice as much space as the amount of RAM in the system

. SQL admin account—SQL Server should be administered with a separate set of credentials than those used for SharePoint.

. Installation account—Used to install the SharePoint binaries on the SharePoint role servers. This account requires local admin rights on each SharePoint server and DBCreator and SecurityAdmin rights on the SQL Server.

. SharePoint farm admins—Used to administer the farm; should be configured. Typically, one account for each physical admin is created.

. Application pool identity accounts—Needed for each app pool. Generally speaking, it is good practice to have a separate app pool for each application. These accounts must be separate from farm admin accounts.

. Default content access account—The default account used to crawl SharePoint and other content. It must not be a farm admin, or the search results will include unpublished data in the results. There may be additional content access accounts created for other data sources that are crawled as well.

. Search service application account—This account is used to run the search service application.

The high-level steps involved are as follows:

. Install Windows Server 2008 R2 with the defaults.
. Activate the server.
. Install any server-specific tools required.
. Patch and update the operating system.
. Add the server to an Active Directory domain.
. Copy the SharePoint 2010 binaries local to the server (recommended).
. Copy the SQL Server 2008 R2 binaries local (if installing the database role).

Create multiple service accounts for use by SharePoint. Do not use a single service account, and do not use any domain admin accounts for SharePoint.

Patch the operating system with all critical updates before installing SharePoint.

Patch SharePoint 2010 with all the latest service packs and cumulative update patches before running the configuration wizard.

Fuente:

http://www.amazon.com/Microsoft-SharePoint-2010-Unleashed-Michael/dp/0672333252

Developing custom field type for SharePoint 2010

2012-02-05T06:33:00.001-08:00

The ECM features of SharePoint 2010 are excellent. The best thing is the extendibility of the platform using SharePoint designer and Visual Studio. By default SharePoint includes field types such as Single line text, multi-line text etc. The following is the snapshot of the fields available in SharePoint 2010

The out of the box field controls are useful for most situations, but still you may need additional field types when building business applications. Fortunately you can build custom field controls using Visual Studio 2010 and deploy to SharePoint. Custom field control can provide a unique editing and display experience. Custom field controls can be used to include custom client-side validation and a unique editing experience.

In this article I am going to demonstrate how you can build custom field control for SharePoint 2010. For the purpose of this article, I am going to build a custom field control that inherits the single line of text. When displaying the control, it will show the entered text in <h1> tags. Also the field will convert the text to upper case while displaying. The custom field will throw error if it contains more than 10 characters. The examples looks simple, my intention is to show you how easily you can build custom controls. In real time you can add your business logic to build your own field controls.

Open Visual Studio, from the file menu select new project. In the new project dialog, select empty SharePoint project as the template. I have named the project as “MyCustomFieldProject”

In the SharePoint customization wizard, make sure you select “deploy as farm solution”. Also you can enter the local site URL where you can deploy the custom field.

Click the Finish button. Visual Studio will create an empty project. In Visual Studio solution explorer, the project looks as follows.

Now you need to add a class to the solution that represents the custom field. Now right click the project and select Add -> Class

I have named the class as “MyHeaderField”

The class just created have the following code.

Now you need to set the class as public. You need to include the using statement to include Microsoft.SharePoint to get access to the Sharepoint built in types. As I mentioned initially MyHeaderField needs to inherit the SharePoint Text field which is “SPFieldText”. Now you need to override the 2 default construtors. After making the mentioned changes, the code file looks as follows.

Now I am going to override 2 methods as follows.

GetValidatedString – This will be used to validate the data before saving to database.
GetFieldValueAsHtml – this is how the value will be displayed in the page.

The implementation of the methods are as follows.

Each field type you define should have a corresponding entry in the form of XML file in the XML folder under 14\Template folder. The XML file will have the following naming convention

It should start with fldtypes_
After _ you can define the field name. It is a good practice to specify the class name as the field name, though it is not a must
In the XML file, you need to define the fields such as TypeName, parent type name, type display name, corresponding class and assembly.

Now in the Visual Studio project, you need to add a XML file and while deploying it should be deployed to the folder 14\Template\XML. To do this, you can add a mapped folder to your project. Right click the project in solution explorer, select Add -> SharePoint mapped folder

In the Add mapped folder dialog, expand Template and select XML

Now you can see the XML folder under your project. Any files created here will be deployed to the 14\Template\XML folder in the SharePoint farm where the solution is deployed. Now you need to add the XML file for your field.

Right click the project, select Add -> New Item. Now in the template selection, select Data as the category and then select XML as the file type. I have named fldtypes_MyHeaderField.xml

I have updated the content of the XML file as follows. Be noted that $SharePoint.Project.AssemblyFullName$ will be replaced automatically by the correct assembly name wile deploying. All the other fields are self-explanatory.

Now we are done with all the requirements. From the solution explorer, right click the project and click deploy.

Once deployed, you can add new columns to SharePoint lists and libraries with the type “MyHeaderField”. Add the new column to SharePoint types will show the new type you added.

I have added a new column named “MyHeader” to my publishing page content type. Now when I try to add text to the column, it will validate it. See a simple validation

SharePoint 2010 is extensible as you can build and deploy custom fields that address your custom business requirements.

Fuente: http://weblogs.asp.net/sreejukg/archive/2012/02/05/developing-custom-field-type-for-sharepoint-2010.aspx

SharePoint Performance Troubleshooting

2012-02-04T14:53:00.001-08:00

Para ver el post completo: http://www.sharepointpromag.com/article/sharepoint-server-2010/sharepoint-performance-troubleshooting-141506

Windows Server Hardware Sizing

You need to correctly size your hardware to support the SharePoint tier that is being hosted. You'll also need to ensure that Windows Server has been optimized.

For the optimal RAM profile, examine what your app pools will require, multiply that number by the number of app pools that you expect to have, and then add half again as much to ensure room for growth and the occasional application that doesn't dispose properly:

(Required RAM) ´ (# of App Pools) ´ 1.5 = Proposed RAM Profile

Hard disk space is a fairly straightforward decision: 80GB is never going to be enough. Each web and application server will have its own Microsoft User Location Server (ULS), IIS, and event logs; copy of the 14 hive; and WinSxS directory. Add the need for a pagefile that doubles your RAM count and a desire to make sure that your server doesn't crash because you didn't have enough disk space. I recommend a minimum of 200GB per server -- 400GB if you can afford it. Rather than splitting drives into multiple partitions, keep a single, larger C partition to manage growth.

SQL Server Hardware Sizing

he SQL Server tier is the one in which you'll want to make your hardware investment. If you don't give SQL Server enough horsepower, you're sunk before you leave port. CPU and RAM are both crucial to SQL Server performance, but be aware that SQL Server will chew up as much RAM as it can get its teeth into, regardless of load

When sizing SQL, always consider which services you can separate out. The minimum requirements refer specifically to the relational database management system (RDBMS) engine, not taking into account any SQL Server Integration Services (SSIS), Reporting Services (SSRS), or Analysis Services (SSAS) needs that you might have. Separate these services onto their own hardware whenever possible, and address their specific hardware requirements as well.

SQL Server Performance

Pregrow your databases and set automatic growth parameters. Why are pregrowing databases and setting automatic growth parameters important? SQL Server is at its most efficient when it has a large block of contiguous space.

One of the worst-performing base operations for SQL Server is its database growth operation. SQL Server goes out, finds available space on disk, and adds that space to the database. By default, this operation is set to grow by 1MB per operation. When a content database is created, it has a 20MB data file and a 3MB log file.

If variable auto growth still needs to be a part of your maintenance strategy, consider these points:

Set standard autogrow to somewhere between 500MB to 1GB.
Create a daily maintenance job to check for the amount of free space in your database.
If the amount of free space is less than 10 percent, then grow free space at a scheduled time when users will not be affected

the log files in SQL Server are high-intensity write, whereas the data files can be a healthy mix of both read and write. Based on this generality, the databases that SharePoint uses (other than TempDB, which is dominantly write-intensive) are generally read\write in nature. You can set up archival content databases that house read-only site collections, but the real power of SharePoint is in its collaboration functionality, which by its nature needs both read and write elements.

The difficult decision regarding I/O is cost versus return. RAID 10 is extremely storage inefficient and costly but provides the best possible performance and redundancy. RAID 5 is storage efficient and provides redundancy, but you'll contend with a performance hit.

SharePoint Web Server Load Testing

Load testing is an often overlooked and highly disregarded art when it comes to SharePoint. We all plan to test for loads, but it seems rare that anyone actually takes the time to do so. There are several simple (as well as many more-complex) tools that allow you to load-test your environment:

Load balancing in your SharePoint application tier. In SharePoint 2010, Microsoft seems to have done a good job with a simple feature called the Service Application Load Balancer. This feature serves round-robin requests to all listening service applications that can respond to a given request.

Numerous Causes

Top 10 SharePoint 2010 Configuration Mistakes -- and How to Fix Them

2012-02-04T14:37:00.001-08:00

Ver el post completo:http://www.sharepointpromag.com/content1/topic/sharepoint-2010-misconfigurations-141636/catpath/sharepoint

Mistake #1: Scrimping on SharePoint's RAM or Hard Disk Space

Virtualization itself isn't bad, but it must be done intelligently and without sacrificing SharePoint's ability to do its job.

If SharePoint finds itself starved for RAM, it starts shutting off functionality so that it can fit into the available space. It also caches less in the web application pools and recycles those pools more often. Less caching and more recycles result in a degraded end-user experience, as SharePoint must compile the same ASP.NET code over and over. And no one likes unhappy users, not even their mothers.

The solution to this particular issue is easy: Add RAM.

Mistake #2: Using Virtualized Microsoft SQL Server

Virtualization isn't bad. But virtualization allows administrators to make mistakes on a much grander scale. Take virtualizing SQL Server. Everything in SharePoint is stored in SQL Server, if SQL Server is slow, SharePoint is slow.

The obvious solution is to move SQL Server to a physical box.

Mistake #3: Using the Farm Configuration Wizard

All the databases that the wizard creates have nasty globally unique identifiers (GUIDs) at the end of their names. The wizard also creates a content web app, at http://servername, that just doesn't scale well. To add insult to injury, the wizard creates your My Site host on that same web app, at http://servername/my. Finally, the wizard encourages you to create service applications that you might not actually use.

Mistake #4: Using an Incorrect URL when Creating a Content Web App

SharePoint doesn't tell IIS about changes that you might make to a web app after it is created. For instance, if you create an Alternate Access Mapping (AAM) for a web app in Central Administration, you still need to go into IIS and add the host header for the new address.

Mistake #5: Running Web Apps or Service Apps in Separate App Pools

Web apps and service applications run inside of an application pool, which is a W3WP.exe process that runs on your server. Unless you have reason to do otherwise, you should run all SharePoint web apps inside one application pool; the same goes the service applications. Running each web app in its own application pool makes inefficient use of the server's memory. Each application pool has a minimum overhead of more than 100MB, and its memory footprint increases as it caches content that is frequently rendered. multiple application pools mean that the same content is cached multiple times.

For service applications, this problem is easy to fix. First, make sure that you have a good service application pool to use. I recommend calling this pool Default SharePoint Service App Pool so that it floats to the top of all your drop-down lists. Use a dedicated sp_serviceapps account for the pool's identity. Most service applications allow you to assign them to a new service application pool by modifying their properties in Central Administration. If the option is unavailable there, look for it in PowerShell.

Mistake #6: Using One Account for Everything

if you use one dedicated account for SharePoint, you leave yourself vulnerable to attack. If that account is compromised via a security exploit, the bad guys will have access to everything in SharePoint.

To fix this mistake, start by creating the accounts that I outline in this blog post . Add the sp_webapps and sp_serviceapps accounts as managed accounts.

Mistake # 7: Keeping Default SharePoint Database Settings

When SharePoint creates its multitudes of databases, it makes some bad assumptions. Take the autogrow settings: The database files grow by 1MB at a chunk, almost ensuring that they're going to autogrow with every upload. Not only does this slow down SQL Server (which slows down SharePoint), but it also results in database files that are spread all over your drives in itty-bitty 1MB chunks.

SharePoint also creates most of its databases, notably the Config and Content databases, with the recovery model set to Full. Although this is great if you want to recover data, you must manage the process correctly or those sneaky .ldf files will slowly, methodically fill your hard disk. If you think users get upset when SharePoint is slow because of fragmented databases, you should see how angry they get when SharePoint stops completely because the SQL Server drives are full.

To fix this mistake, set your databases' autogrow settings in such a way that they don't need to grow frequently. For most farms, I recommend changing the 1MB autogrow to something like 500MB or 1GB. Autogrow should also be a last resort. Someone, either the SharePoint administrator or a dedicated DBA, should pregrow your databases so that autogrow is unnecessary.

Your recovery model setting needs to be consistent with your disaster recovery plans. If you need your transaction logs, make sure you're performing routine log backups to keep those .ldf files in check. If you don't need your transaction logs, then consider switching your databases to the simple recovery model. Doing so will keep your .ldf files from swelling up like a nasty bee sting.

Mistake #8: Not Enabling BLOB Caching

Enable BLOB caching, of course! BLOB caching is actually a function of IIS; SharePoint just takes advantage of it. Therefore, to enable BLOB caching requires a change to each web app's web.config file on each server. Fortunately, the setting already exists and just needs to be enabled. By default, the web.config files are in a directory under C:\inetpub\wwwroot\wss\virtualdirectories\. Each web app has a directory and a web.config file. Open one of these files and look for the following line:

To enable BLOB caching, replace "false" with "true" and save the web.config file. You should also move the file to a directory on a drive other than the C drive. The maxSize parameter is measured in gigabytes, with a default of 10GB. If the space is available, you might want to increase this size.

If editing this file in Notepad on all your servers isn't your idea of fun, you can use PowerShell to automate the process. You still need to perform the process on each server, but using PowerShell is quicker and reduces the chances of a mistake. To begin, download the script and save it to a file named blobcache.ps1. This script contains two functions: Enable-SPBlobCache and Disable-SPBlobCache. Each function takes a web app from the pipeline and enables or disables BLOB caching on that app. The code to enable BLOB caching on each web application in the farm looks like this:

PS E:\Install\Scripts> . .\blobcache.ps1

PS E:\Install\Scripts> Get-SPWebApplication | Enable-SPBlobCache

Mistake #9: Not Installing a PDF iFilter

Mistake #10: Not Pointing Your SharePoint Servers at Themselves

make sure that every server in the SharePoint farm points to itself for all web apps. If I get sporadic reports about SharePoint not responding

Pointing your Search indexer at itself has another advantage: It improves performance for your end users. If you don't point your Search server at itself, then when it starts to perform a crawl, it lets DNS do its work and then starts crawling whichever web front end DNS points it to.

There is a simple fix for this mistake: Open the hosts file (C:\windows\system32\drivers\etc\hosts) on each SharePoint box, and add all the URLs that SharePoint knows about. Point those URLs to 127.0.0.1, which translates to "this computer."

This approach provides all the benefits that I've mentioned but uncovers a nasty beast: loopback detection. This monster, as well as how to defeat it, is scary and too long for this article, but you can read all about it in my blog post "Can’t crawl web apps you KNOW you should be able to crawl."

Fuente:

http://www.sharepointpromag.com/content1/topic/sharepoint-2010-misconfigurations-141636/catpath/sharepoint

Límites de rendimiento y capacidad probados de SharePoint Server 2010

2012-02-04T13:39:00.001-08:00

Este artículo contiene información que le ayudará a entender los límites de rendimiento y capacidad probados de SharePoint Server 2010 y proporciona directrices sobre la relación de los límites con un rendimiento aceptable. Use la información incluida en este artículo para determinar si la implementación que planeó se encuentra dentro de límites de rendimiento y capacidad aceptables y para configurar de forma adecuada los límites en su entorno.

Límites máximos, umbrales y límites admitidos

En SharePoint Server 2010, hay ciertos límites que son de diseño y que no se pueden exceder y otros límites que se establecen en valores predeterminados que el administrador de la granja de servidores puede modificar. También hay ciertos límites que no están representados por un valor configurable, como el número de colecciones de sitios por aplicación web.

Los límites máximos son límites absolutos que no se pueden exceder por diseño Es importante entender estos límites para no hacer suposiciones incorrectas al diseñar una granja de servidores.
Un ejemplo de límite máximo es el límite de tamaño de documento de 2 GB; no se puede configurar SharePoint Server para almacenar documentos de más de 2 GB. Éste es un valor absoluto integrado y no se puede exceder por diseño.
Los umbrales son límites que tienen un valor predeterminado que no se puede exceder a menos que se modifique el valor. En ciertos casos, los umbrales se pueden exceder para dar cabida a desviaciones en el diseño de la granja de servidores, pero es importante entender que al hacerlo se puede ver afectado el rendimiento de la granja además del valor efectivo de otros límites.
El valor predeterminado de ciertos umbrales solo se puede exceder hasta un valor máximo absoluto. Un buen ejemplo es el límite de tamaño de documento. De forma predeterminada, el umbral de tamaño de documento predeterminado está establecido es 50 MB, pero puede modificarse para admitir un límite máximo de 2 GB.
Los límites admitidos definen el valor probado de un parámetro específico. Los valores predeterminados de estos límites se definen mediante pruebas y representan las limitaciones conocidas del producto. Si se exceden los límites admitidos, se pueden producir resultados inesperados, una reducción considerable en el rendimiento u otros efectos perjudiciales.
Algunos límites admitidos son parámetros configurables que se establecen de forma predeterminada en el valor recomendado, mientras que otros están relacionados con parámetros no representados por un valor configurable.

Un ejemplo de un límite admitido es el número de colecciones de sitios por aplicación web. El límite admitido es de 250.000, que es la cantidad máxima de colecciones de sitios por aplicación web que alcanzó los niveles de referencia de rendimiento durante las pruebas.

Es importante tener en cuenta que muchos de los valores límite que se proporcionan en este documento representan un punto en una curva que describe una carga de recursos creciente y una reducción concomitante en el rendimiento a medida que aumenta el valor. Por lo tanto, si se exceden ciertos límites, como el número de colecciones de sitios por aplicación web, solo podría obtenerse una reducción fraccional en el rendimiento de la granja de servidores. No obstante, en la mayoría de los casos, el funcionamiento a un límite establecido o a un nivel próximo no es un procedimiento recomendado, ya que es más fácil alcanzar las metas aceptables de rendimiento y confiabilidad cuando el diseño de una granja de servidores proporciona un equilibrio razonable de los valores límite.

Las directrices de umbrales y límites admitidos están determinadas por el rendimiento. En otras palabras, se pueden exceder los valores predeterminados de los límites, pero a medida que se aumenta el valor límite, el rendimiento de la granja de servidores y el valor efectivo de otros límites pueden verse afectados. Muchos de los límites de SharePoint Server pueden modificarse, pero es importante entender cómo se verán afectadas otras partes de la granja de servidores al modificar un determinado límite.

Establecimiento de los límites

En SharePoint Server 2010, los umbrales y límites admitidos se establecen mediante pruebas y la observación del comportamiento de la granja de servidores bajo cargas en aumento hasta el punto en que los servicios y operaciones de la granja de servidores alcanzan sus límites de funcionamiento efectivos. Algunos servicios y componentes de la granja de servidores pueden admitir una carga mayor que otros, por lo que en algunos casos debe asignarse un valor límite basado en un promedio de varios factores.

Por ejemplo, las observaciones del comportamiento de la granja de servidores bajo carga cuando se agregan colecciones de sitios indican que ciertas características presentan una latencia inaceptablemente alta mientras que otras características siguen funcionando con parámetros aceptables. Por lo tanto, el valor máximo asignado a la cantidad de colecciones de sitios no es absoluto, sino que se calcula en función de un conjunto esperado de características de uso en el que el rendimiento de la granja de servidores en general sería aceptable en el límite especificado en la mayoría de los casos.

Obviamente, si algunos servicios funcionan con parámetros más altos que los usados en las pruebas de límites, los límites efectivos máximos de otros servicios se reducirán. Por lo tanto, es importante ejecutar rigurosos ejercicios de administración de la capacidad y pruebas de escala para implementaciones específicas a fin de establecer límites efectivos para dicho entorno.

Nota: no se describe el hardware que se usó para validar los límites indicados en este documento, ya que estos se recopilaron de varias granjas de servidores y entornos. Para obtener descripciones de las granjas de servidores que se usaron en las pruebas, vea Recomendaciones y resultados de pruebas de rendimiento y capacidad (SharePoint Server 2010) y Casos prácticos técnicos de rendimiento y capacidad (SharePoint Server 2010).

La metáfora del ecualizador

Los umbrales y límites admitidos pueden considerarse como los controles deslizantes de un ecualizador gráfico, donde cada límite representa una determinada frecuencia. Según esta metáfora, al aumentar el valor de un límite, se puede reducir el valor efectivo de uno o más límites.

Suponga que un control deslizante representa el número máximo de documentos por biblioteca, un límite admitido con un valor probado máximo de aproximadamente 30 millones. Sin embargo, este valor depende de otro control deslizante, que representa el tamaño máximo de los documentos de la granja de servidores y que es un umbral con un valor predeterminado de 50 MB.

Si cambia el tamaño máximo de los documentos a 1 GB para admitir vídeos u otros objetos grandes, el número de documentos que la biblioteca puede servir a los usuarios de forma eficiente se reduce de la misma forma. Por ejemplo, la configuración de hardware y la topología de una determinada granja de servidores pueden admitir 1 millón de documentos hasta 50 MB. No obstante, la misma granja de servidores con el mismo número de documentos no puede alcanzar la misma latencia y metas de rendimiento si sirve un tamaño de documento promedio mayor, ya que el límite de tamaño de archivo se estableció en 1 GB.

El grado en que se reduce el número máximo de documentos en este ejemplo es difícil de predecir y se basa en el número de archivos grandes de la biblioteca, el volumen de datos que contienen, las características de uso de la granja de servidores y la disponibilidad de recursos de hardware.

Límites y límites máximos

En esta sección se enumeran los objetos que pueden formar parte de una solución y se proporcionan directrices para el rendimiento aceptable de cada tipo de objeto. Un rendimiento aceptable significa que el sistema, tal como se probó, puede admitir ese número de objetos, pero el número no se puede exceder sin que se produzca cierta reducción en el rendimiento o en el valor de los límites relacionados. Los objetos se enumeran por ámbito y por característica. Se proporcionan datos de límites, así como notas que describen las condiciones en las que se obtiene el límite y vínculos a información adicional según corresponda.

Use las directrices incluidas en este artículo para revisar sus planes de solución generales. Si sus planes de solución exceden las recomendaciones para uno o varios objetos, siga uno de estos procedimientos:

Evalúe la solución para garantizar que se realizan compensaciones en otras áreas.
Marque estas áreas para probarlas y supervisarlas durante su implementación.
Rediseñe o particione la solución para asegurarse de que no se excedan los niveles de capacidad recomendados.

Límites por jerarquía

Límites por característica

Arquitectura Web Analytics

2012-02-04T13:36:00.001-08:00

Create simple WCF Web Service for SharePoint 2010 with Visual Studio 2010

2012-02-04T05:40:00.001-08:00

This Web Service will provide two methods:

Ping => Just as test.
GetUsedEmailAliasses => This method reports all aliasses used for “E-Mail enabled lists” in SharePoint.

Here is the code: http://spwcfwebservicedemo.codeplex.com/

Let’s start.

1. Create a new SharePoint 2010 project in Visual Studio 2010. Use the “Empty Project” template. Name the project “ik.SharePoint2010.SPWCFWebServiceDemo”.

2. In the project creation wizard specify the Central Administration address as deployment location. You need to deploy as “Farm Solution”:

3. Now add this Assembly References:

Microsoft.SharePoint.Client
Microsoft.SharePoint.Client.Runtime
Microsoft.SharePoint.Client.ServerRuntime
(You may need to locate this assembly in the file system: “C:\Windows\assembly\GAC_MSIL\Microsoft.SharePoint.Client.ServerRuntime\14.0.0.0__71e9bce111e9429c\Microsoft.SharePoint.Client.ServerRuntime.dll”)
System.Configuration
System.ServiceModel
System.ServiceModel.Web

4. Now map the SharePoint hive folder “Layouts” to your project:

a) Right click your project in the Solution Explorer Pane

b) In the context menu open sub menu “Add” and click “SharePoint Mapped Folder”

c) Select this:

d) Click “OK”

5. Create a sub folder named “ik.SharePoint2010.SPWCFWebServiceDemo” in folder “Layouts”

6. Add a new project item of type “Interface” to your project. Name it “ISPWCFSvc.cs”.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Runtime.Serialization;
using System.Runtime.InteropServices;
using System.ServiceModel;
using System.ServiceModel.Web;

namespace ik.SharePoint2010.SPWCFWebServiceDemo
{
    [ServiceContract(Namespace="http://schemas.microsoft.com/sharepoint/soap/"),      Guid("f01e2ff6-c291-4b8b-a154-cd7059ed4900")]
    public interface ISPWCFSvc  {
        [OperationContract, WebInvoke(Method = "GET")]
        List<string> GetUsedEmailAliasses();

        [OperationContract, WebInvoke(Method = "GET")]
        string Ping();
    }
}

7. Add a new project item of type “Class” and name it “SPWCFSvc.cs”

using System;
using System.Collections.Generic;
using System.Reflection;
using System.Runtime.InteropServices;
using System.Security.Permissions;
using System.ServiceModel;
using System.ServiceModel.Activation;
using System.Web;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Administration;
using Microsoft.SharePoint.Client;
using Microsoft.SharePoint.Security;

namespace ik.SharePoint2010.SPWCFWebServiceDemo
{
    [Guid("ae428eb5-02d1-4e50-8cee-eb3806f16ffd"),
    ServiceBehavior(Namespace = "http://schemas.microsoft.com/sharepoint/soap/"),
    AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Required),
    ClientRequestServiceBehavior,
    SharePointPermission(SecurityAction.Demand, ObjectModel = true),
    AspNetHostingPermission(SecurityAction.Demand, Level = AspNetHostingPermissionLevel.Minimal)]
    public class SPWCFSvc : ISPWCFSvc  {
        [SharePointPermission(SecurityAction.Demand, ObjectModel = true)]
        public List<string> GetUsedEmailAliasses()
        {
            List<string> l = new List<string>();

            SPProcessIdentity pi = SPContext.Current.Site.WebApplication.Farm.TimerService.ProcessIdentity;
            string userName = pi.Username;
            object configDB = pi.GetType().GetProperty("ConfigurationDatabase", BindingFlags.Instance | BindingFlags.NonPublic).GetValue(pi, null);
            SPServer server = (SPServer)configDB.GetType().GetProperty("Server").GetValue(configDB, null);
            string dbName = (string)configDB.GetType().GetProperty("Name").GetValue(configDB, null);
            string serverName = server.Name;

            SPSecurity.RunWithElevatedPrivileges(() =>
            {
                System.Data.SqlClient.SqlConnection s = new System.Data.SqlClient.SqlConnection(new System.Data.SqlClient.SqlConnectionStringBuilder {
                    DataSource = serverName,
                    InitialCatalog = dbName,
                    IntegratedSecurity = true }.ConnectionString);

                SPConfigDBDataContext dc = new SPConfigDBDataContext(s);

                foreach( var item in dc.EmailEnabledLists )
                {
                    l.Add(item.Alias);
                }
            });

            return l;
        }

        [SharePointPermission(SecurityAction.Demand, ObjectModel = true)]
        public string Ping()
        {
            return "Pong";
        }
    }
}

8. Now add a new “Text File” project item and name it “spwcfsvc.svc”

<% @ServiceHost Service="$SharePoint.Type.ae428eb5-02d1-4e50-8cee-eb3806f16ffd.AssemblyQualifiedName$" Factory="Microsoft.SharePoint.Client.Services.MultipleBaseAddressWebServiceHostFactory, Microsoft.SharePoint.Client.ServerRuntime, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>

Here we use an existing service factory of SharePoint that will handle the service instanciation for us.

In this file we use the token replacement functionality of Visual Studio 2010 for SharePoint 2010 development. We like to replace the token “$SharePoint.Type.ae428eb5-02d1-4e50-8cee-eb3806f16ffd.AssemblyQualifiedName$” through the “real” full qualified name during package creation.
By default *.svc files will not be processed by the token replacement engine. We need to specify *.svc files for that build step. Therefore we edit the C# project file in notepad. Insert this line as shown in the screenshot:
<TokenReplacementFileExtensions>svc</TokenReplacementFileExtensions>

After deploying the solution you may have a look into the SharePoint hive and look into “spwcfsvc.svc”

9. Now Copy & Paste this file into the you folder in the mapped Layouts folder:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\web.config

10. You need to edit this file. Remove the complete “<system.web>” tag and the (four) “location” tags at the beginning of the copied file! – The configuration settings in the copied & modified web.config file will manage the diffrent authentication methods for us. This works by using the class attribute “ClientRequestServiceBehavior” in the code above.

11. Now we add a “Linq to SQL” connection to the SharePoint Configuration database. Be sure only to read this DB!!!

12. Add a new project item of type “Linq to SQL Classes” to the project. Name it “SPConfigDB.dbml”

13. In the Server Explorer of Visual Studio 2010 create a connection to the SharePoint Configuration DB of your development environment. – After that, open the connection, open the “Table” node and select “EmailEnabledLists”.

14. Drag the “EmailEnabledLists” node to the “SPConfigDB.dbml” canvas. – It looks like this:

15. In the Properties Pane set the “Context Namespace” property to “ik.SharePoint2010.SPWCFWebServiceDemo”. (If you do not see this properties like in the screenshot below you need to right click the “SPConfigDB.dbml” project item node in the Solution explorer and click “Properties” in the context menu.

16. Now you should be able to compile and deploy your project.

17. Edit the startup settings. In the “Debug” select “Start browser with URL” and enter there the URL to your webservice: “http://<central-administration-url-and-port>/_layouts/ik.sharepoint2010.spwcfwebservicedemo/spwcf.svc/GetUsedEmailAliasses”

18. Now start the project. You get something like this:

I’ve only one e-mail enabled list or library in my current dev system.

Se puede utilizar para crear servicios para Sharepoint:http://cksdev.codeplex.com/

Fuente: http://ikarstein.wordpress.com/2012/01/21/walkthrough-create-simple-wcf-web-service-for-sharepoint-2010-with-visual-studio-2010/

CAML and the Client Object Model

2012-02-04T05:20:00.001-08:00

Working with the .NET Client Object Model

Before you can start working with the .NET Client Object Model, you have to add a reference to the assemblies Microsoft.SharePoint.Client.dll and Microsoft.SharePoint.Client.Runtime.dll. You can find these assemblies in the 14\ISAPI folder.

The Where clause

The Where clause can range from very simple to very complex with one or more nested <And> or <Or> elements. The CAML for the Where clause has not been changed since SharePoint 2003, and can be used with the SharePoint Server Object Model and with the three Client Object Models. Also the Web Services are still there, for which you can also use CAML to retrieve and/or update list items.

To retrieve list items from a SharePoint list, you have to define an instance of type CamlQuery, defined within the Microsoft.SharePoint.Client.CamlQuery namespace. You can specify your CAML query within the ViewXml property. This property is of type string but its content must be XML. The root element for this property is <View>. The Where clause needs to be embedded within a <Query> element.

Microsoft.SharePoint.Client.CamlQuery query = new Microsoft.SharePoint.Client.CamlQuery();
query.ViewXml = "<View>"    + "<Query>"    + "<Where><Eq><FieldRef Name='Country' /><Value Type='Text'>Belgium</Value></Eq></Where>"    + "</Query>"    + "</View>";
// execute the query
ListItemCollection listItems = spList.GetItems(query);
clientContext.Load(listItems);
clientContext.ExecuteQuery();

http://msdn.microsoft.com/en-us/library/ms414805.aspx

OrderBy

The OrderBy element is the most simple one: you can define a sort order using one or more <FieldRef> elements that you include in the ViewXml property of the CamlQuery object:

query.ViewXml = "<View>"    + "<Query>"    + "<Where><Eq><FieldRef Name='Country' /><Value Type='Text'>Belgium</Value></Eq></Where>"    + "<OrderBy><FieldRef Name='City'/></OrderBy>"    + "</Query>"    + "</View>";

http://msdn.microsoft.com/en-us/library/ms467378.aspx

ViewFields

You can also limit the number of columns returned to the client, using the good old ViewFields element, which you can also include in the ViewXml property of the CamlQuery object:

CamlQuery query = new CamlQuery();
query.ViewXml = "<View>"      + "<Query>"    + "<Where><Eq><FieldRef Name='Country' /><Value Type='Text'>Belgium</Value></Eq></Where>"    + "</Query>"    + "<ViewFields>"    + "  <FieldRef Name='Title' /><FieldRef Name='City' />"    + "</ViewFields>"    + "</View>";
// execute the query
ListItemCollection listItems = spList.GetItems(query);
clientContext.Load(listItems);
clientContext.ExecuteQuery();

But this also returns a number of system columns. If you really want to limit the columns returned to the columns you specify, you have to use a LINQ query within the Load method. The code looks as follows:

CamlQuery camlQuery = new CamlQuery();
camlQuery.ViewXml = "<View><Where><Eq><FieldRef Name='Country' /><Value Type='Text'>Belgium</Value></Eq></Where></View>";
ListItemCollection listItems = spList.GetItems(camlQuery);
clientContext.Load(listItems,       items => items.Include(       item => item.Id,       item => item.DisplayName,       item => item.HasUniqueRoleAssignments));
clientContext.ExecuteQuery();

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spquery.viewfields.aspx

Query Options

The different Query Options need to be handled a bit differently than with the SharePoint Server Object Model.

The row limit can also be specified within the ViewXml property:

query.ViewXml = "<View>"    + "<Query>"    + "<Where><Eq><FieldRef Name='Country' /><Value Type='Text'>Belgium</Value></Eq></Where>"    + "<OrderBy><FieldRef Name='City'/></OrderBy>"    + "</Query>"    + "<RowLimit>5</RowLimit>"    + "</View>";

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spquery.rowlimit.aspx

Dates in UTC

You can choose to return dates in UTC (Coordinated Universal Time) by setting the DatesInUtc property of the CamlQuery instance:

query.DatesInUtc = true;

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spquery.datesinutc.aspx

Include attachment URLs

Using CAML you are able to know if list items have attachment by adding a w> element to the ViewFields element in the ViewXml property:

query.ViewXml = "<View>"      + "<ViewFields>"    + "  <FieldRef Name='Title' /><FieldRef Name='City' /><FieldRef Name='Attachments' />"    + "</ViewFields>"    + "</View>";

SharePoint will return a boolean indicating whether the list item has attachments or not.

The attachments are not stored in the list item itself, but are stored in a sub folder of the list. More specifically, the list contains a folder named Attachments and if a list item has one or more attachments, a folder is created based on the ID of the list item. This sub folder will then contain the attachment(s). The URL of the attachment is not stored in the list item itself.

CAML contains an option IncludeAttachmentURLs that can be used to retreive the URL of the attachment(s), together with the other properties of the list item. It works on the server side SPQuery and with the <QueryOptions> node of the GetListItems method of the Lists.asmx web service , but it doesn’t seem to be available with the CamlQuery object of the .NET Client Object Model.

If you need to retrieving the attachments itself you will have to write some extra code that retrieves the files from the Attachment folder:

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spquery.includeattachmenturls.aspx

Folder folder = clientContext.Web.GetFolderByServerRelativeUrl(     spList.RootFolder.ServerRelativeUrl + "/Attachments/" + item.Id);     FileCollection files = attFolder.Files;     // If you only need the URLs     ctx.Load(files, fs => fs.Include(f => f.ServerRelativeUrl));     ctx.ExecuteQuery();

Limitations

Following CAML subtilities doesn’t seem to be working with the CamlQuery object of the .NET Client Object Model, although they exist when retrieving list items with the server object model and the SharePoint web services:

IncludeMandatoryColumns: this option also returns the required fields besides the other fields specified in the ViewFields property or element.
ExpandUserField: when you query a User field, you only see the login name of the user. When you indicate that you want to expand a user field, SharePoint will also return information like the user name and the email address.
IncludeAttachmentURLs: cfr. higher
IncludeAttachmentVersion:

Files and folders options

CAML for retrieving files and folders at different levels of a document library, is always a bit more complex. To make the explanation hereunder a bit more readable, I have created a document library with the following structure:

You can easily query the files and folders in the root folder of a document library without having to use specific CAML elements. Only if you want to start querying the folder structure within a document library, you have to apply specific CAML.

To be able to better demonstrate the subtilities I created a folder structure in my Shared Documents library, and added a set of files to the different folders. (Needless to say that SharePoint Manager 2010 provided me this insight in my document library ).

For example, if you want to query all files and folders in your document library, no matter how deep they are nested, you have to add a Scope attribute to the View element, and set its value to RecursiveAll:

query.ViewXml = "<View Scope='RecursiveAll'></View>";

You can always add a Query element in the View element and specify a Where clause to add an extra filter to the query, or anOrderBy clause to sort the result.

If you want to query only the folders, you have to add an extra where clause:

query.ViewXml = "<View Scope='RecursiveAll'>"    + "<Query>"    + "   <Where>"    + "      <Eq><FieldRef Name='FSObjType' /><Value Type='Integer'>1</Value></Eq>"    + "   </Where>"    + "</Query>"    + "</View>";

If you want to query only the files, the extra where clause can be changed as follows:

query.ViewXml = "<View Scope='RecursiveAll'>"    + "<Query>"    + "   <Where>"    + "      <Eq><FieldRef Name='FSObjType' /><Value Type='Integer'>0</Value></Eq>"    + "   </Where>"    + "</Query>"    + "</View>";

If you want to retrieve the content of a specific folder, i.e files and folders, you have to add the relative URL to that folder to the FolderServerRelativeUrl property of the query instance:

query.FolderServerRelativeUrl = "/Shared Documents/Folder 1";

If you only want to see the files of a specific sub folder, you have to set the Scope attribute of the ViewXml property toFilesOnly:

query.ViewXml = "<View Scope='FilesOnly' />";
query.FolderServerRelativeUrl = "/Shared Documents/Folder 1";

Of course you can also query all files in a specific sub folder and its underlying sub folders. In that case you also have to specify the relative URL to the folder, but you also have to set the Scope attribute of the ViewXml property to Recursive:

query.ViewXml = "<View Scope='Recursive' />";
query.FolderServerRelativeUrl = "/Shared Documents/Folder 1";

If you want to retrieve all files AND folders from a specific folder and its underlying sub folders, you have to set the Scopeattribute of the ViewXml property to RecursiveAll:

query.ViewXml = "<View Scope='RecursiveAll' />";
query.FolderServerRelativeUrl = "/Shared Documents/Folder 1";

Fuente:

http://karinebosch.wordpress.com/2012/02/03/caml-and-the-client-object-model/

Farm Solution Deployment Lock and Removal

2012-02-04T04:27:00.001-08:00

Farm Solution Deployment Lock may occur when a solution (.wsp) deployment fails unexpectedly.

Solution Deployment in SharePoint happens through the timer jobs. When you deploy a solution along with the deployment job a timer job named "Solution Deployment Job Lock" is created which store the deployment job's id and the lifetime of the job is till the deployment job is completed. With this SharePoint ensures that no two deployments conflict with each other.

From the above we can conclude that in SharePoint one deployment job happens at a given time courtesy the solution deployment lock. Hence using this feature SharePoint ensures that no more than one deployment or retraction can happen at a given time.

To recover from this lock you need ton use the following PowerShell command which releases the solution deployment lock.

http://technet.microsoft.com/en-us/library/ff607750.aspx

Fuente:

http://www.dhirendrayadav.com/2012/02/farm-solution-deployment-lock-and.html

Exclude Asset Library from search results by modifying search scopes

2012-02-04T04:21:00.001-08:00

It’s possible to exclude SharePoint Lists from search results by excluding their types in the search scope definition.

Therefore you need to define an search scope rule based on a “property”. You have to use “contentclass” and a value. There are much lists of the possible values out in the web.

Value	Description
STS_Web	Site
STS_List	Custom List
STS_ListItem	Custom List item
STS_List_DocumentLibrary	Document Library
STS_ListItem_DocumentLibrary	Document Libary item
STS_List_Links	Link List
STS_ListItem_Links	Link List item
STS_List_Events	Event List
STS_ListItem_Events	Event List item
STS_List_Tasks	Task List
STS_ListItem_Tasks	Task List item
STS_List_Contacts	Contact List
STS_ListItem_Contacts	Contact List item
STS_List_Announcements	Announcements List
STS_ListItem_Announcements	Announcements List item
STS_List_DiscussionBoard	Discussion Board
STS_ListItem_DiscussionBoard	Discussion Board item
STS_List_GanttTasks	Gantt Task List
STS_ListItem_GanttTasks	Gantt Task item
STS_List_IssueTracking	Issue Tracking list
STS_ListItem_IssueTracking	Issue Tracking item
STS_List_Survey	Survey
STS_ListItem_Survey	Survey item
STS_List_PictureLibrary	Picture Library
STS_ListItem_PictureLibrary	Picture Library Item
STS_List_WebPageLibrary	Web Page Library
STS_ListItem_WebPageLibrary	Web Page Library Item
STS_List_XMLForm	(InfoPath) Form Library
STS_ListItem_XMLForm	(InfoPath) Form Library item
STS_List_850	Page Library
STS_ListItem_850	Page Library item
urn:content-class:SPSSearchQuery	Search Query
urn:content-class:SPSListing:News	News Listing
urn:content-class:SPSPeople	People
urn:content-classes:SPSCategory	Category
urn:content-classes:SPSListing	Listing
urn:content-classes:SPSPersonListing	Person Listing
urn:content-classes:SPSTextListing	Text Listing
urn:content-classes:SPSSiteListing	Site Listing
urn:content-classes:SPSSiteRegistry	Site Registry Listing

You can generally exclude list items from search by using the value “STS_ListItem_PictureLibrary” for the property “contentclass”.

But how to exclude items or lists of type “Asset Library” which is also a standard list template like “Document Library”, “Picture Library”, “Calendar List”, … and “Page Library” which has as code (850) as name. (Marked red in the list above.)

I checked the 14 hive and figured out the 850 is the list template ID of “Page Library”. And the list template ID of “Asset Library” is 851.

So I used the following query in the search box: “(scope:"All Websites") (contentclass:STS_List_851)”

I created a new search scope exclude rule on the site collection using “STS_List_851” in it worked! Now there are no more Asset Libary links in the search result. If you you “STS_ListItem_851” you can exclude Asset Library Litems.

Fuente: http://ikarstein.wordpress.com/2011/11/28/exclude-asset-library-from-search-results-by-modifying-search-scopes/

Things to note when installing Service Pack 1 for SharePoint 2010

2012-02-04T04:13:00.001-08:00

1. Make sure you have all the Service Pack 1 updates you need

When installing Service Pack 1 you need to make sure you have all the right Service Pack 1 upgrades. Unfortunately, Language Packs are all individual and there is a Foundation and a Server for each one.

2. List of the SharePoint 2010 SP1 downloads:

SharePoint Foundation 2010 Service Pack 1
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26640
SharePoint Foundation Language Packs SP1 (only needed if you have the Language packs installed)
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26629
SharePoint Server 2010 Server Service Pack
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26623
SharePoint Server Language Packs SP1
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26621
Service Pack 1 for Project Server 2010 (only needed if you have project server installed)
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26623
Service Pack 1 for Office Web Apps 2010
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26639
Microsoft FAST Search Server 2010 Service Pack 1
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26612

3. Stop the User Profile synchronization service

There have been a lot of issues when installing service pack 1 related to the user profile service. Stop any running synchronizations and stop the user profile synchronization this will help to avoid these errors from happening.

4. Restart your Servers

Make sure that you restart your servers after installing all of the foundation updates and then again after installing the server updates. If you do not restart you servers you can run it to some challenging issues.

5. Cache issues

Sometimes after installing a service pack to a server you will run the configuration wizard and it will give you an error that the service pack is not installed on the server. This issue will persist even after hitting the refresh button on the configuration wizard. To resolve this issue run the powershell command below from the SharePoint Management Console. This will reset the cache file that the configuration wizard is looking to.

Get-spproduct-local

6. The Configuration Wizard Fails

There is a good chance when you are doing the SP1 upgrade that the Configuration Wizard will fail on one of your servers. If it does run the psconfig.exe command (from the 14 hive bin folder) shown below:

.\psconfig.exe –cmd upgrade –inplace b2b –force –wait

Fuente: http://digsharepoint.blogspot.com/2012/02/things-to-note-when-installing-service.html

Top 15 things you should consider when thinking about SharePoint Online (Office 365)

2012-02-04T04:10:00.001-08:00

Each My Site gets 500MB of personal storage. This amount cannot be adjusted.
The My Content part of a My Site is not provisioned until the user clicks on My Content from their My Profile page. After they do, a personal My Site site collection is created. This does not count against the 300 site collection limit as that applies to non-My Site site collections.
BCS within SharePoint Online does not support a direct connection to SQL Azure. A WCF endpoint is required. -- See next Blog on how to do this with WCF here http://www.sharepointfabian.com/blog/Lists/Posts/Post.aspx?ID=212
Access reporting is not supported by SharePoint Online Access Services because SQL Server Reporting Services (SSRS) is not currently enabled for SharePoint Online. Access reporting requires SSRS.
SharePoint Online does not support auditing capabilities to log the opening and downloading of files in a document library.
SharePoint Online does not support PerformancePoint Services.
SharePoint Online does not support Excel Services and PowerPivot for SharePoint
PDFs and other types of files can potentially run scripts against sites. To prevent this security threat, SharePoint Online requires users to download those types of files. When the user tries to open a PDF document stored in a SharePoint Online document library, the user will see a “Save As…” window and must download the PDF file to their local directory.
SharePoint Online does support Enterprise Search, but does not currently support FAST Search.
Vanity URLs can only be applied to the public website. Customers cannot apply a vanity URL to an intranet zone site.
Editing the Public Website with SharePoint Designer is not supported. SharePoint Designer 2010 cannot be used to edit the public website. This site can only be edited with the built-in Site Designer tool. SharePoint Online only supports SharePoint Designer 2010.
SharePoint Online development patterns and practices are currently targeted at site collection level solutions.
“Server Resources” quota, what are used to determine amount of processing power available to Sandboxed Solutions, is determined by the number of licensed user seats in a company's tenancy. To calculate server resource quota in Office 365, you can use the following equation: (#seats×200) + 300.
SharePoint Online does not currently support customer use of Windows PowerShell for service administration.
You cannot create property based search scopes in Office 365 (SharePoint Online) -- Credit Wictor Wilen athttp://www.wictorwilen.se/Post/You-cannot-create-property-based-search-scopes-in-Office-365-SharePoint-Online.aspx

Things that Flat Out are not available in SharePoint Online but ARE available in SharePoint 2010 Server

Timer Jobs
BCS Profile Pages
Business Data Integration with the Office Client
Audit Opening and Downloading
Records Center
Word Automation Services
Business Intelligence Center
Chart Web Parts
Data Connection Library
Dashboards
Decomposition Tree
Advanced Content Processing
Tunable Relevance with Multiple Rank Profiles
Business Intelligence Indexing Connector
SharePoint 2010 Search Connector Framework
Deep Refinement
Federated Search
Query Suggestions, "Did You Mean?” and Related Queries
Relevancy Tuning
Rich Web Indexing
Similar Results
Thumbnails and Previews
Visual Best Bets
Advanced Sorting
Web Analytics

Fuente:

https://www.nothingbutsharepoint.com/sites/eusp/Pages/15-Considerations-for-SharePoint-Online-Office-365.aspx

Comparison between Server-side object model/Client object model/REST API(s) and Decision Matrix on what to use when

2012-02-04T04:04:00.001-08:00

Server-Side Object Model

Client Object Model

REST API(s)

· Most extensive set of options to customize SharePoint 2010

· Any Components consuming server-side object model needs to be deployed on the server

· Slower Performance than Client OM and REST API(s)

· Synchronous

· Documentation:

o Class Library

· Client OM APIs are wrappers around a custom Web service that calls the server-side object model.

· Better Performance than server-side OM

· Asynchronous

· Execute calls in a batch of commands

· Limited options/types as compare to server-side OM

· Designed to be used in the remote client –side components

· Documentation:

o Client Class Library

o ECMAScript Library

· Limited set of REST interfaces

· Supports JSON(JavaScript Object Notation),Atom and AtomPub standards

· Based on ADO.NET Data Services

· Eliminated the need for intermediate layers between client and server by mapping Read, create, update, and delete operations directly to GET, POST, PUT, and DELETE HTTP verbs

· Interoperable

· Documentation:

o REST Interface

Decision Matrix:

Reference: http://msdn.microsoft.com/en-us/sharepoint/ff462048

Iniciar un Flujo de Trabajo programáticamente - Modelo de Objetos

2012-02-04T03:35:00.001-08:00

El siguiente fragmento de código crea primero una instancia (SPListItem) de un elemento en una Lista o Biblioteca, luego encuentra el GUID de un Flujo de Trabajo que ya se ha configurado en la Lista (llamado "FlujoPrueba"), encuentra la asociación del flujo y finalmente lo inicia con parámetros por defecto:

SPListItem item = otherWeb.Lists["nm3"].Items[0];
Guid approvalworkflowId = item.Web.WorkflowTemplates.GetTemplateByName("number02", CultureInfo.InvariantCulture).Id;

if (approvalworkflowId != Guid.Empty)
{
    foreach (SPWorkflowAssociation workflowAssociation in item.ParentList.WorkflowAssociations)
    {
        if (workflowAssociation.BaseId == approvalworkflowId)
        {
            item.Web.Site.WorkflowManager.StartWorkflow(item, workflowAssociation, workflowAssociation.AssociationData, true);
            break;
        }
    }
}

El tercer parámetro del método StartWorkflow es una enumeración del tipo SPWorkflowRunOptions que puede tener tres valores: sincrónico, asincrónico o sincrónico posponiendo todas las operaciones en ejecución.

Si es necesario insertar parámetros de iniciación, el parámetro "eventData" del tipo string puede contenerlos definidos en formato xml de la siguiente forma:

String data = String.Format("<dfs:myFields
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"
xmlns:dms=\"http://schemas.microsoft.com/office/2009/documentManagement/types\"
xmlns:dfs=\"http://schemas.microsoft.com/office/infopath/2003/dataFormSolution\"
xmlns:q=\"http://schemas.microsoft.com/office/infopath/2009/WSSList/queryFields\"
xmlns:d=\"http://schemas.microsoft.com/office/infopath/2009/WSSList/dataFields\"
xmlns:ma=\"http://schemas.microsoft.com/office/2009/metadata/properties/metaAttributes\"
xmlns:pc=\"http://schemas.microsoft.com/office/infopath/2007/PartnerControls\"
xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">
<dfs:queryFields></dfs:queryFields><dfs:dataFields>
<d:SharePointListItem_RW>
<d:NombreCampo>ValorCampo</d:NombreCampo>
</d:SharePointListItem_RW></dfs:dataFields>

Cada parámetro debe ser especificado como "<d:Nombre>Valor</d:Nombre>" después del parámetro "<d:SharePointListItem_RW>".

Nota: Flujos de Trabajo no se pueden iniciar con una cuenta de sistema, deben ser siempre iniciados por cuentas de usuarios de SharePoint

Fuente: http://www.gavd.net/servers/sharepointv4/spsv4_item.aspx?top=1&itm=1408

Ocultar el nombre de creador y modificador

2012-02-04T03:31:00.001-08:00

El objeto SPList que representa Listas y Bibliotecas en el Modelo de Objetos de SharePoint dispone de una propiedad "ShowUser" que permite hacer que el nombre de los usuarios que crearon y modificaron elementos sean remplazados por "***".

La siguiente rutina cambia la propiedad indicada en la Biblioteca de Documentos Compartidos:

static void OcultarNombre()
{
    using (SPSite mySite = new SPSite("http://sp"))
    {
        using (SPWeb myWeb = mySite.OpenWeb())
        {
            SPList myList = myWeb.Lists["Documentos compartidos"];
            myList.ShowUser = false;
            myList.Update();
        }
    }
}

El mismo efecto se puede conseguir con PowerShell:

$mySite = Get-SPSite -Identity http://sp
$myWeb = $mySite.OpenWeb()
$myList = $myWeb.Lists["Documentos compartidos"]
$myList.ShowUser = $true
$myList.Update()

Fuente: http://www.gavd.net/servers/sharepointv4/spsv4_item.aspx?top=1&itm=1410

Walkaround for common “TaxonomyPicker.ascx” error in Windows Event Log: SharePoint Feature that renames the file

2012-02-03T02:12:00.001-08:00

Event Type: Error
Event Source: SharePoint Foundation
Event Category: None
Event ID: 7043
Computer: SERVERNAME
Description: Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type ‘Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker’ from assembly ‘Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.

Fix:

http://gallery.technet.microsoft.com/scriptcenter/32d06697-ab7f-447e-9d0e-b6d93bee3fda

http://spdisabletaxpicker.codeplex.com/

http://www.sharepointdan.com/2010/05/19/taxonomypicker-ascx-bug-sp2010-rtm/

Fuentes:

http://ikarstein.wordpress.com/2012/02/01/walkaround-for-common-taxonomypicker-ascx-error-in-windows-event-log-sharepoint-feature-that-renames-the-file/

http://blogs.technet.com/b/praveenh/archive/2010/12/16/sharepoint-2010-gt-gt-taxonomy-picker-ascx-failed-error.aspx

10 SharePoint Security Mistakes You Probably Make

2012-02-03T01:38:00.001-08:00

Para ver los temas completos: http://informationweek.com/news/security/app-security/232500768?pgno=2

1. Poor security training

2. Collaboration barriers.

3. Unclear security oversight.

4. Overly broad access rights.

5. Not watching watchers.

6. Failure to encrypt

7. Sloppy search indexing.

8. Poor Internet Information Services maintenance.

9. Poor endpoint security.

10. Failure to scan for viruses.

soap:ServerServer was unable to process request

2012-02-03T01:35:00.001-08:00

Problem
You've created a new website and site collection. You then successfully connect to the site collection using SharePoint Designer 2010 using the site collection's fully qualified domain name (FQDN). However, when you then attempt to edit any page (e.g., by clicking the "Edit this page" link), you experience the following prompt:

When you click on the prompt's Details button to learn more about the error, you see the following:

soap:ServerServer was unable to process request. ---> Value does not fall within the expected range.

You then try to connect to the site collection (through Designer) using the server name, and this works fine, enabling you to use SharePoint Designer to access site pages and even edit them. However, when you close out this connection, and then connect using the site's FQDN, you experience the same error whenever trying to edit a page. Enabling SharePoint Designer 2010 access to your site collection via the collection's FQDN is critical, in that you cannot connect to servernames when accessing the sharepoint instance from outside the corporate intranet.
Discussion
The problem involves SharePoint Alternate Access Mapping (AAM). The site collection is viewable just fine through a browser, because the browser interacts with IIS (or the web server) in order to navigate among the website pages. However, SharePoint Designer interacts directly with SharePoint itself. Setting up a new site collection properly updates the web server with the host header information associated with the new site collection, and this is why you can browse just fine to the site. However, SharePoint does not yet know how to map this FQDN to the appropriate page, and thus this information must be manually configured in SharePoint in order for Designer to connect to the site collection using the host header.
Resolution
Login to Central Administration.
Navigate to: Central Administration > System Settings > Farm Management | Configure alternate access mappings.
On the Alternate Access Mappings page, in the Alternate Access Mapping Collection dropdown (upper right), select the appropriate website.
Click the Edit Public URLs link. The Edit Public Zone URLs page appears.
In the Intranet and Internet boxes, enter the FQDN for the site collection.

Then click OK.
If you still have SharePoint Designer connected to the site collection, close that connection, and then connect back to the site collection using its FQDN. You should now be able to connect to the site collection from SharePoint Designer 2010 using the FQDN to the site collection.
Summary
Setting the AAM is not critical, when using SharePoint Designer from within the corporate intranet, as you can easily connect using the servername of the machine hosting the SharePoint instance. However, if you want to enable Designer access to your site collection from the Internet, you will need to configure AAMs appropriately.

Fuente:

http://alstechtips.blogspot.com/2012/02/soapserverserver-was-unable-to-process.html

References

XLST Algunos tips

2012-02-03T01:32:00.001-08:00

TIP 1

Select the lookup column item and in the document map bar in the bottom, choose the context menu for “xsl:value-of”, and select ”Edit Tag…”

You will see the “Edit Tag” window

La siguiente línea borra todos lo que está antes de > y después de <

<xsl:value-of select=”substring-before(substring-after($thisNode/@*[name()=current()/@Name],’>’), ‘<’)” disable-output-escaping=”yes”>

TIP 1

* Current date = 22/07/2011

As it can be noticed in the above picture that the condition is false for 29/07/2011 but true for 05/08/2011. If I go to advance view the condition it generates behind the scenes is the one below

I forced the Due Date to the correct format in this condition I used “ddwrt:FormatDate” function

ddwrt:DateTimeTick(ddwrt:GenDisplayName(ddwrt:FormatDate(
string($thisNode/@DueDate), 2057, 1))) <
ddwrt:DateTimeTick(ddwrt:GenDisplayName(string($Today)))

In the above line, 2057 is the LCID for British English, and “1″ is a simple date format.

And it worked for me

Fuente:

http://aleemsheikh.wordpress.com/2011/07/08/remove-hyperlink-from-lookup-column-in-sharepoint/

http://aleemsheikh.wordpress.com/2011/07/22/conditional-formatting-in-sharepoint-designer-2010-doesnt-compare-dates-correctly/

http://panvega.wordpress.com/2008/12/08/ddwrtformatdate-with-different-formatflags/

Todo Sharepoint

SharePoint Software Factory

Incrementar el tamaño máximo de template de listas

PDF Files en SharePoint Online

Privilegios elevados en código de Sharepoint

Algunos códigos de idioma ID (LCID) de configuración regional

Encontrar todos los archivos desprotegidos (check out) de un sitio

Detrás de escenas de una consulta de search en Sharepoint 2010

Resetear la “Farm Passphrase”

Al activar la feature “Document Id” en la site collection me lanza “Acceso denegado“

Microsoft IT Showcase para SharePoint Server 2010

Conocer el tamaño y la cantidad de documentos de una content database

Tips to optimize SharePoint performance

Agregar servidores de bases de datos a una farm existente

Añadir servidores de base de datos a una granja existente

Creating a Web Part with Custom Properties

URL path length restrictions (SharePoint Server 2010)

Internet Explorer URL length limitations

Resolving URL length problems

Content DB has been deleted from SQL Server but still get an error 'A SharePoint database named ‘….. ‘ already exists'

Instalar REST en Sharepoint 2010

Obtener un term de metadata Sharepoint 2010

SharePoint Configuration Cache

Host header for Web application Sharepoint 2010

Copiar los items de una lista a otra Sharepoint 2010 Server Object

Copiar una libreria de SharePoint library usando PowerShell

Determinar que proceso del w3wp es un servicio de Sharepoint

Using a SharePoint List as a Data Source in SQL Server Reporting Services 2008 R2

Create a Data Source

Create a Dataset

Clase SPSiteDataQuery

Crear una página custom de error Sharepoint 2010

Obtener el lenguaje de la UI via jquery o javascript

Sharepoint 2010–Orden correcto de instalación

Enable folder creation on a list in Sharepoint

Word Web App cannot open this document for viewing because of an unexpected error (Word Web App no puede abrir este documento por un error inexperado)

SharePoint Server 2010–Todas las versiones hasta el 02/12

Logging in SharePoint

Identify and clean up orphan sites in sharepoint

SharePoint SandBox Solution Execution process

Renombrar Servidor de Sharepoint

Display the sandboxed solutions service configuration settings

Esquema Regional Settings

Actualizar manualmente el período de horario de verano de una definición de zona horaria:

Remover base de datos de Servicios renombradas

Instalación de Sharepoint–Cuentas locales

Enable ASP.NET Session State on SharePoint 2010 Application

Funcionamiento de Client Object de manera gráfica

Clases Sharepoint Development Server Object

Alias para el SQL SERVER

OSearch14 VSS Writer No aparece

Improving SharePoint’s Performance

Send email from Powershell with attachment SQL Server

SharePoint 2010: Debugging Visual Studio 2010

Site Collections vs Sites vs Web Applications

SharePoint Dispose tool

Install SharePoint Dispose tracker tool.

Configure the project what you analyze

Analyze the code

Procedimientos recomendados para virtualización (SharePoint Server 2010)

1. Usar la virtualización asistida por hardware

2. Habilitar hyperthreading en los procesadores que admiten esta tecnología

3. Configurar correctamente el acceso a memoria no uniforme

4. Configurar el host de Hyper-V para un rendimiento óptimo

5. Mantener la compatibilidad de versiones de los servicios de integración

6. Determinar las opciones de almacenamiento que se basan en cargas de trabajo y roles de máquinas virtuales

7. Establecer la configuración general de la máquina virtual para mejorar el rendimiento y la estabilidad

8. No usar instantáneas en un entorno de producción

9. Diseñar la topología virtual para un rendimiento óptimo

10. No sobrecargar el host de Hyper-V

11. No ejecutar trabajos con uso intensivo de recursos en las VM y el host de Hyper-V al mismo tiempo

Slide Show desde una librería de imágenes

Notes Chapter 5 – Sharepoint 2010 Unleashed

Notes Chapter 4 – Sharepoint 2010 Unleashed

Notes Chapter 3 – Sharepoint 2010 Unleashed

Developing custom field type for SharePoint 2010

SharePoint Performance Troubleshooting

Para ver el post completo: http://www.sharepointpromag.com/article/sharepoint-server-2010/sharepoint-performance-troubleshooting-141506

Windows Server Hardware Sizing

SQL Server Hardware Sizing