El Blog de JuanBO

  $farm = Get-SPFarm $file = $farm.Solutions.Item("extendeddiagnosticproviders.wsp").SolutionFile $file.SaveAs("c:\temp\extendeddiagnosticproviders.wsp")

Requirement Display security permissions for site collection, subsites, and lists/libraries in each site. Solution This can be achieved by a simple powershell script. To use it, you must modify the $site variable to point to your site collection. Syntax: <script name>.ps1 | out-file c:\permissions.txt   1: #Add SharePoint PowerShell SnapIn if not already added 2: if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $ null ) { 3: Add-PSSnapin "Microsoft.SharePoint.PowerShell" 4: } 5:   6: #Define variables 7: $site = Get-SPSite "http://<site collection>" 8:   9: #Get all subsites for site collection 10: $web = $site.AllWebs 11:   12: #Loop through each subsite and write permissions 13:   14: foreach ($web in $web) 15: { 16: if (($web.permissions -ne $ null ) -and ($web.hasuniqueroleassignments -eq "True" )) 17: { 18: Write-Output ...

  Error: Log Name:      Application Source:        MsiInstaller Date:          27/11/2013 05:04:10 p.m. Event ID:      1004 Task Category: None Level:         Warning Keywords:      Classic User:          NETWORK SERVICE Description: Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist. Solución: Éste puede ser fácilmente resuelto mediante la asignación de permisos de servicios a la cuenta “NETWORK SERVICE” en la carpeta "'C:\Program Files\Microsoft Office Servers\14.0\" Fuente: http://sharepointsoldiers.wordpress.com/2011/...

After provisioning and starting the User Profile Synchronization Service: Under services FIM Started: You click on User Profile Service Application: You create a new User Profile Service Application and try browsing to the Manage link for the User Profile Service Application, this page might fail with the following error, If you filter on the "User Profiles" category in the ULS Logs, you should see these errors: UserProfileServiceUserStatisticsWebPart:LoadControl failed, Exception: System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.InitializeIlmClient(String ILMMachineName, Int32 FIMWebClientTimeOut) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager..ctor(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID) at Microsoft.SharePoint.Portal.WebControls.UserProfileServiceSta...

Problem You have followed Harbar’s Rational Guide to setting up the User Profile Service Application in SharePoint 2010 but the User Profile Service is still stuck on starting. Solution Ensure that the account you are running the UPS service is a local administrator for the provisioning process. This is normally the farm account which also runs the SharePoint Timer service. You can remove admin rights later. If it is not a local admin, you will need to restart the Timer service after you grant the correct permissions. Log on as the account that will run the User Profile Synchronization service. If the User Profile Service Synchronisation Service is stuck on ‘Starting’: Run SharePoint Management Shell as a farm administrator. Type: stop-spserviceinstance | where { $_.typename -eq “user profile synchronization service” } The User Profile Synchronization service status should now be ‘Stopped’ or ‘Disabled’. Check the Certificates store on the server that runs the User Profile Synchr...

Problema SharePoint constantemente pide credenciales de autenticación en los siguientes escenarios: Le pide las credenciales cuando se accede al sitio en el navegador. Le pide las credenciales cuando se abre un documento de SharePoint. Le pide las credenciales después de abrir un documento de SharePoint y tratar de "Guardar como". Causa La causa más probable de su problema es que usted está utilizando un nombre de dominio completo para SharePoint (Por ejemplo, sharepoint.company.com) y la máquina cliente ejecuta Windows 7. De forma predeterminada, Internet Explorer y Webdav asumen que esta dirección se encuentra en Internet y como medida de seguridad, no pasa de forma automática sus credenciales. Solución Si el escenario es el mismo que el anterior, entonces usted tendrá que hacer dos cosas. Añadir FQDN de su servidor SharePoint a sus sitios de confianza o a sitios de la zona intranet. Modificar la configuración del Registro para el servicio WebClient. Añadir F...

Problem A service application database was deleted in SQL Server Management Studio. After a while, I noticed errors in the event viewer on the WFE and ULS logs complaining that SharePoint was not able to login to the database that I deleted. Obviously, SharePoint still thought that the database existed so I needed to find a way to remove it. PowerShell to the rescue. Solution Using PowerShell, run the following command: Get-SPDatabase | where {$_.exists -eq $ false } This will list all databases in SharePoint that no longer exist on the database server. If you are happy with the result and wish to remove the orphaned databases, run the following command: Get-SPDatabase | where {$_.exists -eq $ false } | foreach {$_.delete()} All orphaned databases should now be removed and SharePoint should stop complaining about being unable to login to the non-existent database.   Fuente: http://www.mysharepointadventures.com/2012/02/cleaning-up-deleted-databases-in-sharepoint/